AdguardTeam / AdGuardHome

Network-wide ads & trackers blocking DNS server
https://adguard.com/adguard-home.html
GNU General Public License v3.0
24.9k stars 1.79k forks source link

DNS Over HTTPS fails when WAN IP Changes #3958

Closed LewisSpring closed 2 years ago

LewisSpring commented 2 years ago

Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

Issue Details

Expected Behavior

When the WAN IP address changes, DNS Over HTTPS resolution should continue.

Actual Behavior

DNS queries are not resolved, they time out. The Container needs restarting for DNS Resolution to continue.

Screenshots

Screenshot of failed NSLookup: ![image](https://user-images.githubusercontent.com/40576482/146650443-e3aacd7f-c4a5-41e9-bd5e-ce76115d0f29.png)

Additional Information

My PiHole running DNSCrypt-Proxy suffers from the same issue. If I change the DNS AGH uses (before restarting the container, after WAN IP change), the issue does not fix. The container needs to be restarted.

The Docker container is bridged. There are no apparent log entries.

EugeneOne1 commented 2 years ago

@LewisSpring, hello. The issue looks similar to #3217. Could you please try one of the latest edge/beta builds and check if the issue reproduces there?

LewisSpring commented 2 years ago

Hi @EugeneOne1 , I didn't spot that one since It used different keywords. I'll try it and get back to you.

LewisSpring commented 2 years ago

Good Evening @EugeneOne1 , seems like the latest Edge build has fixed the issue. I've had some WAN changes and the resolution has continued. When can I expect to see these fixes in a stable release?

Thanks for your help.

ainar-g commented 2 years ago

Either later today or tomorrow, if all goes to plan.