From: Adam Thornton <athornton@gmail.com>
To: arnold@skeeve.com
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] UREP
Date: Wed, 10 Jul 2019 12:31:59 -0700 [thread overview]
Message-ID: <CBA8FC8B-7790-4BCD-81CD-5B7971B1BE6E@gmail.com> (raw)
In-Reply-To: <201907100544.x6A5ilIN020551@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
I have sort-of resurrected the bitnet zone file.
SInce bitnet is not an official TLD you will need to specify the nameserver, since the root won’t forward it.
So, grab a copy with:
dig IN AXFR bitnet @ns.fsf.net
Note that the old zone file had underscores in the hostnames. Anywhere you see a dash here, it should be an underscore to be the correct bitnet name.
bit.net <http://bit.net/> is still alive (from the IP address it’s still a machine at Princeton) serving a document explaining the bitnet history.
Adam
[-- Attachment #2: Type: text/html, Size: 1069 bytes --]
prev parent reply other threads:[~2019-07-10 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 20:08 Lyndon Nerenberg
2019-07-10 5:44 ` arnold
2019-07-10 19:31 ` Adam Thornton [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=CBA8FC8B-7790-4BCD-81CD-5B7971B1BE6E@gmail.com \
--to=athornton@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).