Re: Moving DNS out of non-cooperative provider

We've just resolved this amicably--I'd missed the commercial.service@rcn.comaddress, but was contacted off-list by one of RCN's engineers, who read this thread and has removed our domain from their nameservers. He was quite helpful. No cease-and-desist letter needed--not by a long shot! John

Re: Moving DNS out of non-cooperative provider

On 19/06/12 11:18, Alexander Gurvitz wrote: >> >> 3282. [bug] Restrict the TTL of NS RRset to no more than that >> >>of the old NS RRset when replacing it. >>[RT #27792] [RT #27884] >> > > Just to clarify - does this rule applies also whi

Re: Moving DNS out of non-cooperative provider

Thanks to everyone for their help with this, and I didn't even start the thread! I definitely hadn't considered the issue of external CNAMES or their ramifications. RCN's now returning SERVFAIL for us, which is still a bit weird (most everyone answers with REFUSED for other people's domains),

Re: Moving DNS out of non-cooperative provider

In article , Tony Finch wrote: > Mark Andrews wrote: > > In message <4fdf631a.4060...@brandeis.edu>, John Miller writes: > > > > > > We've actually run into this before. Once upon a time, RCN cable used > > > to run some slave servers for us, but we've long since moved away from > > > them, in

Re: Moving DNS out of non-cooperative provider

Mark Andrews wrote: > In message <4fdf631a.4060...@brandeis.edu>, John Miller writes: > > > > We've actually run into this before. Once upon a time, RCN cable used > > to run some slave servers for us, but we've long since moved away from > > them, including zone transfers. We yanked them from o

Re: Moving DNS out of non-cooperative provider

> > 3282. [bug] Restrict the TTL of NS RRset to no more than that > >of the old NS RRset when replacing it. >[RT #27792] [RT #27884] > Just to clarify - does this rule applies also while replacing parent NS records with (more credible) ch

Re: Moving DNS out of non-cooperative provider

Mark, > 3282. [bug] Restrict the TTL of NS RRset to no more than that >of the old NS RRset when replacing it. >[RT #27792] [RT #27884] "TTL of the old NS RRset" here means the current "remaining" TTL, or the original TTL value as recei

Re: Moving DNS out of non-cooperative provider

On 06/19/2012 04:18 AM, Barry Margolin wrote: Didn't this used to be a problem? When the caching server queries the cached nameservers, the response would include the old NS records in the Authority section. The caching server would then replaced the cached NS records with these records, reset

Re: Moving DNS out of non-cooperative provider

In message , Barry Mar golin writes: > In article , > Mark Andrews wrote: > > > In message <4fdf631a.4060...@brandeis.edu>, John Miller writes: > > > Hi Alexander, > > > > > > We've actually run into this before. Once upon a time, RCN cable used > > > to run some slave servers for us, but we

Re: Moving DNS out of non-cooperative provider

In message , Barry Mar golin writes: > In article , > Phil Mayers wrote: > > > On 18/06/12 16:49, Alexander Gurvitz wrote: > > > > > with each query gets new NS record, and... refreshes the NS TTL ? > > > > No, that's not how TTLs work. They always count down. > > Didn't this used to be a pr

Re: Moving DNS out of non-cooperative provider

In article , Mark Andrews wrote: > In message <4fdf631a.4060...@brandeis.edu>, John Miller writes: > > Hi Alexander, > > > > We've actually run into this before. Once upon a time, RCN cable used > > to run some slave servers for us, but we've long since moved away from > > them, including zo

Re: Moving DNS out of non-cooperative provider

In message <4fdf631a.4060...@brandeis.edu>, John Miller writes: > Hi Alexander, > > We've actually run into this before. Once upon a time, RCN cable used > to run some slave servers for us, but we've long since moved away from > them, including zone transfers. We yanked them from our registra

Re: Moving DNS out of non-cooperative provider

In article , Phil Mayers wrote: > On 18/06/12 16:49, Alexander Gurvitz wrote: > > > with each query gets new NS record, and... refreshes the NS TTL ? > > No, that's not how TTLs work. They always count down. Didn't this used to be a problem? When the caching server queries the cached namese

Re: Moving DNS out of non-cooperative provider

In message <4fdf5396.7000...@imperial.ac.uk>, Phil Mayers writes: > On 18/06/12 16:49, Alexander Gurvitz wrote: > > > with each query gets new NS record, and... refreshes the NS TTL ? > > No, that's not how TTLs work. They always count down. Which is because most for most queries there isn't a

Re: Moving DNS out of non-cooperative provider

Hi Alexander, We've actually run into this before. Once upon a time, RCN cable used to run some slave servers for us, but we've long since moved away from them, including zone transfers. We yanked them from our registrar a long time ago, and life was good. For whatever reason, RCN's still

Re: Moving DNS out of non-cooperative provider

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2012 12:19 PM, Tom Diehl wrote: > 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.OLDpr

RE: Moving DNS out of non-cooperative provider

ner=water@lists.isc.org] On Behalf Of Tom Diehl Sent: Monday, June 18, 2012 12:19 PM To: Alexander Gurvitz Cc: bind-users@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

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 coo

Re: Moving DNS out of non-cooperative provider

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 f

Re: Moving DNS out of non-cooperative provider

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

Re: Moving DNS out of non-cooperative provider

On 18/06/12 16:49, Alexander Gurvitz wrote: with each query gets new NS record, and... refreshes the NS TTL ? No, that's not how TTLs work. They always count down. Will ns.isp.com EVER query ns.NEWprovider.net ? Yes, when the TTL has expired

Moving DNS out of non-cooperative provider

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 1728