Moving DNS out of non-cooperative provider
tdiehl at rogueind.com
Mon Jun 18 16:19:12 UTC 2012
On Mon, 18 Jun 2012, 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.
It is not a question of how bind behaves. It is a question of how does
dns work. Bottom line is, setup nameservers with $NEWPROVIDER and change
the nameserver records with your registrar and move on. All will be well
when the ttl's time out.
Until the ttl's timeout, resolvers with the old nameservers cached will still
query them. Once the ttl's time out the new servers will be queried.
Hope this helps,
Tom Diehl tdiehl at rogueind.com Spamtrap address mtd123 at rogueind.com
-------------- next part --------------
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
More information about the bind-users