DNS Issues
-
Wednesday, November 14, 2012 6:37 PM
Greetings. I need some assistance with an apparent DNS issue, please.
Workstations have intermittent errors for W32Time, Dhcp, DnsApi, Netlogon, RPC, "There are currently no logon servers available". I am able to ping the DC/DNS server by IP address, common name, and FQDN.
On the server I have errors that go back as far as the logs do: "Name resolution for the name hcmserver.hcm.local timed out after none of the configured DNS servers responded", "Name resolution for the name 1.0.0.127.in-addr.arpa timed out after none of the configured DNS servers responded", "Name resolution for the name www.microsoft.com timed out after none of the configured DNS servers responded", "DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols".
Running ipconfig /displaydns on the server returns:
_ldap._tcp.default-first-site-name._sites.hcmserver.hcm.local
----------------------------------------
Name does not exist._ldap._tcp.hcmserver.hcm.local
----------------------------------------
Name does not exist.They have a SonicWALL handing out DHCP - it was handing out external DNS servers and I updated it to point to the DC instead.
Here is the dcdiag along with some additional error details:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine hcmserver, is a Directory Server.
Home Server = hcmserver
* Connecting to directory service on server hcmserver.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=hcm,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=hcm,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\HCMSERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
* Active Directory RPC Services Check
......................... HCMSERVER passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\HCMSERVER
Starting test: Advertising
The DC HCMSERVER is advertising itself as a DC and having a DS.
The DC HCMSERVER is advertising as an LDAP server
The DC HCMSERVER is advertising as having a writeable directory
The DC HCMSERVER is advertising as a Key Distribution Center
The DC HCMSERVER is advertising as a time server
The DS HCMSERVER is advertising as a GC.
......................... HCMSERVER passed test Advertising
Starting test: CheckSecurityError
* Dr Auth: Beginning security errors check!
Found KDC HCMSERVER for domain hcm.local in site Default-First-Site-Name
Checking machine account for DC HCMSERVER on DC HCMSERVER.
* SPN found :LDAP/hcmserver.hcm.local/hcm.local
* SPN found :LDAP/hcmserver.hcm.local
* SPN found :LDAP/HCMSERVER
* SPN found :LDAP/hcmserver.hcm.local/HCM
* SPN found :LDAP/ec37dbda-e1ee-48da-82d9-bda2b441bb7e._msdcs.hcm.local
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ec37dbda-e1ee-48da-82d9-bda2b441bb7e/hcm.local
* SPN found :HOST/hcmserver.hcm.local/hcm.local
* SPN found :HOST/hcmserver.hcm.local
* SPN found :HOST/HCMSERVER
* SPN found :HOST/hcmserver.hcm.local/HCM
* SPN found :GC/hcmserver.hcm.local/hcm.local
[HCMSERVER] No security related replication errors were found on this
DC! To target the connection to a specific source DC use
/ReplSource:<DC>.
......................... HCMSERVER passed test CheckSecurityError
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for DC=ForestDnsZones,DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=DomainDnsZones,DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Configuration,DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... HCMSERVER passed test CutoffServers
Starting test: FrsEvent
* The File Replication Service Event log test
Skip the test because the server is running DFSR.
......................... HCMSERVER passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
......................... HCMSERVER passed test DFSREvent
Starting test: SysVolCheck
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... HCMSERVER passed test SysVolCheck
Starting test: FrsSysVol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... HCMSERVER passed test FrsSysVol
Starting test: KccEvent
* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... HCMSERVER passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
Role Domain Owner = CN=NTDS Settings,CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
Role PDC Owner = CN=NTDS Settings,CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
Role Rid Owner = CN=NTDS Settings,CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
Role Infrastructure Update Owner = CN=NTDS Settings,CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
......................... HCMSERVER passed test KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC HCMSERVER on DC HCMSERVER.
* SPN found :LDAP/hcmserver.hcm.local/hcm.local
* SPN found :LDAP/hcmserver.hcm.local
* SPN found :LDAP/HCMSERVER
* SPN found :LDAP/hcmserver.hcm.local/HCM
* SPN found :LDAP/ec37dbda-e1ee-48da-82d9-bda2b441bb7e._msdcs.hcm.local
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ec37dbda-e1ee-48da-82d9-bda2b441bb7e/hcm.local
* SPN found :HOST/hcmserver.hcm.local/hcm.local
* SPN found :HOST/hcmserver.hcm.local
* SPN found :HOST/HCMSERVER
* SPN found :HOST/hcmserver.hcm.local/HCM
* SPN found :GC/hcmserver.hcm.local/hcm.local
......................... HCMSERVER passed test MachineAccount
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC HCMSERVER.
* Security Permissions Check for
DC=ForestDnsZones,DC=hcm,DC=local
(NDNC,Version 3)
* Security Permissions Check for
DC=DomainDnsZones,DC=hcm,DC=local
(NDNC,Version 3)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=hcm,DC=local
(Schema,Version 3)
* Security Permissions Check for
CN=Configuration,DC=hcm,DC=local
(Configuration,Version 3)
* Security Permissions Check for
DC=hcm,DC=local
(Domain,Version 3)
......................... HCMSERVER passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\HCMSERVER\netlogon
Verified share \\HCMSERVER\sysvol
......................... HCMSERVER passed test NetLogons
Starting test: ObjectsReplicated
HCMSERVER is in domain DC=hcm,DC=local
Checking for CN=HCMSERVER,OU=Domain Controllers,DC=hcm,DC=local in domain DC=hcm,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local in domain CN=Configuration,DC=hcm,DC=local on 1 servers
Object is up-to-date on all servers.
......................... HCMSERVER passed test ObjectsReplicated
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure Channels test because /testdomain: was
not entered
......................... HCMSERVER passed test OutboundSecureChannels
Starting test: Replications
* Replications Check
* Replication Latency Check
......................... HCMSERVER passed test Replications
Starting test: RidManager
* Available RID Pool for the Domain is 1600 to 1073741823
* hcmserver.hcm.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1100 to 1599
* rIDPreviousAllocationPool is 1100 to 1599
* rIDNextRID: 1303
......................... HCMSERVER passed test RidManager
Starting test: Services
* Checking Service: EventSystem
* Checking Service: RpcSs
* Checking Service: NTDS
* Checking Service: DnsCache
* Checking Service: DFSR
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: w32time
* Checking Service: NETLOGON
......................... HCMSERVER passed test Services
Starting test: SystemLog
* The System Event log test
An error event occurred. EventID: 0xC0002719
Time Generated: 11/13/2012 14:39:05
Event String:
DCOM was unable to communicate with the computer 151.164.11.201 using any of the configured protocols.
A warning event occurred. EventID: 0x000003F6
Time Generated: 11/13/2012 14:39:17
Event String:
Name resolution for the name www.microsoft.com timed out after none of the configured DNS servers responded.
An error event occurred. EventID: 0xC0002719
Time Generated: 11/13/2012 14:39:38
Event String:
DCOM was unable to communicate with the computer 151.164.193.201 using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 11/13/2012 14:39:59
Event String:
DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols.
......................... HCMSERVER failed test SystemLog
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for DC=ForestDnsZones,DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=DomainDnsZones,DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Schema,CN=Configuration,DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Configuration,DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=hcm,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... HCMSERVER passed test Topology
Starting test: VerifyEnterpriseReferences
......................... HCMSERVER passed test
VerifyEnterpriseReferences
Starting test: VerifyReferences
The system object reference (serverReference)
CN=HCMSERVER,OU=Domain Controllers,DC=hcm,DC=local and backlink on
CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
are correct.
The system object reference (serverReferenceBL)
CN=WIN-HD6J825O8D9,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=hcm,DC=local
and backlink on
CN=NTDS Settings,CN=HCMSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hcm,DC=local
are correct.
The system object reference (msDFSR-ComputerReferenceBL)
CN=WIN-HD6J825O8D9,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=hcm,DC=local
and backlink on CN=HCMSERVER,OU=Domain Controllers,DC=hcm,DC=local are
correct.
......................... HCMSERVER passed test VerifyReferences
Starting test: VerifyReplicas
......................... HCMSERVER passed test VerifyReplicas
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
See DNS test in enterprise tests section for results
......................... HCMSERVER passed test DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : hcm
Starting test: CheckSDRefDom
......................... hcm passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... hcm passed test CrossRefValidation
Running enterprise tests on : hcm.local
Starting test: DNS
Test results for domain controllers:
DC: hcmserver.hcm.local
Domain: hcm.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS
Microsoft Windows Server 2008 R2 Standard (Service Pack level: 1.0)
is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter
[00000007] Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client):
MAC address is 84:2B:2B:5C:62:1A
IP Address is static
IP address: 10.10.17.2
DNS servers:
10.10.17.2 (hcmserver.hcm.local.) [Valid]
127.0.0.1 (hcmserver.hcm.local.) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders Information:
151.164.11.201 (<name unavailable>) [Valid]
151.164.193.201 (<name unavailable>) [Invalid (unreachable)] **I removed this one**
8.8.8.8 (<name unavailable>) [Valid]
TEST: Delegations (Del)
Delegation information for the zone: hcm.local.
Delegated domain name: _msdcs.hcm.local.
DNS server: hcmserver.hcm.local. IP:10.10.17.2 [Valid]
DNS server: hcmserver.hcm.local. IP:::1 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone hcm.local
Test record dcdiag-test-record deleted successfully in zone hcm.local
TEST: Records registration (RReg)
Network Adapter
[00000007] Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client):
Matching CNAME record found at DNS server 10.10.17.2:
ec37dbda-e1ee-48da-82d9-bda2b441bb7e._msdcs.hcm.local
Matching A record found at DNS server 10.10.17.2:
hcmserver.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.1714bdd3-e712-4afa-8a54-63d3277b7c70.domains._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._tcp.dc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.dc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._tcp.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._udp.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kpasswd._tcp.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.Default-First-Site-Name._sites.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._tcp.Default-First-Site-Name._sites.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.gc._msdcs.hcm.local
Matching A record found at DNS server 10.10.17.2:
gc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_gc._tcp.Default-First-Site-Name._sites.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.pdc._msdcs.hcm.local
Matching CNAME record found at DNS server 10.10.17.2:
ec37dbda-e1ee-48da-82d9-bda2b441bb7e._msdcs.hcm.local
Matching A record found at DNS server 10.10.17.2:
hcmserver.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.1714bdd3-e712-4afa-8a54-63d3277b7c70.domains._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._tcp.dc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.dc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._tcp.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._udp.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kpasswd._tcp.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.Default-First-Site-Name._sites.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_kerberos._tcp.Default-First-Site-Name._sites.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.gc._msdcs.hcm.local
Matching A record found at DNS server 10.10.17.2:
gc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_gc._tcp.Default-First-Site-Name._sites.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.hcm.local
Matching SRV record found at DNS server 10.10.17.2:
_ldap._tcp.pdc._msdcs.hcm.local
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 151.164.193.201 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 151.164.193.201 [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 10.10.17.2 (hcmserver.hcm.local.)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS delegation for the domain _msdcs.hcm.local. is operational on IP 10.10.17.2
DNS server: 151.164.11.201 (<name unavailable>)
All tests passed on this DNS server
DNS server: 8.8.8.8 (<name unavailable>)
All tests passed on this DNS server
DNS server: ::1 (hcmserver.hcm.local.)
All tests passed on this DNS server
DNS delegation for the domain _msdcs.hcm.local. is operational on IP ::1
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: hcm.local
hcmserver PASS PASS PASS PASS PASS PASS n/a
......................... hcm.local passed test DNS
Starting test: LocatorCheck
GC Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
PDC Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
Time Server Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
Preferred Time Server Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
KDC Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
......................... hcm.local passed test LocatorCheck
Starting test: FsmoCheck
GC Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
PDC Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
Time Server Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
Preferred Time Server Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
KDC Name: \\hcmserver.hcm.local
Locator Flags: 0xe00031fd
......................... hcm.local passed test FsmoCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... hcm.local passed test Intersite
**Addtional Info:**
C:\Users\Administrator>ipconfig /displaydns
Windows IP Configuration
_ldap._tcp.default-first-site-name._sites.hcmserver.hcm.local
----------------------------------------
Name does not exist.
_ldap._tcp.hcmserver.hcm.local
----------------------------------------
Name does not exist.
Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 11/13/2012 2:44:54 PM
Event ID: 1014
Task Category: None
Level: Warning
Keywords:
User: HCM\administrator
Computer: hcmserver.hcm.local
Description:
Name resolution for the name www.microsoft.com timed out after none of the configured DNS servers responded.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />
<EventID>1014</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2012-11-13T20:44:54.850038100Z" />
<EventRecordID>182869</EventRecordID>
<Correlation />
<Execution ProcessID="5356" ThreadID="5336" />
<Channel>System</Channel>
<Computer>hcmserver.hcm.local</Computer>
<Security UserID="S-1-5-21-1434587139-2989609233-1450342578-500" />
</System>
<EventData>
<Data Name="QueryName">www.microsoft.com</Data>
<Data Name="AddressLength">16</Data>
<Data Name="Address">0200003597A4C1C90000000000000000</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 11/13/2012 1:37:41 PM
Event ID: 1014
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: hcmserver.hcm.local
Description:
Name resolution for the name 1.0.0.127.in-addr.arpa timed out after none of the configured DNS servers responded.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />
<EventID>1014</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2012-11-13T19:37:41.026821400Z" />
<EventRecordID>182858</EventRecordID>
<Correlation />
<Execution ProcessID="6428" ThreadID="6388" />
<Channel>System</Channel>
<Computer>hcmserver.hcm.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="QueryName">1.0.0.127.in-addr.arpa</Data>
<Data Name="AddressLength">16</Data>
<Data Name="Address">0200003597A4C1C90000000000000000</Data>
</EventData>
</Event>Any assistance is greatly appreciated. Thanks.
All Replies
-
Friday, November 16, 2012 6:56 AMModerator
Hi,
Based on my research, this should be has something related with Windows Firewall, please disable firewall and check the result, in addition, please also go through the below thread:
DCOM was unable to communicate with the computer x.x.x.x using any of the configured protocols.
Hope this helps.
Regards,
Yan Li
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Yan Li
TechNet Community Support
- Marked As Answer by Yan Li_Microsoft Contingent Staff, Moderator Friday, November 23, 2012 2:25 AM
-
Friday, November 16, 2012 7:13 AM
Hi,
I believe this link will fix the DNS client issue that you are referring to:
For more awareness I suggest you to check the following links as well.
- Marked As Answer by Yan Li_Microsoft Contingent Staff, Moderator Friday, November 23, 2012 2:25 AM
-
Friday, November 16, 2012 8:09 AMModerator
Is it SBS or normal standard/enterprise edition server? Why are you using IP 8.8.8.8 in your server, this is public IP & you should be using public IP for external DNS resolution given by your ISP. Most of the event id posted relates to the warning, they are not errors & warning can be intermittent. Also, most of the warning/error points to the DNS misconfiguration.
DNS recommendations from Microsoft http://awinish.wordpress.com/2011/03/08/dns-recommendations-from-microsoft/
Please post unedited ipconfig /all >>ipconfig.text report here.
Awinish Vishwakarma - MVP
My Blog: awinish.wordpress.com
Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.- Marked As Answer by Yan Li_Microsoft Contingent Staff, Moderator Friday, November 23, 2012 2:25 AM
-
Sunday, November 18, 2012 12:35 AM
Form the dcdiag output the health of DC is good and no errors are reported except the dcom error.
How to troubleshoot DCOM 10009 error logged in system event?
http://blogs.msdn.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspxEvent ID: 1014 Source: DNS Client Events
http://www.eventid.net/display-eventid-1014-source-DNS%20Client%20Events-eventno-10623-phase-1.htmAlso ensure the correct dns setting on DC and client as below.
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
Also, disable local windows firewall service, by default it is enabled in vista/windows 2008 and above.
Disable Windows Firewall: http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx
It could be due to AV(McAfee,Symantec, Trend, etc) or 3rd party security application which act as firewall and block AD communuctaion.AV like Symantec,trend,etc have new features to "protect network traffic".Please check AV setting and disable the same if defined.Hope this helps
Best Regards,
Sandesh Dubey.
MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.- Marked As Answer by Yan Li_Microsoft Contingent Staff, Moderator Friday, November 23, 2012 2:25 AM
-
Monday, November 19, 2012 3:01 AMModerator
Hi,
Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Yan Li
TechNet Community Support
.png)
