starred/AdGuardHome

Fork 0

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

AdGuard tries IPv6 when there is no IPv6 connectivity and thus fails #3523

New issue

Open

opened 2026-03-04 03:48:01 -05:00 by deekerman · 4 comments

deekerman commented

2026-03-04 03:48:01 -05:00

Owner

Originally created by @JsBergbau on GitHub (Mar 2, 2022).

Originally assigned to: @ainar-g on GitHub.

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:
- AdGuard Home, version v0.107.4
How did you install AdGuard Home:
- via curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v
How did you setup DNS configuration:
default, see below
If it's a router or IoT, please write device model:
CPU architecture:
Operating system and version:

Raspberry PI Debian Bullseye

Expected Behavior

AdGuard is able to resolve DNS in the default configuration.

Actual Behavior

AdGuard doesn't resolve DNS, it can't because it tries to connect via IPv6, but there is no IPv6 connectivity.

Screenshots

AdGuard Home error log states

2022/03/02 22:19:30.347468 [error] POST /control/version.json: Couldn't get version check json from https://static.adguard.com/adguardhome/release/version.json: *fmt.wrapError updater: HTTP GET https://static.adguard.com/adguardhome/release/version.json: Get "https://static.adguard.com/adguardhome/release/version.json": requesting https://dns10.quad9.net:443/dns-query: Get "https://dns10.quad9.net:443/dns-query?dns=QJ0BAAABAAAAAAAABnN0YXRpYwdhZGd1YXJkA2NvbQAAAQAB": all dialers failed: 2 errors: "dial tcp [2620:fe::10]:443: connect: network is unreachable", "dial tcp [2620:fe::fe:10]:443: connect: network is unreachable"

Screenshot:

Additional Information

I've changed the default DNS Resolver from https://dns10.quad9.net/dns-query to tls://dns.adguard.com and now it works. Obviously it also tried to connect to the DoH resolver via IPv6 which also fails.
It is probably related to this issue https://github.com/AdguardTeam/AdGuardHome/issues/1104

For me this issue is done. I know how to handle it. I've opened it so that less experienced users don't run into this problem and then don't know what to do.

I'd like to say that I'm currently using stubby with dnsmasq as DNS-Cache and AdGuard Home is so much better. It is much easier to setup and also has a very nice Webinterface which gives stats and makes maintenance much easier. Thank you very much for providing this great software as OpenSource Software and also for using efficient Go language.

Originally created by @JsBergbau on GitHub (Mar 2, 2022). Originally assigned to: @ainar-g on GitHub. 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:** *  * AdGuard Home, version v0.107.4 * **How did you install AdGuard Home:** *  * via `curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v` * **How did you setup DNS configuration:** default, see below * **If it's a router or IoT, please write device model:** *  * **CPU architecture:** *  * **Operating system and version:** *  Raspberry PI Debian Bullseye ### Expected Behavior  AdGuard is able to resolve DNS in the default configuration. ### Actual Behavior  AdGuard doesn't resolve DNS, it can't because it tries to connect via IPv6, but there is no IPv6 connectivity. ### Screenshots  AdGuard Home error log states ``` 2022/03/02 22:19:30.347468 [error] POST /control/version.json: Couldn't get version check json from https://static.adguard.com/adguardhome/release/version.json: *fmt.wrapError updater: HTTP GET https://static.adguard.com/adguardhome/release/version.json: Get "https://static.adguard.com/adguardhome/release/version.json": requesting https://dns10.quad9.net:443/dns-query: Get "https://dns10.quad9.net:443/dns-query?dns=QJ0BAAABAAAAAAAABnN0YXRpYwdhZGd1YXJkA2NvbQAAAQAB": all dialers failed: 2 errors: "dial tcp [2620:fe::10]:443: connect: network is unreachable", "dial tcp [2620:fe::fe:10]:443: connect: network is unreachable" ``` <details><summary>Screenshot:</summary>  </details> ### Additional Information I've changed the default DNS Resolver from `https://dns10.quad9.net/dns-query` to `tls://dns.adguard.com` and now it works. Obviously it also tried to connect to the DoH resolver via IPv6 which also fails. It is probably related to this issue https://github.com/AdguardTeam/AdGuardHome/issues/1104 For me this issue is done. I know how to handle it. I've opened it so that less experienced users don't run into this problem and then don't know what to do. I'd like to say that I'm currently using stubby with dnsmasq as DNS-Cache and AdGuard Home is so much better. It is much easier to setup and also has a very nice Webinterface which gives stats and makes maintenance much easier. Thank you very much for providing this great software as OpenSource Software and also for using efficient Go language.

deekerman added the

needs investigation

label

2026-03-04 03:48:01 -05:00

deekerman commented

2026-03-04 03:48:13 -05:00

Author

Owner

@jumpsmm7 commented on GitHub (Mar 3, 2022):

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.
* [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:**
  
  * 
  * AdGuard Home, version v0.107.4

* **How did you install AdGuard Home:**
  
  * 
  * via `curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v`

* **How did you setup DNS configuration:**
  default, see below

* **If it's a router or IoT, please write device model:**
  
  *

* **CPU architecture:**
  
  *

* **Operating system and version:**
  
  *
Raspberry PI Debian Bullseye

Expected Behavior

AdGuard is able to resolve DNS in the default configuration.

Actual Behavior

AdGuard doesn't resolve DNS, it can't because it tries to connect via IPv6, but there is no IPv6 connectivity.

Screenshots

AdGuard Home error log states
2022/03/02 22:19:30.347468 [error] POST /control/version.json: Couldn't get version check json from https://static.adguard.com/adguardhome/release/version.json: *fmt.wrapError updater: HTTP GET https://static.adguard.com/adguardhome/release/version.json: Get "https://static.adguard.com/adguardhome/release/version.json": requesting https://dns10.quad9.net:443/dns-query: Get "https://dns10.quad9.net:443/dns-query?dns=QJ0BAAABAAAAAAAABnN0YXRpYwdhZGd1YXJkA2NvbQAAAQAB": all dialers failed: 2 errors: "dial tcp [2620:fe::10]:443: connect: network is unreachable", "dial tcp [2620:fe::fe:10]:443: connect: network is unreachable"
Screenshot:

Additional Information

I've changed the default DNS Resolver from https://dns10.quad9.net/dns-query to tls://dns.adguard.com and now it works. Obviously it also tried to connect to the DoH resolver via IPv6 which also fails. It is probably related to this issue #1104

For me this issue is done. I know how to handle it. I've opened it so that less experienced users don't run into this problem and then don't know what to do.

I'd like to say that I'm currently using stubby with dnsmasq as DNS-Cache and AdGuard Home is so much better. It is much easier to setup and also has a very nice Webinterface which gives stats and makes maintenance much easier. Thank you very much for providing this great software as OpenSource Software and also for using efficient Go language.

You know you are not limited to using https://dns10.quad9.net/dns-query
you could also specify the ipaddress for the ipv4 to ensure it only uses ipv4.

https://someipv4.address/dns-query

But you need to nslookup dns10.quad9.net and only use the ipv4 address specified. valid examples would be

https://149.112.112.10/dns-query

and

https://9.9.9.10/dns-query

@jumpsmm7 commented on GitHub (Mar 3, 2022): > 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:** > > * > * AdGuard Home, version v0.107.4 > > * **How did you install AdGuard Home:** > > * > * via `curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v` > > * **How did you setup DNS configuration:** > default, see below > > * **If it's a router or IoT, please write device model:** > > * > > * **CPU architecture:** > > * > > * **Operating system and version:** > > * > > > Raspberry PI Debian Bullseye > ### Expected Behavior > > AdGuard is able to resolve DNS in the default configuration. > ### Actual Behavior > > AdGuard doesn't resolve DNS, it can't because it tries to connect via IPv6, but there is no IPv6 connectivity. > ### Screenshots > > AdGuard Home error log states > > ``` > 2022/03/02 22:19:30.347468 [error] POST /control/version.json: Couldn't get version check json from https://static.adguard.com/adguardhome/release/version.json: *fmt.wrapError updater: HTTP GET https://static.adguard.com/adguardhome/release/version.json: Get "https://static.adguard.com/adguardhome/release/version.json": requesting https://dns10.quad9.net:443/dns-query: Get "https://dns10.quad9.net:443/dns-query?dns=QJ0BAAABAAAAAAAABnN0YXRpYwdhZGd1YXJkA2NvbQAAAQAB": all dialers failed: 2 errors: "dial tcp [2620:fe::10]:443: connect: network is unreachable", "dial tcp [2620:fe::fe:10]:443: connect: network is unreachable" > ``` > > Screenshot: > ### Additional Information > > I've changed the default DNS Resolver from `https://dns10.quad9.net/dns-query` to `tls://dns.adguard.com` and now it works. Obviously it also tried to connect to the DoH resolver via IPv6 which also fails. It is probably related to this issue #1104 > > For me this issue is done. I know how to handle it. I've opened it so that less experienced users don't run into this problem and then don't know what to do. > > I'd like to say that I'm currently using stubby with dnsmasq as DNS-Cache and AdGuard Home is so much better. It is much easier to setup and also has a very nice Webinterface which gives stats and makes maintenance much easier. Thank you very much for providing this great software as OpenSource Software and also for using efficient Go language. You know you are not limited to using **https://dns10.quad9.net/dns-query** you could also specify the ipaddress for the ipv4 to ensure it only uses ipv4. https://someipv4.address/dns-query But you need to nslookup dns10.quad9.net and only use the ipv4 address specified. valid examples would be **https://149.112.112.10/dns-query** and **https://9.9.9.10/dns-query**

deekerman commented

2026-03-04 03:48:13 -05:00

Author

Owner

@JsBergbau commented on GitHub (Mar 3, 2022):

You know you are not limited to using https://dns10.quad9.net/dns-query

Of course I know and I've changed the server as described. It wanted to hint that in the default configuration there is this problem and so users have trouble using AdGuard and might go away from that great software because it doesn't work out of the box.

@JsBergbau commented on GitHub (Mar 3, 2022): > You know you are not limited to using https://dns10.quad9.net/dns-query Of course I know and I've changed the server as described. It wanted to hint that in the default configuration there is this problem and so users have trouble using AdGuard and might go away from that great software because it doesn't work out of the box.

deekerman commented

2026-03-04 03:48:13 -05:00

Author

Owner

@jumpsmm7 commented on GitHub (Mar 4, 2022):

You know you are not limited to using https://dns10.quad9.net/dns-query

Of course I know and I've changed the server as described. It wanted to hint that in the default configuration there is this problem and so users have trouble using AdGuard and might go away from that great software because it doesn't work out of the box.

I am still able to resolve the IPV6 addresses over IPV4, so I am not sure how this is applicable to all users, but it should be considered if the user has specified to disable AAAA queries under the DNS settings section of AdGuardHome.

@jumpsmm7 commented on GitHub (Mar 4, 2022): > > You know you are not limited to using https://dns10.quad9.net/dns-query > > Of course I know and I've changed the server as described. It wanted to hint that in the default configuration there is this problem and so users have trouble using AdGuard and might go away from that great software because it doesn't work out of the box. I am still able to resolve the IPV6 addresses over IPV4, so I am not sure how this is applicable to all users, but it should be considered if the user has specified to disable AAAA queries under the DNS settings section of AdGuardHome.

deekerman commented

2026-03-04 03:48:13 -05:00

Author

Owner

@JsBergbau commented on GitHub (Jun 13, 2022):

Still an issue

@JsBergbau commented on GitHub (Jun 13, 2022): Still an issue

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#3523

No description provided.

Rows
Columns