Or, you could have some serious bottlenecks in your network which cause
problems with the name service requests getting through in time. I'd
check out "netstat" and look at collisions and network topology, esp. in
the neighborhood of the DNS server and amanda server. Beware of "dumb"
hubs and long thinnet segments with lots of nodes.
If collisions and topology look good, I would check for Denial of
Service attack on the DNS server(s)--I doubt this is the problem, but I
would still check anyway, especially if you're running BIND 4. The DoS
would most likely take the form of evil DNS packets or flooding.
Distributed Denial of Service (DDoS) seems to be the popular thing these
days, so the attack would probably come from several if not many
addresses such as a stacheldraht network rather than a single source
address.
----- Original Message -----
From: "John R. Jackson" <[EMAIL PROTECTED]>
Date: Tuesday, March 20, 2001 5:10 pm
Subject: Re: This is just weird!
> > How can a given client "sometimes" not be able to resolve the
> > tapehost?
>
> You're asking the wrong folks. Amanda just calls the system provided
> gethostby* routines. You need to look into how those work (i.e.
> whetherthey look at /etc/hosts, DNS, etc) and guess at why those
> are failing
> sometimes.
>
> My guess would be that you are using DNS and that the server just goes
> to sleep on occasion. And/or you don't have enough fallback
> servers to
> take up the cause when the primary does not respond.
>
> >Stan Brown
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
