best practices dealing with lame delegations

[Kal Feher]

First perhaps you might want to quantify how bad this really is. Just
ignoring/filtering the log messages my suffice.

I guess it depends on why those lame delegations are there in the first
place. 

Could any of the lame delegations be your customers and represent a failure
in provisioning?

Perhaps some domain name delegation process has your server hardcoded/listed
as a default.

Is there some historical reason your server would have lame delegations from
a previous business activity? This might represent a failure to cut
over/away from that activity.

Fixing the above processes will be a more permanent although not necessarily
complete solution.

HTH

On 19/4/08 12:46 AM, "Ken" <ka_ at pacific.net> wrote:

> I'm looking for a way to deal with lame delegations.
> 
> There's an old script called lamers.sh that will email the hostmaster of
> a domain. I really don't want to automated any kind of email these days.
> 
> Also, the hostmasters in question are not likely to care, or understand
> a word of this.
> 
> I'm tempted to resolve the domain to a parked page full of google ads,
> or to resolve it to 127.0.0.1, or even to the registrar's NS - since
> they don't seem to care either.
> 
> None of these options really seems like a good idea, so I'm left
> thinking perhaps I should just stop logging lame delegations. Is that
> current best practices? :-(
> 
> What do you do when you are being swamped by a lame delegation?
> 
> Thanks,
> Ken
> 
> (remove the underscore in my email address if you are replying to me)
> 

-- 
Kal Feher