Creating an Active Directory domain without a root domain extension?

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.
 
C

Chai

If the DC is not connected direct to the Internet or host
PC need to access or connect to it over public internet
then the naming of the domain can be anything (like your
case).

To allow dynamic register, make sure the DNS is set to
allow dynamic update!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top