Cannot add a dc to existing domain

[ron]

I have a domain with one server in it. I have just built a
new server and ran dcpromo. It keeps saying it cannot
resolve the dns of the domain. I can resolve it by
running nslookup so I know it sees it. Any ideas?

Thanks

 

[Herb Martin]

I have a domain with one server in it. I have just built a

new server and ran dcpromo. It keeps saying it cannot
resolve the dns of the domain. I can resolve it by
running nslookup so I know it sees it. Any ideas?

"it sees it" -- Nope.

DNS as used by AD is far more extensive than simple name
lookup -- odds are you don't have DYNAMIC DNS enabled
for the zone that supports this AD domain.

If you do, then perhaps the DC is NOT a client of that DNS
(so isn't registering itself properly.)

Note: Even servers usually need to be name resoloution "clients"
even name servers like DNS and WINS server typically need to
be set as a CLIENT (of themselves usually.)

 

[Danny Sanders]

See the section on adding an additional DC to an existing domain.
HOW TO: Promote and Demote Domain Controllers in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;238369



As Herb mentioned, it is probably DNS related.



hth

DDS W 2k MVP MCSE

 

[John A]

-----Original Message-----
I have a domain with one server in it. I have just built a
new server and ran dcpromo. It keeps saying it cannot
resolve the dns of the domain. I can resolve it by
running nslookup so I know it sees it. Any ideas?

Thanks
.
Check to see if your namespace is correct on your new

server.
If your original server is for example,
server1.microsoft.com your new server should have the same
DNS ie newserver.microsoft.com.
If the namespace is disjointed you're looking at a rebuild
of the new server.

I've seen disjointed namespace problems especially when
the new server is an upgrade from NT4

 

[ron]

I figured it out. The originial DC had its IP address
specified as the primary DNS entry. I made it the local
host 127.0.0.1(this was a trick in itself), then stopped
the DNS client, DNS server and netlogon and then restarted
in that order and that seemed to have corrected it.

Thanks