The DNS PTR record might be deleted if you change the DNS server order on a Windows 2003 machine

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
Source: Microsoft Support
RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Symptom


Under certain circumstances, if you change the Dynamic Name Server (DNS) order on a Windows Server 2003 computer configured with a fixed IP address, the pointer (PTR) resource record of the server might disappear from DNS.
Cause


This problem might occur if the following conditions are true:

 

1.            The Windows 2003 Server is configured with a fixed IP address.

2.            There are two DNS servers configured for this computer, both severs are set to host the Active Directory (AD) integrated reverse zone.

3.            You change the DNS Server order in the LAN TCP/IP properties user interface, for example from (dnsserver1,dnsserver2) to (dnsserver2,dnsserver1) 

 

 

 

In this case, you can see the followings in a network trace

 

a, A single “delete PTR” request is sent dnsserver1 (old primary)

b, A “delete + add PTR” request is sent to dnsserver2 (new primary)

The “delete +add” request might not mean any change in the current data on dnsserver2.

If that is the case, dnsserver2 responds with “SUCCESS”, but does not change anything in AD, because there is no modification in the data.

 

From the AD perspective, we have a single “delete” performed on dnsserver1.

 

This gets replicated, and the PTR record is deleted on all DNS servers.

 

The PTR record disappears only temporarily, because the host re-registers its records by default every 24 hours.
Resolution


To resolve this problem immediately, start a DNS update after changing the DNS server order by executing ipconfig /registerdns at a command prompt on the Windows 2003 machine.
More Information
DISCLAIMER
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Properties

Article ID: 961256 - Last Review: 01/14/2015 12:04:44 - Revision: 1.0

  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • kbnosurvey kbarchive kbnomt kbrapidpub KB961256
Feedback