Re: 127.0.1.1 in /etc/hosts, why?

On 08/10/2007 07:21 AM, Gerald Dachs wrote:
Quoting Derek Broughton <news@xxxxxxxxxxxxxx>:

Gerald Dachs wrote:

Quoting Casey Stamper <casey.stamper@xxxxxxxxx>:

I will admit my ignorance as to why that entry is in there but I DO
know that if you add mycomputer.mydomain mycomputer to the first line
as well, your name resolution speed increases and DNS lookups are much
faster.

Yes, I have read this too when I searched for a reason for this 127.0.1.1
IP. This makes it even more questionable. Is this a bug?
I have seen this only in Ubuntu and I have seen many Linux and Unix
installations.

Is which a bug? If domain name resolution is really slowed, I'd think
that's a bug. Using 127.0.1.1 is not a bug. It can be quite handy to use
different IPs for different ways to name the local machine, and 127.* is
always the local machine. I really don't see how using multiple 127
addresses should slow down my name resolution.

Slow name resolution is not my problem. That amavisd-new has now to
handle connects from 127.0.0.1 and 127.0.1.1 is my problem. Maybe
there are other services that have similar problems. From your post I
understand that this
IP 127.0.1.1 is not an ubuntu requirement, so I will change the hosts to
only use the 127.0.0.1 to make my configuration more easy.

Thanks
Gerald


I have always changed mine back to 127.0.0.1 thinking it was a bug.
However, now I find:

http://ubuntuforums.org/showthread.php?t=388765
#6: Re: Performance tip for Feisty users
Explanation why.

This is a fix for the new system that was started back in edgy where the
host name was split off to 127.0.1.1, the problem is that some
applications still look for the host name @ 127.0.0.1, so to keep those
applications happy and running smoothly you simple need to add the host
name where those applications expect it to be.

Also:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/94048
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/72341

So I guess I'll change mine back to 127.0.1.1 to stay with the standard(?).

My current hosts file (feisty) looks like this:

127.0.0.1 localhost name.sambasharedomain
127.0.0.1 name

My old one from Edgy had:

127.0.0.1 localhost name.sambasharedomain name.sambasharedomain

I have no idea why it had name.sambasharedomain twice.


--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Relevant Pages

  • Re: [Full-disclosure] Security-Assessment.com Advisory: Oracle JRE - java.net.URLConnect
    ... I got the idea of using Java Applet to achieve the ... multiple Host: headers which exploits the Apache feature mentioned above). ... But let's come back to your response - you mention about a bug from ... request between domains that resolve to the same IP address. ...
    (Full-Disclosure)
  • Re: Security-Assessment.com Advisory: Oracle JRE - java.net.URLConnection class - Same&#
    ... I got the idea of using Java Applet to achieve the ... multiple Host: headers which exploits the Apache feature mentioned above). ... But let's come back to your response - you mention about a bug from ... request between domains that resolve to the same IP address. ...
    (Bugtraq)
  • Re: Avian Flu, ToE and ID
    ... His point is that evolution should ... >> advantageous, in the latter generations, the ability to injure the host ... I've seen or heard it asserted that viruses and bug strains that start ... If there's one kid in a school who has ...
    (talk.origins)
  • link-local needed w/static IP and gateway?
    ... I've been trying to wrap my head around the differences between address resolution in IPv6 and IPv4 and I'm a bit confused by a real-world issue I'm seeing in a colo facility where we have dual-stack connectivity. ... I have no issues pinging other hosts on the subnet, but I find that address resolution for the router is spotty at best. ... If I'm pinging from an outside host, once I stop the ping from the host to the gateway, the external ping fails shortly thereafter. ...
    (freebsd-net)
  • Re: kblockd/1: page allocation failure in 2.6.9
    ... special situation on this host causing it. ... up to 200MB per second, and we never saw any kblockd message ... attached to the adaptec 29160 controller that runs with the aic7xxx modul. ... maybe the bug occurs in the aic7xxx ...
    (Linux-Kernel)