#Problems with DNS resolution after a recent upgrade to 2025.11.2

1 messages · Page 1 of 1 (latest)

proven lake
#

I've automatically upgraded both the OS and Supervisor to the latest version and discovered that one of my integrations wasn't working (pushover). Once I started digging I discovered the following:

Failed setup, will retry: HTTPSConnectionPool(host='api.pushover.net', port=443): Max retries exceeded with url: /1/users/validate.json (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f67a51950>: Failed to resolve 'api.pushover.net' ([Errno -3] Try again)"))

When I fired up the terminal within hass, I couldn't resolve any names:

➜  ~ ha dns info  
fallback: true
host: 172.30.32.3
llmnr: true
locals:
- dns://192.168.104.1
- dns://192.168.104.3
mdns: true
servers: []
update_available: false
version: 2025.08.0
version_latest: 2025.08.0
➜  ~ host api.pushover.net
;; communications error to 172.30.32.3#53: host unreachable
➜  ~ ha dns status        
Error: 404 Client Error for http+docker://localhost/v1.51/containers/hassio_dns/json: Not Found ("No such container: hassio_dns")
➜  ~ ha dns restart
Processing... Done.

Error: Can't restart CoreDNS plugin

It would appear as if the CoreDNS service has disappeared.

Has anyone else experienced this?

oak cosmos
#

Check

ha dns logs
ha dns info
ha dns stats
#

Oh, I see. Try ha supervisor repair and ha dns update.

proven lake
#

That solved it - thanks!

Any idea why this happens on one installation and not another?

oak cosmos
#

No. It really shouldn't happen. The host or supervisor logs might give you some hints though.