Home Assistant breaks my DNS resolution

Configuration
1

Hi,

I’m using Home Assistant Green.

I’ve updated it completely.

But since I plugged it for the first time, it breaks something in my router which makes DNS to stop working.

I can ping public IP addresses, and can browse websites (because the web browser can resolve domains using DNS over HTTPS protocol), but if I try to ping a public website, it doesn’t work because it can’t resolve the domain.

And any computer in my home network that needs to resolve a domain, won’t be able to do it.

To solve this, I have to switch off Home Assistant Green and reboot my router.

I’ve looked at HA host logs and I get lots of errors like this:

2024-08-12 20:17:56.107 homeassistant dockerd[491]: time="2024-08-12T20:17:56.107179841Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.232.2:35067" dns-server="udp:80.58.61.250:53" error="read udp 172.30.232.2:35067->80.58.61.250:53: i/o timeout" question=";checkonline.home-assistant.io.\tIN\t A" spanID=10c4d75ded91975f traceID=5cb528c9af94a3dcabf83498f68fdc9e
2024-08-12 20:17:56.108 homeassistant dockerd[491]: time="2024-08-12T20:17:56.108655756Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.232.2:34151" dns-server="udp:80.58.61.250:53" error="read udp 172.30.232.2:34151->80.58.61.250:53: i/o timeout" question=";checkonline.home-assistant.io.\tIN\t AAAA" spanID=b3d4b68da3d2db7a traceID=646c4e64d90cf15738de07968f084231
2024-08-12 20:18:00.109 homeassistant dockerd[491]: time="2024-08-12T20:18:00.108782844Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.232.2:47303" dns-server="udp:80.58.61.254:53" error="read udp 172.30.232.2:47303->80.58.61.254:53: i/o timeout" question=";checkonline.home-assistant.io.\tIN\t A" spanID=74a6b7a996dcc3a6 traceID=5cb528c9af94a3dcabf83498f68fdc9e

Don’t know if this is related, but in those same logs I have lots of messages like this one too:

2024-08-12 20:29:00.006 homeassistant systemd-resolved[380]: Clock change detected. Flushing caches.
2024-08-12 20:29:33.003 homeassistant systemd-resolved[380]: Clock change detected. Flushing caches.
2024-08-12 20:30:38.001 homeassistant systemd-resolved[380]: Clock change detected. Flushing caches.
2024-08-12 20:31:42.009 homeassistant systemd-resolved[380]: Clock change detected. Flushing caches.
2024-08-12 20:32:15.001 homeassistant systemd-resolved[380]: Clock change detected. Flushing caches.
2024-08-12 20:33:19.003 homeassistant systemd-resolved[380]: Clock change detected. Flushing caches.

I don’t know if that’s related, but doesn’t seem fine to check the time every time and find changes in the clock.

Thank you for any help.

2

Was this ever resolved? if so, what’s the magic?

thx

3

I have the same trying to use my own dns…
Found 2 github issues, both stale ‘not planned’…
I feel there is really something wrong in config. Get the feeling it is somehow host related.
I run Home Assistant on Raspberry PI. I know there is an add-in to see and easily change host configs, but can’t remember the name, while the name is not that obvious to me. That is ‘Chrony’, but is specifically for NTP setting.

1 Like