October 14, 20232 yr I have been running unraid with dockerized Adguard as my primary DNS server for my network for over a year. For the last couple days, unraid is not able to reach this DNS service and is not able to resolve anything external. I have Adguard getting its own IP on the unraid server so it is unique and not bridged. All my other devices on my network are able to use the Adguard DNS service without issue. Its only unraid and other containers running on it that are not able to get to the DNS service. Containers are not able to update. The community apps times out and does not load any apps. The plugins page also fails to load the version status of the plugins. My unraid IP is 192.168.0.10 and my dns IP that is assigned to Adguard is 192.168.0.49 In the unraid terminal, I am not able to do an nslookup on any external addresses. On unraid 6.12.2 and have been for a while. My router advertises the Adguard IP as the DNS for my network. I have my unraid server configured with a static ip and manually entered DNS addresses in the network config. I have recycled everything, modem, router, unraid server, docker containers, and still am not able to resolve DNS from the unraid machine. Networking is unfortunately not my strong suit. I have not been able to identify a change that was made to cause this. Any help would be appreciated. Thank you. homelab-diagnostics-20231014-0958.zip Edited October 14, 20232 yr by midwesterner
October 14, 20232 yr Author Solution This appears to be strictly related to getting to the Adguard DNS services running in docker. If I change the DNS address for the network to 8.8.8.8, I am able to resolve lookups from the terminal. So it appears to be something related to why unraid is not able to call the adguard DNS that is running in docker.
October 15, 20232 yr Community Expert This is a general thing. You cannot use a Docker for DNS Services for unraid, not your Adguard and not Pihole or others. This is also not a bug, but a feature. Using the Docker you create a "chicken & egg" problem. UNRAID needs DNS services at boot time already (for instance to dowload and install plugins), but Dockers are started last because they depend on everything else running already. So there is a massive blocking at boot time, the outcome is uncertain, more or less random. You do not want such a situation. You can use the Dockers for everybody else in the LAN, but you need to set UNRAID to use a reachable resolver like google or something.
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.