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

resolv.conf(5) documents glibc implementation behaviour #34

Open
yrro opened this issue May 19, 2023 · 0 comments
Open

resolv.conf(5) documents glibc implementation behaviour #34

yrro opened this issue May 19, 2023 · 0 comments

Comments

@yrro
Copy link

yrro commented May 19, 2023

Of the nameserver keyword, the man page states,

If there are multiple servers, the resolver library queries them in the order listed.

and,

(The algorithm used is to try a name server, and if the query times out, try the next, until out of name servers, then repeat trying all the name servers until a maximum number of retries are made.)

These are implementation details of glibc and relying on this behaviour introduces a number of subtle problems that commonly trip people up.

I think glibc's behaviour should be documented in glibc's documentation, and the text of the man page should be change to something like:

If there are multiple servers, they must all provide the same "view" of the DNS.

and

(Behaviour varies between different resolvers regarding how multiple servers are interpreted.)

Or perhaps the parenthetical remark should be removed altogether.

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

No branches or pull requests

1 participant