4 ms·
Does this mean you (theoretically) can’t name a host "dk" on your local network? That seems bad, (even if naming hosts after TLDs is a bad idea).
by 1f60c 6y ago
Does this mean you (theoretically) can’t name a host "dk" on your local network? That seems bad, (even if naming hosts after TLDs is a bad idea).
- MayeulC 6y agoTechnically, you should be able to have your local host resolve first. To avoid it being resolved and use the TLD instead, use the trailing dot: http://dk./ http://dk./ https://news.ycombinator.com./ https://news.ycombinator.com./ This makes it a FQDN, just like you enter it in your DNS records. Practically, people tend to forget about it, and accessing websites this way sometimes break in unexpected ways when the server doesn't expect the trailing dot in the "host" header. http://www.dns-sd.org./TrailingDotsInDomainNames.html http://www.dns-sd.org./TrailingDotsInDomainNames.html
- kevincox 6y agoYou shouldn't be doing this anyways. There are reserved TLDs for this like .corp https://tools.ietf.org/id/draft-chapin-rfc2606bis-00.html#new https://tools.ietf.org/id/draft-chapin-rfc2606bis-00.html#ne...