Solved

Unable to add a second domain controller to Windows 2003 domain

Posted on 2006-06-19
7
310 Views
Last Modified: 2010-04-18
Pretty sure it is something to do with DNS (I am a little rusty on dns!) Have added some mods to the hosts file to try & help it along the way.....error is as below.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain manchester.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.manchester.local

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

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

manchester.local
local
. (the root zone)

0
Comment
Question by:datafocus
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 16936071
Please verify your TCP/IP settings.  Remember, all members of the domain must point to Windows (internal) DNS servers...and not ISP or router DNS servers...

So, in TCP/IP settings of each machine on your network, make sure the DNS is properly configured

i.e.

DC Server NAme:  DCSERVER1
IP: 10.10.10.5
subnet: 255.255.255.0
gateway: 10.10.10.1
DNS: 10.10.10.5  or 127.0.0.1  (But not pointing to DNS servers other then itself of other Windows DNS...especially not pointing to ISP DNS)
DNS2: <emtpty.>  or to another windows 200x DNS server

CLient name:  Clientmachine1
IP: 10.10.10.51
subnet: 255.255.255.0
gateway: 10.10.10.1
DNS: 10.10.10.5  <--- must be pointing to your inernal windows DNS server(s)
0
 
LVL 11

Expert Comment

by:elbereth21
ID: 16936376
Probably you need to re-register the SRV records of your Domain controller:
first try restarting your Netlogon service, then try running the Windows 2000 tool: netdiag /fix
0
 
LVL 11

Accepted Solution

by:
elbereth21 earned 125 total points
ID: 16936395
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
LVL 22

Expert Comment

by:mcsween
ID: 16936595
Make sure your existing ADC is pointing at itself for DNS then Stop and Start the netlogon service.

Make sure the new server you are trying to promote DNS is pointed at the EXISTING ADC.  After it's promoted you can point the DNS back at itself.
0
 

Author Comment

by:datafocus
ID: 16940733
Hi,

I have double triple checked the dns pointers on adc etc before logging this.... nslookup works fine etc... will have a look at those two articles elbereth21

Thanks,
0
 

Author Comment

by:datafocus
ID: 16940861
Hi Elbereth21,

I just recreated the forward lookup zone & it worked again.

Many thanks... Glad you were barking up the right tree.
0
 
LVL 11

Expert Comment

by:elbereth21
ID: 16940877
Glad I could help.
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question