Some sort of hosts I'd think too.
If you have a normal lan computer group you can use a URL, hostname, or even a FQDN in an address line of a browser if you have one of a few ways to resolve it. One is hosts file. It has been used for decades. Two is some dns on the lan. Kind of rare for a home setup. Can go wild with lmhosts or other windows way.
This is still the basic rules (but use linux terms.)
Host name resolution generally uses the following sequence:
The client checks to see if the name queried is its own.
The client then searches a local Hosts file, a list of IP address and names stored on the local computer.
NOTE: The Hosts file location depends on the operating system:
Windows NT %Systemroot%\System32\Drivers\Etc
Windows 95 <drive>\<Windows folder>
Windows for Workgroups <drive>\<Windows folder>
Windows 3.1 <drive>\<Windows folder>
MS-Client 3.0 <Boot volume>\Net
Lan Manager 2.2c Client <Boot volume>\Net
Where %Systemroot% is the folder in which Windows NT is installed, <drive> is the drive on which the OS is installed, and <boot volume> refers to a boot floppy disk or drive C.
A sample hosts file, Hosts.sam, is installed with the TCP/IP protocol showing the proper format.
Domain Name System (DNS) servers are queried.
If the name is still not resolved, NetBIOS name resolution sequence is used as a backup. This order can be changed by configuring the NetBIOS node type of the client."