Yes you are correct (AFAIK)
The current renewal implementation almost demands people start harvesting
the WHOIS DB to find expiry dates for domains in you RWI, as well as domains
registered by other RSP's so you can compete.
if RSP C manages to steal away 3 renewals of domains you have in your RWI,
then it only makes sense that to compete, you harvest the WHOIS and try and
steal away 4 renewals of domains from RSP C so you have 1 up on them. :)
Today users get hounded by thousands of registrars to "come here to register
your name" -- a year later they now get hounded by thousands of registrars
to "come here to renew your domain".
Domain name registration + renewals is such a saturated market, that no one
looks good anymore. :)
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Scott Goodman
> Sent: Tuesday, January 09, 2001 5:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: renewals + notification
>
>
>
> Ok. I just read some posts on the lists. I didn't realize this was
> actually the way it works. Not only will I look pretty dumb, but I might
> as well throw out any data I have for projecting income for this year. I
> assume domains renewed elsewhere will still remain is my RWI, so I'll
> have domains in there from which I may or may not *ever* receive further
> renewal income. Unless I'm paying real close attention and harvesting
> whois and whatnot I won't even *know* domains are getting renewed
> elsewhere, so I won't even ave the opportunity to try and save the sale.
> Am I correct about this?
>
> -scott
>
> dnsadmin wrote:
>
> > 1. RSP A registers the domain
> >
> > 2. One year passes
> >
> > 3. RSP B sells the domain owner on the idea of renewing with RSP B, and
> > collects $35 from the domain owner
> >
> > 4. RSP B uses the renew.cgi on RSP B's server
> >
> > 5. One domain year gets deducted from RSP B, and added to the
> expiry date of
> > the domain
> >
> > 6. RSP A is clueless through the whole procedure, and knows
> nothing. A few
> > days later (without checking the WHOIS DB) RSP A contacts the
> domain owner
> > telling them that their domain is up for renewal
> >
> > 7. Domain owner laughs at RSP A saying "I've already renewed
> with someone
> > else, don't you know that?"
> >
> > 8. RSP A looks dumb.
> >
> >> -----Original Message-----
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED]]On Behalf Of Scott Goodman
> >> Sent: Tuesday, January 09, 2001 2:53 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: renewals + notification
> >>
> >>
> >>
> >> Is this really the way it works? Seems unlikely to me...If someone uses
> >> my renewal interface I get the money, as my system charges the
> >> customer's card real-time, while some other RSP loses the
> domain credits
> >> from their account. Or does the renewed domain get moved to the other
> >> RSP's profile?
> >>
> >> -sg
> >>
> >> dnsadmin wrote:
> >>
> >>> Regarding the "renew anywhere" implementation of OpenSRS domains.
> >>>
> >>> Another RSP can renew or add domain years to any OpenSRS domain
> >>
> >> whether or
> >>
> >>> not it is in their profile.
> >>>
> >>> However, is the original RSP notified of the domain years
> >>
> >> added? If not, is
> >>
> >>> the only way to discover this information is by building a script to
> >>> cultivate the WHOIS database?
> >>>
> >>> It would make sense that the original RSP who registered the
> >>
> >> domain and is
> >>
> >>> currently "responsible" for the domain be part of the process.
> >>>
>
>
>
