I removed my router’s DNS completely (its anyway rooting to google) and kept only google ones… doesnt work, even weather app doesnt work!
1 Like
Yes but before the last update an own DNS works. So …
Strange …
For me and another member of this forum that works
I will check that tomorrow morning
Thanks
is that similar?
1 Like
Same here, this behavior started with 2024.12.4, if I change the DNS then integrations work again, then I can roll back to my default DNS, very weird.
1 Like
This has started to happen for me tonight too, on two different HA/RPi installs at separate locations. one on 2024.12.4 another on 2024.12.5
lots of custom components fail to load/can’t be found
1 Like
So, I tried the same HA url from a browser I don’t normally use and HA / custom components worked fine. Cleared browser cache in my normal browser and that’s now working too.
1 Like
Ok but I don’t understand the link between DNS and cache …
I will check
There was an update this morning Core in 2024.12.5
- Core 2024.12.5
- Supervisor 2024.12.0
- Operating System 14.1
- Interface utilisateur 20241127.8
So I fall back to my own DNS
Message for Repair Issue has disappear. I’m waiting some days
Also DNS log not very verbose
Same as two days ago
Dig doesn’t work
Ping the FQDN
Dig works
No difference into log output 
Not sure how it happened, but was able to update to core 12.5… but problem persists. Cannot resolve anything, direct ping works.
s6-supervise coredns warning unable to spawn ./run Exec format error
2 Likes
Same problem for me. Worked for years, but now the configuration of a local DNS breaks the DNS resolution of some external addresses (like github) but not all of them.
I was able to fix it once when it first happend to me 2 weeks ago by rebuilding core via ‘ha core rebuild’ using my local DNS but that does not work anymore either.
Additionally, there seems to be no way to rebuild or reload the ‘to be removed add-ons’ and repository entries when the DNS resolution works again, which is very annoying.
I’m running HA version 2024.12.5
Any help would be appreciated.
Thanks!
1 Like
I tried some restart oh HA (5 or 6)
And after the last restart, the problem is present again
I’m going to change the DNS by 8.8.8.8 same as yesterday
Rhhhhaaaaaa fuck 
I didn’t think that
I change my own DNS by Google DNS
Like that HA can resolv FQDN for external sources.
But now my HA can’t resolv my internal device
Example with a camera
Screw-it! I reinstalled HA and restored from backup to 2024.8.2 trying updated core to 12.15 but waiting 30 minutes and nothing is happening… maybe its for better, because all my services are working fine now.
EDIT: now on 12.15 will all updates in, and DNS working perfectly… all services up.
1 Like
I hope that will be ok for you
On my side, I tried reboot and reboot during one day. And after the 6th, the problem come back. But ok I didn’t reinstall HA.
Hello!
I had the same problem as the OP.
In my case, my old DNS server (win2kxx) did not support the DNS COOKIE, so any query using the latest dig would return an error…
The “recursion requested but not available” warning is the DNS COOKIE giveaway…
Same dig query with +nocookie works.
I ended up switching to a dns server that supports DNS COOKIE, but it would be nice if HA would add the +nocookie option to the checkdns.
John
1 Like
I think I’m seeing something like this with my install too. Twice in the last 3 days I’ve seen that some local network services cannot be accessed by HA, such as Unifi Protect and Unifi Network. Xiaomi component can no longer connect to local network devices, even though these are all still accessible via their local app and IP address etc. Supervisor logs has some odd errors similar to what is seen here. And finally, I can see the CPU usage of home assistant go from 3% to approx 20%, probably due to repeated failures for requests.
I can still connect to home assistant locally and remotely, and MQTT still seems to work OK (zigbee2mqtt, tasmota etc), but local network devices connected to home assistant are unreachable (eg wled devices).
A restart of how assistant has resolved the issue for me the 2 times it has occurred.
1 Like
Thanks for this answer John 