At 10:37 PM 3/9/02 +0000, Scott C. Best wrote:
>Michael:
>
> Heya. Each of the LAN machines gets a DHCP lease
>from the DS box, with the DS box indicated as the DNS
>server. Only the DS box has the /etc/hosts entries.
> For example, in the /etc/hosts file it reads:
>
>192.168.123.1 pc.private.network pc1
>192.168.123.2 winnt.private.network winnt
>
> I can see my WinNT Box (at .2) query the DS box
>for a reverse-lookup (PTR?) for 1.123.168.192, and I cannot
>see that the DH box replying with "pc.private.network".
>
> Hope this helps clarify.
Clear as a bell, now. Entries in /etc/hosts are useless for DNS; they get
used only for *local* resolution on the host (and not always even then; MTAs
are particularly bad about this).
Not sure if there is a way to provide local-resolution information to
dnscache directly, since it is designed to act as a forwarder, and you're
presumably forwarding to off-LAN nameservers that don't know anything about
your NAT'd machines.
The only ways I know to get around this are:
1. Have an /etc/hosts file (or Windows or Mac equivalent)
on each workstation, so they can resolve LAN names
and addresses without using DNS.
2. Run a real nameserver (BIND, I suppose, if tinydns won't
serve the purpose) on the LAN and have all hosts
use it to resolve names and addresses.
I'd imagine tinydns will do this, as long as you provide it with suitable
zone files (I'm using BIND terminology here, but tinydns must have an
equivalent) both for name lookup -AND- for reverse lookup.
I do a mix of the two here, and it's worked nicely for eons now. But my LAN
is mostly Linux machines, with only a sprinking of WinXX clients.
[old stuff deleted]
--
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
