|
Hi,
My vote goes to /etc/hosts files method to startoff. Later you can do DNS setup as well if you are the system administrator there and dare to get your hands dirty. More Details follow....
Server Names to IP Translation is what can be achieved by multiple mechamisms:
1) simplest and easiest way when there are lesser no of machines - /etc/hosts in unixes. However, its hard to maintain as the no of servers/printers grows - ex change in name or ip address or addition of new servers etc - PRoblem - you need to change the /etc/hosts file on each machine in the network to know about the changes. It becomes impossible and too cumbersome everytime there is any change(add/delete/edit of name or ip addresses) since it needs to be made on all the servers and clients in the network.
This is why long ago DNS came into existence on the then "Internet". Domain Name Service (DNS) is a service that centrally manages the "server name" to "IP address" resolution and vice-versa(reverse DNS). Because of explosive growth of internet, DNS evolved and its currently a very complex branched hierarchy up in the cloud. However, you can have your own DNS server inside your company and manage your own internal private DNS network from a central admin console/interface.
BIND is a software which comes for most Unixes. you can configure DNS first. You can make your life more easier by supplying your desktops/laptops get DNS details along with dynamic IP using DHCP service. the flow of config:
1) configure DHCP service
2) configure DNS
3) supply DNS server details in DHCP server
4) boot clients using DHCP over network
5) upon booting client will get its own temporary IP from DHCP server and will also get the DNS details from the DHCP Server itself.
6) now you are ready to use server names and need not bother to remember IP addresses of all machines in your network.
PS - Easier said then done.
Regards,
rISK
 |