DNS record dynamic update error

DNS server has updated its own host (A) records.  In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update.  An error was encountered during this update, the record data is the error code. 

If this DNS server does not have any DS-integrated peers, then this error should be ignored. If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it. To ensure proper replication:

 1) Find this server's Active Directory replication partners that run the DNS server.

 2) Open DNS Manager and connect in turn to each of the replication partners.

 3) On each server, check the host (A record) registration for THIS server. 

 4) Delete any A records that do NOT correspond to IP addresses of this server. 

 5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact.  (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.) 

6) Note, that is not necessary to update EVERY replication partner.  It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

Solutions:This error occurs when you have enable Active Directory replication or you may have additional domain controller running in your network. In such case you need to perform following steps:

• Try to clear dns record from your system and server. To flush dns open Command Prompt and type command  : ipconfig /flushdns and then press enter.
• If the above step doesn't solve your problem then try to restart you server in the following pattern. You shutdown all your server and first start the main domain controller or dns server then start the other servers at last start your additional domain controller(active directory replication partner server).

If any one has a better solution than this please feel free to provide it in comments.

Share on Google Plus

About Mohammed Sajid Bagban

Assalam Alaikum, Myself Mohammed Sajid (Bagban) a resident of Kalaburagi city(formerly known as Gulbarga), Karnataka State, India. An IT professional working in Kuwait as "Network Engineer" since 2010.