Any benefits of use a .local for internal vs. your external .com?

  • Thread starter Thread starter Jeremy Stevens
  • Start date Start date
J

Jeremy Stevens

I am setting up a new windows domain and we have several registered names.
Is there any benefit of using the .local for this? I am new to this one and
we like to know any input.

Thank you.

Jeremy
 
I am setting up a new windows domain and we have several registered names.
Is there any benefit of using the .local for this? I am new to this one and
we like to know any input.

I always use .lan or .local for non-public systems. This means that I
don't have to worry about PUBLIC DNS issues and I don't have to worry
about outsiders registering the names that I've picked. I choose .lan
more than .local.
 
Jeremy said:
I am setting up a new windows domain and we have several registered
names. Is there any benefit of using the .local for this? I am new to
this one and we like to know any input.

Thank you.

Jeremy

You can use only one name internally anyway, and .local or .lan is one
option to ensure that your internal DNS never has any issues when clients
want to see resources on the real domain.com domain. If you have any Macs,
use .lan instead of .local. You can also set up your AD domain as
internal.realdomain.com as long as that doesn't exist on the Internet....
 
It is just logical. Your AD Domain name is not your Public Internet Domain
and vice-versa. They are two different things and they need to be
distinguishable. The only hting they have in common is they are called
"domains", beyond that they don't even exist for the same reason.

When people use the same name for both, the *right* way to handle it is by
using Split-DNS. There are other ways to "fudge" it, but the proper way is
Split-DNS. Here's an article on the,...read how much fun it is to work with.

[Those are underscores, not spaces between the words]
You Need to Create a Split DNS!
http://www.isaserver.org/tutorials/You_Need_to_Create_a_Split_DNS.html
 
Back
Top