| 1 |
> > Chad Huneycutt wrote: [Sun Oct 07 2001, 06:46:30PM EST] |
| 2 |
> > > I have the entry |
| 3 |
> > > 127.0.0.1 localhost localhost.localdomain |
| 4 |
> > > |
| 5 |
> > > in my /etc/hosts files, and a 'ping localhost' fails. I am pretty sure |
| 6 |
> > > that syntax is correct. Anyone see the problem. |
| 7 |
> > |
| 8 |
> > Do you have the lo interface up? I think all you need to do is |
| 9 |
> > |
| 10 |
> > ifconfig lo up |
| 11 |
> |
| 12 |
> maybe your .localdomain is your problem ... do you have a nameserver |
| 13 |
> for localdomain ?!? and it is not common to define localhost.localdomain. |
| 14 |
> |
| 15 |
> cya |
| 16 |
> |
| 17 |
> Holger |
| 18 |
|
| 19 |
|
| 20 |
Note, it is *incorrect* to list localhost before localhost.localdomain. The |
| 21 |
FQDN needs to be first, followed by any aliases you want to use. |
| 22 |
|
| 23 |
Ie., this is wrong: |
| 24 |
127.0.0.1 localhost localhost.localdomain |
| 25 |
|
| 26 |
It must be done thusly: |
| 27 |
127.0.0.1 localhost.localdomain localhost |
| 28 |
|
| 29 |
Another common mistake is to list your real hostname in the 127.0.0.1 |
| 30 |
record. Ie, if your hostname is 'pluto', then dont do this!: |
| 31 |
127.0.0.1 ..... pluto |
| 32 |
|
| 33 |
Theres nothing wrong with defining localhost.localdomain though. In fact |
| 34 |
its done a lot, mostly out of tradition, to serve as a placeholder. But the |
| 35 |
order issue is important. |
| 36 |
|
| 37 |
Cheers |
| 38 |
-- |
| 39 |
Donny |
Archives