Hass.io cannot use local DNS names in place of IP addresses in configuration.yaml

Configuration
2

I’ve been futzing around with the hassio dns options and I discovered that mine was configured like this:

~ $ hassio dns info
host: 172.30.32.3
latest_version: "1"
locals:
- dns://192.168.0.8
- dns://1.1.1.1
servers:
- dns://8.8.8.8
- dns://1.1.1.1
version: "1"
~ $

The 192.168.0.8 is my pihole server and it should be coming from the DHCP assignment but I wondered if for reason HassOS/hass.io was using hardcoded dns://8.8.8.8 and dns://1.1.1.1 for name resolution. I tried manually setting the values to my pihole server like this:

~ $ hassio dns options --servers dns://192.168.0.8
Command completed successfully.
~ $ hassio dns info
host: 172.30.32.3
latest_version: "1"
locals:
- dns://192.168.0.8
- dns://1.1.1.1
servers:
- dns://192.168.0.8
version: "1"
~ $ hassio dns restart
Processing... Done.

Command completed successfully.
~ $ hassio dns info
host: 172.30.32.3
latest_version: "1"
locals:
- dns://192.168.0.8
- dns://1.1.1.1
servers:
- dns://192.168.0.8
version: "1"
~ $

but that still didn’t solve the problem, removing the IP from envoy and restarting hassio yields this:

image
image736×44 8.13 KB

I can easily see my envoy device by using its hostname in the hassio ssh window:

~ $ ping envoy
PING envoy (192.168.1.37): 56 data bytes
64 bytes from 192.168.1.37: seq=0 ttl=63 time=1005.991 ms
64 bytes from 192.168.1.37: seq=1 ttl=63 time=7.220 ms
64 bytes from 192.168.1.37: seq=2 ttl=63 time=4.584 ms
^C
--- envoy ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 4.584/339.265/1005.991 ms
~ $ nslookup envoy
Server:         127.0.0.11
Address:        127.0.0.11#53

Name:   envoy
Address: 192.168.1.37

~ $ nslookup envoy pihole
Server:         pihole
Address:        192.168.0.8#53

Name:   envoy
Address: 192.168.1.37

~ $

What is the meaning of locals vs. servers in the HassOS CLI hassio dns info output?

1 Like