[59093] in North American Network Operators' Group
(NSI) LAME-DELEGATION.ORG hijacking IP space ??
daemon@ATHENA.MIT.EDU (John Brown)
Sun Jun 15 00:34:57 2003
Date: Sat, 14 Jun 2003 22:34:29 -0600
From: John Brown <jmbrown@chagresventures.com>
To: nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu
could someone explain this
shorts# nslookup LAME2850.LAME-DELEGATION.ORG
Server: ns1.chagres.net
Address: 216.223.236.233
Aliases: 233.236.223.216.in-addr.arpa
Non-authoritative answer:
Name: LAME2850.LAME-DELEGATION.ORG
Address: 1.1.1.1
or this
shorts# nslookup LAME41178.LAME-DELEGATION.ORG
Server: ns1.chagres.net
Address: 216.223.236.233
Aliases: 233.236.223.216.in-addr.arpa
Non-authoritative answer:
Name: LAME41178.LAME-DELEGATION.ORG
Address: 4.3.145.66
shorts# nslookup 4.3.145.66
Server: ns1.chagres.net
Address: 216.223.236.233
Aliases: 233.236.223.216.in-addr.arpa
Name: lsanca1-145-066.biz.dsl.gtei.net
Address: 4.3.145.66
seems 4.3.146.66 is some DSL link in GTEI / BBN / Name today
if NSI is going to use this as a way to deal with lame zones, fine,
but how about using RFC 1918 space, or a public IP and a machine that
returns NXDOMAIN.....
instead of what looks like random IP allocations, some of which may
cause pain for others...
Hey, better yet, why not just learn how to DELETE host records from
a zone ???
