Could not contact DNS servers coming and going after restarts

Normann_P_Nielsen · March 11, 2026, 11:02am

I run a simple network at home, just 10.0.0.x

DNS: 8.8.8.8 directly. All cabled.

A ubuntu server 24.04:

network:
  version: 2
  ethernets:
    enp4s0:
      dhcp4: no
      addresses: ["10.0.0.183/24"]
      gateway4: 10.0.0.1
      nameservers:
        search: ["mos-eisley.dk"]
        addresses:
          - "8.8.8.8"
          - "8.8.4.4"

With Home Assistant Core in a docker:

services:
  home-assistant:
    container_name: home-assistant
    restart: unless-stopped
    network_mode: host
    image: homeassistant/home-assistant:2026.2.2
    volumes:
      - /run/dbus:/run/dbus:ro
      - /etc/localtime:/etc/localtime:ro
      - /opt/homeassistant:/config
    devices:
      - /dev/ttyACM0:/dev/ttyACM0
    ports:
      - 8123:8123
    environment:
      - TZ=Europe/Copenhagen
    privileged: true
    dns:
      - 8.8.8.8

After updating integrations, I started seeing "Could not contact DNS servers " in the logs:

Then I upgraded 2 integrations:

oot@sparrow:/opt/homeassistant/custom_components# ls -lt | more

total 144

drwxr-xr-x 4 root root 4096 Mar 7 08:50 cardata
drwxr-xr-x 6 root root 4096 Mar 7 08:49 entity_manager

and restarted Home Assistant - through “Repair”

Then the messages disappeared complely until this morning after Integrations update:

drwxr-xr-x 8 root root 4096 Mar 11 07:30 energidataservice
drwxr-xr-x 4 root root 4096 Mar 11 07:29 ics_calendar

And they are back:

I have pretty much ruled out network and Ubuntu now, It for sure seems that restart of Home Assistent causes this go start - or disappear.

Heres a log sample:

2026-03-11 09:45:35.731 ERROR (MainThread) [homeassistant.components.google.coordinator] Error fetching [email protected] data: Error communicating with API: Error connecting to API: Cannot connect to host www.googleapis.com:443 ssl:default [Could not contact DNS servers]
2026-03-11 09:45:35.770 ERROR (MainThread) [homeassistant.components.spotify] Error requesting Normann P. Nielsen Devices data: Cannot connect to host api.spotify.com:443 ssl:default [Could not contact DNS servers]
2026-03-11 09:45:35.776 ERROR (MainThread) [homeassistant.components.spotify.coordinator] Error requesting spotify data: Cannot connect to host api.spotify.com:443 ssl:default [Could not contact DNS servers]
2026-03-11 09:45:35.867 ERROR (MainThread) [homeassistant.components.google.coordinator] Error fetching Normann (gmail) data: Error communicating with API: Error connecting to API: Cannot connect to host www.googleapis.com:443 ssl:default [Could not contact DNS servers]
2026-03-11 09:45:36.943 ERROR (MainThread) [homeassistant.components.google.coordinator] Error fetching Helligdage i danmark data: Error communicating with API: Error connecting to API: Cannot connect to host www.googleapis.com:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.ring.com:443 ssl:default [Could not contact DNS servers]
ring_doorbell.exceptions.RingError: aiohttp Client error during query of url https://api.ring.com/clients_api/dings/************/share/play: Cannot connect to host api.ring.com:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.ring.com:443 ssl:default [Could not contact DNS servers]
ring_doorbell.exceptions.RingError: aiohttp Client error during query of url https://api.ring.com/clients_api/dings/************/share/play: Cannot connect to host api.ring.com:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.connectedcars.io:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.connectedcars.io:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.connectedcars.io:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.connectedcars.io:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.connectedcars.io:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.connectedcars.io:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.connectedcars.io:443 ssl:default [Could not contact DNS servers]
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers
    raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.connectedcars.io:443 ssl:default [Could not contact DNS servers]
2026-03-11 10:31:35.777 ERROR (MainThread) [homeassistant.components.spotify.coordinator] Error requesting spotify data: Cannot connect to host api.spotify.com:443 ssl:default [Could not contact DNS servers]

So its in “bulks” - the errors comes in…

Impact · March 11, 2026, 8:33pm

What’s this look like?

docker exec home-assistant cat /etc/resolv.conf
docker exec home-assistant nslookup google.com
docker exec home-assistant nslookup google.com 8.8.8.8

Note that ports is unneccessary with host networking and the recommended image comes from ghcr.io. See docs. devices is not needed with privileged either. I’d also recommend to use the same container name as in the docs.

Normann_P_Nielsen · March 11, 2026, 9:24pm

Hi,

Thanks for the response - I am aware of the details You are writing about

I have had endless pings and stuff running in the docker instance without issues… but here goes:

root@sparrow:/home/bnp# docker exec home-assistant cat /etc/resolv.conf
# Generated by Docker Engine.
# This file can be edited; Docker Engine will not make further changes once it
# has been modified.

nameserver 8.8.8.8
search mos-eisley.dk
options edns0 trust-ad

# Based on host file: '/etc/resolv.conf'
# Overrides: [nameservers]
root@sparrow:/home/bnp#

root@sparrow:/home/bnp# docker exec home-assistant nslookup google.com
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	google.com
Address: 192.178.25.110
Name:	google.com
Address: 2a00:1450:4003:810::200e

root@sparrow:/home/bnp#

root@sparrow:/home/bnp# docker exec home-assistant nslookup google.com 8.8.8.8
;; UDP setup with 8.8.8.8#53(8.8.8.8) for google.com failed: permission denied.
;; no servers could be reached
;; UDP setup with 8.8.8.8#53(8.8.8.8) for google.com failed: permission denied.
;; no servers could be reached
;; UDP setup with 8.8.8.8#53(8.8.8.8) for google.com failed: permission denied.
;; no servers could be reached

root@sparrow:/home/bnp# docker exec home-assistant nslookup google.com 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	google.com
Address: 192.178.25.110
Name:	google.com
Address: 2a00:1450:4003:810::200e

root@sparrow:/home/bnp#

the errors in the last is interesting., running it several times gives both success and failures…

Its a pretty standard ubuntu and I have not found any iptables block on udp:53 or similar

Normann_P_Nielsen · March 11, 2026, 9:26pm

As stated - 2 things are wierd:

It comes in spikes - not a constant error rate
I have seen 2 times that a Home Assistant restart changed the situation completely - like 2 days without a single error, and now after morning restart - spikes again

Normann_P_Nielsen · March 11, 2026, 9:27pm

I am at the same kernal as mentioned here: Unstable network connection from inside Home Assistant Docker Container - #6 by maks

Impact · March 11, 2026, 9:40pm

Hmm. Can you try with another DNS Server?

docker exec home-assistant nslookup google.com 1.1.1.1
docker exec home-assistant nslookup google.com 9.9.9.9

Just out of curiosity, does this mention e1000e?

ls -l /sys/class/net/*/device/driver

Anything interesting in the kernel logs?

journalctl -kr

Also try to add this to the compose and up again

cap_add:
  - NET_RAW

Perhaps also disable UFW if enabled

ufw disable

Normann_P_Nielsen · March 12, 2026, 6:27am

root@sparrow:/home/bnp# ufw status
Status: inactive
root@sparrow:/home/bnp#
root@sparrow:/home/bnp# ls -l /sys/class/net/*/device/driver
lrwxrwxrwx 1 root root 0 Feb 21 17:21 **/sys/class/net/enp4s0/device/driver** -> **../../../../bus/pci/drivers/tg3**
root@sparrow:/home/bnp#

root@sparrow:/home/bnp# docker exec home-assistant nslookup google.com 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
Name: google.com
Address: 142.250.147.102
Name: google.com
Address: 142.250.147.113
Name: google.com
Address: 142.250.147.100
Name: google.com
Address: 142.250.147.101
Name: google.com
Address: 142.250.147.138
Name: google.com
Address: 142.250.147.139
Name: google.com
Address: 2a00:1450:4025:c01::66
Name: google.com
Address: 2a00:1450:4025:c01::65
Name: google.com
Address: 2a00:1450:4025:c01::8b
Name: google.com
Address: 2a00:1450:4025:c01::8a

root@sparrow:/home/bnp# docker exec home-assistant nslookup google.com 9.9.9.9
Server: 9.9.9.9
Address: 9.9.9.9#53
Non-authoritative answer:
Name: google.com
Address: 142.251.142.46
Name: google.com
Address: 2a00:1450:4005:804::200e
root@sparrow:/home/bnp#

And no DNS errors since yesterday around 21:00

Normann_P_Nielsen · March 12, 2026, 6:29am

github.com/home-assistant/core

Ubuntu 24.04 Kernel 6.8.0-100 breaks UDP multiple integrations with PermissionError

opened 12:11PM - 09 Feb 26 UTC

fanderko

### The problem I encountered issues with multiple integrations (GoodWe, Tuya, …Ariston, HACS). Any integration attempting to use UDP or network discovery fails with PermissionError or Network Unreachable. This is a system-wide networking issue affecting the Docker host mode over Wi-Fi. ### What version of Home Assistant Core has the issue? core-2026.2.1 ### What was the last working version of Home Assistant Core? core-2026.2.1 ### What type of installation are you running? Home Assistant Container ### Integration causing the issue GoodWe, Ariston, HACS, Tuya ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt Logger: homeassistant.config_entries Source: config_entries.py:749 First occurred: 9:58:37 PM (1 occurrence) Last logged: 9:58:37 PM Error setting up entry GoodWe for goodweTraceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/goodwe/__init__.py", line 21, in async_setup_entry inverter = await connect( ^^^^^^^^^^^^^^ ...<3 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/goodwe/__init__.py", line 56, in connect await inv.read_device_info() File "/usr/local/lib/python3.13/site-packages/goodwe/et.py", line 461, in read_device_info response = await self._read_from_socket(self._READ_DEVICE_VERSION_INFO) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/goodwe/inverter.py", line 132, in _read_from_socket result = await command.execute(self.host, self.timeout, self.retries) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/goodwe/protocol.py", line 149, in execute transport, _ = await loop.create_datagram_endpoint( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<2 lines>... ) ^ File "/usr/local/lib/python3.13/asyncio/base_events.py", line 1461, in create_datagram_endpoint raise exceptions[0] File "/usr/local/lib/python3.13/asyncio/base_events.py", line 1448, in create_datagram_endpoint await self.sock_connect(sock, remote_address) File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 641, in sock_connect return await fut ^^^^^^^^^ File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 649, in _sock_connect sock.connect(address) ~~~~~~~~~~~~^^^^^^^^^ PermissionError: [Errno 13] Permission denied Logger: custom_components.ariston Source: custom_components/ariston/__init__.py:88 integration: Ariston (documentation, issues) First occurred: 9:58:34 PM (2 occurrences) Last logged: 9:58:55 PM Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1248, in _wrap_create_connection sock = await aiohappyeyeballs.start_connection( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<6 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 122, in start_connection raise first_exception File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 73, in start_connection sock = await _connect_sock( ^^^^^^^^^^^^^^^^^^^^ ...<6 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 208, in _connect_sock await loop.sock_connect(sock, address) File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 641, in sock_connect return await fut ^^^^^^^^^ File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 649, in _sock_connect sock.connect(address) ~~~~~~~~~~~~^^^^^^^^^ OSError: [Errno 101] Network unreachable The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/config/custom_components/ariston/__init__.py", line 88, in async_setup_entry device = await ariston.async_hello( ^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<2 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/ariston/__init__.py", line 78, in async_hello await self.async_discover() File "/usr/local/lib/python3.13/site-packages/ariston/__init__.py", line 65, in async_discover cloud_devices = await _async_discover(self.api) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/ariston/__init__.py", line 187, in _async_discover ] = await asyncio.gather( ^^^^^^^^^^^^^^^^^^^^^ api.async_get_detailed_devices(), api.async_get_detailed_velis_devices() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/local/lib/python3.13/site-packages/ariston/ariston_api.py", line 551, in async_get_detailed_velis_devices detailed_velis_devices = await self._async_get( ^^^^^^^^^^^^^^^^^^^^^^ f"{self.__api_url}{ARISTON_VELIS}/{ARISTON_PLANTS}" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/local/lib/python3.13/site-packages/ariston/ariston_api.py", line 992, in _async_get return await self.__async_request("GET", path, params, None) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/ariston/ariston_api.py", line 948, in __async_request response = await session.request( ^^^^^^^^^^^^^^^^^^^^^^ method, path, params=params, json=body, headers=headers ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 770, in _request resp = await handler(req) ^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 725, in _connect_and_send_request conn = await self._connector.connect( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ req, traces=traces, timeout=real_timeout ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 622, in connect proto = await self._create_connection(req, traces, timeout) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1189, in _create_connection _, proto = await self._create_direct_connection(req, traces, timeout) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1561, in _create_direct_connection raise last_exc File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1530, in _create_direct_connection transp, proto = await self._wrap_create_connection( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<7 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1271, in _wrap_create_connection raise client_error(req.connection_key, exc) from exc aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host www.ariston-net.remotethermo.com:443 ssl:default [Network unreachable] ``` ### Additional information This is a host-level kernel regression. If you encounter this, downgrading the kernel to 6.8.0-94-generic restores full functionality. This seems to be related to how the new kernel handles unprivileged UDP sockets over Wi-Fi.

Normann_P_Nielsen · April 7, 2026, 6:52am

Just for Info - after moving to another kernel: