Probably stupid question, but

[Liam Proven]

On 28 August 2013 18:34, Gene Heskett <gheskett at wdtv.com> wrote:
> The network I grew up with is, and still is, hard coded in hosts files.
>
> I did try DHCP, 2 or 3 times here, but that instantly disabled my ability
> to ssh -Y shop, or ssh -Y lathe, lappy whatever is out there at the moment.
> I have asked on a list or two, how that can work with a DHCP driven
> network.  No one could tell me.
>
> So be a first, and tell me how. ;-)
>
> nfs, which is ip driven, but apparently uses hosts lookup for ip's as this
> is in my fstab
> shop.coyote.den         /net/shop       nfs     defaults        ext3    0
> 0
> lathe.coyote.den        /net/lathe      nfs     defaults        ext3    0
> 0
>
> that and ssh must work transparently.  So how is this done, assuming the
> router is the dhcp server?

Various ways.

* Lock particular PC's MAC addresses to particular IP addresses and
use a hosts file.

* Set up an internal DNS server

Q.v.

https://help.ubuntu.com/lts/serverguide/network-configuration.html#name-resolution

I used to run DHCP and DNS on my own fileservers. This is relatively
easy if you don't want anything fancy.

These days, I don't bother. I give important machines that I want
remote access to meaningful IP addresses (e.g. my fileserver is a 3GHz
P4, i.e. 3000 MHz, so I gave it 192.168.1.30 - the first 2 digits of
its clock speed). That's easy enough to remember.

You could also use multicast DNS, essentially the modern,
standards-based version of Windows-style broadcast name resolution:
https://help.ubuntu.com/community/HowToZeroconf



-- 
Liam Proven • Profile: http://lproven.livejournal.com/profile
Email: lproven at cix.co.uk • GMail/G+/Twitter/Flickr/Facebook: lproven
MSN: lproven at hotmail.com • Skype/AIM/Yahoo/LinkedIn: liamproven
Tel: +44 20-8685-0498 • Cell: +44 7939-087884