bind not caching?

Joe Kattner joe at
Thu Dec 19 13:15:50 UTC 2002


You must take into account the Time To Live (TTL) of the records you are 
caching. Both sites you mention and have very short 
TTL's and will expire from your cache quickly. Take a look at them using 
dig and notice how long they have left before they expire, the second field 
shows the TTL in the answer section, noted in seconds. There is no 'fix' 
for you to perform, as the TTL is set by the owner of the record.


; <<>> DiG 9.2.2rc1 <<>>
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11390
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 4, ADDITIONAL: 0

;                   IN      A

;; ANSWER SECTION:            152     IN      CNAME                79      IN      A                79      IN      A                79      IN      A                79      IN      A                79      IN      A                79      IN      A                79      IN      A                79      IN      A

At 12/19/2002 08:00 AM, Ayotunde Itayemi wrote:
>       Hi All,
>       I have two Linux RH7.2 systems running BIND 9.2 I noticed though 
> that within minutes of losing my Internet Connection, the DNS servers 
> stops resolving. Even sites that have obviously been queried before 
> (google, cnn etc) don't resolve. What could be the problem? I work for an 
> ISP and once in a long while our Internet link goes down for some minutes 
> and this "no-resolution" problem happens. It looks as if the DNS servers 
> are not caching? What can I do to fix this problem?
>       Thanks. Tunde Itayemi.
>       Below is the relevant section of my config (false ip please!):
>       options {
>               directory "/namedint";
>               pid-file "/namedint/";
>               listen-on {; };
>               allow-query { validclients; };
>               allow-recursion { validclients; };
>       };

More information about the bind-users mailing list