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

Is NXDomain really a failure #78

Open
fl1ger opened this issue Nov 21, 2019 · 3 comments
Open

Is NXDomain really a failure #78

fl1ger opened this issue Nov 21, 2019 · 3 comments
Assignees
Labels
ready for text Ready to be written up

Comments

@fl1ger
Copy link
Collaborator

fl1ger commented Nov 21, 2019

This is about the hostname resolution algorithm (3.3). If we think NXDomain is a failure which it is not in DNS then we will leak this name to all further resolvers we try. If we believe that for the enterprise case have a PVD from the network with the private domain that continuing the resolution when getting an NXDomain is the wrong thing from a privacy perspective.

@tfpauly
Copy link
Owner

tfpauly commented Nov 21, 2019

Please note that for VPN use cases or internal domains, we specify that fallback must not be done:

1. An Exclusive Direct Resolver, such as a resolver provisioned by a VPN, with domain rules that include the hostname being resolved. If the resolution fails, the connection will fail. See Section 3.2 and Section 6.

Perhaps it makes sense to do the same for the case of local authority, i.e. (2):

2. A Direct Resolver, such as a local router, with domain rules that are known to be authoritative for the domain containing the hostname. If the resolution fails, the connection will try the next resolver configuration based on this list.

Changing to if the resolution fails, the connection will fail.

@fl1ger
Copy link
Collaborator Author

fl1ger commented Nov 21, 2019

Yeah that is better. If we say NXDomain is a failure should we not also say the same about NoError/NoData? I guess happy eyeballs will ask AAAA and A, so getting that answer will not be uncommon.

@tfpauly tfpauly self-assigned this Nov 21, 2019
@tfpauly tfpauly added the ready for text Ready to be written up label Nov 21, 2019
@tfpauly
Copy link
Owner

tfpauly commented Nov 21, 2019

Yes, we should also mention that NoError/NoData applies the same way.

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

No branches or pull requests

2 participants