Stop handling a domain if all nameservers don't provide sufficient glue records when they should #417
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Wanted to get a specific review on this since it seems to core logic that affects more than just IPv6 lookups.
The issue that caused me to look into this was trying to get
A
records foresrg.stanford.edu
fromStanford.edu
nameservers over IPv6We can't proceed to look up
dns-01.esrg.stanford.edu
any further, and without anAAAA
record to continue IPv6 iteration, we cannot proceed.Solution
NONEEDEDGLUE
status that is returned if a given name is beneath the current layer (esrg.stanford.edu
is beneathStanford.edu
and the glue doesn't contain a next hop.)iterateOnAuthorities
return this, we'll terminate the iterationTesting
esrg.stanford.edu
lookupipv6 base branch
ipv6-recursive-base
Ensuring this doesn't break known working domains
main
ipv6-recursive-base