Charles Oliver Wolff said:
> ....Win 98 machine that was once configured for DHCP address allocation kept
> looking for the DNS server, even though that was supposedly disabled via
> the networking control panel....
Well, I'll be distributing this one around the office to add to our growing
list of win head bangers.
> But not the problem! 5 minutes after my Linux server starts, diald dials
> out. Filter rules matched show me that it is looking to connect up with the
> various DNS root servers, and even after a connection is down, it won't
> hang up. When it is forced down, it immediately tries to dial out again.
> I've tried this, as per suggestion:
>
> Filters file:
> ignore tcp tcp.dest=tcp.domain
> ignore tcp tcp.source=tcp.domain
I think you might really need
ignore udp udp.dest=udp.domain,udp.source=udp.domain
to ignore nameserver to nameserver requests.
You can ignore all nameserver requests by setting some flag in
/etc/sysconfig/dialdcfg (is that the right filename - sorry at work we have a
different setup) which comes with the diald-config rpm. The file comments
regarding this are illuminating.
The FAQ section in the DNS-HOWTO is also worth looking at. In particular it
describes using ip-{up,down} (better in ip{up,down}-post i think) to replace
the root.hints file with an empty one to avoid the named timeout delay when
off line (dont get out of sync though).
What I dont like about any of this is that you end up having to bring the link
up and down manually.
It also a lot of trouble to go to for the marginal benefits of a
non-persistent nameserver cache. I would however like to hear of any other
benefits that named might offer to my very simple 2 machine home network. In
the meantime I'm back to /etc/hosts and a stock standard diald-config.
---
peta
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
