Any "gotchas" in using "non-internet" domain name suffixes?

[Trust No One®]

Hi Folks,

I notice some AD designs using "non-internet" suffixes such as .local and
..corp in their forest/domain names.

Is there anything to watch out for when using these suffixes or is it
recommended best practices these days?

Any technical papers around ?

tia

 

[Danny Sanders]

Is there anything to watch out for when using these suffixes or is it

recommended best practices these days?

There are tons of thing to look out for when *using* single label domain
names. Tons now and there are sure to be more in the future.

See:
http://support.microsoft.com/kb/300684/en-us

hth
DDS W 2k MVP MCSE

 

[Danny Sanders]

After re reading your post, I don't think I answered your question.

About the only this you would have to worry about is if they made.loc or
..corp registered suffixes.

You can avoid this possibility like so:

Internet domain name is mydomain.com
Make your AD domain name Internal.mydomain.com or AD.mydomain.com or
Corp.mydomainname.com.


hth
DDS W 2k MVP MCSE

 

[Fran]

Personally, I prefer them over public internet names like .com or
..net. I use .local and .corp frequently. It makes it very easy to
distinguish between public and private networks and there is no DNS
management you have to do (creating host records for things like WWW
and SMPT or POP so your internal clients can hit your company's web
site at www.mycorp.com or pop.mycorp.com for mail.)

Of course if you have an intranet and an internet site that must be
available that's a different story.

There are certainly those that disagree and Microsoft recommends
registering all your DNS names (I suppose that's if they're .com or
..net and the such.) no matter what.

-Fran-

 

[Dave Nickason [SBS MVP]]

A probably minor issue - you'll have problems with clients running Mac OS X
if you use .local.