datafocus
asked on
Unable to add a second domain controller to Windows 2003 domain
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.manch
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)
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.manch
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)
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
first try restarting your Netlogon service, then try running the Windows 2000 tool: netdiag /fix
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
ASKER
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,
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,
ASKER
Hi Elbereth21,
I just recreated the forward lookup zone & it worked again.
Many thanks... Glad you were barking up the right tree.
I just recreated the forward lookup zone & it worked again.
Many thanks... Glad you were barking up the right tree.
Glad I could help.
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)