[21927] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: NSI policy on lame delagations

daemon@ATHENA.MIT.EDU (Jon Zeeff)
Tue Nov 24 09:25:34 1998

To: randy@psg.com (Randy Bush)
Date: Tue, 24 Nov 1998 08:57:37 -0500 (EST)
Cc: elezar@pfrc.org, nanog@merit.edu
In-Reply-To: <m0zi9xk-0008G5C@rip.psg.com> from "Randy Bush" at Nov 23, 98 08:20:28 pm
From: jzeeff@verio.net (Jon Zeeff)
Reply-To: jon@zeeff.com


How do you make sure that these get cleaned out after they fix the problem
and the name is in use?

> which has been lamely delegated to one of my servers, i just put in an
> authoritative zone for it with a short ttl soa and a wildcard mx
> 
> *    MX  0 some.schmuck.lame.delegated.to.the.host.name.
> 
> or the analogous PTR for in-addr zones.
> 
> it immediately stops any overload on my server and usually gets fixed
> fairly quickly, no muss no fuss.


home help back first fref pref prev next nref lref last post