|
There's nothing special about ntop - it simply uses
whatever name resolution is offered by the host (i.e. the /etc/resolv.conf
configuration) via the standard C library calls (e.g.
gethostbyip()).
To prevent the queue from growing too large, we cut it off
if there are 4K awaiting - this handles an intial burst when ntop starts up,
without wasting too much space if there is a DNS problem.
If name resolution fails - for whatever reason - then the
queue will build. If the problem is transient (gets fixed), then ntop will
work the queue and it will decrease. If the problem doesn't get fixed, it
will eventually max out the queue and issue the warning
message.
Sounds like you need to reboot your box - this cures all
kinds of ills.
-----Burton
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kiellerup Sent: Wednesday, March 22, 2006 4:26 PM To: [email protected] Subject: Re: [Ntop-dev] Ntop runs, but can't be reached from http Well, that might be the problem. I have no local
DNS for my eternal network on ETH2 yet. The resolv.conf has 2 external DNS
records on the ETH0. Do I need a internal DNS to make it work, or can
I somehow link to the external DNS?
The strange thing about it is that NTOP has been
running fine for about a month or so and suddenly makes these
errors?
- Thomas
|
_______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
