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

Printable View

05-09-2008
Agilent

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

Everytime the below error pops up when DNS was queried for the service location (SSRV) resource record that is used to locate a domain controller for domain smallbusiness.local:

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

The query was for the SRV record for _ldap._tcp.dc._msdcs.smallbusiness.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:

24.92.226.41
24.92.226.40

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

smallbusiness.local
local
.. (the root zone)

For information about correcting this problem, click Help.

Any ideas?
05-09-2008
Mr. Boo Bear

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

Could you please explain in more details how your domain is setup exactly and also how do you configure the DNS, AD integrated or primary. You need to also post the ipconfig /all from the server. On which machine are you getting this error? Incase you also have a client issues, then please post also the ipconfig /all from it.
05-09-2008
kattman

Re: "DNS name does not exist."(error code 0x0000232B RCODE_NAME_ERROR)
You can try to run diagnostics against your Active Directory domain. Incase you dont have the support tools installed, then install them from your server install disk. After that you can run dcdiag, netdiag and repadmin in verbose mode:
- DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
- netdiag.exe /v > c:\netdiag.log (On each dc)
- repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
- dnslint /ad /s "ip address of your dc"
08-09-2008
Bon-Z

Can you please tell us whether this machine is a SBS version? If it is not, then do no multihome DCs with different ip addresses. The 2 ip address has to be configured as a forwarder under the DNS server properties in the DNS management console. The only DNS IP addresses that must be defined are those that refer to your AD DNS servers. All the other dns servers should then forward external dns requests to your ISPs dns server.