disjointed name space

[art]

What
Im doing is replacing my 2k dc with a new dell rack
mount. The AD is not setup right on it. It has a
disjointed namespace and someone tweaked it for ad to
work. I know of the script to run to fix the disjointed
name space but Im not confident that will fix my problem.
As of right now I can not add an additional dc to my
domain using dcpromo because it says it can not find
server. So I was just thinking about recreating the whole
domain with the new server and then moving all clients
over. My dilema is I have an sbs4.0 server and im worried
about losing all my mail boxes. I really would like to
setup another dc in ad and then transfer roles, but im not
confident ad will work after I do that because it is
disjointed right now yet ad still works. I can add new
workstations to the domain I can pull up all AD programs
on the dc but I can not run dcpromo or use the
adminpak.msi programs because it will not connect. Has any
body had experience with this before. Thanks in advance.

 

[Joe Richards [MVP]]

First off, AD will run fine on a disjoint namespace. I am aware of an
environment running some 250,000 users across 400 domain controllers and
thousands of servers and hundreds of thousands of workstations that way.

The question is, why can't it find your your DC. That is a DNS issue, you need
to dive into DNS to make sure it is working correctly. Most likely someone
didn't set up the Zone for the disjoint... I.E. If you have a machine name
machine.somednsname.company.com in a domain of company.com, someone needs to set
up the somednsname zone off the company.com root and set it up to take
registrations.

joe

 

[Guest]

thanks for thre post joe. the server is server.pacbell.net
and the domain is hq.company.com ...there is a zone
called hq.company.com . I dont see a zone for the disjoint
which is server.pacbell.net .....

 

[Joe Richards [MVP]]

Ok, well you will need to create one then and set it up for dynamic registration
or manually insert the HOST record for the DC.

 

[art]

thanks joe, so let me understand...right now i have a
server running ad. the name of the server is hal2000....
the name of the domain is hq.company.com ..........
but the fully qualified domain name of the server is
hal2000.pacbell.net..................................
there is a zone in dns called hq.company.com that has a
running ad, which is working. except for the dns issue...

You are saying to create a new zone for pacbell.net ?

should that be an ad integrated zone?

Let me tell you some of the records that exist in the
current dns zone ....
SOA to Hal2000.pacbell.net
two NS one to hal2000.pacbell.net and one to
hal2000.company.com.......
A record for hal2000 pointing to its ip
WINS pointing to servers ip
RP called admin.

Do you think that running the microsoft script would fix
my dns issue by editing the registry and changing the
domain info?

 

[Joe Richards [MVP]]

Either solution will work to do the new promo. In fact you don't even need the
script, you just need to modify the
hklm\system\currentcontrolset\services\tcpip\parameters\NV Domain registry value
to your new FQDN.

The point is, if you want a disjoint you can have it, if you don't want one you
can revert to not having one. Your choice, it will work either way.

joe