The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <>
To: Henry Bent <>
Cc: The Eunuchs Hysterical Society <>
Subject: Re: [TUHS] 4.3 BSD network name resolution
Date: Sat, 29 Jan 2022 18:02:20 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Jan 29, 2022 at 05:08:32PM -0500, Henry Bent wrote:
> > gettable uses flat files to map names to numbers.  It hasn't existed in
> > probably 30+ years, and I can't even imagine how large the files it creates
> > would be for the modern internet.

This brings back memories.

Way back when I was on the MIT Network Group[1], I wrote a program
which translated a file in HOSTS.TXT format into a DNS zone file for
BIND, since originally the HOSTS.TXT format file (stored in RCS for
source control) was the source of truth for IP address assignments at
MIT.  Later on, the authoratative source was the Moira[2] server,
which stored the information in an Oracle database, but the nightly
extract from the database was still done in a HOSTS.TXT format, which
then got translated into a zone file and distributed to MIT's DNS

It's quite possible, Moira DCM extract to the HOSTS.TXT file is still
in use today; MIT is still using Moira, although there is a web front
end that I suspect most of the admins are using these days, instead of
the CLI or Curses interfaces.  (The hard core Moira admins or
developers would occasionally need to do surgery by accessing the
Oracle database directly; that's how I first learned SQL.  :-)


						- Ted

  reply	other threads:[~2022-01-29 23:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 21:48 Will Senn
2022-01-29 21:56 ` Henry Bent
2022-01-29 22:08   ` Henry Bent
2022-01-29 23:02     ` Theodore Y. Ts'o [this message]
2022-01-29 22:13 ` Warner Losh
2022-01-29 22:25   ` George Michaelson
2022-01-29 22:35     ` Erik E. Fair
2022-01-29 22:59 ` Clem Cole
2022-01-29 23:24   ` Phil Budne
2022-01-30  0:09 ` Jeremy C. Reed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).