Client settings - Identifier with IPv6(fe80::) can`t use the upstream dns settings.

AdguardTeam / AdGuardHome

Network-wide ads & trackers blocking DNS server

https://adguard.com/adguard-home/overview.html

GNU General Public License v3.0

25.74k stars 1.85k forks source link

Client settings - Identifier with IPv6(fe80::) can`t use the upstream dns settings. #6872

Open whatagoodboy opened 8 months ago

whatagoodboy commented 8 months ago

Prerequisites

[x] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to report a bug and not ask a question or ask for help
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Synology DSM 7.2, AMD64 (aka x86_64)

Installation

Docker

Setup

On one machine

AdGuard Home version

v0.108.0-b.54

Action

Client settings - Identifier settings: ipv4 can use the upstream dns, but ipv6 use the global settings upstream dns.

Expected result

ipv6 can use the Client settings upstream dns

Actual result

ths is the result

Additional information and/or screenshots

No response

overwatch3560 commented 8 months ago

@whatagoodboy have you added any ipv6 dns upstream servers in the dns settings?

whatagoodboy commented 8 months ago

@whatagoodboy have you added any ipv6 dns upstream servers in the dns settings?

@overwatch3560 yes, I added ipv6 dns (include domains and ip format), it still goes to the global dns.

ghost commented 8 months ago

Are you using AGH DHCP Server, or another DHCP server?

whatagoodboy commented 8 months ago

Are you using AGH DHCP Server, or another DHCP server?

@jslawler-gh I am using another dhcp server, and the dns set to AGH server. My ipv4 clients settings goes to the correct dns. Only ipv6 clients settings goes wrong.

ghost commented 8 months ago

Thank you for confirming. Which OS are you hosting your AGH server on?

whatagoodboy commented 8 months ago

Thank you for confirming. Which OS are you hosting your AGH server on?

@jslawler-gh Synology DSM7.2 - Docker , network=host

ghost commented 8 months ago

@whatagoodboy thanks. I'll be as I won't be able to test that exact setup, I'll be shooting in the dark a bit here.

To determine where the issue is: Are you able to reproduce this outside of a containerised environment? Also, can you check your IPv6 setup on the DSM?

whatagoodboy commented 8 months ago

@whatagoodboy thanks. I'll be as I won't be able to test that exact setup, I'll be shooting in the dark a bit here.

To determine where the issue is: Are you able to reproduce this outside of a containerised environment? Also, can you check your IPv6 setup on the DSM?

@jslawler-gh Thank you for your reply. ADG works fine with ipv6 in docker, as the second screenshot provided at the beginning shows, it is using global ipv6 dns (https://[2606:4700:4700::1001]:443/dns-query), and it already get the correct result. Can you try to have a test use "Client settings" to customize upstream DNS? Does the customized upstream DNS was used correctly by client requests with ipv6 from local link fe80:: in your environment? Sorry for poor English...

rubeo-O commented 1 week ago

I am also seeing this same issue where IPv6 identifiers cannot use custom upstream resolvers. I am running two instances of Adguard Home - one in an LXC and another in Docker.

cashford8 commented 17 hours ago

I also see this issue. My adguard is running as a snap on raspian OS. In addition to it not obeying the upstream DNS settings, the ipv6 client doesn't get any of the other custom settings when you untick "use global settings" in the settings tab - such as safe search options The same client connected via ipv4 works as expected.