Skip to content

isDomainName in dnsclient does not do what its name suggest #1168

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

Closed
gopherbot opened this issue Oct 6, 2010 · 1 comment
Closed

isDomainName in dnsclient does not do what its name suggest #1168

gopherbot opened this issue Oct 6, 2010 · 1 comment

Comments

@gopherbot
Copy link
Contributor

by bortzmeyer:

Which operating system are you using?

Debian "squeeze"

Which revision are you using?  (hg identify)

9b116c4a5f91 tip

Please provide any additional information below.

The function isDomainName actually check that its argument is a valid HOST name, not
that it is a valid DOMAIN name. (URLs use host names, for instance, but not all
protocols do. See RFC 2181, section 11, for a discussion of the difference) Legitimate
domain names like _jabber._tcp.gmail.com yield false.

This is related to bug #1167 but it seems there is no way in the bug tracker to reopen a
closed bug.
@rsc
Copy link
Contributor

rsc commented Oct 6, 2010

Comment 1:

Status changed to Duplicate.

Merged into issue #1167.

@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants