From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31958 invoked from network); 29 Jan 2022 22:26:25 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 29 Jan 2022 22:26:25 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id B742A9B8EC; Sun, 30 Jan 2022 08:26:24 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id B6DEB9510A; Sun, 30 Jan 2022 08:26:08 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=algebras-org.20210112.gappssmtp.com header.i=@algebras-org.20210112.gappssmtp.com header.b="x99YN67L"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 233179510A; Sun, 30 Jan 2022 08:26:07 +1000 (AEST) Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) by minnie.tuhs.org (Postfix) with ESMTPS id D4F1495109 for ; Sun, 30 Jan 2022 08:26:02 +1000 (AEST) Received: by mail-lj1-f178.google.com with SMTP id t14so14131180ljh.8 for ; Sat, 29 Jan 2022 14:26:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=E89plgyalLOioksalDEKzfgSvHpuZfWz3XByzGYY3GU=; b=x99YN67LlY2+rFwtAVI44oDM3L1m/IVBHvHila/bEsMxt0KJAnFn+l5RulHS5GpAFl BUybJkf1mSXRs7QREYA0YvtaHcwhnk8OB1uA7KFvespmHjX3T412R+CXjWlGatCw0hGq g6RBLUiXln01eead/IkR2XVpp4WyBqwZeuRlXsMnqSNDex1FCuoFfYl1IPVhQobWJYOX FnQZ5MrfkPufA5Jmek8PN1WxqVJOUCPWYOT7OG8eO5/oV0uDwYYyOy1nGIDPiRWj0dbj hrk8Dxe0jypb3OnHZoB9FVB7Qz1IF1tAIJyZYCh5cMY9KGRZtMAmje8EZSgtTqSvKKYN JXTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=E89plgyalLOioksalDEKzfgSvHpuZfWz3XByzGYY3GU=; b=73DG+meeHwEYYfh9Csu6V2IRpa9i6uibswH71CWv1B9DLYmtgC+NEBKXvgGybDT6tP hGRee54qZXASQvjPd+txB+9G4foQR/vXwHDacflWyD2qZyAPa/3c7I3g/RzWzYAiykgD fai/q+Rni5ZlqcrNTyzu4FzMD+hWx8Wcw3yKQWxT6MtZgoRK5kuo3o12AsWDvllAxI+h MOl/aDceftL8V1g+A6gQZfvBdGHsKW+MRl5CIparXgfajq6BRQ/GrLPbcWw+yk1PbnVU N1Ce4AUdo2Jwxh23uqjz2utp7jsYmq6uhWoAgVGkjmJ854n/3bjYwJk8UNLXmvR3KZIe ZkMA== X-Gm-Message-State: AOAM533GgbU5jSX6hW0DTM6gn3Av+arOfRSuDgSTTOSmnkZPX7M4qA9o zpogvwYIuId6PonFGfvwYxu7ni1ce7HtEp6pRm39Zl8r4Dv3Sg== X-Google-Smtp-Source: ABdhPJydauAN2uUS3mF04zUKRA2DEM9G42lVWdOKlpmodSmW927nkVYoxLqMwQuRvGgN1/gpHO7xIIAS5+JLaeTOtlo= X-Received: by 2002:a05:651c:897:: with SMTP id d23mr9777233ljq.522.1643495161143; Sat, 29 Jan 2022 14:26:01 -0800 (PST) MIME-Version: 1.0 References: <0C7FF60E-D7B1-434A-87D1-35E1102D7DC6@gmail.com> In-Reply-To: From: George Michaelson Date: Sun, 30 Jan 2022 08:25:49 +1000 Message-ID: To: Warner Losh Content-Type: multipart/alternative; boundary="00000000000045362705d6c009b0" Subject: Re: [TUHS] 4.3 BSD network name resolution X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000045362705d6c009b0 Content-Type: text/plain; charset="UTF-8" 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 resolver. G 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 >> yahoo.com 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 > --00000000000045362705d6c009b0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If you can find source for bind 4<=3D=C2=A0 I'm su= re it will compile and give you a working named. Getting the client side co= de 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 ge= thostbyname(). If the link loader ordering thing works, they might superced= e simply by placing -lresolv before libc.

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

G

On Sun, 30 Jan 2022, 8:13 am Warner Losh, <imp@bsdimp.com> wrote:


On Sat, Jan 29, 2022= at 2:49 PM Will Senn <will.senn@gmail.com> wrote:

I'm working thr= ough 4.3BSD setup and configuration and came across this:


"There is no e= quivalent service for network names yet. The full host and network name dat= abases are normally derived from a file retrieved from Internet Network Inf= ormation Center at SRI... use gettable to retrieve the NIC host database an= d htable to convert it to the format used by the libraries."


Does this mean I sh= ould expect functionality like resolv.conf and ping yahoo.com 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=
--00000000000045362705d6c009b0--