[WARNING] Cannot find a primary authoritative DNS server for the name

[WARNING] Cannot find a primary authoritative DNS server for the name
            'serverA.domain.local.'. [ERROR_TIMEOUT]
            The name serverA.domain.local.' may not be registered in DNS.
    PASS - All the DNS entries for DC are registered on DNS server xxx.xxx.xxx.xxx and other DCs also have some of the names registered.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS server xxx.xxx.xxx.xxx. Please wait for 30 minutes for DNS server replication.
       [WARNING] The DNS entries for this DC cannot be verified right now on DNS server xxx.xxx.xxx.xxx, ERROR_TIMEOUT.

I got these results on both servers when I ran netdiag.  

Server A reports in its event viewer file replication service logs:

Event Type:      Information
Event Source:      NtFrs
Event Category:      None
Event ID:      13516
Date:            3/28/2011
Time:            10:08:19 AM
User:            N/A
Computer:      Server A
Description:
The File Replication Service is no longer preventing the computer serverAfrom becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
 
Type "net share" to check for the SYSVOL share.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Then one minute later I get the following warning:
Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13508
Date:            3/28/2011
Time:            10:09:59 AM
User:            N/A
Computer:      Server A
Description:
The File Replication Service is having trouble enabling replication from Server  B to Server A for c:\windows\sysvol\domain using the DNS name ServerB.domain.local. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name FINANCIAL.Pooleinc.local from this computer.
 [2] FRS is not running on FINANCIAL.Pooleinc.local.
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
 
 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

On Server B my event log states:

Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13508
Date:            4/10/2009
Time:            11:29:40 AM
User:            N/A
Computer:      ServerB
Description:
The File Replication Service is having trouble enabling replication from ServerA to ServerB for c:\windows\sysvol\domain using the DNS name serverA.domain.local. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name dancingrabbit.Pooleinc.local from this computer.
 [2] FRS is not running on dancingrabbit.Pooleinc.local.
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

 and
Event Type:      Information
Event Source:      NtFrs
Event Category:      None
Event ID:      13516
Date:            4/21/2009
Time:            1:37:55 PM
User:            N/A
Computer:      FINANCIAL
Description:
The File Replication Service is no longer preventing the computer FINANCIAL from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
 
Type "net share" to check for the SYSVOL share.

They are both in default-first-site.
They are on didfferent subnets.

I get more of the event IDs 13508 than event ID 13516.

What I have done to date:
1.  confirmed file replication service is running on both DCs
2. ran netdiag on both DCs - the results for netdiag are at the top of this message.
3. check AD sites and server.  Was able to initiate replication from wthin this environment successfully.
4. Confirmed the schedules of both DCs and they do match.
5.  Sites and services, NTDS Settings, each server is set up to replcilate from/to the other DC
6.  both machines are running w2k3 sp2

thanks in advance.
PCully
 
LVL 2
IT20701Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TheTechManCommented:
This is quite normal and usually automatically corrects itself over time.  It happens particularly often if you restart all DC's at the same time.  If you stagger them by a half hour, usually you navigate through this issue with no problems.  However:

Make sure your Global Catalog server uses it's own address for DNS for all NIC's
Make sure your other DC's use this 1st server's IP, then its own IP in DNS

If DNS fails at first, then AD fails at first, which means FRS fails at first.  IF DNS succeeds and AD fails at first, FRS will still fail, but this is very uncommon and usually only happens when the two DC's can't communicate correctly or are disconnected.

Make the above changes and reboot all the servers.
0
IT20701Author Commented:
If DNS fails at first, then AD fails at first, which means FRS fails at first

not sure what you mean by this.

thanks
0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

TheTechManCommented:
It means all these services are dependent upon each other and the order of succession to make sure the services run is DNS, AD, FRS.  DNS must be running, so if it's not, make it run. Once that's done, run AD.  Once that's run, run FRS.  By run, I mean start the service.  If one fails, troubleshoot that one.  I think making the DNS change listed above with fix all the issues.  Try it and let me know!
0
IT20701Author Commented:
services are all running.  Looks like one machine was upgraded before my time and there are legacy entries I need to clean up.  I'm going to accept your solution for now.  This is going to require lots of testing before I can implement.  thanks.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IT20701Author Commented:
discovered that one DC was actually upgraded (2) - before my time - and there are legacy policies and settings that need to be identified, tested and removed.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.