P
PT
I ran across this while working on a network for one of my
new clients. It appears that the AD domain was created
without a root domain extension. For instance, instead of
calling the AD domain "some_domain.edu", it was simply
called "some_domain".
My question is, does this create a "corrupt" AD domain?
Is it a good idea to do this? What problems, if any,
could arise by naming an AD domain this way? Doesn't this
mis-naming create "illegal" FQDN's?
I ask this because I am seeing all sorts of DNS related
issues in this domain with nothing being able to
dynamically register with the DNS servers, not being able
to resolve a DC, etc. The FQDN's of the machines that do
resolve correctly are showing up
as "machine1.some_domain." with this trailing period.
Anyone ever see anything like this?
Thanks,
-PT
BTW: Please post responses here as my posted e-mail
address is not real.
new clients. It appears that the AD domain was created
without a root domain extension. For instance, instead of
calling the AD domain "some_domain.edu", it was simply
called "some_domain".
My question is, does this create a "corrupt" AD domain?
Is it a good idea to do this? What problems, if any,
could arise by naming an AD domain this way? Doesn't this
mis-naming create "illegal" FQDN's?
I ask this because I am seeing all sorts of DNS related
issues in this domain with nothing being able to
dynamically register with the DNS servers, not being able
to resolve a DC, etc. The FQDN's of the machines that do
resolve correctly are showing up
as "machine1.some_domain." with this trailing period.
Anyone ever see anything like this?
Thanks,
-PT
BTW: Please post responses here as my posted e-mail
address is not real.