nanog mailing list archives

Re: Anyone from NeuLeve.bizl listening?


From: "Stewart, William C (Bill), RTSLS" <billstewart () att com>
Date: Thu, 11 Dec 2003 19:37:09 -0600


I can see a couple of obvious approaches for getting Neulevel's attention

- Their web site lists two Registry Relationship Managers, one with popup contact info
        Ivor Sequeira - Senior Manager, European, African, and Middle Eastern Regions
        571-434-5776 ivor.sequeira () neulevel biz
                (That appears to be +1-571-434-5776 ...)

- Their whois entry for neulevel.biz lists
         +1.5714345757 as their phone number, fax +1.5714345758,
        and snailmail address list.
        http://www.whois.biz/whois.cgi?TLD=biz&WHOIS_QUERY=neulevel.biz&TYPE=DOMAIN&Search=Submit+Query

- They've got a snailmail address, you've got a lawyer and Fedex, 
        they've got a Nasty Letter....   Since the requests to use
        your DNS server were bogus, you could probably file a John Doe suit
        and do discovery on Neulevel, but a Nasty Letter is probably enough.

- They've got an online trademark dispute process.
        It's got pointers to ICANN dispute resolution mechanisms,
        which are more likely to get their attention than random email.
        Their entry point is stopsupport () neulevel biz
        Normally, if somebody registers that 
                annoying-little-spammer.com has nameserver 1.2.3.4,
        you'd be using this to complain that you own the name
        annoying-little-spammer.com, but you could try using it
        to complain that you own 1.2.3.4, and maybe even contend that
        since the registrant falsely listed you as the nameserver for the domain,
        that it's theft of service and you ought to be awarded ownership of the name.

- You might also drop a note to ICANN about the lack of a phone number
        on their web site and the lack of email responsiveness.

- Personally I like the suggestion that someone had that you
        start serving DNS for the fake names, either pointing to 127.0.0.3
        or to a CNAME pointing to Annoying-spammers-forged-their-DNS-again.com,
        which is some disposable address block on which you run a web site 
        and stub email server explaining that it's not your fault.





Current thread: