Moving DNS out of non-cooperative provider

[Barry Margolin]

In article <mailman.1085.1340102760.63724.bind-users at lists.isc.org>,
 Tony Finch <dot at dotat.at> wrote:

> Mark Andrews <marka at isc.org> wrote:
> > In message <4FDF631A.4060405 at brandeis.edu>, John Miller writes:
> > >
> > > We've actually run into this before.  Once upon a time, RCN cable used
> > > to run some slave servers for us, but we've long since moved away from
> > > them, including zone transfers.  We yanked them from our registrar a
> > > long time ago, and life was good.  For whatever reason, RCN's still
> > > answering queries for brandeis.edu.
> >
> > And if there is another zone with a CNAME to a brandeis.edu domain
> > on those servers the clients will be getting old data.  As you have
> > no control over creation of CNAMEs in other zones I would suggest
> > that you send them a Cease and Decist notice if they are still doing
> > it.
> 
> Here's a tip for anyone running an open DNS hosting service: you can use
> "additional-from-auth no; additional-from-cache no;" to reduce problems of
> this kind.

Good ideas, but if you're a customer there's not much you can do about 
this.

-- 
Barry Margolin
Arlington, MA