Closed mdegat01 closed 2 years ago
For the record, I am linking the .local
issues to show evidence of the forward plugin getting stuck on cloudflare. In reality the recent changes to the mdns plugin (#73) should've resolved those, it seems to have helped users currently on the 2022.3
(https://github.com/home-assistant/plugin-dns/issues/54#issuecomment-1066164588 and https://github.com/home-assistant/plugin-dns/issues/54#issuecomment-1066208858)
Reverting the removal of policy: sequential
after talking to @pvizeli . We should still go sequential and prefer the user provided DNS overrides over the local ones provided by DHCP. Also removing healthcheck doesn't disable it, it defaults to 0.5s
😱 Setting max_fails
to 0 to disable.
Cloudflare's DNS server in the corefile config was intended only to be a fallback, one to be used when the provided ones failed. However it is currently listed twice in this config: as a fallback and as the last forwarding DNS server. This creates two issues:
We made the fallback plugin so we could use cloudflare as a fallback if the others fail to minimize the amount of DNS issues faced by users that pay no attention to DNS and expect it to just work. We should limit our usage of it to just that so the local DNS servers are always preferred.