DNS Warning

alex.olynyk

Getting this warning logged on 1 DC in our domain.
0_1467378763115_error.txt
Is this something to be concerned about?
Primary DNS has always pointed to the servers IP. Should I use the loopback address instead?

scottalanmiller

Contents of the error...

Log Name:      DNS Server
Source:        Microsoft-Windows-DNS-Server-Service
Date:          6/30/2016 12:28:04 PM
Event ID:      4013
Task Category: None
Level:         Warning
Keywords:      (131072)
User:          SYSTEM
Computer:      TRI-DC1A.ROSE.internal
Description:
The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DNS-Server-Service" Guid="{71A551F5-C893-4849-886B-B5EC8502641E}" />
    <EventID>4013</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000020000</Keywords>
    <TimeCreated SystemTime="2016-06-30T16:28:04.126115300Z" />
    <EventRecordID>345</EventRecordID>
    <Correlation />
    <Execution ProcessID="2940" ThreadID="3000" />
    <Channel>DNS Server</Channel>
    <Computer>TRI-DC1A.ROSE.internal</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData Name="DNS_EVENT_DS_OPEN_WAIT">
  </EventData>
</Event>

travisdh1

@alex.olynyk said in DNS Warning:

Getting this warning logged on 1 DC in our domain.
0_1467378763115_error.txt
Is this something to be concerned about?
Primary DNS has always pointed to the servers IP. Should I use the loopback address instead?

Looks like the directory replication isn't happening fast enough to keep that warning away. Do you know if you can login using the server?

scottalanmiller

Is active directory up and running there?

alex.olynyk

Yes, AD is up and running at all sites on a single domain.

alex.olynyk

@travisdh1 unsure what you mean login "using" the server? I can Dameware and RDP into it.

Dashrender

@alex.olynyk said in DNS Warning:

@travisdh1 unsure what you mean login "using" the server? I can Dameware and RDP into it.

In other words - are any computers actually authenticating off of it.

Try this. On the server along, change it's IP settings so it's DNS servers only point to itself.. then try to logon. If this takes a very long time, then you have issues.

OK you really probably shouldn't do that during the day, while I don't think it should cause other issues it might.

do a dcdiag on it.

momurda

dcdiag -v /test:dns

alex.olynyk

ran dcdiag -v /test:dns on 1 DC and all tested passed
ran on another DC at a diff site and get this
0_1467394966617_dcdiag.txt
both are joined to same domain

Dashrender

@alex.olynyk said in DNS Warning:

ran dcdiag -v /test:dns on 1 DC and all tested passed
ran on another DC at a diff site and get this
0_1467394966617_dcdiag.txt
both are joined to same domain

what are the DNS entries in the IP stacks on each server?

alex.olynyk

127.0.0.1

alex.olynyk

0_1467723347117_TR-DCDiag.txt
Full DCDIAG from 1 DC, getting latency warnings. Ill post DCDIAG from the others.

alex.olynyk

0_1467723689449_SADCDIAG.txt
DCDIAG from a DC at another site

alex.olynyk

0_1467724012122_RVDCDIAG.txt

alex.olynyk

0_1467724163421_KEDCDIAG.txt