DCPromo Not working Netdiag error RCODE_SERVER_FAILURE

[Guest]

Our Dns servers are not single-layer so the kb article on this doesn't apply.
When I dcpromo a child server with a dns server at the remote site that is
authoritative for child zone that I am putting this server into I get the no
dns server can be found would you like to install one at this time message
through the wizard.

Our Dns servers are Third Party and I have that vendor involved in this
issues as well.

Doing nslookup on the server to be promo'd and querytype=ns I get a response
back with a server name that does not exist and is none pingable. SOA
records the same.

So My question is when you do the dcpromo and get to that portion of the
wizard is it not using the primary dns entry in the TCP/IP setting and
actually looking for the SOA and NS of the zone. If this is the case then I
need to fix the records. Which I need to fix anyways. But we have a very
lengthy change control process and this would take a few weeks. Looking for
some answers as to how DCpromo starts the registration process in DNS.

 

[Tim Springston [MSFT]]

Hi Jerry-

The DCPROMO code is simply checking the availability and accesibility of a
DNS server for the namespace. Most commercial DNS servers do not allow
dynamic registration for DNS records.

For a domain controller to advertise itself properly to clients and other
domain controllers for the services it provides it must have service
specific SRV DNS records (plus a host record) on the DNS server which hosts
the namespace. If it cannot dynamically register those records then they
must be manually added. It sounds like you have a change control process
for that in place.

In situations where your environment does not allow dynamic registration as
yours doesn't you can safely bypass the 'install DNS now' dialogue during
DCPROMO.

Unfortunately, your domain controller promotion will not complete until you
have the needed DNS records in place and accesible to the clients and
servers that need them.

Here's some doumentation on the records needed. Please repost if you have
additional questions or concerns.

Troubleshooting Common Active Directory Setup Issues in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;260371

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/kb/237675/EN-US/

and finally the article below. Although it specifcally mentions BIND
interopability the information in it is useful, particularly if you need a
list of the needed SRV records the server wants to register (located in the
NETLOGON.DNS file):

Integrating Windows 2000 DNS into an existing BIND or Windows NT 4.0-based
DNS namespace
http://support.microsoft.com/default.aspx?scid=kb;en-us;255913
--

Tim Springston
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.