Networks

Ask something
Discussion Locked

Domain naming

0 helpful
8 replies

by eminent87

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

For a smaller company of 100 or less, is it better to name the domain.local instead of domain.com. I have read somewhere that says it is better now a days to name the internal domain .local instead of the registered .com or .net since it won't conflict with your Internet domain name. It is also better for networking reasons as well. Is this true?

8 replies

by curlergirl

I have done it both ways, and I honestly don't see the point of adding .local to the domain name. I think it's one of those things that Microsoft recommends to avoid people getting confused between their internal DNS and external DNS zones. The only tricky thing about configuring a local zone using the public domain name (i.e., the ".com" or ".net", etc.) is that you have to be sure that your DNS server is not configured as a root server. This is the little "gotcha" that using the .local designation would get around. All I do is remove the root indicator in DNS after I've created the zone, and I've never had any problems using the public domain name internally. If anyone else seeing this post has a real-life rationale for using the .local designation, I'd really like to hear it.

Hope this helps!

by cg it

As synergy pointed out, there really isn't any advantage networking wise in using the .local extension than a .com/net/org/ except with DNS. There are security ideas [though I've yet to see a paper on it] where if your corporate network is an extension that is not a public root such as .com/net/info/org etc

by rhantson

Security... that's my best answer to why you would want to use the .local extension to the network instead of using the public domain name for your company. Especially in an organization that contains less than 100.

At the uppermost, it's relatively a question of preference, you'll find many admins stay away from the .local extension all they can, but there have been no problems in my past use of it. In fact, I've found that it helps keep things a little more secure on the internal end of things without mucking up the public domain.

Besides, it's a great way to hide every DNS entry on your network of every local workstation and non-public server to the general public...

by sonicclang

If it were up to me, I'd keep the .com or .local out of the domain name. Whoever originally set up the domain where I work put .com after the name and we had major problems with our mail server because of it.

by parthiv_13

Its nothing like you should put .Local or .Com or else. Its only for byforgetion of intraetwork and internet.

And there is nothing for Networking reasons.

This discussion is closed to new replies.