All upstream dns fails to exchange

[Lorac]

2021/12/14 02:23:54.700474 [info] Failed to update filter https://www.malwaredomainlist.com/hostslist/hosts.txt: Get "https://www.malwaredomainlist.com/hostslist/hosts.txt": synthetic.wrap: all upstreams failed to exchange request, cause: couldn't do a GET request to 'https://1.1.1.1:443/dns-query', cause: Get "https://1.1.1.1:443/dns-query?dns=t9wBAAABAAAAAAAAA3d3dxFtYWx3YXJlZG9tYWlubGlzdANjb20AABwAAQ": all dialers failed to initialize connection: , cause: dial tcp 1.1.1.1:443: connect: no route to host (hidden: read udp 172.17.0.2:36532->94.140.14.140:53: i/o timeout, read udp 172.17.0.2:49160->94.140.14.14:53: i/o timeout, read udp 172.17.0.2:48753->94.140.14.15:53: i/o timeout, read udp 172.17.0.2:43578->185.228.168.9:53: i/o timeout)

2021/12/14 02:31:03.531282 [info] upstream "https://1.1.1.1/dns-query" fails to exchange: couldn't communicate with upstream: couldn't do a GET request to 'https://1.1.1.1:443/dns-query', cause: Get "https://1.1.1.1:443/dns-query?dns=SIkBAAABAAAAAAAAE2dvb2dsZS1wdWJsaWMtZG5zLWEGZ29vZ2xlA2NvbQAAAQAB": all dialers failed to initialize connection: , cause: dial tcp 1.1.1.1:443: connect: no route to host
2021/12/14 02:31:13.531627 [info] upstream "94.140.14.140" fails to exchange: couldn't communicate with upstream: read udp 172.17.0.2:38148->94.140.14.140:53: i/o timeout
2021/12/14 02:31:23.531935 [info] upstream "94.140.14.14" fails to exchange: couldn't communicate with upstream: read udp 172.17.0.2:41378->94.140.14.14:53: i/o timeout
2021/12/14 02:31:33.532248 [info] upstream "94.140.14.15" fails to exchange: couldn't communicate with upstream: read udp 172.17.0.2:43438->94.140.14.15:53: i/o timeout
2021/12/14 02:31:43.532591 [info] upstream "185.228.168.9" fails to exchange: couldn't communicate with upstream: read udp 172.17.0.2:45196->185.228.168.9:53: i/o timeout

I set up my router to use my server as the DNS server you upstream, but it somehow can't.

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:
  • v0.106.3
• How did you install AdGuard Home:
  • Docker
• How did you setup DNS configuration:
  • Router
• If it's a router or IoT, please write device model:
  • Bell Home Hub 4000
• CPU architecture:
  • AMD64
• Operating system and version:
  • Ubuntu 21.10

Expected Behavior

I would like to be able to scan upstream DNS

Actual Behavior

They all fail to communicate, and the host can't do nslookup anymore.

[ainar-g]

Hello. It looks like the machine has completely lost connection to the Internet.

Also, the v0.107 betas and the upcoming release have several fixes to make AGH recover from connection failures better, so you might want to check them out.

[Lorac]

I will test out v0.107 as soon as possible and come back with feedback.

[Lorac]

2021/12/15 20:41:23.424796 [info] AdGuard Home, version v0.107.0-b.16
2021/12/15 20:41:23.426040 [info] Upgrade yaml: 10 to 11
2021/12/15 20:41:23.426057 [info] Upgrade yaml: 11 to 12
2021/12/15 20:41:23.437108 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
2021/12/15 20:41:23.437216 [info] auth: initialized.  users:1  sessions:1
2021/12/15 20:41:23.437236 [info] Initialize web module
2021/12/15 20:41:23.462475 [info] AdGuard Home is available at the following addresses:
2021/12/15 20:41:23.462694 [info] Go to http://127.0.0.1:80
2021/12/15 20:41:23.462703 [info] Go to http://172.17.0.2:80
2021/12/15 20:41:23.827598 [info] Starting the DNS proxy server
2021/12/15 20:41:23.827624 [info] Ratelimit is enabled and set to 20 rps
2021/12/15 20:41:23.827630 [info] The server is configured to refuse ANY requests
2021/12/15 20:41:23.827635 [info] DNS cache is enabled
2021/12/15 20:41:23.827646 [info] MaxGoroutines is set to 300
2021/12/15 20:41:23.827660 [info] Creating the UDP server socket
2021/12/15 20:41:23.827760 [info] Listening to udp://[::]:53
2021/12/15 20:41:23.827772 [info] Creating a TCP server socket
2021/12/15 20:41:23.827827 [info] Listening to tcp://[::]:53
2021/12/15 20:41:23.827972 [info] Entering the UDP listener loop on [::]:53
2021/12/15 20:41:23.828031 [info] Entering the tcp listener loop on [::]:53

2021/12/15 20:43:12.455941 [info] upstream "https://1.1.1.1/dns-query" fails to exchange: couldn't communicate with upstream: couldn't do a GET request to 'https://1.1.1.1:443/dns-query', cause: Get "https://1.1.1.1:443/dns-query?dns=89MBAAABAAAAAAAAE2dvb2dsZS1wdWJsaWMtZG5zLWEGZ29vZ2xlA2NvbQAAAQAB": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2021/12/15 20:43:22.456718 [info] upstream "94.140.14.140" fails to exchange: couldn't communicate with upstream: read udp 172.17.0.2:44658->94.140.14.140:53: i/o timeout
2021/12/15 20:43:32.457032 [info] upstream "94.140.14.14" fails to exchange: couldn't communicate with upstream: read udp 172.17.0.2:53596->94.140.14.14:53: i/o timeout

Is it normal that the DNS server seems to only listen on IPv6?

[Lorac]

After googling a bunch, it looks like a lot of router doesn't like having a DNS server in the LAN. And my model might be one of them. The workaround for that would be to use the AdGuard Home server as the DHCP.