Adguard Home won't respond to DNS Queries (Docker Install) #2957
Replies: 9 comments 2 replies
-
Hi, please add the following information:
Thanks! |
Beta Was this translation helpful? Give feedback.
-
2021/04/01 16:49:49 1#25 [debug] Filters: update finished ;; QUESTION SECTION: 2021/04/01 16:50:04 1#46 [debug] github.com/AdguardTeam/AdGuardHome/internal/home.(*RDNS).Begin(): rDNS: adding 192.168.1.106 ;; QUESTION SECTION: 2021/04/01 16:50:06 1#60 [debug] AutoHosts: answer: aol.com.netwerxplus.com -> [] ;; QUESTION SECTION: 2021/04/01 16:50:08 1#61 [debug] AutoHosts: answer: aol.com -> [] ;; QUESTION SECTION: 2021/04/01 16:50:10 1#62 [debug] AutoHosts: answer: aol.com -> [] ;; QUESTION SECTION: 2021/04/01 16:50:14 1#46 [debug] github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpHandlePacket(): error handling DNS (udp) request: talking to dnsUpstream failed, cause: couldn't initialize HTTP client or transport, cause: couldn't initialize HTTP transport, cause: couldn't bootstrap https://dns10.quad9.net:443/dns-query, cause: failed to lookup dns10.quad9.net, cause: synthetic.wrap: all resolvers failed to lookup, cause: dial udp [2620:fe::fe:10]:53: connect: cannot assign requested address (hidden: dial udp [2620:fe::10]:53: connect: cannot assign requested address, read udp 172.17.0.3:55668->9.9.9.10:53: i/o timeout, read udp 172.17.0.3:38338->149.112.112.10:53: i/o timeout) |
Beta Was this translation helpful? Give feedback.
-
FYI, I have another container running on ports 80 & 443 so I adjusted the mapping to 82 and 444 Thanks |
Beta Was this translation helpful? Give feedback.
-
Thanks for the log, it's very helpful.
Judging by these lines, none of the bootstrap servers could be reached. Please make sure that:
|
Beta Was this translation helpful? Give feedback.
-
So I just rebuilt it again from scratch, followed the directions to "Running on a system with 'resolved' daemon" at https://hub.docker.com/r/adguard/adguardhome and I can not start it as its telling me port 53 isn't available. "Error starting userland proxy: listen tcp 0.0.0.0:53:bind: address already in use. |
Beta Was this translation helpful? Give feedback.
-
If I run a netstat -tulpn | grep LISTEN I get this:
so obviously it's systemd-resolve the file /etc/systemd/resolved.conf.d/adguardhome.conf contains:
/etc/resolv.conf contains: (I replaced my internal domain name with *****)
|
Beta Was this translation helpful? Give feedback.
-
Are you sure that you also ran:
After adding that configuration? And also linked |
Beta Was this translation helpful? Give feedback.
-
hi, ihave some problem too |
Beta Was this translation helpful? Give feedback.
-
I'm facing some related problem; I've been using IPv4 and IPv6 Upstream servers but the IPv6 don't work. Error message:
These are my Upstream DNS servers:
This is how the container started:
The IPv4 Upstream DNS servers works like a charm PS: I started the AdGuardHome directly from Raspberry Pi (outside a docker container) and both IPv4 and IPv6 Upstream servers worked |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Issue Details
Followed the directions at https://hub.docker.com/r/adguard/adguardhome to install adguard home via docker. Got the error that resolved is running. Followed the directions to change it, and I was able to get Ad Guard Home to launch, and go through the initial setup. I can login to the Ad Guard Home UI, but it won't resolve any dns queries from outside the docker host.
Beta Was this translation helpful? Give feedback.
All reactions