From: "Jeremy C. Reed" <reed@reedmedia.net>
To: Will Senn <will.senn@gmail.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] 4.3 BSD network name resolution
Date: Sat, 29 Jan 2022 18:09:12 -0600 (CST) [thread overview]
Message-ID: <alpine.NEB.2.22.394.2201291753100.29476@t1.m.reedmedia.net> (raw)
In-Reply-To: <0C7FF60E-D7B1-434A-87D1-35E1102D7DC6@gmail.com>
> "There is no equivalent service for network names yet. The full host and
I see that in usr/doc/smm/01.setup/5.t
Do you have usr/doc/smm/11.named ?
Have a look at the resolver(3) and resolver(5) and gethostbyname(3n)
and named(8) manual pages with 4.3BSD.
And see /usr/src/etc/named/doc
for the November 1983 RFC 883 specification.
(I haven't used that old one, but I did use a 1990 BIND 4.8.3 from
4.3BSD-Reno / 386BSD using NetBSD compat and documented some of its
behavior with modern DNS.)
prev parent reply other threads:[~2022-01-30 0:26 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
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 [this message]
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=alpine.NEB.2.22.394.2201291753100.29476@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/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).