Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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?
could be anything really, even if you would use yahoo.com or google.com :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...
.local
.lan
.internal
.<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?
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)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.