Domain Registrar Woes

[Python]

On Wed, 2005-11-16 at 18:18 -0500, Thomas Charron wrote:
>   Check this URL out!
>  
> http://www.aitsucks.com/cgi-bin/yabb2/YaBB.pl?num=1132147323
>  
>   They admitted it's their fault, thousands of .org domains went poof.
>  
>   Thomas

That's not how I read that link.  It could be that stuff was deleted in
the meantime.  The only postings now are from labrat reporting the same
kind of problem and the aitsucks administrator fanning the flames.

> 
>  
> On 11/16/05, Thomas Charron <twaffle at gmail.com> wrote: 
>         On 11/16/05, Python <python at venix.com> wrote: 
>                 On Wed, 2005-11-16 at 12:03 -0500, Thomas Charron
>                 wrote:
>                 The registry, PIR.Org insisted that I had to deal with
>                 the registrar, 
>                 AIT.
>          
>           Makes sense.  If you own a domain, in the end, regardless of
>         who you resold it thru, the domain is the registrars
>         responsibility.
>          
>         >   If it's paid up, which it appears to be, tell em you want
>         it fixed
>         > in the next 24 hours, or taken off hold in 24 hours, or you
>         A) Show up
>         > with machine guns,
>         Can I hire you to go with the guns. 
>          
>           Just post on slashdot that they run all windows..  ;-)
>          
>         AIT disagrees with PIR's assessment of the situation.  The
>         Registry
>         claims to have received a notice from us asking that several
>         hundred
>         domains be deleted.  That's not how AIT systems work;
>         deletions are a
>         manual process that cannot be executed en masse.
>          
>           Sounds like bluff off material to me.  Something screwed up
>         someplace, unless they claimed to recieve 'hundreds of
>         deletions'.  How do you manually request the deletion of
>         hundreds of domains?
>         
>         I realize this does nothing to alleviate your issue, but I
>         want you to
>         have an understanding of what's going on.  We have asked the
>         Registry to
>         restore the affected domains, but it refuses to admit
>         wrongdoing and 
>         insists on restoration fees before doing so.  Our fallback
>         position is
>         to register secondary domains that point to the main website
>         so affected
>         customers get relief.
>          
>           Technically, it sounds like someone screwed up either way.
>         Whoever you bought it thru has the financial responsibility to
>         fix it, regardless of the cost.
>          
>         So far as I know, the restoration fee is $6.  I'm quite
>         annoyed and have
>         told both sides that this is ridiculous.  Just bill us the $6
>         and put
>         the domain back on the root servers!
>         
>         No reply to that yet.  I was a bit sarcastic.  I may yet ask
>         you to 
>         supply the heavy fire power.
>          
>           Hehe, see above.
>          
>           Thomas
>         
> 
-- 
Lloyd Kvam
Venix Corp