Date: Sat, 5 May 2001 12:16:58 +0930 From: Greg Lehey <grog@lemis.com> To: Michael O'Henly <michael@tenzo.com> Cc: freebsd-questions@freebsd.org, Rich Haney <rich@haneys.net> Subject: Re: What is the correct way to name my machine? Message-ID: <20010505121658.G67787@wantadilla.lemis.com> In-Reply-To: <01050417544600.02640@h24-69-46-74.gv.shawcable.net>; from michael@tenzo.com on Fri, May 04, 2001 at 05:54:46PM -0700 References: <Pine.LNX.4.30.0105042031410.2601-100000@home.haneys.net> <01050417544600.02640@h24-69-46-74.gv.shawcable.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 4 May 2001 at 17:54:46 -0700, Michael O'Henly wrote: > On Friday 04 May 2001 17:34, Rich Haney wrote: >> On Fri, 4 May 2001, Michael O'Henly wrote: >>> My internet access is provided via cable modem and DHCP. The result is a >>> default machine name that looks like "h123-123-123-123.gv.shawcable.net" >>> (those "123's" are actually my IP address). Well, in fact it's h24-69-46-74.gv.shawcable.net. Since this name appears in the headers (and *must* appear in the headers for your mail to get through to FreeBSD.org), there's not much point in trying to hide it. >>> 1. I'd like to change the default name to something else so that wherever >>> the above is used now, the new name would be used instead. What do I >>> update to make this change? > >> Unless they're going to delegate this IP to something where you >> can maintain it, they would need to make the change for you in their DNS >> as the authority for the netblock. Not likely. > > Sorry. I should have said this more clearly. I meant a local change only. If > my ISP wants to think of me as "h123-123-123-123.gv.shawcable.net", then > great. ;-) Hmm. I suppose that depends on what you want to do with the name. You can change the host name with (wait for it) hostname, but you still need to appear to the outside world as a name which will reverse map, and that's h24-69-46-74.gv.shawcable.net.. >>> 2. I'd like to create some aliases that may also be used to refer to the >>> machine. Under Linux, I'd do this once in /etc/hosts and the aliases >>> would become globally available. Is this true of FreeBSD as well? > >> Adding them to /etc/hosts doesn't make them globally available >> (unless, by 'globally available' you mean on the entire machine). >> /etc/hosts is strictly local to the machine. > > That's what I meant. Just wanted to be sure I wasn't overlooking > something if I updated /etc/hosts only. I can't think of any good reason to use /etc/hosts. On your own machine you don't need any IP addresses; if you have a local LAN, you should run a local name daemon. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010505121658.G67787>