Quote From : jevingala April 2, 2024, 5:34 am Hi,
Can you stop and disable dnsmasq service and then check :
systemctl stop dnsmasq
systemctl disable dnsmasq
Hello there, and btw, thanks for your responses!
Using:
Code systemctl stop dnsmasq
systemctl disable dnsmasq
Made sadly no difference.
However, I made a little breakthrough, though it just gives me another headache.
First I installed the full dnsmasq as some people in older threads on other boards recommended to do, to get the /etc/dnsmasq.conf file.
No matter what I change there, I’m unable to start the “service dnsmasq start” service unless I change the port to be 5353 instead of 53.
This doesn’t really make sense, since it doesn’t complain about the port, but the IP address. I can achieve the same by adding the port to the libvirt-daemon found under /etc/dnsmasq.d-available.
But that doesn’t seem to fix 'virsh net-start natbr1'. It still give me the same error.
After Googling the full syslog error message, and a bit of digging, I found a thread recommending to disable “Bind9” and see there, 'virsh net-start natbr1' is now starting like a charm.
The DOWNSIDE is, though, that besides Virtualizor, there's also a Plesk installation that uses Bind9 for its DNS/Domain services on the host system.
I don’t really get why this all of a sudden is an issue, since I use the same setup on my old server running Ubuntu 20.04.
I’m able to stop Bind9, start the bridge, and then start Bind9 without any problems. I’ll have to observe if they collide somehow.
But that isn’t a perma fix, since I have to do so every reboot or in worst case automate that process after boot is complete, since Bind9 starts before the bridge
Anyone who might have an idea why it suddenly is a problem to run dnsmasq in combination with Bind9?
|