Explanation of DNS Notify List "Secondary Notification" Behavior
This article was previously published under Q163745
This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Windows NT Primary Domain Name Service (DNS) Servers do not sendchange notification messages to Secondary DNS Servers that are included onthe Primary's Notify List until selecting the menu option "DNS/UpdateServer Data Files".
Microsoft Windows NT DNS Server allows the Administrator to specify (on thePrimary DNS Server) any Secondary DNS Servers that should be notifiedimmediately of changes to the Zone file. When Zone changes occur, thePrimary name server sends DNS change notification messages to all Secondaryname servers on the list. When notified, the Secondary name server canquery the SOA record on the Primary immediately, without waiting for theRefresh Interval to expire.
The notification process does not occur until the "DNS/Update Server DataFiles" menu item is selected. Since there is no Incremental Zone transfercapability, when a Zone Transfer is triggered, the entire Zone file istransferred - not just changes made to the zone file.
Normally, the Administrator will make several changes in a singleadministrative session. If the Secondary DNS Servers were notified afterevery change, there would be a continuous stream of Zone transfers during asingle session, generating unnecessary network traffic. Waiting for theAdministrator to trigger the process by selecting "DNS/Update Server DataFiles" prevents continuous Zone transfers.
Article ID: 163745 - Last Review: 10/26/2013 03:26:00 - Revision: 2.0
Microsoft Windows NT Server 4.0 Standard Edition
- kbnosurvey kbarchive kbusage KB163745