hi all, i might have found a bug in dns resolution in hass.io. i had a separate pihole instance in my network, which i moved into a docker container on a linux host. after moving pihole from a host into a container the integration stopped working.
setup before:
- pihole host: 192.168.1.50
- pihole dns: “pihole.my.domain → A 192.168.1.50”
- integration working
- browser access working
setup after:
- pihole host: 192.168.1.20 (generic linux vm with multiple containers)
- pihole dns: “pihole.my.domain → CNAME box.my.domain”
- integration stopped working
- browser access still working
when i connected into the hass vm using ssh i got this (really weird) behavior:
$ curl pihole.my.domain
curl: (6) Could not resolve host: pihole.my.domain
$ host pihole.my.domain
pihole.my.domain is an alias for box.my.domain
resolution:
- pihole dns: "pihole → A 192.168.1.20`
- integration working again
- browser access still working
- curl in SSH session working again as expected
it seems hass does not resolve CNAMEs correctly, which is basically just astonishing cause i would not even know how to achieve this if i wanted to (to not “just handle” CNAME responses correctly). can somebody maybe confirm this behavior?