You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set up coredns docker container address as Private reverse DNS server
Start both adguard and coredns at the same time (using docker-compose)
Expected result
I would expect adguard home to re-try using Private reverse DNS server after failure, rather than trying once and then disregarding it forever until restart.
Actual result
Adguard home probably tries to contact Private reverse DNS server after start, it fails because coredns instance is still not ready to serve, then it continues to ignore it completely, unless adguard home is restarted, or Private reverse DNS server entry is re-done and saved again.
Uh oh!
There was an error while loading. Please reload this page.
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
Installation
Docker
Setup
On one machine
AdGuard Home version
v0.107.59
Action
Expected result
I would expect adguard home to re-try using Private reverse DNS server after failure, rather than trying once and then disregarding it forever until restart.
Actual result
Adguard home probably tries to contact Private reverse DNS server after start, it fails because coredns instance is still not ready to serve, then it continues to ignore it completely, unless adguard home is restarted, or Private reverse DNS server entry is re-done and saved again.
Additional information and/or screenshots
docker-compose
The text was updated successfully, but these errors were encountered: