tuxbass Posted February 17 Share Posted February 17 DNS images such as the bind9 usually ask to start the container in host network. This however is blocked by dnsmasq service used by KVM. What is odd is I've already been running bind (and VMs) for years, but only now stumbled upon this problem. 1. how is this possible I haven't been affected by this problem before? Haven't changed any settings, containers nor VMs in months, and this config (roughly speaking) is 6+ years old on my system. 2. what's the correct way to go about standing up bind9? Use br0 network instead of host and ask for its own static IP from the router? Running Unraid 6.12.6 Quote Link to comment
Stuntard Posted April 5 Share Posted April 5 I have just come across this same problem since upgrading Unraid. I can't get Wireguard and Adguard to play along nicely any more, as I have to run Adguard on br0 to not conflict with port 53, which makes it unaccessible to Wireguard Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.