• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 344
  • Last Modified:

2nd domain controller dns records

We have 2 Windows 2008 server dc's in 2 AD sites. When I ping the 2nd dc (from my pc)it resolves the address of dc1. I noticed this yesterday and in the dns mmc on dc1 I manually entered the correct ip address of dc2 in the forward lookup zone: _msdcs.domain.local, also have a host A record for dc2 in domain.local with the wrong IP (auto updated itself) this morning. Why is this occurring? Dcdiag has errors,  (failed test Kccevent) and DS event log is full of 1311 and 1566 id's.
  • 5
  • 4
2 Solutions
Remove any static entry of domain controllers from the zone, try restarting netlogon services on both DCs, run ipconfig /registerdns from both DCs, if it doesn't fix try running dcdiag /fix and netdiag /fix.
tcinfoAuthor Commented:
In the forward lookup zone:

Are you saying remove the A records for the 2 servers in domain.local?   OR
In _msdcs.domain.local there are static NS entries; there are also static entries in userconnect.com and userconnect.com/bd/portal

Thank you.
I meant A record you manually created under _msdcs.domain.local also remove A record in domain.local if it is static.

If the records are not automatically created by any of the above method, post any DNS related errors logged by dcdiag/netdiag.

Check this link also

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

tcinfoAuthor Commented:
I did not create an A record in _msdcs.domain.local but modified the ip address of the 2nd dc in the NS record in that zone. I left that as is.

I deleted the host A record in domain.local for the 2nd dc, (it was showing the wrong IP) and then restarted netlogon on both dc's and ran ipconfig /registerdns on both.

Seen a new host record (A) was created for dc2 with the correct ip and after ipconfig /flushdns on my pc - pinging the the 2nd dc resolves the correct ip. So that is better thanks.

Dcdiag still has errors, related to KCC and Group Policy (cause for concern)? - attaching relevant snippet.
Premkumar YogeswaranAnalyst II - System AdministratorCommented:
We do not find any file attached. You have did right process now.

For the DCDIAG error, i belive it should be fixed in certain replication interval.

If not paste the error you receive?

tcinfoAuthor Commented:
Dcdiag reports failed system log test and kcc errors, dns seems fine,
Can you post detailed error messages from event viewer? The error can be caused by replication issue between domain controllers either due to Antivirus or firewall or corruption on domain controller.

Does both domain controller have same errors? If firewall or AV is not the issue and this is showing only one domain controller, try transferring FSMO roles to healthy domain controller, demote DC having issues, remove from domain, cleanup NTDS, rejoin to domain and promote it again.
tcinfoAuthor Commented:
Event viewer better today, yesterday though:

Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Date:          4/1/2014 4:10:57 PM
Event ID:      1311
Task Category: Knowledge Consistency Checker
Level:         Error
Keywords:      Classic
User:          ANONYMOUS LOGON
Computer:      SOMDC01.domain.LOCAL
The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
Directory partition:
There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.
User Action
Perform one of the following actions:
- Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.
- Add a Connection object to a directory service that contains the directory partition in this site from a directory service that contains the same directory partition in another site.
If neither of the tasks correct this condition, see previous events logged by the KCC that identify the inaccessible directory servers.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS KCC" />
    <EventID Qualifiers="49152">1311</EventID>
    <TimeCreated SystemTime="2014-04-01T20:10:57.795Z" />
    <Correlation />
    <Execution ProcessID="616" ThreadID="1860" />
    <Channel>Directory Service</Channel>
    <Security UserID="S-1-5-7" />

It's only on one DC.
Does it show any error after fixing DNS issue.
check this link for troubleshooting.
tcinfoAuthor Commented:
The last technet link seems helpful (but applies to Win2008 server?) - I still have a Kcc error, but may open a separate question for it.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now