This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] Followup to IANA TLD delegation problem
- Previous message (by thread): [dns-wg] Followup to IANA TLD delegation problem
- Next message (by thread): [dns-wg] Followup to IANA TLD delegation problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Matt Larson
mlarson at verisign.com
Wed Jun 15 15:50:06 CEST 2005
On Fri, 10 Jun 2005, Doug Barton wrote: > Thanks again for the opportunity to discuss these issues. I hope that the > group finds these answers satisfactory. We are of course happy to discuss > this in further detail if desired. In the interests of further explanation and clarification, I'd like to add some details of these events from VeriSign's perspective. First, to be clear, the VeriSign registry database that generates the root zone has supported multiple name server names (i.e., A records) with the same IP address for some time. There was never a technical restriction on multiple names with the same IP address during these events. On November 11, 2005, VeriSign performed a root zone edit as requested by an IANA Name Server Change template for the .FR ccTLD. The template requested name server NAME changes. A request to change the name DNS.PRINCETON.EDU. was included in the template. As a result of the execution of the change, the name DNS.PRINCETON.EDU did not exist and had been replaced by C.EXT.NIC.FR. Considering the template semantics, this was the correct result. It was not, however, the result that IANA desired. After VeriSign discovered the undesired results, DNS.PRINCETON.EDU was immediately re-added to the root zone by ADDing a new name server. In retrospect, it is apparent that the correct way to accomplish the original request would have been to request a new server ADD for C.EXT.NIC.FR, and then to delegate .FR to it while leaving the older name server DNS.PRINCETON.EDU untouched, and thus leaving delegations of BI, CH, HT, LI, and LU untouched. Below is an example of a preferred template semantic for a name server NAME change, followed by the original template as it arrived: New/GOOD: ************************************************************ CCTLD MODIFICATION TEMPLATE v.1.3 1. Purpose/Description.............: Add 7 name servers, add an IPv6 address for 1 name server and remove 6 name servers 2. Top-Level Domain Name...........: .fr 3. Sponsoring Organization [no change] 4. Administrative Contact [no change] 5. Technical Contact [no change] Primary Name Server [add primary nameserver] 6a. Primary Server Hostname.........: A.NIC.FR 6b. Primary Server Netaddress.......: 192.93.0.1 [remove NS1.NIC.FR from delegation] Secondary Name Server [add secondary nameserver] 7a. Secondary Server Hostname.......: B.NIC.FR 7b. Secondary Server Netaddress.....: 192.93.0.4 7c. Secondary Server Netaddress.....: 2001:660:3005:1::1:2 [remove NS2.NIC.FR from delegation] Secondary Name Server [no change] 7a. Secondary Server Hostname.......: C.NIC.FR 7b. Secondary Server Netaddress.....: 192.134.0.49 7c. Secondary Server Netaddress.....: 2001:660:3006:1::1:1 Secondary Name Server [add secondary nameserver] 7a. Secondary Server Hostname.......: A.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 193.51.208.13 [remove DNS.INRIA.FR from delegation] Secondary Name Server [add secondary nameserver] 7a. Secondary Server Hostname.......: B.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 128.105.2.10 [remove DNS.CS.WISC.EDU from delegation] Secondary Name Server [add secondary nameserver] 7a. Secondary Server Hostname.......: C.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 128.112.129.15 [remove DNS.PRINCETON.EDU from delegation] Secondary Name Server [add secondary name server] 7a. Secondary Server Hostname.......: D.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 204.152.184.85 7c. Secondary Server Netaddress.....: 2001:4f8:0:2::8 Secondary Name Server [add secondary name server] 7a. Secondary Server Hostname.......: E.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 193.176.144.6 REMOVE: NS-EXT.VIX.COM (204.152.184.64) from delegation ************************************************************ Old/BAD: ************************************************************ CCTLD MODIFICATION TEMPLATE v.1.3 1. Purpose/Description.............: Change the hostname for 5 name servers, add 2 name servers, add an IPv6 address for 1 name server and remove 1 name server 2. Top-Level Domain Name...........: .fr 3. Sponsoring Organization [no change] 4. Administrative Contact [no change] 5. Technical Contact [no change] Primary Name Server [change the hostname and add GLUE] 6a. Primary Server Hostname.........: A.NIC.FR 6b. Primary Server Netaddress.......: 192.93.0.1 [previous hostname was NS1.NIC.FR] Secondary Name Server [change the hostname, add IPv6 address, add GLUE] 7a. Secondary Server Hostname.......: B.NIC.FR 7b. Secondary Server Netaddress.....: 192.93.0.4 7c. Secondary Server Netaddress.....: 2001:660:3005:1::1:2 [previous hostname was NS2.NIC.FR] Secondary Name Server [no change] 7a. Secondary Server Hostname.......: C.NIC.FR 7b. Secondary Server Netaddress.....: 192.134.0.49 7c. Secondary Server Netaddress.....: 2001:660:3006:1::1:1 Secondary Name Server [change the hostname and add GLUE] 7a. Secondary Server Hostname.......: A.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 193.51.208.13 [previous hostname was DNS.INRIA.FR] Secondary Name Server [change the hostname and add GLUE] 7a. Secondary Server Hostname.......: B.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 128.105.2.10 [previous hostname was DNS.CS.WISC.EDU] Secondary Name Server [change the hostname and add GLUE] 7a. Secondary Server Hostname.......: C.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 128.112.129.15 [previous hostname was DNS.PRINCETON.EDU] Secondary Name Server [add secondary name server] 7a. Secondary Server Hostname.......: D.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 204.152.184.85 7c. Secondary Server Netaddress.....: 2001:4f8:0:2::8 Secondary Name Server [add secondary name server] 7a. Secondary Server Hostname.......: E.EXT.NIC.FR 7b. Secondary Server Netaddress.....: 193.176.144.6 REMOVE: NS-EXT.VIX.COM (204.152.184.64) ************************************************************ VeriSign has taken action to avoid this situation in the future. We have shared details of this incident with all relevant VeriSign personnel and alerted them that we should watch for name server NAME changes and not execute them literally. That is, a name server name "change" should not actually be a change, but we should interpret that a name server name change is really a name server name "add." We consider this a temporary fix for the ambiguous name server name change template. The long-term fix should be a less ambiguous name server name change template. To that end, we have opened a discussion with IANA regarding the format and semantics of the root zone change template. Matt -- Matt Larson <mlarson at verisign.com> VeriSign Naming and Directory Services
- Previous message (by thread): [dns-wg] Followup to IANA TLD delegation problem
- Next message (by thread): [dns-wg] Followup to IANA TLD delegation problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]