Domain name conflict

[MSCS_LCS]

I have created a AD domain and named it as
test.cov.xx.yy.com. I have installed the DNS server on the
same AD box. It looks like there is another domain already
with the name test. However, when I installed AD, I did
not get any errors regarding the existance of the other
domain. Some people here have concern that having the same
domain name is a problem. Maybe having unique domain name
is probably a better practice but do you think we should
face problems

 

[Herb Martin]

I have created a AD domain and named it as
test.cov.xx.yy.com. I have installed the DNS server on the
same AD box. It looks like there is another domain already
with the name test. However, when I installed AD, I did
not get any errors regarding the existance of the other
domain.

Do you mean "it looks like" another DNS name or an AD domain?

DCPromo will only claim about another AD domain, and only
if that domain is either in the same forest or if it has the same
NetBIOS name and is locally resovlable.

If those names above are real then do you own yy.com?
Or are you delegated ownership of test.cov.xx.yy.com from
those owners? (If that is a made up name then the question
still applies to the actual name.)

Some people here have concern that having the same
domain name is a problem. Maybe having unique domain name
is probably a better practice but do you think we should
face problems

Correct. You should never use the same names within the
same name space. If you want private name you can safely
use things like .local and only have to ensure that no one
else in your local networks is using the same subdomain/zone.

 

[Guest]

Having two domains with the same DNS name in the forest should not occur.
In a seperate forest scenario, you will see some conficts. Most likely
users/computers looking for that domain will receive inconsistent DNS info
depending on which domain DNS server replies to them.
A best practice would be to use different names to prevent confusion and DNS
conflicts.