Date: Tue, 12 Sep 2000 22:45:19 -0400 From: Peter Radcliffe <pir@pir.net> To: freebsd-stable@freebsd.org Subject: Re: Anyone having dial-up problem with sendmail 8.11.0 ? (FIXED) Message-ID: <20000912224519.A21064@pir.net> In-Reply-To: <20000912214431.D22846@speedy.gsinet>; from Gerhard.Sittig@gmx.net on Tue, Sep 12, 2000 at 09:44:31PM %2B0200 References: <20000912092221.A29216@carroll.com> <200009121419.e8CEJZh12561@greatoak.home> <20000912214431.D22846@speedy.gsinet>
next in thread | previous in thread | raw e-mail | index | archive | help
Gerhard Sittig <Gerhard.Sittig@gmx.net> probably said: > > 127.0.0.1 localhost greatoak.home > > I had > > 127.0.0.1 localhost myname.my.domain > > not exactly this but this is the idea. > > It's generally considered a Bad Idea(TM) anyway to have any other > name assigned to 127.x.x.x but localhost. Just don't do so and > assign a "real" address to your NIF and name your machine > appropriately. Even if you don't get official IPs from ARIN and > friends, RFC1918 has plenty of them for your toying ... That isn't entirely true. As long as the first entry on the line is "localhost", everything will still work as expected. On any mobile machine I have that may or may not have real (or RFC private) addresses to use at any given time I put an entry for the name of the machine on the localhost line so it can resolve it's own name when not connected. I also dislike fully qualified node names, so just use the short form. On a laptop that may connect to someone's internal RFC private network and use DHCP you can't rely on any address space being legitimate for a "private" interface or name on a mobile machine. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000912224519.A21064>