Hostnames - What are they all about?

Solution 1:

These days, a system may have multiple interfaces, each with multiple addresses, and each address may even have multiple DNS entries associated with it. So what does a "system hostname" even mean?

Many applications will use the system hostname as a default identifier when they communicate elsewhere. For example, if you're collecting syslog messages at a central server, the messages will all be tagged with the hostname of the originating system. In an ideal world you would probably ignore this (because you don't necessarily want to trust the client), but the default behavior -- if you named all your systems "localhost" -- would result in a bunch of log messages that you wouldn't be able to associate with a specific system.

As other folks have pointed out, the system hostname is also a useful identifier if you find yourself remotely accessing a number of system. If you've got five windows attached to a systems named "localhost" then you're going to have a hard time keeping them straight.

In a similar vein, we try to make the system hostname matches the hostname we use for administrative access to a system. This helps avoid confusion when referring to the system (in email, conversations, documentation, etc).

Regarding DNS:

You want to have proper forward and reverse DNS entries for your applications in order to avoid confusion. You need some forward entry (name -> ip address) for people to be able to access your application conveniently. Having the reverse entry match is useful for an number of reasons -- for example, it helps you correctly identify the application if you find the corresponding ip address in a log.

Note that here I'm talking about "applications" and not "systems", because -- particularly with web servers -- it's common to have multiple ip addresses on a system, associated with different hostnames and services.

Trying to maintain name to ip mappings in your /etc/hosts file quickly becomes difficult as you manage an increasing number of systems. It's very easy to for the local hosts file to fall out of sync with respect to DNS, potentially leading to confusion and in some cases malfunction (because something tries to bind to an ip address that no longer exists on the system, for example).

Solution 2:

You could set every hostname to "localhost", but it's very handy to have alix@plato ~ $ in your command prompt when you manage machines over ssh. Managing servers remotely could become very confusing if you don't.

Having a correct FQDN is important for when you host a web server, or a mail server. These kinds of server applications like to know "who" they are running on.

For choosing a good naming scheme, I refer you to this very popular question .

A FQDN becomes useful only when it is meaningful to another computer. There are three levels to this:

• One computer on your local network has an entry in his hosts file that points to that machine
• You have a DNS server running on your local network and every local computer that uses it as a DNS server now knows plato by name.
• You register a domain name and now the whole world knows what machine the name plato.alixaxel.com points to.

When sending email or serving web pages to the outside world, the third one is the one you want to have. For most other cases, you can make do with a local DNS or even editing hosts files.

In that case, you can just make up a domain name (plato.alixnetwork could be fine as a FQDN) for use within your local network. The only added value of having the "alixnetwork" part (the domain name) is convenience when you have another local network you wish to distinguish it from.

Solution 3:

A basic overview. Hostname are just pointers; you might assign one specific one to be the hostname referenced by the machine, but it could have multiple. Some services, notable mail and HTTP rely on domain names to know where services should be located and how to get to them.

A long time ago, all these names (which again, are just pointers to IP addresses) were kept track of in a file called hosts. As the system grew they were unable to keep the file synchronized across all the relevant computer participating in the various interconnected networks. So the DNS system was invented. When you do a name lookup, it still checks the hosts file first, then the DNS system. Windows may also check other systems like WINS or NetBIOS.

When you put an entry in a hosts file, you are not assigning it to the computer. Assigning a hostname as the one used by the computer is done in the configuration files (on *nix systems) and System Properties in Windows systems (Windows system can also have NIC specific suffixes).

Entries in the hosts file, like the DNS system, are just a mapping from a hostname to an IP address. In order to use the hostname 'localhost' (there's nothing special about it, it's a hostname like all the rest) it must be mapped to the loopback interface (so it will always point to the local computer). To ensure this works, all computers come with this default mapping in their hosts file, but it could potentially be removed, if you didn't want to be able to use that hostname.

Further, as others have noted, it's very useful to assign a hostname to a computer. When connected to the computer, you can have it display its hostname when you login, or as your prompt, or any number of other places. This makes identifying the computer you're connected to easier. If you setup that hostname in DNS or put it in all the hosts files, you will be able to connect to the computer by referencing its hostname instead of having to know its IP address all the time. (Even more useful if the computer is using DHCP, as the address could change. If the computer updates DNS then the DNS record would point to the new IP address; you could still connect without knowing the new IP address because you know the DNS name).

There are many other uses of both hosts and DNS, but I suspect you've got more questions than answers if you read all this.