Moving DNS out of non-cooperative provider
JLightner at water.com
Mon Jun 18 16:34:51 UTC 2012
Just to verify - when you say "old provider" you're just talking about somewhere you had pointed your DNS records to and NOT the actual Registrar for the domain?
If it is the Registrar you have to make changes at the Registrar's site to change which DNS servers to use. If they're not being cooperative that might be problematical. (I wouldn't think they'd prevent you from changing which DNS servers to use for your domain - even the putzes that like to lock domains when you try to transfer to a registrar still allow you to control your DNS setup within their sites but I guess it's possible they could do it if they were also your hosting provider and didn't want you pointing away from their web servers.)
From: bind-users-bounces+jlightner=water.com at lists.isc.org [mailto:bind-users-bounces+jlightner=water.com at lists.isc.org] On Behalf Of Tom Diehl
Sent: Monday, June 18, 2012 12:19 PM
To: Alexander Gurvitz
Cc: bind-users at lists.isc.org
Subject: Re: Moving DNS out of non-cooperative provider
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
Athena(r), Created for the Cause(tm)
Making a Difference in the Fight Against Breast Cancer
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
More information about the bind-users