DNS not working on homeassistant under Hassio

Anyone have any idea what this image is?

homeassistant/armhf-hassio-dns

From what I can tell, homeassistant is now offloading DNS requests to this. Problem is, homeassistant now keeps failing at any DNS requests that are internal to my network, which is a huge problem…

From homeassistant container:

root@hassio:/home/brad# docker exec -it homeassistant bash
bash-5.0# cat /etc/resolv.conf 
search local.hass.io
nameserver 172.30.32.3
bash-5.0# nslookup camera-server.home
nslookup: can't resolve '(null)': Name does not resolve

nslookup: can't resolve 'camera-server.home': Name does not resolve

So it is offloading my DNS requests to a host of 172.30.32.3, which clearly can’t find my camera-server.home host, which is a bad thing since it is referenced in configuration.yaml. I can’t ssh to 172.30.32.3, but by the luck of it, figured out that this is homeassistant/armhf-hassio-dns. So then…

root@hassio:/home/brad# docker exec -it hassio_dns bash  
bash-5.0# ip addr show | grep inet
    inet 127.0.0.1/8 scope host lo
    inet 172.30.32.3/23 brd 172.30.33.255 scope global eth0 
bash-5.0# cat /etc/resolv.conf
search local.hass.io
nameserver 127.0.0.11
options ndots:0
bash-5.0# ping 127.0.0.11
PING 127.0.0.11 (127.0.0.11): 56 data bytes
64 bytes from 127.0.0.11: seq=0 ttl=64 time=0.231 ms
64 bytes from 127.0.0.11: seq=1 ttl=64 time=0.329 ms
^C
--- 127.0.0.11 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.231/0.280/0.329 ms
bash-5.0# nslookup camera-server.home
nslookup: can't resolve '(null)': Name does not resolve

nslookup: can't resolve 'camera-server.home': Name does not resolve

But what is 127.0.0.11? If I SSH to that, it’s my hassio host. Ok, but that host can properly resolve DNS requests. So what is going on?

brad@hassio:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain home
nameserver 192.168.10.1
brad@hassio:~ $ nslookup
-bash: nslookup: command not found
brad@hassio:~ $ ping camera-server.home
PING camera-server.home (192.168.30.202) 56(84) bytes of data.
64 bytes from camera-server.home (192.168.30.202): icmp_seq=1 ttl=128 time=0.392 ms

Look at my suggestion here, maybe it will work…

Thanks. I went ahead and updated the docker instance running, and i may be partly there. Now I can go into the hassio_dns container, and it is resolving the internal DNS entry maybe 20% of the time. That’s not good enough for the configuration.yaml since if it doesnt always resolve, it will error out.

Post an issue on github, or add to the one there already.

Yes, this is directly related to https://github.com/home-assistant/hassio/issues/1231