DNS name does not exist 0x0000232B RCODE_NAME_ERROR

[Stibbs]

I am trying to add my new computers to my Active Directory 2003 Std Server
Domain. (The computers are in the list of AD computers - I added them first.)

I get the error is:

The domain name {mydomain} might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
{mydomain}:

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.{mydomain}

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

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

{mydomain}
.. (the root zone)


I checked using the NSLOOKUP and verified that the Domain is contacting. I
do not have any anti-virus software loaded. I have disabled the MS Firewall.

When I do an IPCONFIG /ALL the system shows me that I am picking up and IP
address, Gateway, DNS Server from the DHCP server. Still could not add the
computers to the domain.

I tried to "hard coded" the Internet Protocol (tcp/ip) Propteries but that
did not resolve it.

Any suggestions would be greatly appreciated.

 

[Guest]

Stibbs,

microsoft.public.windows.server.dns

I build servers daily & never came across this exact error message

When I add a machine I put it into the domain as normal

Usually a netbios name slightly differs from the domain name. Example:

MyDomain
MyDomain.admin

When you added it to the domain did it create an 'A' record in DNS (forward
lookup zone)?

Does the server have an associated poiter set?

Is there a reverse lookup zone in DNS?

Is the DNS registered on this server or does it say non-existant domain on
nslookup?

Is primary DNS set to look at itself on the server. Example:

10.36.91.10 <---- IP
255.255.255.0 <--- Subnet Mask
10.36.91.254 <--- Default Gateway

10.36.91.10 <--- Primary DNS


Would like to know more information

 

[Stibbs]

Okay Let me try to answer the questions:
The new computer are not createing A records.

I do not create records in the DNS zone for new computers. I simply add
them to the Active Directory only.

The Computer name is the same on the computer properties as it is in AD

Yes the server has a pointer record in the DNS as well as and A record
Reverse lookup zone does exist in the DNS

Can not anser the "DNS registrer on this Server" - don't know what the
meaning of this question is.

Don't know how to tell if the DNS is set to look at itself.

My domain name on the server is different name for the actual server name
hosting the DNS service.

 

[Guest]

Stibbs,

The DNS server should be looking at itself first. That is what I meant. Are
you using 2 servers as that's what it sounds like to me because you say the
domain name is a different name to the server hosting the DNS

The server's A record should have a pointer too. Douuble-click the A record
& tick the associated pointer box. Did it give you a warning? Is this
pointer staying checked? Double-click again to see if it's still checked

What version of server are you using? Home Server, 2003, 2003 R2, 2008...

What are the client logon times like?

When showing up in DNS what is the qualifying names of the machines?
Example: Machine1.MyDomain.admin or just Machine1?

 

[Stibbs]

I am not using 2 servers as the DNS server. One server with the one domain.
This server does DHCP, DNS, Wins, & AD. The Domain name is 2003Server1 and
the actual server name is Mainoffice.

I double clicked on the A record with the host name (same as parent folder),
IP address of the server and fully qulified domain
2003server1.local.{location} and the tick for associated pointer box was
already checked. I unchecked it, applied, rechecked it and applied.

I did the same process for the server name Mainoffice A record.

Each time I open the A records the tick associated pointer box is checked.

I am using Windows Standard Server 2003 R2. I have two active niche card in
this server.

Computer get registered as Machine1. They are not qualified by the Domain.

Client Logon times are very slow. This problem I have had for a long time.
MS tech told me to load User Profile Hive Clean to correct this. It works
but we still have slow logon.

 

[Stibbs]

When I spoke to MS about the slow logon (5 to 10 minutes) they had me add the
following registry key

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters]
"MaxPacketSize"=dword:00000001

Now the logon are slow but by 30 to 60 seconds instead of minutes.

 

[Drew210]

I am trying to add my new computers to my Active Directory 2003 Std Server
Domain. (The computers are in the list of AD computers - I added them first.)

I get the error is:

The domain name {mydomain} might be a NetBIOS domain name.  If this is the
case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
{mydomain}:

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.{mydomain}

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

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

{mydomain}
. (the root zone)

I checked using the NSLOOKUP and verified that the Domain is contacting.  I
do not have any anti-virus software loaded.  I have disabled the MS Firewall.

When I do an IPCONFIG /ALL the system shows me that I am picking up and IP
address, Gateway, DNS Server from the DHCP server.  Still could not addthe
computers to the domain.

I tried to "hard coded" the Internet Protocol (tcp/ip) Propteries but that
did not resolve it.

Any suggestions would be greatly appreciated.

First, are all the computers experiencing a slow logon?
If so turn on user profile logging http://support.microsoft.com/kb/221833
I also think your DNS is misconfigured for the domain, slow logons
only occur when the dns server can fine the domain, install the server
2003 support tools and run dcdiag and netdiag to repair DNS.
Hope this helps

 

[Stibbs]

Thank you for the help. Could you assist me in deciphering the results? I
have listed my warning below.

My results after runing netdiag /fix showed this:

First set of IP Tests:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : MAINOFFICE.2003Server1.Local.FortFrances
IP Address . . . . . . . . : 142.141.147.135
Subnet Mask. . . . . . . . : 255.255.255.128
Default Gateway. . . . . . : 142.141.147.137
Primary WINS Server. . . . : 142.141.147.135
Dns Servers. . . . . . . . : 142.141.147.135
192.75.156.245
209.91.128.10
209.91.128.11


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

Second set of IP Tests:
Adapter : Local Area Connection 2

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : MAINOFFICE.Mainoffice
IP Address . . . . . . . . : 142.141.147.135
Subnet Mask. . . . . . . . : 255.255.255.128
Default Gateway. . . . . . : 142.141.147.137
Dns Servers. . . . . . . . : 142.141.147.135
192.75.156.245
209.91.128.10
209.91.128.11


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.


The results after running dcdiag /fix shows this:

Starting test: systemlog
An Error Event occured. EventID: 0xC00010DF
Time Generated: 05/07/2009 09:07:24
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC00010DF
Time Generated: 05/07/2009 09:31:37
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC00010DF
Time Generated: 05/07/2009 09:49:17
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC00010DF
Time Generated: 05/07/2009 09:49:32
(Event String could not be retrieved)
......................... MAINOFFICE failed test systemlog


Second Set of IP Tests:
NETBT Name Test Passed
Warning: At Least one of the <00> "workstation service", <03> "messager
service", <20> "WINS" names is missing