Question : MS 2003 Server - System Event ID 11166 Source DnsApi Errors since change of DNS server

Recently die to harware faikure

Code Snippet:

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:

           
           
             Due to hardware failure a Microsoft 2003 Domain, it was reqiured to create a new DC/DNS server. A secondary DC was built and all roles switched i.e. DC-01 is now GC abd holds FSMO roles new DC is a GC but holds no FSMO roles. All servers in the domain are configured to use DC-01 and DC-01 as their DNS servers.
Since this introdiction of the new DC (dc-02) we have been getting entries on some server eventlogs - I donot think it is an issue but would like to confirm this and how do I remove these entries .
 
SYSTEM LOG entires as follows :-
 
Sourec : DnsApi Event IT : 11166
 
The system failed to register host (A) resource records (RRs) for network adapter
with settings:
 
   Adapter Name : {CC5D224C-4A45-47EF-845C-BF0701AAB485}
   Host Name : inta-iag-db-01
   Primary Domain Suffix : inta.iag.sydney.com.au
   DNS server list :
     	192.168.10.8, 192.168.10.12
   Sent update to server : 192.168.10.8
   IP Address(es) :
     192.168.10.19
 
 The reason the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.
 
 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, see the record data displayed below.
 
 
Thanks

           
         

Open in New Window

Select All

Answer : MS 2003 Server - System Event ID 11166 Source DnsApi Errors since change of DNS server

If you use static addresses, this will just be an annoying message you see in your logs. The clients will try to register themselves in DNS as a matter of course, but even if they fail, everything will keep working. The only thing you need to worry about if when you either change an IP address of an existing client or add a new client. You will have to double check the DNS entry manually to ensure that it's current. Since you do the IP addresses manually, it won't be that much more work to double check DNS settings.