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

Jump to bottom

net: builtin dns stub resolver doesn't take care of domain option in resolv.conf #8631

Closed
mikioh opened this issue Sep 3, 2014 · 1 comment
Closed

net: builtin dns stub resolver doesn't take care of domain option in resolv.conf #8631

mikioh opened this issue Sep 3, 2014 · 1 comment
Labels
FrozenDueToAge

Comments

@mikioh
Copy link
Contributor

mikioh commented Sep 3, 2014 

In the review of CL 140040043 iant said that: 

func dnsReadConfig(...) {
switch f[0] {
case "domain": // set search path to just this domain

This comment is no longer accurate.  Now, if there are multiple domain entries in
resolv.conf, we will search all of them.  Actually, I think the comment may be right and
the code wrong.  According to "man resolv.conf" on GNU/Linux "The domain
and search keywords are mutually exclusive.   If  more  than one instance of these
keywords is present, the last instance wins."
@mikioh
Copy link
Contributor Author

mikioh commented Sep 4, 2014

Comment 2:

never mind,  i misunderstood the behavior of de facto dns stub resolvers.
dnsmasq+resolvconf makes me mad.

Status changed to Invalid.

@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mikioh @gopherbot