Humm... I didn't know that machimals (you know... half machine / half
animal) could get headaches... Interesting...
Kudos to the programmer who wrote the code to control your feeling/emotion
logic, Chuck.
:o)
-Mark

----- Original Message -----
From: "Charles Daminato" <[EMAIL PROTECTED]>
To: "Paul Chvostek" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, April 14, 2002 10:51 AM
Subject: Re: Child nameservers of a transferred domain


> Actually this is only partially true.
>
> When verisign is dealing with hosts that are NOT CNO names, they do not
> hold the IP address (any longer, anything you see is legacy and doesn't
> matter anyway) and changes are as much as "create/delete"
>
> If you have a .ca host record with a .ca domain and THAT'S transfered, we
> can accept control.
>
> Did I mention that host records give me a headache?
>
> Charles Daminato
> TUCOWS Product Manager
> [EMAIL PROTECTED]
>
> On Sun, 14 Apr 2002, Paul Chvostek wrote:
>
> > On Sat, 13 Apr 2002 [EMAIL PROTECTED] wrote:
> > >
> > > What will happen to the child nameservers of a domain name after we
> > > transfer the domain from another registrar to OpenSRS?
> >
> > On Sat, Apr 13, 2002 at 08:46:51AM -0500, Charles Daminato wrote:
> > >
> > > nameservers based on domains are moved over during the transfer
process
> >
> > Only for gTLD domains.  Last I heard, OpenSRS didn't have a mechanism
> > for grabbing control of host records from any registry except Verisign.
> > So if you have a .ca host record at Network Solutions, the only way you
> > can transfer it to OpenSRS is to have Network Solutions change the
> > hostname of the record to a gTLD domain, transfer that, and then change
> > it back to the .ca hostname once it gets to OpenSRS.  Maybe.  (Chuck,
> > will that work?)
> >
> > p
> >
> > --
> >   Paul Chvostek                                             <[EMAIL PROTECTED]>
> >   Operations / Development / Abuse / Whatever       vox: +1 416 598-0000
> >   it.canada                                            http://www.it.ca/
> >
> >
>


Reply via email to