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

DNS Help - Server 2003 - Dnsapi Error

Okay so about 10 days ago a lot of my servers started throwing "Dnsapi" Warnings in the System Event Viewer with Event ID 11164. I have not made any system wide or DNS changes recently so I dont really know why this is surfacing. We have about 45 servers and I also noticed the the Forward Lookup Zone A Records for about 6 servers dissapeared so they are not accessable via computer name.

I've read over some of the MS KB articles and tried the ipconfig /registerdns but that doesnt add the entry into DNS and throws the same error in event viewer on the local server. This doesnt seem to be occuring on any of our Server2008 servers and only on about half of our 2003 servers.

All of our servers are configured with static IPv4 addresses. We only have 1 DHCP Scope setup and that is on a different subnet for desktop computers. I mention that because I know there is a configuration setting in DHCP scope for dynamic DNS updating.

Any insight or direction resolving this would be greatly appreciated! I am afraid the problem could spread causing more issues.

Here is a copy of the Dnsapi entry in Event Viewer on one of the servers:

Event Type:      Warning
Event Source:      DnsApi
Event Category:      None
Event ID:      11164
Date:            10/24/2011
Time:            5:51:09 PM
User:            N/A
Computer:      ServerV8
Description:
The system failed to register host (A) resource records (RRs) for network adapter
with settings:

   Adapter Name : {F8E0CDD1-2803-437B-B014-1449E24BFA2D}
   Host Name : ServerV8
   Primary Domain Suffix : abc.net
   DNS server list :
           10.20.1.30, 10.20.1.31
   Sent update to server : <?>
   IP Address(es) :
     10.10.1.53

 The reason the system could not register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates.

 To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: b4 05 00 00               ยด...    
0
AIC-Admin
Asked:
AIC-Admin
  • 6
  • 3
1 Solution
 
JAN PAKULACommented:
have you installed teaming nics software on faulty machine ServerV8?

Team software has to be uninstalled to release both NICs after they have been teamed.

Remve team restart - should be ok then

JAN MA CCNA
0
 
AIC-AdminAuthor Commented:
Some of my machine have NIC teaming and some do not. Actually many of the machines throwing these Dnsapi warning are Virtual Machine running on the Virtual Iron paltform. Some of the Server 2008 machines have NIC teaming enabled and do not have this error and others do not have NIC teaming and still don't have the error. The observation that my Server 2008 machines don't ahve this problem may be unrelated as some of my Server 2003 machines don't show these Dnsapi errors either.

Thanks!
0
 
JAN PAKULACommented:
you could try also delete a record of Server V8

and then run ipconfig /flushdns
ipconfig /registerdns
0
 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

 
AIC-AdminAuthor Commented:
First deleting the A record from DNS then performing the ipconfig /flushdns and then ipconfig /registerdns from a Server 2008 did create a new DNS A Record. I guess I will need to try that on the problematic servers after hours.
0
 
AIC-AdminAuthor Commented:
Any idea why some of our servers are now all of a sudden throwing Dnsapi errors? I can manuaully register these prbolem servers but I dont want to worry about this happening to others. I assuem there must be a DNS configuration that is incorrect but I dont know what. Is there any special configuration for server with Status IP addresses and how they register with DNS?
0
 
AIC-AdminAuthor Commented:
Okay so tried the ipconfig /flushdns and ipconfig /registerdns on one of the problematic Server 2003 servers and it just throws the same Dnsapi error in event viewer and doesnt register in DNS on the DC.
0
 
JAN PAKULACommented:
Are You sure that you have dns server ip set-up properly on faulting server?

netsh interface ip set dns name="Local Area Connection" source=dhcp
netsh interface ip set dns name="Local Area Connection" static 10.20.1.30 primary

I am assuming that 10.20.1.30 is your primary DNS IP

also check in registry that

 regedit

 HKLM\System\CCS\Services\Tcpip\Parameters\NameServer=10.20.1.30

NameServer should have ip of your current dns server 10.20.1.30

Is you dns/DHCP server has IEES on

To switch it of follow http://www.youtube.com/watch?v=OO3PPN1olHY

 
Also check that

http://technet.microsoft.com/en-us/library/cc735648(WS.10).aspx

and that

http://technet.microsoft.com/en-us/library/cc756815(WS.10).aspx

0
 
AIC-AdminAuthor Commented:
when I run netsh interface ip show dns the corrected dns information is present.

Strangely enough though when I checked the Registry Key you listed and there is no ip entry for that key. I entered in the ip address and ran an ipconfig /flushdns and /registerdns  but the same Dnsapi error appeared in the windows event viewer.

I am in the process of reviewing the YouTube and two kb articles you provided.

Thanks for all of the suggestions!
0
 
AIC-AdminAuthor Commented:
Alright well turns out its more then likely a Active Directory replication problem.... even though it doesnt really account for exactly who is happening we are have various AD replication errors and somenoe left some old DC's in the current AD. T
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now