On 3 Aug 1998, Jake Colman wrote:
> Hmmm.  I though that the diald FAQ says that you should NOT run named!  I had
> had a chaching name server set up (using the default caching name server RPM
> included with RH 5.1) but removed it because of the FAQ.  I am I
> misremembering (is that a word?) something?

The problem, as best I recall, is that with a caching server the initial
request may try to establish a connection (TCP) rather than being a
datagram (UDP) DNS request.  This can cause problems especially with a
link that has a dynamic IP address - that initial TCP session is doomed,
since it has an incorrect source IP address.  I believe there's a kernel
hack that attempts to deal with this, but from what I've read it is less
than perfect.  As I think I said, I'm lucky enough to have a fixed IP
address, so my knowledge of dealing with dynamic addresses is secondhand
and theoretical.

> In any case, what version of named or bind are you using?  How do you have it
> set up?  Can you point me to a FAQ?  My network is quite small.  A Linux box
> running Samba, diald, and with ability to connnect to ISP via PPP, and
> several Win95 boxes.  I use IP Masq to successfully masquerade the network
> over PPP, and use Samba to publish Linux-based mounts and to access Win-based
> mounts.

That's very like the home/office network here.  I'm using whichever
version of bind shipped with Debian 1.3.  There's a pretty good HOWTO for
bind/DNS, but the syntax, especially for the very important reverse (IP to
FQDN) tables is hard to get right.  It's not so much inherently hairy, I
think, as just consistently backwards: I didn't find it easy to keep
things wrong-way-around.  :-)

> I'll look at this solution but I think that is already the case.

One gotcha I've seen mentioned about hosts is that the first name really
needs to be the fully-qualified name; aliases follow that.  Aside from
that and typos, no problem!


-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to