On Thu, 27 Jan 2000, Bret Hughes wrote:
> Are you using host files for the internal machine resolution? I use a
> local dns for my internal network so I don't have to change all the
> hostfiles every time I add a machine to the netowork. I think there is
> a DHCP tie to dns somehow I guess I need to read up.
Oh, I should have said that by running a caching only name server, and
telling the clients to use it, and having the search/resolve order to be
the hosts file first, you get to do exactly this. You have one hosts file
to maintain!. In addition, if you have clients that you would like to
always get the same IP, you would let them conenct once, get their mac
address and enter something like this to keep them gettign the same
name/ip.
host piglet {
hardware ethernet 00:e0:98:03:9d:7b;
fixed-address piglet.lhsw.com;
}
where in /etc/hosts I have
192.168.1.6 piglet piglet.lhsw.com
SO eaxch client does not have to have anything (except localhost) in their
hosts file. All dns queries go to your dns sevrer who has th emaster hosts
file, and asks your isp for anything it doesn't know how to resolve :)
hth
charles
> I was also thinking about the ip address conflict that I found last
> night and the fact that none of the logs showed anything was wrong. The
> windows box had a msg box indicating there was a conflict but nothing on
> any of the linux boxes. Is there some thing I can run that will check
> for ip address conflicts? I guess I could use tcpdump and check the arp
> calls for a different hardware address but that seems rather hit or miss
> and I am certainly not script guru.
using dhcp, you would definatley know if there was a confilict (but
wouldn't have any conflicts unless using a mix of static and dynamic
clients)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
