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

"Disable resolving of IPv6 addresses" per client basis #7293

Open
3 tasks done
vincejv opened this issue Sep 27, 2024 · 0 comments
Open
3 tasks done

"Disable resolving of IPv6 addresses" per client basis #7293

vincejv opened this issue Sep 27, 2024 · 0 comments

Comments

@vincejv
Copy link

vincejv commented Sep 27, 2024

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to request a feature or enhancement and not ask a question

The problem

Apparently, there are some problematic clients that try to connect to IPv6 addresses using the returned AAAA record through their link local ipv6 address when the DNS resolver returns an AAAA record.

User experience is slow loading of IPv6 enabled websites in clients which are IPv4 only, the client connects to the IPv6 website and waits for the timeout.

The usual setup for adguardhome is for a single network only, but there some niche setups wherein a single adguardhome instance is used for two networks, one for IPv6 dual stack and the other could be an IPv4 exclusive network.

Examples

Proposed solution

Make the setting per client instead of per device.

Alternatives considered and additional information

The current implementation is lacking, as it's global setting, not client basis.
Edit: Was able to figure out the custom filtering rule

*^$dnstype=AAAA,client=172.16.0.128/25,important
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

1 participant