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

Tech-Archive recommends: Fix windows errors by optimizing your registry

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

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

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

"Danny Sanders" <Danny.Sanders@xxxxxxxxxxxxxxxxx> wrote in message
news:eVWa5YmBGHA.1028@xxxxxxxxxxxxxxxxxxxxxxx
>> 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
>
> "Trust No One®" <dana.scully@xxxxxxxx> wrote in message
> news:40tlhqF1c938sU1@xxxxxxxxxxxxxxxxx
>> 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
>> --
>> Peter <X-Files Fan>
>> Please Note: Emailed replies cc'd / bcc'd , containing HTML or
>> attachments
>> auto-binned as spam
>>
>>
>
>


.

Relevant Pages