Date: Thu, 31 Mar 2005 17:16:34 -0500 From: Charles Swiger <cswiger@mac.com> To: Jonathan Arnold <jdarnold@buddydog.org> Cc: freebsd-questions@freebsd.org Subject: Re: Setting up network Message-ID: <1eddeb2755e7d2aacb065a2988396857@mac.com> In-Reply-To: <d2hrd9$e88$1@sea.gmane.org> References: <d2hrd9$e88$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 31, 2005, at 4:52 PM, Jonathan Arnold wrote: > Something I've never been able to figure out. When installing a > new machine, and you come to the "Network Configuration" dialog, > what do you put in for the Host: and Domain: if it is a machine > on an internal network (ie., 192.168.1.149)? Does it matter? > Just give it a simple hostname and be done with it? Make something > up? If you're using DHCP via one of the ubiquitous broadband firewall/gateway thingies from Linksys or D-Link or whoever, it really doesn't matter. However, most people like to give their machines a name, anyway, even if they don't have a domain to attach it to. You might want to get your own domain, in which case you control the names in it, or one can use dyndns.org or one of the similar sites to obtain a reversible hostname in a domain like homeip.net, even when using a dynamic IP. "Making stuff up" is ok, so long as you don't make stuff up that conflicts with properly configured names. Pretending to be a host in a domain you don't belong to is considered impolite at best, and if you have a local config problem than ends up generating errors or messages sent to the real host (think bounced mail), you will not thrill whoever it is that has to clean up the mess.... -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1eddeb2755e7d2aacb065a2988396857>