Hi!
Try installing the caching nameserver with logging enabled.
This has helped me tracing down who is looking up who. (Invalid host name
in the exports file caused nfs to take forever to start)
It is only the host making the query and the name is displayed, but its
usually telling enough.
I think that caching nameserver is a good idea, especially with logging.
If you install from redhat, you have to enable logging manually.
Put this into /etc/named.conf:
=============snip===
logging {
category queries { default_syslog; };
};
=============snip===
Gerzson
On Thu, 30 Sep 1999, Randall wrote:
>
> ----- Original Message -----
> From: Cliff Hemming III <[EMAIL PROTECTED]>
> To: Randall <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, September 30, 1999 10:06 PM
> Subject: Re: Dial up on boot
>
>
> > My guess is sendmail. He looks himself up at boot time. So does smbd and
> nmbd.
> > Disable diald at startup. If you have a process that takes longer than a
> few
> > seconds to start, it is could be the cause of your dns lookup.
> >
> > You can look at your message log or watch the boot process an see which
> process is
> > starting about the time of the dial up. You can try disabling it. You
> might also
> > try restarting each process one by one and see if it causes the link to go
> up.
> >
>
> Might it nmb that is causing the startup of the modem? Watcing the box boot,
> it always starts after nmb, of course diald and named have started about 10
> steps before.
>
> Randall
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
