Name resolution problem since 0.97.2

[throwaway]

The fix many have mentioned worked for me until a reboot. What I did was a combination of multiple fixes.

First, issue this command:

hassio dns options --servers dns://x.x.x.x

Then I downgraded the supervisor to the previous working version with this command:

hassio supervisor update --version=173

To prevent the supervisor from auto-updating on reboot, I went into my router and blocked outbound internet traffic for the device’s mac address.
That caused my internet based integrations to fail, so I added firewall rules to allow those particular IP addresses to work.

Everything is working wonderfully now, but it’s only a bandaid.

[DavidFW1960 (David)]

@throwaway

The fix many have mentioned worked for me until a reboot

I’ve done 3 full reboots now and my corefile with the dns server I added via the command has been retained. No idea why you are losing yours. It’s stored in a persistent area of the disk…

[frenck (Franck Nijhof)]

@DavidFW1960

One issue this caused for me, because I use Caddy (Reverse Proxy) and my caddy was set to forward to localhost… well none of the dns resolvers have localhost and thus couldn’t be resolved. So I edited caddy to use the ip-address of the NUC instead of localhost and all is now well again.

That response is genius! Thank you, I just resolved an issue because of this little piece of text. Thanks!

[AutoT]

Would the supervisor make use of a hosts file if it existed? (I know, dark-ages networking )

In a normal system, I’d know where to create one and test it, but I just don’t know how to approach this in the Hass IO system

[bucksbass (Michael Moyse)]

Anyone know when the fix will be out, I’m still getting random DNS results for what should be internal devices, sometimes internal IPs sometimes incorrect external IPs

[frenck (Franck Nijhof)]

@bucksbass Fix was just released, for more details, see my comment here:

https://github.com/home-assistant/hassio/issues/1231#issuecomment-522312855

[frenck (Franck Nijhof)]

Supervisor 180 has been released

This release addresses a couple of issues & comments:

• Google DNS has been replaced by the privacy-aware Quad9
• Random hostnames no longer resolve to AWS.
• localhost should now work, independent of add-on state.
• Custom DNS is now preferred correctly, CloudFlare & Quad9 are secondary
• Ability added to restart Hass.io DNS to apply settings

All add-ons providing the hassio CLI have been updated with CLI v3.1.0

This version of the CLI adds the hassio dns restart command, connecting to the restarting endpoint added in Supervisor 180.

Setting your own DNS server

This requires both supervisor 180 and the latest add-ons with CLI v3.1.0

• hassio dns options --servers dns://IP_ADDRESS
• hassio dns restart

Thank you all for the feedback, sorry for the trouble

[Winni (Winni Neessen)]

Confirmed! Thanks for the quick fix frenck!

[bucksbass (Michael Moyse)]

Two errors for me:

19-08-18 12:28:59 ERROR (MainThread) [hassio.dns] Can’t write local resolv: [Errno 13] Permission denied: ‘/etc/resolv.conf’

hassio dns restart
The dns command allows you to manage the internal Hass.io DNS server by
exposing commands to view, monitor, configure and control it.

Usage:
hassio dns [command]

Examples:

hassio dns logs
hassio dns info
hassio dns update

Available Commands:
info Shows information about the internal Hass.io DNS server
logs View the log output of the Hass.io DNS server
options Allow to set options for the internal Hass.io DNS server
stats Provides system usage stats of the Hass.io DNS server
update Updates the internal Hass.io DNS server

[gotson (Gauthier)]

Hi, i’ve updated to the latest hassio supervisor 180, but my local hostnames are still not resolved. It should get my router IP as the first DNS server from DHCP, but it seems it doesn’t ?

[frenck (Franck Nijhof)]

@bucksbass Update the add-ons, as listed in my post. That is CLI v3.0.0, which indeed does not have the restart command.

Regarding the error, please report issues on GitHub, thanks

[frenck (Franck Nijhof)]

@gotson

Hi, i’ve updated to the latest hassio supervisor 180, but my local hostnames are still not resolved. It should get my router IP as the first DNS server from DHCP, but it seems it doesn’t ?

If you want to use a custom DNS, please read my post. By default it doesn’t use it. This releases addresses a part of the issues.

[bucksbass (Michael Moyse)]

None of my add-ons are showing they need updates.

[gotson (Gauthier)]

will a future release bring this behaviour as default ?

[frenck (Franck Nijhof)]

@bucksbass

None of my add-ons are showing they need updates.

Go to the add-on store, top right corner a refresh button is shown… .hit it!

[aidbish (Adrian)]

Cheers for the work Frenck
Choo-choo homie

[frenck (Franck Nijhof)]

@gotson

will a future release bring this behaviour as default ?

We are looking into the possibilities.

[gotson (Gauthier)]

that would seem quite normal to honor the DNS returned by the DHCP. Fiddling with commands to setup something that everyone seems to expect as default is a bit counter-intuitive

[frenck (Franck Nijhof)]

Agree, this release we’ve focused on getting the heat and biggest issues out first. Which is simply more important right now.

[bucksbass (Michael Moyse)]

I give up. Sorry but I’ve lost confidence in this platform, although I appreciate your attempts to fix this I don’t really enjoy spending my valuable weekends looking for problems caused by an auto update that I have no control over. It’s just fortunate that it was this weekend, had it been last weekend I would have been away for a week with a broken system that should have been in vacation mode, this is why I want to control when things update.

Sorry to rant but that’s where I am right now.