Moving DNS out of non-cooperative provider

Michael Graff mgraff at
Mon Jun 18 16:17:11 UTC 2012

Eventually, if you have done the parent delegations (through where you register your zone) and have updated the new NS records to point only to the new spot, the old zone will only be used by that provider, and nowhere else.  So, if com points to the new set of name servers, and has the new set, 99.9999% of the world will be good.

The case exists where's users (say, mail servers, etc) may continue using their copy of the zone.  However, I doubt you care overly much about that unless is huge. 


On Jun 18, 2012, at 8:49 AM, Alexander Gurvitz wrote:

> Can someone enlighten me on the following scenario
> (I guess it's explained somewhere, but can't find the info.):
> was served by
> owner wants to move his domain to
> is not cooperating, and continues to serve
> 172800 NS
> (* and now serve
> 172800 NS
> Recursive resolver queried for every few minutes,
> and currently have 
> 45892 NS
> in it's cache. have TTL of 3600.
> Thus each hour queries,
> with each query gets new NS record, and... refreshes the NS TTL ?
> Will EVER query ?
> I'd be happy to know how BIND behaves, but also
> how other servers may behave in this case.
> Regards,
> Alexander Gurvitz,
> _______________________________________________
> Please visit to unsubscribe from this list
> bind-users mailing list
> bind-users at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bind-users mailing list