The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Aharon Robbins <arnold@skeeve.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Directory services in early Unix networks?
Date: Wed, 7 Nov 2018 12:15:32 -0500	[thread overview]
Message-ID: <CAEoi9W5bzit9y7oew9UCCHn_QHjFa+PCRe_LJPqF80kFUje+Tw@mail.gmail.com> (raw)
In-Reply-To: <201811070905.wA795wxP017303@freefriends.org>

[-- Attachment #1: Type: text/plain, Size: 2577 bytes --]

On Wed, Nov 7, 2018 at 4:05 AM <arnold@skeeve.com> wrote:

> Dan Cross <crossd@gmail.com> wrote:
> > What was the introduction of DNS into the mix like? I can imagine that
> that
> > changed all sorts of assumptions about failure modes and the like.
>
> I'm not sure what you're asking.


Sorry, this was indeed vague.

Ron alluded to what I was asking about; namely, what were the circumstances
that gave rise to the creation of DNS in the first place? I imagine an
unwieldy HOSTS.TXT file being FTP'd daily combined with a linear scan (or
an expensive step to create a DBM file or something) had a lot to do with
it.

When DNS came along, it became
> a matter of editing /etc/nsswitch.conf to include dns as one of the
> options along with files and yp/nis.  I think the average user didn't
> see any big difference since all the apps (ftp, telnet) just went
> through gethostbyname().
>

This doesn't mesh with my memory. I recall building BIND from source and
having to rebuild network programs (e.g. on 4.3 on the RT or VAXen) to pick
up the new version of libresolv.a, and hacking the resolver library into
libc.so on Suns. I remember using resolv.conf fairly early on, but my
memory is that nsswitch.conf came later (Solaris 2.x era?). Ultrix did have
a configuration file for where to do host lookups, but I think the set of
sources was fixed: files, NIS or DNS. This would have been in the Ultrix
4.4 or 4.5 era on MIPS. I remember seeing some description of a
configuration file accompanied by an editorialized comment saying something
like, "this is an idea that's time has come: Ultrix has had it for several
years." The dig on uglix was, well, kind of funny (I had a DECstation at
home at the time).

DNS configuration files were a trip, especially for someone used to the
> very simple Unix configuration files like /etc/passwd and /etc/hosts.
> Circa 1985/1986 I was responsible for bringing up DNS at the Emory U
> campus.  Once in place, things pretty much just worked. Or at least,
> from this distant vantage point, that's what I seem to remember.
>

Ha! Yeah, tell me about it. We used to format our SOA records so that the
'(' was on a line by itself, indented to 'SOA'. At some point, a minor
point revision to BIND changed the parsing behavior so that this was a
syntax error; there was no warning that this would be the case. I
complained on a BIND mailing list and was told, "this is in the RFC." It
wasn't clear to me where, in the documentation, it was specified that the
file format understood by BIND was the RFC-standard format.

        - Dan C.

[-- Attachment #2: Type: text/html, Size: 3382 bytes --]

  parent reply	other threads:[~2018-11-07 19:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06  1:41 Dan Cross
2018-11-07  9:05 ` arnold
2018-11-07 15:52   ` ron minnich
2018-11-07 18:27     ` Arthur Krewat
2018-11-07 21:28       ` William Pechter
2018-11-07 17:15   ` Dan Cross [this message]
2018-11-07 20:15     ` Larry McVoy
2018-11-08 11:34       ` arnold
2018-11-08 16:39         ` Arthur Krewat
2018-11-08 23:14           ` Warner Losh
2018-11-09  0:06             ` Arthur Krewat
2018-11-07 20:15     ` Henry Bent
2018-11-07 21:11     ` Mantas Mikulėnas
2018-11-07 15:02 ` Clem Cole
2018-11-07 15:05   ` Clem Cole
2018-11-07 17:02   ` Jon Forrest
2018-11-07 19:08   ` Aaron Jackson
2018-11-07 19:48   ` Jim Davis
2018-11-07 19:51     ` Clem Cole
2018-11-09 17:05 Richard Tobin

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=CAEoi9W5bzit9y7oew9UCCHn_QHjFa+PCRe_LJPqF80kFUje+Tw@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=arnold@skeeve.com \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).