Use of non-registered domain suffixes in AD domain names?

hi everyone,

i'm interested in thoughts of forum on use of non-registered domain suffixes (.local .priv etc) in active directory domain names.

does use strategy in large implementations containing exchange instance? have come acfross gotchas made wish hadn't?

after digging found technet article states rather tersely "the use of non-registered domain suffixes not recommended". article not expand on why (apparently) microsoft policy. curiously though i've seen odd references around microsoft site using fictional forest contoso.msft  :)

so - run major problems if use non-registered suffix in ad name? understand .local not recommend is not strictly "non registered".

 

hello,

thank post here.

i believe read flowing lines technet document on how plan dns namespace:

active directory domains named dns names. when choosing dns names use active directory domains, start registered dns domain name suffix organization has reserved use on internet, such microsoft.com , combine name either geographical or divisional names used in organization form full names active directory domains.

namespace planning dns--->dns namespace planning active directory

http://technet.microsoft.com/en-us/library/cc759036(ws.10).aspx

there not major problems if have *.local (not registered) ad domain name. *.local , subdomain.registered_doamin.com ad domain both. 1 thing should avoid having identical external , ad domain name.

Windows Server  >  Directory Services