Problem with 9.1.0 to 9.1.0 resolution with zero TTL

Kevin Darcy kcd at daimlerchrysler.com
Wed Feb 7 00:44:53 UTC 2001


Just as a point of reference, I have no problem resolving that name from
a 8.2.3 server. Note, however, that this 8.2.3 server is configured with
"fetch-glue no". I wonder if that has a bearing in some way (e.g. maybe
the A record is expiring from the cache while the nameserver is fetching
glue)?


- Kevin

paul at anastrophe.com wrote:

> I posted about this last week, and decided to do an empirical test.
>
> the story thus far: since upgrading all of my nameservers to 9.1.0, I
> - and my customers - can not reach www.businesswire.com. A dig fails
> to receive an answer. The businesswire folks have the TTL set to zero.
>
> So, just now i added a new record with zero TTL to my own zone --
>
> blink    0   IN A    216.174.195.155
>
> If i look it up locally, the answer comes through fine. From my other
> nameservers running 9.1.0, no answer is returned. From a nearby
> provider running 8.2.3-REL, no answer is returned. From a nearby
> provider running 4.9.7, I do get an answer back.
>
> Is this a bug, or...?
>
> --
> Paul Theodoropoulos                       Advanced TelCom Group, Inc.
> Downtime Is Not An Option                           Internet Services
> Work: http://www.atgi.net             Play: http://www.anastrophe.com
> =Opinions are my own of course, not necessarily those of my employer=





More information about the bind-users mailing list