-
-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adguard on Os 3.x via nspawn seems not not bind the DNS port (dnsmasq is) #595
Comments
FYI:
|
Found the issue, it seems not to be dnsmasq related, but rather what rules dnsmasq will use. And me bright light activate Adblock in security, which will redirect all DNS queries in UDM internally. So be sure to disable
I would close this ticket, not sure about the policies in here though |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I installed adguard via nspwan on OS 3.x and everything is up and running like expected.
When i connect to the pod/container via
machinectl shell adguard
and try DNS resolution of the configured private dns overridesi get the expected result
doing the same with the external ip of the pod from the vlan5 bridge (in my case 10.10.20.3) .. running from the UDM of from a network client
it does not return my private DNS entry or in other words, something else is answering, not adguard.
It becomes clear when checking on the UDM
So UDM runs dnsmasq on the port i expect adguard to run. I configured my vlan5 / container network without DHCP
What could case dnsmasq to listen on that interface (or is that the default on os 3.x) and/or how can i deactivate it
The text was updated successfully, but these errors were encountered: