Message-ID: <BAY126-W35888B2856FC515F090303CA440@phx.gbl>
From: Sean Cavanaugh <millenia2000@hotmail.com>
To: <freebsd-questions@freebsd.org>
Date: Thu, 25 Sep 2008 07:09:50 -0400
Importance: Normal
In-Reply-To: <48db2995.BviIO9/dPuPT8Lza%perryh@pluto.rain.com>
References: <119697.2728.qm@web30808.mail.mud.yahoo.com>
	<2A271C1D-8157-41B3-A2B1-EF57ECFD81FE@mac.com>
	<48d9ca8c.RZOeanRudui/84j4%perryh@pluto.rain.com>
	<18650.20577.490303.567389@jerusalem.litteratus.org> 
	<48db2995.BviIO9/dPuPT8Lza%perryh@pluto.rain.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: My unqualified host name
Precedence: list


> Dunno about the OP, but my FreeBSD machines do not have nor need
> valid FQDNs because they sit behind a NAT firewall (and therefore
> do not have externally-identifiable IP addresses). I want hostname
> to simply return the unqualified host name (say, foo), not foo.com
> nor foo.uucp nor even foo.bogus. I don't need sendmail to handle
> anything but purely local traffic, such as the periodic reports to
> root, and it's just fine for it to identify itself simply as foo.
> We were able to do things like this back in the days of SunOS 4, so
> why should it be difficult to accomplish today? Indeed, why should
> it not be the default mode of operation when hostname returns an
> unqualified name?
 
 
Common practice to handle naming was to use "computer.network.TLD" such as "workstation1.freebsd.org" for the internet facing side of your network. Internal, if you were not running a split-horizon DNS setup would be to use "network.local" or simply "local" for the effect of "workstation1.freebsd.local" or "workstation1.local". therefore if for some strange reason it ever did get the FQDN outside the local network, nothing would be able to resolve it to make it an issue since there is no TLD of .Local on the internet but could easily be added to an internal DNS server for personal use.
 
 -Sean