DNSEXT Working Group                                        Levon EsibovINTERNET-DRAFT                                               Stuart KwanCategory: Best Current Practice                                Microsoft<draft-esibov-dnsext-dynupdtld-00.txt>February 22, 2001       Dynamic DNS Update of the Top Level Domain and Root ZonesThis document is an Internet-Draft and is in full conformance with allprovisions of Section 10 of RFC2026.Internet-Drafts are working documents of the Internet Engineering TaskForce (IETF), its areas, and its working groups.  Note that other groupsmay also distribute working documents as Internet- Drafts.Internet-Drafts are draft documents valid for a maximum of six monthsand may be updated, replaced, or obsoleted by other documents at anytime.  It is inappropriate to use Internet-Drafts as reference materialor to cite them other than as "work in progress."The list of current Internet-Drafts can be accessed athttp://www.ietf.org/ietf/1id-abstracts.txtThe list of Internet-Draft Shadow Directories can be accessed athttp://www.ietf.org/shadow.html.Status of this MemoThis document specifies an Internet Best Current Practices for theInternet Community, and requests discussion and suggestions forimprovements.  Distribution of this memo is unlimited.Copyright NoticeCopyright (C) The Internet Society (2001).  All Rights Reserved.AbstractWith an increasing number of implementations where the DNS client iscapable of performing dynamic DNS updates, an increase in the number ofthe dynamic DNS updates sent to the servers hosting top level domainzones has been observed. The purpose of this document is to recommendDNS client configuration that prevents sending dynamic DNS updates forthe top level domain zones and root zones.Esibov & Kwan                     BCP                           [Page 1]INTERNET-DRAFT   Dynamic Update of the TLD DNS Zones    22 February 20011.  IntroductionRFC 2136 [1] specifies Dynamic Updates in DNS, but does notconsider updates of the top level domain zones (e.g. "com", "edu", "ca","uk", etc...) and the root zone as a special case. Usually requests toperform dynamic updates of the top level domain zones and the root zoneare expected to fail because these zones (on the Internet) areconfigured to prohibit any dynamic updates. The same is true for mostorganizations' private internal DNS infrastructures. The unnecessaryload of the dynamic updates sent by DNS clients attempting dynamicupdates of these zones consumes the resources of the DNS serversauthoritative for these zones and consumes network bandwidth.With an increasing number of implementations where the DNS client iscapable of performing dynamic DNS updates, an increase in the number ofthe dynamic DNS updates sent to the servers hosting top level domainzones has been observed. The purpose of this document is to recommendDNS client configuration that prevents sending dynamic DNS updates forthe top level domain zones and root zones.In this document, the key words "MAY", "MUST,  "MUST  NOT", "optional","recommended",  "SHOULD",  and  "SHOULD  NOT",  are to be interpreted asdescribed in [2].2. Dynamic updates of the top level domain zones and root zones.To prevent dynamic DNS update requests to the top level domain zones androot zone, it is recommended that DNS clients are configured by defaultto suppress dynamic DNS updates of the top level domain zones and theroot zone.To address the needs of the organizations using top level domain zonesand/or the root zone in their private internal DNS infrastructures, andto allow dynamic updates of such zones, DNS clients MAY be configured toallow dynamic DNS updates to be sent to the top level domain zones.3.  IANA ConsiderationsIANA's consideration is not required.4.  Security ConsiderationsThis draft does not introduce any additional security concerns.Esibov & Kwan                     BCP                           [Page 2]INTERNET-DRAFT   Dynamic Update of the TLD DNS Zones    22 February 20015.  AcknowledgementsAuthors would like to thank Aristotle Balogh and Mark Kosters forbringing to our attention the raising volume of the dynamic updaterequests sent to the top level domain zones. We would also like to thankMichael Cretzman for review of this document.6.  Authors' AddressesLevon EsibovMicrosoft CorporationOne Microsoft WayRedmond, WA 98052EMail: levone@microsoft.comStuart KwanMicrosoft CorporationOne Microsoft WayRedmond, WA 98052EMail: skwan@microsoft.com7.  References[1]  Vixie, P., Thomson, S., Rekhter, Y., Bound, J., "Dynamic Updates     in the Domain Name System (DNS UPDATE)", RFC 2136, April 1997.[2]  Bradner, S., "Key words for use in RFCs to Indicate Requirement     Levels", BCP 14, RFC 2119, March 1997.8.  Intellectual Property StatementThe IETF takes no position regarding the validity or scope of anyintellectual property or other rights that might be claimed to  pertainto the implementation or use of the technology described in thisdocument or the extent to which any license under such rights might ormight not be available; neither does it represent that it has made anyeffort to identify any such rights.  Information on the IETF'sprocedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11.  Copies of claims ofrights made available for publication and any assurances of licenses tobe made available, or the result of an attempt made to obtain a generallicense or permission for the use of such proprietary rights byimplementors or users of this specification can be obtained from theIETF Secretariat.Esibov & Kwan                     BCP                           [Page 3]INTERNET-DRAFT   Dynamic Update of the TLD DNS Zones    22 February 2001The IETF invites any interested party to bring to its attention anycopyrights, patents or patent applications, or other proprietary rightswhich may cover technology that may be required to practice thisstandard.  Please address the information to the IETF ExecutiveDirector.9.  Full Copyright StatementCopyright (C) The Internet Society (2001).  All Rights Reserved.This document and translations of it may be copied and furnished toothers, and derivative works that comment on or otherwise explain it orassist in its implementation may be prepared, copied, published anddistributed, in whole or in part, without restriction of any kind,provided that the above copyright notice and this paragraph are includedon all such copies and derivative works.  However, this document itselfmay not be modified in any way, such as by removing the copyright noticeor references to the Internet Society or other Internet organizations,except as needed for the purpose of developing Internet standards inwhich case the procedures for copyrights defined in the InternetStandards process must be followed, or as required to translate it intolanguages other than English.  The limited permissions granted above areperpetual and will not be revoked by the Internet Society or itssuccessors or assigns.  This document and the information containedherein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THEINTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THEINFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."10.  Expiration DateThis memo is filed as <draft-esibov-dnsext-dynupdtld-00.txt>, andexpires August 22, 2001.Esibov & Kwan                     BCP                           [Page 4]