Michael wrote: > Tim Wescott wrote: > >> Does that mean that I need to make my host machine a fixed IP (currently >> I'm getting that from the router)? Or can I just call my router a >> "nameserver" in /etc/resolv.conf and have it work? >> > > You can't just call your router a "nameserver" to make it so any more than you > can call me a millionaire to make me financially comforted. > Thank you for the useful information, and for the reminder of the depths of my ignorance. Perhaps you could help out even more by illuminating the difference between what my router is doing when it assigns IP addresses, and what a nameserver is? > You may be able to configure the router (what is it anyway?) to always assign > thatthere the same IP address. In which case you could then add it to > /etc/hosts, as Rich demontrated, and have things work. > It's a Linksys (mumble mumble)54G. I'll update this when I get upstairs. > With the stability of home networks it is pretty, reasonably likely the IP > address for thatthere will never change anyway. So you can determine what the > address is and add it to /etc/hosts. > > If you go that route figure out where to put a reminder for yourself so that > when it breaks you know what you did and why. > If I'm going to play those games I may as well just assign the desktop with a fixed address. We live out in the boonies with enough power outages that the network gets a complete power-down and power-up several times a month in the winter; that would scramble the IP addresses each time and I certainly don't want to try to chase after it.
Going back a bit -- there's no way I can just ping by name? And all this discussion of modifying configuration files -- that happens on the client side, _not_ the host side, right? -- Tim Wescott Wescott Design Services Voice: 503-631-7815 Cell: 503-349-8432 http://www.wescottdesign.com _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
