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

Discard custom IP range results based on IP-CIDR #6998

Open
3 tasks done
1000oaks opened this issue May 15, 2024 · 0 comments
Open
3 tasks done

Discard custom IP range results based on IP-CIDR #6998

1000oaks opened this issue May 15, 2024 · 0 comments

Comments

@1000oaks
Copy link

1000oaks commented May 15, 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

My IPv4 and IPv6 are from two different operators. Typically, IPv6 is better but there are some exceptions.

For specific IPv6 CIDR Ranges such as 2001:41b8::/32, 2a04:4e42::/32, etc. My IPv6 network is worse than IPv4 in QoS and speed (some times 10x slower in speed or latency) for certain domains in my network. Thus I want to exclude DNS results whose AAAA is in this range.

For example, if example.com has a A record to 1.2.3.4 and AAAA record to 2001:41b8::313, when Chrome queries, AdGuard could only return 1.2.3.4. (Do not let Chrome "know" AAAA results since I want to exclude this specific IP/CIDR range for AAAA.)

Proposed solution

Provide a special field such as ip_cidr_exclusion for users to exclude specific IP/CIDRs when DNS queries.

For example, if example.org resolves to 1.2.3.4 and 5.6.7.8 and I exclude 5.6.7.8/32, then Chrome would only know 1.2.3.4.

Alternatives considered and additional information

I read the docs and discussions; it seems that this feature does not exist. I apologize for my any possible mistakes.

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