To:
"'Antoin Verschuren'" <averschuren@vianetworks.nl>, ietf-provreg@cafax.se
From:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Date:
Thu, 23 Aug 2001 11:36:12 -0400
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: host transfers -- actually, out-of-zone-glue (fwd)
>-----Original Message----- >From: Antoin Verschuren [mailto:averschuren@vianetworks.nl] >Sent: Thursday, August 23, 2001 10:33 AM >To: ietf-provreg@cafax.se >Subject: RE: host transfers -- actually, out-of-zone-glue (fwd) > > >On Thu, 23 Aug 2001, Hollenbeck, Scott wrote: > >> What do you want to change that you can't change? There are no IP addresses >> associated with the hosts in the non-authoritative registry, so the only >> thing that's changeable is the name of the host itself. If that's what you >> need to do, just register the new host name(s) yourself with your registrar >> of choice and the hosts will be usable for your purposes. > >But then, our current host records are not changeable anymore to >ns1.vianetworks.nl because this hostname allready excists at this >registrar, but with another host handle. To be more precise, we want to >change: > >Host Handle: NS7389-HST >Nameserver: ns1.iae.nl >IP number: 212.61.26.34 > >into: > >Host Handle: NS7389-HST >Nameserver: ns1.vianetworks.nl >IP number: 212.61.15.8 If I'm reading this correctly, the real issue here is with the way one particular registrar manages hosts. They shouldn't attempt to create a new host object if the host you need to delegate to is already in the registry. If they would just accept the name change as you described above (they really don't need to collect address info as we're all well aware), all of the domains currently delegated to ns1.iae.nl would be delegated to ns1.vianetworks.nl and everything would work. <Scott/>