To:
DNSOP WG <dnsop@cafax.se>
From:
Måns Nilsson <mansaxel@sunet.se>
Date:
Tue, 10 Dec 2002 14:22:36 +0100
In-Reply-To:
<20021210123136.F55309@Space.Net>
Sender:
owner-dnsop@cafax.se
Subject:
Re: DNS abuse handling/complaining strategies
--On Tuesday, December 10, 2002 12:31:36 +0100 Markus Stumpf
<maex-lists-dns-ietf-dnsop@Space.Net> wrote:
> Sorry if this is not fully on topic, but I couldn't find any documents
> or a IMHO better place to ask.
NANOG or similar would probably suit you better.
> What would be the best strategy to get the problem fixed, i.e.
> misconfigured delegation and non-responsive contacts?
> - Add the zone and setup PTRs like we.are.clueless.ignorants.<isp-domain>
> - Write the RIR (i.e. ARIN) and ask them to remove the delegation for
> 20.68.in-addr.arpa? Would/should the RIR take (such) actions?
Write the RIR. That is a good start.
Other than that? AXFR the zone and start answering it. Then bill Ameritech
for secondary service. That ought to get wheels turning.
If they do not let you AXFR, just do this:
#!/bin/ksh
#
# $Id: force-reverse-axfr.sh,v 1.1 2002/05/21 13:29:00 mansaxel Exp $
#
# Call with the zone name (eg "125.36.192.in-addr.arpa") as argv(1)
# Needs DiG v9.
#
ZONE=$1
D=0
echo "; for zone $ZONE"
# Do zone APEX.
dig $ZONE SOA | grep ^$ZONE
# do bulk.
while [ $D -lt 256 ] ; do
dig $D.$ZONE PTR| grep ^$D.$ZONE
D=$(($D+1))
done
--
Måns Nilsson Systems Specialist
+46 70 681 7204 KTHNOC MN1334-RIPE
We're sysadmins. To us, data is a protocol-overhead.