DNS and Backup Domain Controller

[Greg]

We have upgraded our first NT server to Windows 2003 (Active Directory and
DNS) and are in the process of upgrading the NT BDC. The upgrade to Active
directory failed due to the inability to access the domain name
xxx.xxx.xxx.xxx. The Upgraded BDC recognises the old format NT domain name
XXXXXXXX but not the full DNS name.

When we run DCPROMO we get the following error

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
GMSN.UK.EDS.COM:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.GMSN.UK.EDS.COM

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the domain
are not registered in DNS. These records are registered with a DNS server
automatically when a domain controller is added to a domain. They are updated
by the domain controller at set intervals. This computer is configured to use
DNS servers with following IP addresses:

192.85.18.6 - Existing DNS server
206.122.76.5 - NEW WINDOWS 2003 Domain Controller

- One or more of the following zones do not include delegation to its child
zone:

GMSN.UK.EDS.COM
UK.EDS.COM
EDS.COM
COM
.. (the root zone)

For information about correcting this problem, click Help.

Any help would be appreciated

[Danny Sanders]

You need to point the new DC to the DNS server that holds the SRV records
for your domain in the properties of TCP/IP under the DNS tab. It should
point to this server ONLY. From your description it shouild be your first
server. Your first server MUST be pointed to itself in the properties of
TCP/IP under the DNS tab ONLY. Pointing your DNS server to itself will allow
the server to register the SRV records, the second server is looking for,
during logon.

See:
Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default...b;en-us;825036

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default...b;en-us;237675

For internet access see:

How to configure DNS for Internet access in Windows Server 2003

http://support.microsoft.com/default...b;en-us;323380

[Greg]

Danny, I followed your instructions but I am still having problems. I
downloaded DCDIAG and the following error is reported.

Testing server: Default-First-Site-Name\GMSN0006
Starting test: Connectivity
* Active Directory LDAP Services Check
GMSN0006's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(959eb256-8a2d-48b9-89e1-5370b07459a7._msdcs.GMSN.UK.EDS.COM) couldn't be
resolved, the server name
(gmsn0006.GMSN.UK.EDS.COM) resolved to the IP address
(206.122.76.5) and was pingable. Check that the IP
address is registered correctly
with the DNS server.
......................... GMSN0006 failed test Connectivity

[eiger3970]

I have the same problem and the client pc has the dns pointed directly to the server's IP address.

All the configuration seems correct, so I'm not sure?

Here's the error message that comes up after I enter the Domain for the Computer Name/Domain Changes on the client pc.

Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "frickfinance.local":

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.frickfinance.local

Common causes of this error include the following:

- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

8.8.8.8
192.168.1.105

- One or more of the following zones do not include delegation to its child zone:

xxxxxxxxxxxx.local
local
. (the root zone)

[Solaris]

Networking for Small Business Server 2000, Microsoft recommends that you use the local IP address of DNS server on all client computers. To arrange Windows XP to use Small Business Server 2000 DNS server, follow these steps:

1. In Windows XP, click Start, and then click Control Panel.
2. If Control Panel is in Category view, click Switch to Classic View.
3. Double-click Network Connections.
4. Click the right mouse button on the Local Area Connection icon and then click Properties.
5. Click Internet Protocol (TCP / IP), and then click Properties.
6. Use the following DNS server addresses, type the internal IP address of Small Business Server 2000, and then click OK twice.

If this is also not working, then try to remove software from third-party firewall.