Problem with Caching Name Server

[Andrew Poling]

In article <13624 at boulder.Colorado.EDU> grunwald at foobar.colorado.edu writes:
>
>Following the Ultrix users guide, I set my host up as a caching name
>server; this appears to work well, and nslookup appears to be telling
>me that I'm using my own named.
>
>However, it appears that the local named always consults a higher
>level server; this is fine, except when that server (or a gateway) is
>down.  Operationally, what happens is that when booting (say, after a
>power outage), my host hangs for a long time. At first, I thought this
>was a YP problem; well, it wasn't. The problem was that resolver calls
>to named was eventually timing out & then /etc/hosts was being used.

Your authorative server may be using short ttls.  While you may have that
data in your cache, it also may be stale.  If it's stale, BIND won't use it.

I 
did
too
say
more
than
I
quoted!!!

-Andy


Andy Poling                              Internet: andy at gollum.hcf.jhu.edu
Network Services Group                   Bitnet: ANDY at JHUVMS
Homewood Academic Computing              Voice: (301)338-8096    
Johns Hopkins University                 UUCP: mimsy!aplcen!jhunix!gollum!andy