Hi all,
I hope I’m in the right place with this problem, and I’d really appreciate any help.
I’ve installed AdGuard as an Add-on to my Home Assistant, started it and added the integration to my dashboard. Then I put my Home Assistant’s IP into my router as the DNS server, and now I can’t resolve any URLs anymore, from any of the devices on my network.
If I click on the setup guide tab of the adguard settings it says
AdGuard Home DNS server is listening on the following addresses:
127.0.0.1
I’ve tried adding my router as a persistent client in the client settings tab, but as far as i can tell that shouldn’t affect basic functionality? As you maybe can tell, I’m a little lost.
That’s the problem. I don’t use the AdGuard addon but it must be using some means to resolve DNS lookups. 127.0.0.1 means that it’s going to HA’s host DNS settings. Is that the default? What if you point HA to 1.1.1.1?
I’m not quite sure what you mean by “point HA to 1.1.1.1” - I’ve already defined 1.1.1.1 as one of the upstream DNS servers in AdGuard’s DNS settings, in fact I think that was in the default configuration.
Can you elaborate?
Because you said above that AdGuard is listening on 127.0.0.1 I supposed that it was using HA’s internal DNS. But maybe it rather means that it’s not listening on the external machine IP, only on the loopback. If you do docker ps on the HA machine, does it show the AdGuard container with an external port mapping?
I’m about ready to tear my hear out, I’m sure I’m missing something really obvious, but it’s eluding me. I wish I could access the AdGuard configuration files via CLI, but I can’t find them.
I’m running it as Home Assistant OS on a Raspberry Pi - so I’m kind of surprised that there’s not a docker command, since I’d assume that to be part of the default installation. Do I need to install it or something?
I am having this exact same issue, and thanks to this thread I’ve been able to conclude that the docker container does not have an external port mapping.
That being said, similar to @rabbitambulance, I’m not quite sure how to address the issue. However, I find it weird because it does work some of the time, and not others. Perhaps this is related to caching, but it also sometimes works if I wait a little longer after getting the error.
Edit:
I reset my hardware and its working fine again at the moment, cleared my dns cache and did nslookup google <ip> and got an almost instant response. I checked the AdGuard logs and it did the query to https://dns.quad9.net:443/dns-query as expected, which only took 3ms. Right now it’s working great again, but within an hour or two it starts to have weird timeouts every time.
One notable difference is that mine is listening on quite a few more addresses,
This command was able to ping the IP, but AdGuard is also working at the moment, so I’ll try again when it goes down again. docker exec -it <container id> ping -c 4 google.com
I think I fixed it… I’ve had it working for about 5 hours now. The Address that was assigned to Home Assistant after I set it to static was ending in like 102 or something and my DHCP Address pool on my router was from 20 to 250. Even though Home Assistant was set to static, the router doesn’t know that and I think it was assigning out the IP Address again, which is why it would work for a while and then stop for seemingly no reason.
So I changed the Home Assistant static address to end in 15, rebooted the system, and it’s been working for 5 hours so far. I’ll update here if it starts failing again, but that may have been the issue.
But you had reserved that IP for HA in your router, right? Otherwise the router would assign it to something else. Although when that happens Windows computers sometimes detect that there’s a duplicate IP on the network and tell you.