I have had this happen several times and decided it was time to ask on forum as I’m certain I may have something misconfigured. I have had my home assistant up and running for several months now and have run into situations where it was unable to communicate to DNS and my deployment as a whole becomes unresponsive, unreachable - It been the same behavior on each of these occasions and just wrote it off as an anomaly previously but today it stuck. Again lost ability to talk to DNS and my HA deployment became unreachable, fixed dns communications, reboot and everything came back fine. Is this expected behavior??
How do you connect to home assistant? If you connect to something like http:192.168.10.123:8123 no DNS,but if you connect with a name like “http://home assistant.local:8123/“ then, depending, DNS may be required. Try the former next time and see?
I have tried both methods and both are non-functional - I get a “Connection Refused” in my web browser. I can connect to it via ssh and also through console so it’s up, it is just not healthy. I wouldn’t think that because of a simple thing such as dns that it would render the entire system unstable.
Are you running a system that has supervisor? If so, then the DNS server is hardcoded in the aystem and if it is unable to reach the DNS server (internet connection lost for example) it will stop working correctly.
i am running system with a supervisior and dns is not hardcoded (I figured out how to change it). It just blows me away that a system would be rendered useless because it cannot speak to a dns server.
I mean aside from your specific case, which i certainly don’t want to disregard because it sounds like a real problem for you, but is this really a well established issue on a more general scale ? Does HassOS or Supervised really become completely useless without access to a DNS (so, without internet access) ?
I have a hard time believing this, to be honest. One of HAs main ‘selling’ points is entirely local control. If HA went down completely - even on the LAN - just because you lost your internet access, I would expect this to be much more prominently discussed, no ?
Edit: I use HA Core, so I can’t test myself.
Well unless I got the worse build Home Assistant put out I would think this would be very easy to test and prove out. These are the software versions I’m running, you simply need to run it - kill it’s ability to communicate to dns and then reboot:
Core
Supervisor
Host
Version Version Hostname CHANGE
core-2021.2.3 supervisor-2021.03.0 homeassistant
Newest Version
core-2021,3.0b6
Newest Version
UPDATE „ UPDATE
supervisor-2021.03.1
IP Address
192.168.60.148/24
CHANGE
Channel
. LEAVE BETA CHANNEL
beta
Operating System
Home Assistant OS 5.11
UPDATE
Share Diagnostics Deployment
Share crash reports and diagnostic information.
Learn more
production
Core CPU Usage Supervisor CPU Usage
2.1% 1 0.7% 1
Core RAM Usage Supervisor RAM Usage Used Space
4.7% • 0.8% 1 40.9%
RESTART CORE
RELOAD SUPERVISOR
RESTART SUPERVISOR
REBOOT HOST
SHUTDOWN HOST
(In case this doesn’t work. Check the logs, if there’s an error where a host can’t be resolved (eg: lookup ghcr.io: no such host) there might be a problem with your network settings (eg: dns server that can’t be reached)). This my problem From the beginning I have had to set my DNS to 1.1.1.1 each and every time I had to reinstall HA SP. It will never find it on my router with basic [homeassistant.local:8123] nor does it find any tasmota DNS names.