Event ID DNSapi log in the event viewer
Hi ,
We have a windows 2003 Network with two DNS servers A/D integrated. All my
Clients received their IP from DHCP. The DNS configuration on the DHCp is
set to always Update DNS A and PTR records.
One my Windows 2003 Memeber server Getting this error
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11163
Date: 10/28/2005
Time: 10:51:36 AM
User: N/A
Computer: SVR2003
Description:
The system failed to register host (A) resource records (RRs) for network
adapter
with settings:
Adapter Name : {EDA71A11-7916-4433-BC9F-F
Host Name : isdsk63
Primary Domain Suffix : imaginesolutions.com
DNS server list :
192.168.0.26, 192.168.0.27
Sent update to server : 192.168.0.26
IP Address(es) :
192.168.0.150
The reason the system could not register these RRs was because the DNS
server failed the update request. The most likely cause of this is that the
authoritative DNS server required to process this update request has a lock
in place on the zone, probably because a zone transfer is in progress.
You can manually retry DNS registration of the network adapter and its
settings by typing "ipconfig /registerdns" at the command prompt. If problems
still persist, contact your DNS server or network systems administrator.
We have a windows 2003 Network with two DNS servers A/D integrated. All my
Clients received their IP from DHCP. The DNS configuration on the DHCp is
set to always Update DNS A and PTR records.
One my Windows 2003 Memeber server Getting this error
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11163
Date: 10/28/2005
Time: 10:51:36 AM
User: N/A
Computer: SVR2003
Description:
The system failed to register host (A) resource records (RRs) for network
adapter
with settings:
Adapter Name : {EDA71A11-7916-4433-BC9F-F
Host Name : isdsk63
Primary Domain Suffix : imaginesolutions.com
DNS server list :
192.168.0.26, 192.168.0.27
Sent update to server : 192.168.0.26
IP Address(es) :
192.168.0.150
The reason the system could not register these RRs was because the DNS
server failed the update request. The most likely cause of this is that the
authoritative DNS server required to process this update request has a lock
in place on the zone, probably because a zone transfer is in progress.
You can manually retry DNS registration of the network adapter and its
settings by typing "ipconfig /registerdns" at the command prompt. If problems
still persist, contact your DNS server or network systems administrator.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
This is a common issue.
In the Forward Lookup zone for the domain, delete the A record for isdsk63.
In the Reverse Zone for the subnet, delete all PTR records for the IP address 192.168.0.150.
Run: ipconfig /registerdns from the member server to reregister it.
Sometimes, records will not update if you changed computernames after it registered with DNS using the old name. It should update, but it doesn't always.
Deleting the offending records will fix the issue.
In the Forward Lookup zone for the domain, delete the A record for isdsk63.
In the Reverse Zone for the subnet, delete all PTR records for the IP address 192.168.0.150.
Run: ipconfig /registerdns from the member server to reregister it.
Sometimes, records will not update if you changed computernames after it registered with DNS using the old name. It should update, but it doesn't always.
Deleting the offending records will fix the issue.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial