Can't get AdGuard-home to work for docker containers #6252
Replies: 2 comments
-
Hi, you can bind your adguard 53 port to the internet interface, it seems that some routing issues cause adguard to respond via the wrong interface when all interfaces are bound. There's a similar issue I experienced in PiHole that worked the same. https://dockerlabs.collabnix.com/intermediate/networking/Configuring_DNS.html In my example, my compose ports section looks like this:
|
Beta Was this translation helpful? Give feedback.
-
Thank you @antoniozh for reminding me this issue was still open. |
Beta Was this translation helpful? Give feedback.
-
Today I had to remove and re-install my AdGuard-home container.
I've removed the container, pruned docker and reinstalled AdGuard-home in a docker container.
I expected it to work as it used to, but unfortunately now my other docker containers fail to resolve dns requests.
I do see the requests being processed by AdGuard, but the application in another container seems to time out on dns.
I have my router give all clients the IP-address of my NAS as DNS server. This also means my NAS get's its own IP-address as DNS server and that seems to work if I ping a url from SSH and across the devices on my network. When I ping an address from within a docker container however, it won't resolve (
ping: bad address
error). Usingnslookup
it times out (';; communications error to 192.168.1.104#53: timed out
, where 192.168.1.104 is my NAS's IP, so should be the correct IP for the DNS server)The only way to fix it seems to manually overwrite the DHCP DNS in my Synology to use the router as DNS instead of AdGuard. But that defeats the purpose of using AdGuard as DNS.
Does anyone have any thoughts on how to resolve?
I've tried so many things now, that I can't list them, but happy to engage in some trouble shooting.
Beta Was this translation helpful? Give feedback.
All reactions