The option used is reflected in the nf of the container but doesn't seem to have any effect/isn't honored. But unlike with AdGuard DNS, you can customize filtering as you prefer: add your own blocking lists, exclude or block certain domains. It acts as a blocking DNS server, you can learn more about DNS blocking in this Knowledge base article. I tried to use the paramter -dns-opt=use-vc to force dns over tcp like suggested here. Despite AdGuard Home offers you much more than that, its main purpose is arguably blocking ads and trackers. I'm thankful for any help and hope i provided enough detail. It seems as if the embedded docker DNS doesn't understand the response from the adguard service or is otherwise not behaving as i'd expect it to. There are a few things i tried so far which include: To make the nslookup i used a busybox container (I can ping the adguard container): docker run -network=adguardhome_default busybox nslookup -debug -type=A host.local

All requests (also the ones matching the timestamps of the request from within the containers) are answered and the correct address is returned. In the log of adguard home there are no noticeable problems. However when making an nslookup from within a container the following message is returned: connection timed out no servers could be reached (resolving local and external dns names successfully) I have deployed an Adguard Home docker container which i want to use as my DNS server/proxy.ĭNS resolution is working fine when i'm making an nslookup from a machine (as well as the docker host) on my local network.

Adguard dns