starred/AdGuardHome

Fork 0

mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2026-03-04 00:01:12 -05:00

DNS Over HTTPS fails when WAN IP Changes #3262

New issue

Closed

opened 2026-03-04 03:18:17 -05:00 by deekerman · 4 comments

deekerman commented

2026-03-04 03:18:17 -05:00

Owner

Originally created by @LewisSpring on GitHub (Dec 18, 2021).

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.

I am running the latest version
I checked the documentation and found no answer
I checked to make sure that this issue has not already been filed

Issue Details

Version of AdGuard Home server:
- 0.106.3
How did you install AdGuard Home:
- Docker
How did you setup DNS configuration:
- OpenWRT DHCP settings
If it's a router or IoT, please write device model:
- N/A
CPU architecture:
- AMD64
Operating system and version:
- Debian 11 (Linux nuc 5.10.0-9-amd64 # 1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux)

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:

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.

Originally created by @LewisSpring on GitHub (Dec 18, 2021). Have a question or an idea? Please search it [on our forum](https://github.com/AdguardTeam/AdGuardHome/discussions) to make sure it was not yet asked. If you cannot find what you had in mind, please [submit it here](https://github.com/AdguardTeam/AdGuardHome/discussions/new). ### Prerequisites Please answer the following questions for yourself before submitting an issue. **YOU MAY DELETE THE PREREQUISITES SECTION.** - [x] I am running the latest version - [x] I checked the documentation and found no answer - [x] I checked to make sure that this issue has not already been filed ### Issue Details  * **Version of AdGuard Home server:** * 0.106.3 * **How did you install AdGuard Home:** * Docker * **How did you setup DNS configuration:** * OpenWRT DHCP settings * **If it's a router or IoT, please write device model:** * N/A * **CPU architecture:** * AMD64 * **Operating system and version:** * Debian 11 (Linux nuc 5.10.0-9-amd64 # 1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux) ### 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  <details><summary>Screenshot of failed NSLookup:</summary> ![image](https://user-images.githubusercontent.com/40576482/146650443-e3aacd7f-c4a5-41e9-bd5e-ce76115d0f29.png) </details> ### 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.

deekerman

2026-03-04 03:18:17 -05:00

closed this issue
added the
duplicate
label

deekerman commented

2026-03-04 03:18:42 -05:00

Author

Owner

@EugeneOne1 commented on GitHub (Dec 20, 2021):

@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?

@EugeneOne1 commented on GitHub (Dec 20, 2021): @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?

deekerman commented

2026-03-04 03:18:45 -05:00

Author

Owner

@LewisSpring commented on GitHub (Dec 20, 2021):

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

@LewisSpring commented on GitHub (Dec 20, 2021): Hi @EugeneOne1 , I didn't spot that one since It used different keywords. I'll try it and get back to you.

deekerman commented

2026-03-04 03:18:45 -05:00

Author

Owner

@LewisSpring commented on GitHub (Dec 20, 2021):

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.

@LewisSpring commented on GitHub (Dec 20, 2021): 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.

deekerman commented

2026-03-04 03:18:45 -05:00

Author

Owner

@ainar-g commented on GitHub (Dec 21, 2021):

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

@ainar-g commented on GitHub (Dec 21, 2021): Either later today or tomorrow, if all goes to plan.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/AdGuardHome#3262

No description provided.

Rows
Columns