Closed idfxken closed 2 years ago
This problem bas been around for at least 1 year, devs can't/won't fix.
As a work-around, I’m using an edited /usr/share/tempio/corefile.
This is on Home Assistant OS, so that file is located inside the hassio_dns docker container.
Of course this meant i need to re-apply the edit after every update to HAOS, beats having to do ha dns restart
every few hours.
was running a script every hour, to restart the container. but this way seems cleaner for now :) ty. Hope that they one day fix it, I'll leave it open, as it rly is a dirty bug
in 2021.11 bug is still present
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Still present in 2021.12.7.
still present, the workaround doesnt help for long uptime
Fixed by #82
Also note that there is a new option to disable the fallback dns added here: https://github.com/home-assistant/supervisor/pull/3586 as I would guess a number of users on here would be interested in that.
Ha is configured with a local dns resolver, while all other means of resolving are blocked on our home automation subnet.
When (re)started, HA dns runs perfectly fine, and can resolve all queries through the assigned server.
After a few hours, the resolver just stops resolving through the programmed server. and switches to dot 1.0.0.1/1.1.1.1:853 for all dns requests, which are all refused by the router ofcourse. Somehow HA jforgot, that 192.168.1111.1 is its assigned dns server.
Edit: logs from the second the issue starts: