Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!decwrl!palo-alto!vixie
From: vixie@palo-alto.DEC.COM (Paul Vixie)
Newsgroups: news.sysadmin
Subject: Re: How to sign-up a host in the .US Domain.
Message-ID: <3499@palo-alto.DEC.COM>
Date: 19 Jul 88 04:47:38 GMT
References: <8807141838.0.UUL1.3#948@Fernwood.MPK.CA.US> <3441@palo-alto.DEC.COM> <1096@maynard.BSW.COM> <1477@spdcc.COM> <4829@killer.DALLAS.TX.US>
Organization: DEC Western Research Lab
Lines: 25

In article <4829@killer.DALLAS.TX.US> wisner@killer.UUCP (Bill Wisner) writes:
# Part of the US domain information I was sent said something to the
# effect that if you can, you should probably register in a "real" domain.

It's definitely not being pushed as something to replace .COM/.EDU/etc.

It suits my home machine well, because I'm not COM or EDU or NET or MIL
and I never understood ORG (and I'm not an org, either, if it mattered).

Trouble is, my home machine would be in .SF.CA.US right now, but it could
move to .MPK.CA.US some evening soon, and it (and I) may move across the
street to .EPA.CA.US or across the creek to .PA.CA.US.

I want to name the machine in .BA.CA.US, since "BA" represents the area I'm
likely to live in no matter how many times I move across the street.

It ain't gonna fly, though.  Host.City.State.US, note "Host" and not "Domain".
If Geoff gets a second machine after Fernwood.MPK.CA.US, it'll be some other
thing in .MPK.CA.US, not inside .Fernwood.MPK.CA.US.  Or so I suspect.

Very bizarre.  Much needed and appreciated, but bizarre nonetheless.
-- 
Paul Vixie
Digital Equipment Corporation	Work:  vixie@dec.com	Play:  paul@vixie.UUCP
Western Research Laboratory	 uunet!decwrl!vixie	   uunet!vixie!paul
Palo Alto, California, USA	  +1 415 853 6600	   +1 415 864 7013