Hi,
my hassio constantly tries to resolve cbsnews - nearly every minute. I already disabled dns fallback but the requests still appears.
My rpi5 with hassio installed is receiving the network configuration from my home router and the dns server itself is a adguard container running within hassio. That’s working and I can see that the ha dns container itself is sending packages to cbsnews and I wonder why.
Any ideas?
I tried to dig a bit deeper but couldn’t find any usefull information on that topic, nor do I see a reason why my instance tries to resolve that domain. The CoreDNS Log is looging fine:
[11:07:22] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/corefile.sh
cont-init: info: /etc/cont-init.d/corefile.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun coredns (no readiness notification)
s6-rc: info: service legacy-services successfully started
.:53
.:5553
CoreDNS-1.8.4
linux/arm64, go1.15.15, 053c4d5-dirty
Also the Settings are fine in my opinion:
~ ha dns info
fallback: false
host: 172.30.32.3
llmnr: true
locals:
- dns://192.168.178.37
mdns: true
servers: []
update_available: false
version: 2023.06.2
version_latest: 2023.06.2
~ ha resolution info
checks:
- enabled: true
slug: backups
- enabled: true
slug: addon_pwned
- enabled: true
slug: dns_server_ipv6
- enabled: true
slug: supervisor_trust
- enabled: true
slug: core_security
- enabled: true
slug: network_interface_ipv4
- enabled: true
slug: dns_server
- enabled: true
slug: multiple_data_disks
- enabled: true
slug: docker_config
- enabled: true
slug: free_space
issues:
- context: system
reference: null
type: no_current_backup
uuid: f23ca0afa0c34610ab462727f78ed9b6
suggestions:
- auto: false
context: system
reference: null
type: create_full_backup
uuid: ccb43478de80484c8a019f9d8c554536
unhealthy: []
unsupported: []
I can resolve internal containers as well as external domains:
~ nslookup fritz.box
Server: 172.30.32.3
Address: 172.30.32.3#53
Non-authoritative answer:
Name: fritz.box
Address: 192.168.178.2
~ nslookup google.com
Server: 172.30.32.3
Address: 172.30.32.3#53
Non-authoritative answer:
Name: google.com
Address: 142.250.75.14
I don’t have any suspicious addons installed that should try to resolve the domain:
~ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
eacc6208142c ghcr.io/hassio-addons/nginxproxymanager/aarch64:1.0.1 "/init" 45 minutes ago Up 45 minutes 0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp addon_a0d7b954_nginxproxymanager
2d176de9b1be local/aarch64-addon-dyndns-netcup:1.0.5 "/init /run.sh" 45 minutes ago Up 45 minutes addon_local_dyndns-netcup
91155a2cc746 ghcr.io/hassio-addons/adguard/aarch64:5.0.4 "/init" 46 minutes ago Up 46 minutes (healthy) addon_a0d7b954_adguard
ece59c4793d6 ghcr.io/hassio-addons/ssh/aarch64:17.2.0 "/init" 46 minutes ago Up 46 minutes addon_a0d7b954_ssh
4fac921b69b3 homeassistant/aarch64-addon-mosquitto:6.4.0 "/init" 46 minutes ago Up 46 minutes 0.0.0.0:1883-1884->1883-1884/tcp, :::1883-1884->1883-1884/tcp, 0.0.0.0:8883-8884->8883-8884/tcp, :::8883-8884->8883-8884/tcp addon_core_mosquitto
3ae9b2fc0f2d ghcr.io/home-assistant/aarch64-hassio-multicast:2023.06.2 "/init" 46 minutes ago Up 46 minutes hassio_multicast
52e3487f9855 ghcr.io/home-assistant/aarch64-hassio-audio:2023.12.0 "/init" 46 minutes ago Up 46 minutes hassio_audio
8992d1969fa6 ghcr.io/home-assistant/aarch64-hassio-dns:2023.06.2 "/init" 46 minutes ago Up 19 minutes hassio_dns
a76e6ca7d1f5 ghcr.io/home-assistant/aarch64-hassio-cli:2024.02.1 "/init" 46 minutes ago Up 46 minutes hassio_cli
51147347f663 ghcr.io/home-assistant/raspberrypi5-64-homeassistant:2024.3.0 "/init" 5 days ago Up 45 minutes homeassistant
cf880bed4b9a ghcr.io/home-assistant/aarch64-hassio-supervisor:latest "/init" 11 days ago Up 46 minutes hassio_supervisor
0b60001aeaac ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0 "/usr/bin/observer" 2 months ago Up 46 minutes 0.0.0.0:4357->80/tcp, :::4357->80/tcp hassio_observer
I also tried to disable some addons but the hassio instance still tries to resolve cbsnews. Am I the only person with that behaviour?