The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <>
To: Warner Losh <>
Cc: The Eunuchs Hysterical Society <>
Subject: Re: [TUHS] 4.3 BSD network name resolution
Date: Sun, 30 Jan 2022 08:25:49 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

If you can find source for bind 4<=  I'm sure it will compile and give you
a working named. Getting the client side code cleanly would mean a later
release of BSD but there are client side libs in the bind code AFAIK. You
can possibly link against them for rational gethostbyname(). If the link
loader ordering thing works, they might supercede simply by placing
-lresolv before libc.

Bear in mind all the RR type richness postdated this time so you could be
sent UDP > 512, and internal state you can't grok. But for A and PTR lookup
it should be fine. Since it won't do TCP or DNSSEC or large packet EDNS0
signalling, I suspect a bit of dns flow inbound would be perplexing for the


On Sun, 30 Jan 2022, 8:13 am Warner Losh, <> wrote:

> On Sat, Jan 29, 2022 at 2:49 PM Will Senn <> wrote:
>> I'm working through 4.3BSD setup and configuration and came across this:
>> "There is no equivalent service for network names yet. The full host and
>> network name databases are normally derived from a file retrieved from
>> Internet Network Information Center at SRI... use gettable to retrieve the
>> NIC host database and htable to convert it to the format used by the
>> libraries."
>> Does this mean I should expect functionality like resolv.conf and ping
>> not to work in 4.3, or by some miracle is gettable still a
>> functional system?
> DNS post-dates 4.3BSD. The first DNS RFC was published in Nov 1987. 4.3BSD
> was June 1986. The host table update was a thing, but my school was far
> enough off the beaten path that by the time we were on the internet, DNS
> was a thing...
> Warner

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

  reply	other threads:[~2022-01-29 22: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 [this message]
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).