DNSAPI Warning

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Guest
Archived from groups: microsoft.public.win2000.dns (More info?)

Does any one know how to eliminate these warning? I can recreate the
warnings by doing an ipconfig /registerdns. We have verified automatic
registration is working fine for this server and all of its resource records
in DNS. The only information I have found is something stating that the DNS
suffix doesn't match the domain membership, but it does. Anyone have some
ideas?

This is a Windows 2003 DC in a child domain. The other 49 DCs are not
experiencing this problem. For DNS we are using QIP.

Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11155
Date: 6/15/2004
Time: 2:38:11 PM
User: N/A
Computer: NHMANLOG01
Description:
The system failed to register network adapter with settings:

Adapter Name : {2EE9BA5A-DE35-4E61-87CA-9D8938E898A7}
Host Name : NHMANLOG01
Adapter-specific Domain Suffix :
DNS server list :
10.20.9.14, 172.16.57.118
Sent update to server : <?>
IP Address(es) :
<server's IP address was here>

The reason the DNS update request could not be completed was because of a
system problem. 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. For specific error code information, see the record
data displayed below.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 00 00 00 W...
 
Archived from groups: microsoft.public.win2000.dns (More info?)

In news:O8OHVwwUEHA.1020@TK2MSFTNGP11.phx.gbl,
Tim Kalligonis <tkalligonis@comcast.net> posted their thoughts, then I
offered mine
> Does any one know how to eliminate these warning? I can recreate the
> warnings by doing an ipconfig /registerdns. We have verified
> automatic registration is working fine for this server and all of its
> resource records in DNS. The only information I have found is
> something stating that the DNS suffix doesn't match the domain
> membership, but it does. Anyone have some ideas?
>
> This is a Windows 2003 DC in a child domain. The other 49 DCs are not
> experiencing this problem. For DNS we are using QIP.
>
> Event Type: Warning
> Event Source: DnsApi
> Event Category: None
> Event ID: 11155
> Date: 6/15/2004
> Time: 2:38:11 PM
> User: N/A
> Computer: NHMANLOG01
> Description:
> The system failed to register network adapter with settings:
>
> Adapter Name : {2EE9BA5A-DE35-4E61-87CA-9D8938E898A7}
> Host Name : NHMANLOG01
> Adapter-specific Domain Suffix :
> DNS server list :
> 10.20.9.14, 172.16.57.118
> Sent update to server : <?>
> IP Address(es) :
> <server's IP address was here>
>
> The reason the DNS update request could not be completed was because
> of a system problem. 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. For specific error code
> information, see the record data displayed below.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 57 00 00 00 W...


Hi Tim,

Unless you munged it, the Primary DNS Suffix appears to be missing, which
would cause this.

Here's more on it:
http://www.eventid.net/display.asp?eventid=11155&eventno=590&source=DnsApi&phase=1

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================