Skip to content
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

Using DoH upstream causes DNS timeout on WAN failover. #875

Closed
ruifung opened this issue Jul 9, 2019 · 2 comments
Closed

Using DoH upstream causes DNS timeout on WAN failover. #875

ruifung opened this issue Jul 9, 2019 · 2 comments
Assignees
Milestone

Comments

@ruifung
Copy link

ruifung commented Jul 9, 2019

When using DoH upstreams, DNS queries to AGH will timeout when my router switches to the backup internet connection. After few minutes it proceeds to work again.

This does not occur when using DoT instead of DoH. My personal suspicion is that with DoH, persistent HTTPS connections are used and it would stop DNS resolution until the existing connections times out.

Steps to reproduce

  1. Test DNS resolution - it works
  2. Shut down the main internet connection to cause a failover.
  3. Test DNS resolution again - times out
  4. Wait a few minutes, DNS resolution works again.

Expected behavior

DNS Resolution should work without timing out on WAN connection failover

Actual behavior

DNS starts timing out for a few minutes.

Your environment

Router has 2 internet connections, one fiber connection and a backup LTE.
AGH is installed in a docker container and exposed to network with MACVLAN.

Description Value
Version of AdGuard Home server: 0.96-hotfix
How did you setup DNS configuration: Docker container w/ MACVLAN
If it's a router or IoT, please write device model: Official AGH Docker Image
Operating system and version: Docker on Ubuntu 19.04
@ameshkov ameshkov added this to the v0.99 milestone Jul 10, 2019
@ameshkov
Copy link
Member

My personal suspicion is that DoH is that persistent HTTPS connections are used and it would stop DNS resolution until the existing connections times out.

Yeah, most likely this is the reason.

@ameshkov ameshkov modified the milestones: v0.99, v0.100 Sep 16, 2019
@szolin
Copy link
Contributor

szolin commented Sep 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants