I got it! Thanks. Bret Charles Galpin wrote: > > The assumption is that if you want to do what you are describing below, > both client1 and client2 have entries in the server's hosts file, and had > a host block in the dhcp.conf to get them to always get that name/ip. > > Most of the tiem thought you don't care aboput the clients getting > different IPs (think windows PCs) because they just use there smb share > names when sharing resources. > > charles > > On Thu, 27 Jan 2000, Bret Hughes wrote: > > > > > > > Charles Galpin wrote: > > > > > > I guess I haven't explained it properly, but I'm not sure If I can do any > > > better than this. > > > > > > When the machine with the ethernet card having the mac address of > > > 00:e0:98:03:9d:7b requests an IP, the dhcp server will lookup the hostname > > > piglet.lhsw.com (where the dns server will look in the hosts file first > > > and in this case finds it is 192.168.1.6) and assigns it to that > > > machine/nic. If it cannot find this hostname's IP, it will assign one from > > > the pool (so you have to either have this name in your hosts file, or be > > > resolveable by dns some other way) > > I understand the fixed IP deal, its the resolving some other way that I > > am wondering about. Take for instance, this scenario. > > > > Dyamically assigined ip address client named client1. > > Another dynamically assigned address client named client2. > > from client1 : > > > > ping client2 > > > > Since both clients have dynamically assigned IP addresses, how does one > > get name resolution to work? I can't put it into a host file since I > > don't know the ipaddress and it is likly to change. Same with dns. Am > > I missing a tool that talks to DNS server somehow and tells it the newly > > assigned name-address pair? Is my understanding of the whole name > > resolution thing inadequate and I am worrying about something that will > > work magically? BTW magic is defined in this case as merely something I > > don't understand :) > > no I think you understand fine. I hope my explanation above clears up the > confusion > > > > > I suppose it makes since to have a fixed ip address for machines that > > supply services that don't change regularly and most machines on the net > > will use like file, database, mailservers and webservers but this sort > > of defeats my vision of what could/should be possible in a perfect > > world. > > I make all my linux boxes have fix IP's this way :) There are still enough > advantages having a central hosts file fo rthis to be worth the inital > setup. > > -- > 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
