-
Notifications
You must be signed in to change notification settings - Fork 3k
Let the search list have an implicit final top domain entry #10576
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
base: maint
Are you sure you want to change the base?
Let the search list have an implicit final top domain entry #10576
Conversation
CT Test Results 2 files 72 suites 1h 6m 21s ⏱️ For more details on these failures, see this check. Results for commit a55e31b. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts
// Erlang/OTP Github Action Bot |
This is what all OS resolvers we know of does, and it has been on a future improvement list since at least R13B01, in a comment in inet_res.erl. So, when the name to look up has been tried with all domain search list entries, do a final attempt as if the top domain is an invisible last domain search list entry. This only applies to names without a dot (implicit ndots=1), since for names with at least one dot they are tried as absolute names *before* starting with the search list, as before this change.
23b9147 to
2230292
Compare
db92d1e to
bfa8bae
Compare
bfa8bae to
a55e31b
Compare
|
Ready for review. Awaiting, hopefully, comments from issue #10494 reporter..., and from someone with repository write access. |
Closes #10494.
Make the build in DNS resolver
inet_resdo a final request assuming that the given Name to resolve is an absolute name, by having an implicit top domain entry last in the domain search list.