To:
Markus Stumpf <maex-lists-dns-ietf-dnsop@Space.Net>
Cc:
DNSOP WG <dnsop@cafax.se>
From:
Peter Koch <pk@TechFak.Uni-Bielefeld.DE>
Date:
Tue, 10 Dec 2002 13:56:40 +0100
In-reply-to:
Your message of "Tue, 10 Dec 2002 12:31:36 +0100." <20021210123136.F55309@Space.Net>
Sender:
owner-dnsop@cafax.se
Subject:
Re: DNS abuse handling/complaining strategies
Hi, > Currently this happens through > 0.138.20.68.in-addr.arpa. 2H IN NS ns3.dns.space.net. > 0.138.20.68.in-addr.arpa. 2H IN NS ns1.ameritech.net. > 0.138.20.68.in-addr.arpa. 2H IN NS ns2.ameritech.net. > 0.138.20.68.in-addr.arpa. 2H IN NS ns.space.net. that domain is currently delegated "perfectly lame", i.e. none of the servers is authoritative for it. In such cases, we set up a zone in "self defense", giving clear contact info in the SOA RR and an additional TXT RR. You may also wish to add a wildcard PTR (pointing to an existent name) with a high TTL. Usually this should reduce the query flood. -Peter #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.