View Full Version : HOWTO: Editing /etc/hosts

November 6th, 2004, 01:32 AM
Here is a quick how to, to edit your /etc/hosts file.
The $ represents a line of code you may enter in a terminal.

Open /etc/hosts with your favorite text editor. Remember to use sudo.


Example: localhost.localdomain localhost

Replace the <IP> with the IP of your system. If your running DHCP do not worry about editing this file. To detect your IP address run
$ lsconfig Then browse for the connected interface (eth0, wlan0, etc)

Replace the <HOSTNAME> to your systems hostname.

To view current hostname:
$ hostname

To change hostname:
$ sudo hostname 'enterhostname'
(without quotes)

Domain Name
The domain name can be anything you like unless it must be resolv, which then you must use /etc/resolv.conf. But thats another issue i'll cover later! :o

Alias are simply another way to combine a set of arguments. When you create a hosts file, its simply creating a list of hosts on the network, or locally. Its much easier to understand if you kept the alias the same as the hostname. It saves a lot of trouble with debugging and troubleshooting. But you are free to use whatever you like.

That should help you out. Please comment!

November 6th, 2004, 06:35 AM
Nice. You can make shortcuts for webpages with alias www.google.com gType ctrl+L,g,enter in firefox to go to google.

December 1st, 2004, 11:40 PM
you can do the same more practically by giving a keyword to a bookmark, in firefox.
Just go to bookmars->manage bookmarks
and open the bookmark's properties, entering the keyword and
clicking OK.

this link describes more, quick searches, which in my opinion are great:

February 23rd, 2007, 05:19 AM
Would anyone know why this would not work on Edgy?

I'm trying to access my webserver in my LAN, however due to my firewall I cannot use the external address, I have to use my internal address to my DMZ.

I'd like to have my translation done like this HOST.DOMAIN = DMZ IP. It's very useful when looking at information posted on the web with the source on ur webserver.

victor@victor-laptop:~$ cat /etc/hosts localhost victor-laptop www.mysite.dyndns.org home www.google.ca g

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

The alias for google is also not working.

I also restarted my network and logged out and back in, but no doughnut..

sudo /etc/init.d/networking restart



July 7th, 2009, 01:59 PM
Related links:

Why does appear in /etc/hosts? (http://www.linuxquestions.org/questions/linux-networking-3/what-does-
Should /etc/hostname contain the whole FQDN? (http://lists.debian.org/debian-user/2007/09/msg00003.html)
More examples working with hostnames (http://www.linuxquestions.org/questions/slackware-14/hostname-fqdn-etchosts-setup-302189/)

What I can't find is a simple, complete best/standard practices guide on how to set the hostname for a laptop and for a box with a static IP and FQDN.

June 15th, 2010, 07:02 PM
Should I add my static IP address in the hosts file as well as the one I use on my local network?

Example: localhost mmpcubuntu mmpcubuntu

September 17th, 2010, 11:49 PM
The reason this line won't work: www.mysite.dyndns.org (http://www.mysite.dyndns.org) home

is because is a private ip address & www.mysite.dyndns.org (http://www.mysite.dyndns.org) has to resolve to a public ip address. To use www.mysite.dyndns.org (http://www.mysite.dyndns.org) as the FQDN you need to enter the router's public ip address & set the router to forward port 80 traffic to your private ip address. If it's not your network (meaning that your netadmin won't give you access to the router/firewall) you can just replace www.mysite.dyndns.org (http://www.mysite.dyndns.org) with mysite.localhost and use mysite as an alias. The easiest way to access your webserver from the inside, however, is to just enter localhost in the address bar if the server is on your machine, or enter the ip ( in the address bar if it's not. The result will be the same no matter how you address it from your browser. You'll see the same thing everyone else sees.