5 ms·

This enables Cloudfare’s DOH servers - this is probably a good idea for embedded stuff. My ISP for example resolves all unknown hostnames to their advertisemen

by theamk 5y ago

This enables Cloudfare’s DOH servers - this is probably a good idea for embedded stuff. My ISP for example resolves all unknown hostnames to their advertisement server - so a mistyped hostname in MQTT bridge name will result in “connection refused” errors, which are super confusing and misleading.

hassio 5y ago
Were it configurable, I would agree. But the Cloudflare DNS servers can't be disabled nor redirected to local DNS servers because it uses DNS over TLS. For a platform that describes itself as "puts local control and privacy first", forcing DNS queries to be sent to an external third party seems like the exact opposite of what should be done. For those running their own local DNS servers for local control and privacy, Home Assistant won't respect the DNS servers configured manually or via DHCP. It is also worth noting that if Home Assistant loses internet connectivity or if the Cloudflare DNS servers are blocked, Home Assistant will slow to a halt because it constantly (many times a second) tries to connect to Cloudflare.
- salawat 5y ago
  Welcome to the wonderful world of the binary patch. Ve have vays of making things vork ze vay ve vish. ...In the abscence of signed firmware, burned in values in silicon, and other such remote attestation oriented BS, that is.
  - hassio 5y ago
    Unfortunately we do not. The change will get wiped any time HA is restarted.
- theamk 5y ago
  I think it is configurable though? Just edit the source file you linked to on your system disk. I don't use HA's os image, but this looks like a text file on the mutable partition that you can easily edit. If one knows enough to set up local DNS servers, surely they can do this as well. Re "slow to a halt" issue, this sounds like a bug independent of the upstream server issue. If the internet is not working (because general connectivity is lost, or someone blocked the DNS server, whatever) then of course the internet-using parts will cease to work, but local network parts should still be working. The config file is pretty clear that it is not supposed to use DNS servers, cloudfare or any other ones, for the local network connections. If this is not the case, you should file a bug.
  - hassio 5y ago
    > I think it is configurable though? Just edit the source file you linked to on your system disk. Unfortunately it is not :(. The change will get wiped any time HA is restarted. > If the internet is not working (because general connectivity is lost, or someone blocked the DNS server, whatever) then of course the internet-using parts will cease to work, but local network parts should still be working. Local network parts stop working as well. A DNS lookup for a non-existing local domain results in the query being sent to Cloudflare. This cannot be prevented. > The config file is pretty clear that it is not supposed to use DNS servers, cloudfare or any other ones, for the local network connections. If this is not the case, you should file a bug. Many bug reports have been filed about this: https://github.com/home-assistant/plugin-dns/issues https://github.com/home-assistant/plugin-dns/issues. If you look at the config file, SERVFAIL and NXDOMAIN responses are considered to be a "failure" and queries are sent to Cloudflare. This is a poor design decision, not a bug.

by theamk 5y ago

hassio 5y ago

Were it configurable, I would agree. But the Cloudflare DNS servers can't be disabled nor redirected to local DNS servers because it uses DNS over TLS. For a platform that describes itself as "puts local control and privacy first", forcing DNS queries to be sent to an external third party seems like the exact opposite of what should be done. For those running their own local DNS servers for local control and privacy, Home Assistant won't respect the DNS servers configured manually or via DHCP. It is also worth noting that if Home Assistant loses internet connectivity or if the Cloudflare DNS servers are blocked, Home Assistant will slow to a halt because it constantly (many times a second) tries to connect to Cloudflare.

salawat 5y ago
Welcome to the wonderful world of the binary patch. Ve have vays of making things vork ze vay ve vish. ...In the abscence of signed firmware, burned in values in silicon, and other such remote attestation oriented BS, that is.
- hassio 5y ago
  Unfortunately we do not. The change will get wiped any time HA is restarted.
theamk 5y ago
I think it is configurable though? Just edit the source file you linked to on your system disk. I don't use HA's os image, but this looks like a text file on the mutable partition that you can easily edit. If one knows enough to set up local DNS servers, surely they can do this as well. Re "slow to a halt" issue, this sounds like a bug independent of the upstream server issue. If the internet is not working (because general connectivity is lost, or someone blocked the DNS server, whatever) then of course the internet-using parts will cease to work, but local network parts should still be working. The config file is pretty clear that it is not supposed to use DNS servers, cloudfare or any other ones, for the local network connections. If this is not the case, you should file a bug.
- hassio 5y ago
  > I think it is configurable though? Just edit the source file you linked to on your system disk. Unfortunately it is not :(. The change will get wiped any time HA is restarted. > If the internet is not working (because general connectivity is lost, or someone blocked the DNS server, whatever) then of course the internet-using parts will cease to work, but local network parts should still be working. Local network parts stop working as well. A DNS lookup for a non-existing local domain results in the query being sent to Cloudflare. This cannot be prevented. > The config file is pretty clear that it is not supposed to use DNS servers, cloudfare or any other ones, for the local network connections. If this is not the case, you should file a bug. Many bug reports have been filed about this: https://github.com/home-assistant/plugin-dns/issues https://github.com/home-assistant/plugin-dns/issues. If you look at the config file, SERVFAIL and NXDOMAIN responses are considered to be a "failure" and queries are sent to Cloudflare. This is a poor design decision, not a bug.