New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS server settings ignored for resolving lan hosts. #6
Comments
|
As discussed on Discord, I looked a bit deeper into the Core DNS setup to try to understand what could go wrong. It really seems as if Core DNS suddenly stops query the local DNS server (in which case this bug probably belongs to a different place, but that is not certain at this point). One theory I had was that the forward policy to the local server somehow got stuck on the fallback server. However, it seems that the Also the So I am a bit out of idea what could go wrong in your setup... :-( |
|
Thing is, I'm not alone with this. Even it it probably is a margin case. After our talk on Discord, I have added my router (192.168.11.1) as extra dns server. The router has ONLY 192.168.11.2 as its dns server. |
|
it didn't work ... and : and : |
|
Will be fix with next CoreDNS update |
|
sorry to bother you, @pvizeli , is this not yet included in HassOS 4.16 ? |
|
You will all time see that because of health check. Please use Home Assistant Container if you have an issue with that |
HassOS release with the issue:
Journal logs:
Description of problem:
TLDR : After some time (X hours) , HA stops using the user-defined DNS server, thus no longer being able to resolve hosts on the LAN.
HA is configured to use a local DNS server :
Trying to resolve a local host fails :
On the DNS server side, the logs show no request arriving for that lookup.
Forcing the lookup to use the specific DNS server works :
And in this case, the DNS logging indeed confirms name resolution :
Doing the same on the HassOS host works without ant kind of issue :
Additional info :
ha dns restartsolves the issue, for a while (X hours), but it always returns to being broken.The text was updated successfully, but these errors were encountered: