On 27 Feb 2000, Jake Colman wrote:
> Well, this may be the final problem. A central part of
> fixing the "lost packet" problem is to flush the named
> cache by doing a 'ndc restart' whenever diald drops the
> link. When I try this, however, the 'restart' always
> retriggers diald.
> Feb 27 11:31:25 firewall diald[19903]: Trigger: udp
> 207.198.222.7/53 192.168.0.100/1430
Hmmm, looks like your named is sending from port 1430, not
port 53. Make sure the query-source address line is
functioning correctly in your named.conf , and make sure
named is reading the correct conf file.
If everything is fine with query-source address, then your
named must be sending some other chatter out on high ports.
Perhaps there's another option to stop that. I dont have
that problem. Maybe try commenting out the forwarders line
in named.conf , and any other line mentioning 207.198.222.7
.
> ED> You've found the Achilles Heel of this workaround. nslookup won't
> ED> bring up the link if you point it to your local server. Use a server
> ED> option in .nslookuprc to point it elsewhere with a server directive
> ED> and it will correctly bring up the link to resolve all names except
> ED> those in your local net. It's really a bit of a quirk in nslookup,
> ED> to only try one server.
> I don't quite understand this. The 'server' option should
> be specified to point nslookup to one of my ISP's name
> servers? It will first check my local cache and, if not
> found, query my ISP?
No, the problem is that nslookup will use only one server.
It will not use all the servers mentioned in resolv.conf .
If you make that one server localhost, then nslookup will
talk to named on localhost which will probably not have the
information requested and will attempt to consult its peers.
Since named can't bring up the link, if the link is down it
will just sit there and eventually time out without
resolving the name.
So to be of any use, nslookup should be directed to a
nameserver on the internet, not on the local net. The only
drawback of this scheme is that nslookup will not be able to
resolve names on the local net ... but presumably you know
all those already anyway.
Ed
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
