Re: BIND 9.9.8-S1 Release Notes (What's 'S' stands for?)

On Fri, Sep 18, 2015 at 12:07:22PM +0800, stutiredboy wrote: > BIND 9.9.8-S1 was released, but > what's 'S' stands for? > > I did not found any docs described this. > > Can this version be used on production environment? The -S suffix is for a

Re: Speeding up DNS change propagation

On Fri, Sep 18, 2015 at 2:35 PM, Danny Sinang wrote: > Hi, > > Our vendor is changing their FTP server's IP address tomorrow. > > 1. How can I tell how long their DNS change will propagate to us ? Whatever TTL you have cached when the vendor makes the switch is how long it'll

Re: BIND 9.9.8-S1 Release Notes (What's 'S' stands for?)

Thanks Evan. I can not found subscription version in: http://www.isc.org/downloads/. how can I got "BIND 9.9.8-S1"? Is "donate to isc" the right way? Thanks. 2015-09-18 14:11 GMT+08:00 Evan Hunt : > On Fri, Sep 18, 2015 at 12:07:22PM +0800, stutiredboy wrote: > > BIND 9.9.8-S1

Re: Speeding up DNS change propagation

As a follow-up to your answer for question #2, after my clearing the cache or restarting BIND, won't BIND find an old cache of "ftp.example.com" in the ".com" top level DNS server ? Regards, Danny On Fri, Sep 18, 2015 at 2:51 PM, John Miller wrote: > On Fri, Sep 18, 2015

Re: Speeding up DNS change propagation

The .com nameservers don't know anything about ftp.example.com; they just know the nameservers for example.com. So have no fear -- BIND will not cache an upstream response for ftp.example.com: you'll only hear about ftp.example.com from the example.com nameservers. Pretty much all upstream

Re: Speeding up DNS change propagation

Remember, however, that if you are clearing YOUR caches by restarting, everyone else around the world is still seeing the data with the original TTL still "in place". The right thing to do is to lower the TTL on the auth servers to an acceptable "outage" value before you make the change, wait for

Speeding up DNS change propagation

Hi, Our vendor is changing their FTP server's IP address tomorrow. 1. How can I tell how long their DNS change will propagate to us ? a. Do I just run dig a "ftp.example.com" and look for the TTL for that DNS entry ? b. Every time I run that command, the TTL is shrinking. How do I

Re: Speeding up DNS change propagation

On Fri, Sep 18, 2015 at 2:35 PM, Danny Sinang wrote: > Hi, > > Our vendor is changing their FTP server's IP address tomorrow. > > 1. How can I tell how long their DNS change will propagate to us ? > > a. Do I just run dig a "ftp.example.com" and look for the TTL for >