Moving DNS out of non-cooperative provider
mgraff at isc.org
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 example.com has the new set, 99.9999% of the world will be good.
The case exists where oldprovider.net's users (say, mail servers, etc) may continue using their copy of the zone. However, I doubt you care overly much about that unless oldprovider.net 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.):
> example.com was served by ns.OLDprovider.net
> example.com owner wants to move his domain to ns.NEWprovider.net
> oldprovider.net is not cooperating, and continues to serve
> example.com 172800 NS ns.OLDprovider.net
> (*.gtld-servers.net and ns.newprovider.com now serve
> example.com 172800 NS ns.NEWprovider.net)
> Recursive resolver ns.isp.com queried for www.example.com every few minutes,
> and currently have
> example.com 45892 NS ns.OLDprovider.net
> in it's cache. www.example.com have TTL of 3600.
> Thus each hour ns.isp.com queries ns.OLDprovider.net,
> with each query gets new NS record, and... refreshes the NS TTL ?
> Will ns.isp.com EVER query ns.NEWprovider.net ?
> I'd be happy to know how BIND behaves, but also
> how other servers may behave in this case.
> Alexander Gurvitz,
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> bind-users mailing list
> bind-users at lists.isc.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users