On Tue, Aug 17, 1999 at 05:48:56PM -0600, Ed Franks wrote:
> Hi,
>
> However, I am getting annoyed with diald incessantly
> dialing every few minutes.
> But, in the standard.filter file, I thought there
> were some rules for defeating nameserver traffic from
> causing it to dial?! If not, then what are rules 2 & 3
> for? What are rules 24 & 25 doing? It seems that
> 24/25 contradict 2/3? help!
>
rules 2/3 are for named transfers of their caches. This runs over tcp.
standard named calls use udp. furthermore, when named is running as a
client, looking up an address, it uses a non priviledged source port
( >1024 ) [at least the new version 8.x? does].
Think of it this way. When named uses tcp or connects from port 53, it
is performing an administrative task. otherwise it is doing work
directly on someone's or some machine's behalf. We ignore teh former
and bring up the line for the latter.
> FWIW, I do NOT run any named nor gated on my network.
> Each system has all of the other local net systems
> defined in its own host file.
>
You should run named on your network. It will solve or reduce your
problems. This should really be a FAQ. If you use diald, you ought to
run named.
--
Gyepi Sam --+-- Designer/Programmer --+-- Network/System Administrator
[EMAIL PROTECTED] --+-- http://www.praxis-sw.com/gyepi
You can get *anywhere* in ten minutes if you drive fast enough.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
