Secondary DNS Behavior Does Not Match Configured Options (249855)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server 4.0 SP1
  • Microsoft Windows NT Server 4.0 SP2
  • Microsoft Windows NT Server 4.0 SP3
  • Microsoft Windows NT Server 4.0 SP4
  • Microsoft Windows NT Server 4.0 SP5
  • Microsoft Windows NT Server 4.0 SP6
  • Microsoft Windows NT Server 4.0 SP6a

This article was previously published under Q249855

SYMPTOMS

When a Microsoft DNS-based server is configured as a secondary for a given zone, it may query the primary for its SOA record every two minutes rather than the period configured in the Refresh Interval or Retry Interval setting. This behavior takes place in the following circumstances:

The Microsoft DNS-based server is configured as a secondary for a given zone. At least one successful zone transfer has taken place from the primary to the secondary. After that time, if the primary DNS server becomes unavailable to respond to the secondary, the secondary DNS server queries the primary at an interval of approximately every 120 seconds.

STATUS

Microsoft is researching this problem and will post more information in this article when the information becomes available.

Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbenv kbprb KB249855