This has been solved, I missed that change last week about renewals
going into a pending state, (I saw it, for some reason I thought it
applied to the RWI only)
One idea for devel: perhaps the response in those circumstances should
be something OTHER than code 200 Renewal successful, perhaps
some other 20X code and "Renewal spooled" would be more accurate?
-mark
On Mon, 26 Mar 2001, Mark Jeftovic wrote:
>
> We have so far two domains that were deactivated and then renewed
> on March 23rd, yet neither one wound up back in the roots. When we
> manually renewed them both again today they were renewed, rather
> than getting the "Domain already renewed" error message.
>
> This leads us to believe something is up with de-activated domains
> that were renewed on March 23rd, anyone else?
>
> -mark
>
>
--
mark jeftovic
http://www.easydns.com
http://mark.jeftovic.net
