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. 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. Bret Charles Galpin wrote: > > I am no expert at this stuff. In fact i only just recently started runnign > a caching only name server myself (zero config needed btw other than > adding 127.0.0.1 to resolve.conf) - another thing I shoudl have done a > long time ago. > > But I can tell you what I did. > > You simply setup you dhcpd.conf to tell the dhcp client what nameserver(s) > to use. If it's your ISPs, use those. If you use your own namerserver, > give it as the primary and your isps as the sencondary/tertiary. > > But that's it. They behave no differently than if you filled those same > values into the clients settings. > > I have seen no problems, but have honeslty only tested this on a > connection that is always up - no idea how it works with > dialup/intermittent connections. > > charles > > On Thu, 27 Jan 2000, Bret Hughes wrote: > > > Too cool, no problems with DNS? How does naming resolution work. If > > too much to explain no worry I'll RTFM. > > > > Bret > > > > Charles Galpin wrote: > > > > > > It was really quite easy. I have no idea why I didn't do it sooner. Well, > > > I know why. If you have a simple network with a few computers it is really > > > not needed. As soon as you have more thasn a handfull of machines or you > > > start trying to swap a PC between 2 or more networks, it becomes > > > essential! > > > > > > I think all I did was install the dhcpd package, and read the dhcpd.conf > > > man page. It comes with a sample dhcpd.conf file which really > > > helps. Really you just have to understand a few basic concepts - It's job > > > is to listen for requests, and assign an IP (from some range), as well as > > > all the other stuff you would normally configure yourself like the domain > > > name, gateway, netmask etc. And all you do is describe these things in > > > dhcp.conf. Like everything else you can get pretty fancy if you want, but > > > you don't have to. > > > > > > On the client side the setup is as simple as setting the "get my IP > > > dynamically" checkbox. > > > > > > <OT> > > > In windows you can run 'winipcfg' to release and renew the lease at will > > > for testing so you don't have to keep rebooting :) It's also very handy if > > > you want to switch a running machine between two networks like I have been > > > doing lately - release the lease, unplug from one hub, plug into other, > > > renew lease - wallah - completely configured on other (dhcp based network) > > -- > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" > as the Subject.
begin:vcard n:Hughes;Bret tel;fax:918.587.0131 tel;work:918.587.0131 x-mozilla-html:FALSE url:www.elevating.com org:Elevating Communications Inc adr:;;PO Box 1323;Tulsa;OK;74101-1323;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Chief Solutionist/President x-mozilla-cpt:;19888 fn:Bret Hughes end:vcard
