-   Linux - Networking (
-   -   What TLD to use for local network. (

GazL 03-29-2010 11:33 AM

What TLD to use for local network.
As it looks like the number of DNS Top Level Domains are just going to proliferate in the near future, what's your guys views on a good one to use locally on an RFC 1918 private network in order to prevent a future name collision issue?

.local is the most obvious one but as that was stolen by Apple for mDNS/rendezvous use it's probably wise to avoid it now.

What do you guys use? Is there a defacto standard for this?

tredegar 03-29-2010 12:30 PM

AFAIK you can use any names you like on your private LAN, including .local if you so choose.

I just use

No problems after 10yrs :)

djsmiley2k 03-29-2010 12:33 PM

I name mine after myself XXX.Bowers.Net

teebones 03-29-2010 02:18 PM

could be anything really, even if you would use or :P
but.. then you would have a problem, surfing either of them, since they will route to your own machines :P
(dns records and/or wins e.g. hosted locally)

but it's allowed, it can be done.. it your freedom to do so.

But for saveguides...

.<fictional tld here>

is the best way to go, if you would not encounter resolving problems of existing domains you may want to visit.

note: i think you want to use your own dns server for resolving rather than a third party one (e.g. isp dns) right?

GazL 04-01-2010 02:27 PM

I was just curious what people thought best practice was. As far as I can tell, from reading the replies here and other stuff on the subject it looks like there's no one standard that people are adopting (most seem to still be using .local, so I'll just stick with my invented tld and not worry about it until I hit a problem (if I ever do)

Thank you, to those who responded.

suk352 11-20-2013 07:40 AM

.local is not valid for private lans
All of the above comments are incorrect.

It DOES matter what you call your local domain. .local is a reserved name for mDNS and so should be avoided. You may get a delay in resolving a FQDN with .local in it. Technically it would be invalid for use on a private lan.

Names like .lan or .home are better but the best practice would be to use a genuine registered domain name for both inside and outside your network. Reason being should the domain every become a real internet domain, you would end up in a lot of trouble.

cliffordw 01-09-2014 03:22 AM

I know this is an old thread, but thought I'd add my 2c too....

Looking at RFC6761 (paragraph 6.2), it would seem that .test would be the best choice if you want to avoid the possibility of future conflicts, and don't want to use a registered domain name.

Any thoughts on / experience with this?

All times are GMT -5. The time now is 03:51 AM.