Primary Authorative DNS Server

My primary domain controllers in our parent domain don't seem to be replicating as they report "failed due to a DNS lookupup failure". NS Lookup seems to be working fine. But when I run NetDiag i get the following error:

DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'pdc.domain.'. [RCODE_SERVER_FAILURE]
            The name 'pdc.domain.' may not be registered in DNS.
       [FATAL] File \config\netlogon.dns contains invalid DNS entries.    [FATAL] No DNS servers have the DNS records for this DC registered.

Looked into the netlogon.dns file, and at first sight there does not seem to be anything amiss. (obviuosly is!) usual active directory entries pronouncing service location etc.

Help! Not come accross this before, and as its stopping users logging on correctly and causing RPC failures this is top priority for us!
chairborne1Asked:
Who is Participating?
 
oBdAConnect With a Mentor Commented:
If you didn't change the domain name information when posting here, the main problem is that you seem to have a single-label DNS name; Windows can't handle this by default:

Clients cannot dynamically register DNS records in a single-label forward lookup zone
http://support.microsoft.com/?kbid=826743

Information about configuring Windows for domains with single-label DNS names
http://support.microsoft.com/?kbid=300684

Did you create the AD domain recently, that is, would it still be possible to re-create it? It might make things easier in the future.
Here's a bit more information about domain naming (in general, don't mind the "Small Business Server" part):
The Domain Name System name recommendations for Small Business Server 2000 and Windows Small Business Server 2003
http://support.microsoft.com/?kbid=296250
0
 
chairborne1Author Commented:
Below error report for assistance / information

Event Type:      Warning
Event Source:      NTDS KCC
Event Category:      Knowledge Consistency Checker
Event ID:      1265
Date:            29/11/2004
Time:            10:46:19
User:            N/A
Computer:      PDC
Description:
The attempt to establish a replication link with parameters
 
 Partition: CN=Configuration,DC=domain
 Source DSA DN: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain
 Source DSA Address: 99372313-0df4-4996-af24-635d49725152._msdcs.domain
 Inter-site Transport (if any):
 
 failed with the following status:
 
 The DSA operation is unable to proceed because of a DNS lookup failure.
 
 The record data is the status code.  This operation will be retried.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4c 21 00 00               L!..    
0
 
cfairleyCommented:
Hello chairborne1,

This will probably take the help of several experts, but we can start with this link:

http://www.jsifaq.com/subg/TIP3300/rh3370.htm

Thanks,
cfairley
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
cfairleyCommented:
Also, here is one of my favorite links regarding replication errors.

How do I troubleshoot intra-site replication failure?
http://www.jsifaq.com/SUBM/tip6300/rh6356.htm
0
 
chairborne1Author Commented:
Thanks for the links: Scouring as we speak.

The domain is about 2 1/2 years old and has run ok up until recently. The only think that has changed is the promotion of s second server to a DC. Up until this point it was running as a single server domain. I split out the infrastructure and GC roles, but this seems to not had any effect.
0
 
chairborne1Author Commented:
Both the child domains seem to be replicating correctly, (two servers each per domain) and the trusts are fine.

The single label thing i'm persuing at the mo, as this is the root domain of our forest, and is a single label as you say.
0
 
chairborne1Author Commented:
And after checking one of your links which points to dynamic registration, found out that single labels changed at SP4

We have installed SP 4, as recommended by one of our sw suppliers !@$£* !!
0
 
Antknee869Commented:
What are the DNS server settings in the TCP/IP settings on the servers? Are each pointing to thmeselves as Primary DNS? How many DNS servers do you have for your domains?
Try pointing each server's  Primary DNS setting to one DNS server. Allow time for replication, maybe overnite and see what happens.
0
 
chairborne1Author Commented:
Cheers oBdA!

Entered the registry settings for the single label domain, which is fine in our case, re-booted and everything is running fine!!
Just shows I need to check out all the angles before following advice from suppliers!
0
All Courses

From novice to tech pro — start learning today.