home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.domains
- Path: sparky!uunet!news.mtholyoke.edu!jbotz
- From: jbotz@mtholyoke.edu (Jurgen Botz)
- Subject: Re: looking for "the answer"
- Message-ID: <Bun0Iy.27s@mtholyoke.edu>
- Sender: news@mtholyoke.edu (USENET News System)
- Organization: Mount Holyoke College
- References: <mstgil.716574450@sol>
- Date: Tue, 15 Sep 1992 20:49:46 GMT
- Lines: 28
-
- In article <mstgil.716574450@sol> mstgil@sol.acs.unt.edu writes:
- >OK, here's the question...
- > which is "the official name" for a host...
- > hostname or hostname.domain
- >
- >I tend to lean towards hostname.domain since it is more specific,
- >Kinda like is my "official name" Marc or Marc Philip Alexander Jordan St.-Gil.
- >The U.S. Gov. says it's the latter.
- >
- >So, does that mean that gethostname(2) should return host.domain?????
-
- My preference is also host.domain. The only drawback to this is that
- entries in various system files that specify access permissions (such
- as /etc/exports) get much longer (since the reverse lookups from IP#
- to hostname always return the primary name).
-
- Also, users who use the hostname in their prompt will want to do something
- like this: "set prompt="`hostname | cut -d. -f1`%" or get awfully long
- prompts (depending on how long your domain name is ;-)
-
- But generally it makes much more sense... the name of a host on the
- Internet is it's FQDN, and the short name is just an alias that's a
- convenience to users.
- --
- Jurgen Botz | Internet: JBotz@mtholyoke.edu
- Academic Systems Consultant | Bitnet: JBotz@mhc.bitnet
- Mount Holyoke College | Voice: (US) 413-538-2375 (daytime)
- South Hadley, MA, USA | Snail Mail: J. Botz, 01075-0629
-