On 29 Feb 2000, Jake Colman wrote:
> It seems that it cycles through random 143x ports. I'm
> really not clear on what this is all about. How do I
> check whether the 'query-source address' line is
> functioning correctly and how do I confirm that named is
> using the named.conf file that I think it's using?
You want named to always use the same source port so it is
more predictable (and so that other programs which might
want to use ports in the 143x range aren't mistaken for
named).
> ED> If everything is fine with query-source address, then your named must
> ED> be sending some other chatter out on high ports. Perhaps there's
> ED> another option to stop that. I dont have that problem. Maybe try
> ED> commenting out the forwarders line in named.conf , and any other line
> ED> mentioning 207.198.222.7 .
> But why would it be chattering at all?
I don't know, I'm not an expert on named. All I can say is
mine doesn't do that. It may have something to do with the
forwarders lines, that's all I can say.
> In any event, I think I know what to do about all this.
> If I understand correctly, the goal here is to 1) ensure
> that named does not bring up the link spuriously and 2)
> ensure that diald is triggered by a udp packet (for named
> lookup) and not a tcp packet.
Yes.
> Even without the 'query-source address' line in my
> named.conf, my named does not seem to be overly verbose
> and my link does not go up unexpectedly. I guess that the
> entires in my standard.def filter are sufficient. To
> ensure that diald is triggered with a udp packet, I wrote
> an 'ip-goingdown' script that does an 'ndc restart'. Even
> though I mentioned in a prior post that an 'ndc restart'
> seems to trigger a connection, if I do it before the link
> goes down it does not matter. I realize true that an
> 'ip-goingdown' script is only executed when diald
> terminates the link itself and not when the remote side
> forces it to terminate. That should not be a problem,
> however, since, if the remote side terminates, diald
> automatically attempts to reconnect anyway.
That doesn't sound too bad, as long as named doesn't build
up too much of a cache in the time between ip-goingdown and
when the connection is severed. :-) I'd still try to get
to the bottom of why it's generating packets on port 143x,
though.
Ed
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
