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

Support for an additional EDNS client subnet for AAAA queries #21

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

denisu
Copy link

@denisu denisu commented Dec 7, 2016

It is useful on dual-stack connections with mixed AS-Numbers to specify both an IPv4 and IPv6 EDNS client subnet and use the IPv6 client subnet when asking for AAAA records. In that case, you would put your IPv4 subnet into -gdns:edns and your IPv6 subnet into -gdns:edns6

I am not sure how useful this will be for most users, but it has advantages in my setup. I would like to hear feedback or please feel free to close/ignore this pull request if it is beyond dingos scope.

@Opensourcecommunitydevelopment

Makes Sense, for less configuration, if No subnet specified, google Domain Name Server/Service/Scheme/System guesses which is the nearest for you. Depending On the IP Protocol Version the Query is done !. Having one worker On Internet Protocol Version 4 for A querys and secondary over Internet Protocol Version 6 for AAAA would give the Best results, even On chaning, dynamic or Mobile IPS without the hassle of edit config All the time and restart Dingo Just because endns subnet Setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants