I have never seen a bunch of requests for ., not sure what to make of that. Nothing was changed related to the online check for the latest supervisor (or for a while to my knowledge).
However due to this thread I did look into the swarms of checkonline queries. I was confused by this because supervisor actually only does a checkonline call every 10 minutes (or every 30 seconds if it believes your offline). When it does the check it does two things
ask network manager to do a connectivity check to check the host (equivalent to running nmcli networking connectivity check in the host shell)
make one HEAD request to checkonline.home-assistant.io to ensure supervisor’s DNS is good
Yet I too was seeing like 50 DNS requests at the same second every 10 minutes to checkonline.home-assistant.io.
Turns out it is network manager. When I ran nmcli networking connectivity check directly I got the same thing. It seems like it checks every network interface individually, including all the veths made for docker containers. Each one gets an A and an AAAA query
I don’t really know why it does this, it’s automated check doesn’t work like this. I did some investigation with @agners and we think it’s a bug fixed by this commit in an upcoming version of NM.
I changed supervisor to reduce this by not asking NM to run a check and instead just asking it for the latest result of its own automated check. Along with a few other improvements that should massively reduce this in the next version of supervisor
EDIT: Ok actually probably the version after the next one. Next one should be 2022.08.6 which was cut before the PR. The one after that will have it.
