Moving DNS out of non-cooperative provider
WBrown at e1b.org
WBrown at e1b.org
Mon Jun 18 16:18:34 UTC 2012
Did you update your whois information to point to the name servers at
NEWprovider.net?
After this change is made and any cached data expires, the world will
query them (NEWProvider), with the exception of anyone that uses name
servers at OLDprovider.net who still thinks they are authoritative for
your domain.
Alexander wrote on 06/18/2012 11:49:36 AM:
> 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.
>
Confidentiality Notice:
This electronic message and any attachments may contain confidential or
privileged information, and is intended only for the individual or entity
identified above as the addressee. If you are not the addressee (or the
employee or agent responsible to deliver it to the addressee), or if this
message has been addressed to you in error, you are hereby notified that
you may not copy, forward, disclose or use any part of this message or any
attachments. Please notify the sender immediately by return e-mail or
telephone and delete this message from your system.
More information about the bind-users
mailing list