[100160] in North American Network Operators' Group
Re: dns authority changes and lame servers
daemon@ATHENA.MIT.EDU (Jack Bates)
Thu Oct 18 18:02:32 2007
Date: Thu, 18 Oct 2007 16:40:56 -0500
From: Jack Bates <jbates@brightok.net>
To: NANOG <nanog@merit.edu>
In-Reply-To: <46998D43CA4FED489115621F79BDF684673C8A@gf-dc.GravityFree.local>
Errors-To: owner-nanog@merit.edu
Justin Scott wrote:
> We also have home-grown scripts that figure out whether a domain is
> delegated to us or not and flag the ones that aren't. In the case of
> the free service we flag them for two weeks and if they still aren't
> delegated to us after that period we disable them on the DNS servers but
> leave the domain in their account. In the case of the paid service we
> make a note of the status in the database but do not make any changes to
> the account (they're paying us, after all, to have it there). We don't
> do recursive lookups so it's not an issue (even though it's technically
> an RFC violation, if I remember correctly).
We use home-grown scripts to follow the NS trail and verify that we are listed
in some form or fashion. If we aren't, we handle the problem based on the
criteria. If the domain is listed elsewhere, we immediately remove and notify.
If the domain isn't listed in TLD, we notify yet hold the domain for I think 30
days before removing it; unless the status changes.
Jack