Hello, i made a fresh installation last week and migrate from Raspberry to a x86 based image. The load times are really high, so invest some time to find out more informations… I searched also here in the forum, on google but nothing helped. I disabled addons, disabled integrations and so on. The c…

1.1.1.1 But you made my day, i checked also for IPv6 and deactivated it. And the cpu goes down to 0.1! Thank you!!!

My hassio_dns container has started going bonkers as of this morning, as well. It is using 100% of one core and also straining pfsense on another server. In glances, the container is showing a ton of tx/rx (5-6 Mb/s). Anyone have any idea what is going on here? I’m running HAOS on proxmox. [Image…

I got the same things [image] CPU usage increasing a lot this morning 10 AM, maybe related to this release ? Release 2022.05.0 · home-assistant/supervisor · GitHub Don’t know if supervisor is related to hassio_dns EDIT : I disable the fallback dns method and everything is ok now. (Requiremen…

That did it! Jesus Christ that was nuts. Any idea what was in all of that traffic? Was that just millions of dns requests? I’m so curious.

What do your logs say? Should be able to see logs for the dns container by going here and changing the logger to DNS.

Ahhhh that’s how you get the container logs. It’s full of connection refused errors on port 853 on the cloudflare servers, followed by some NS errors on a high port on 127.0.0.1.

I assume you have port 853 and/or cloudflare blocked on your network? That does seem to cause runaway DNS queries. Although I’m still not totally sure why. I stopped the runaway healthchecking with this pr but something else seems to kick in when it gets blocked…

I was rerouted all requests back to pfsense at one point, but I thought I removed that NAT rule. I’ll take another look when I get home. edit: I was pointing home assistant to my pfsense instance for DNS, but I only had pfsense listening on port 53. I did not have the DNS over SSL/TLS option enable…

I think I got similar DNS setup as you Andy. I redirect all DNS queries from my LAN to the local DNS (:53) resolver of my router and I’m also not responding on :853 [core-ssh ~]$ ha dns info fallback: true host: 172.30.32.3 llmnr: true locals: - dns://X.X.X.1 mdns: true servers: [] update_available…

I’ve been having this issue too, quite frustrating as it bumped the power consumption of the host of my Hassio VM by about 20W from the excessive CPU consumption. To resolve it for now I’ve ran the command to disable fallback, hope this helps anyone else.

The runaway DNS is a result of something screwy going on when CoreDNS is looking for the NXDOMAIN rcode in the responding packet, but all it gets is a RST packet. The result is infinitely forwarding requests to the fallback. Remove NXDOMAIN from the list of fallback rcodes and everything is stable a…

High CPU load hassio_dns Container

Installation Home Assistant OS

phier (john) August 14, 2022, 5:43pm 16

@d0nni3q84 is there also fix for that issue?

seems this is the fix > Very high CPU usage for CoreDNS - #2 by Ohjay