On Tue, 2004-06-08 at 11:31, Petter Reinholdtsen wrote: > [Steve Langasek] > > See other responses for the fix for this; but, er, why would you want > > the canonical name for 127.0.0.1 to be anything other than "localhost" > > anyway? That just invites confusion, IMHO. > > Not only that. It break ssh X forwarding because the xauth key will > be wrong. > > IP 127.0.0.1 should only map to localhost, and not to the hostname if > the host is connected to the net. No, it will not. The resolvers stop at the first resolution. Having something like: 127.0.0.1 localhost.localdomain localhost 127.0.0.1 somenode.somedom.com somenode Will not do what you are talking about. BUT having: 127.0.0.1 somenode.somedom.com somenode 127.0.0.1 localhost.localdomain localhost Will cause all kinds of havoc. Including forwarding. Make sure you understand the infrastructure before you answer others. -- greg@gregfolkert.net REMEMBER ED CURRY! http://www.iwethey.org/ed_curry Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup
Attachment:
signature.asc
Description: This is a digitally signed message part