Anyone from NeuLeve.bizl listening?
hrlinneweh at sbcglobal.net
Fri Dec 12 05:54:03 UTC 2003
Looks sane to me once I resolved the name
Dns resolved neulevel.biz to 184.108.40.206
[IPv4 whois information on 220.127.116.11 ]
[Query Origin: Main Whois Query ]
OrgName: NeuStar, Inc.
Address: 45980 Center Oak Plaza
Address: Network Operations Center
NetRange: 18.104.22.168 - 22.214.171.124
NetType: Direct Allocation
TechName: Thomas, Mark
TechEmail: mark.thomas at neustar.com
OrgTechName: Network Engineering
OrgTechEmail: wan.engineering at neustar.biz
# ARIN WHOIS database, last updated 2003-12-11 19:15
# Enter ? for additional hints on searching ARIN's WHOIS database.
"Stewart, William C (Bill), RTSLS" <billstewart at att.com> wrote:
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 at 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.
- 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 at neulevel.biz
Normally, if somebody registers that
annoying-little-spammer.com has nameserver 126.96.36.199,
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 188.8.131.52, 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NANOG