🚀 go-pugleaf

Simple..

For the domain system to be effective everybody must agree on the names.  
This pretty much means a fairly centralized control of the names.

Earlier a totally centralized control was attempted, but this was found
to be unworkable.  The turn around time to get entries into the Official
File became horrendous and, I'm sure, the network bandwidth in transferring
the Official File from the Official Site to hither and yon was driving
the Official Site batty.

So now we have a distributed control of the naming tree.  In order to
establish a domain name at some level, say .com, you talk to the authority
at that level.  In this case hostmaster@nic.ddn.mil.  You tell he guy
and/or gal you want this name, say mmdf.com.  And they mumble for awhile
and decide you're ok and let you have it.  That's the hard part, now whenever
you want to add an entry into mmdf.com, say davids.mmdf.com, you just
add a record to the nameserver servicing your domain.  For instance
this amiga sitting at the other end of the table from my Unix PC (the
Unix PC is davids.mmdf.com) may well soon become known as amy.mmdf.com.

Right now amy is known as amy.funky-do-do.  That's because I was installing
UUCP & mail & Usenet on it, the software asked for a domain name and I
knew I'd better not use one of the legal domain suffixes.  So I made one up.
Weird sh*t, huh? :-)

All that'll be required is telling the guy at rutgers who takes care of my
domain file to add in another MX record...
-- 
<- David Herron; an MMDF guy                              <david@ms.uky.edu>
<- ska: David le casse\*'      {rutgers,uunet}!ukma!david, david@UKMA.BITNET
<-
<- Now arrived at a nameserver near you:  david@davids.mmdf.com