nepk
asked on
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 37C266A34E B}
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.