From: "Jeremy C. Reed" <reed@reedmedia.net>
To: Henry Bent <henry.r.bent@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>,
Internet History <internet-history@postel.org>
Subject: Re: [TUHS] [COFF] Pondering the hosts file
Date: Thu, 11 Mar 2021 19:15:03 -0600 (CST) [thread overview]
Message-ID: <alpine.NEB.2.22.394.2103111844390.6117@t1.m.reedmedia.net> (raw)
In-Reply-To: <CAEdTPBc9=AGmLTP6VpRA0zXrtvrmja9_y5MoVJOp8u0mL2R+Kw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
(I re-added Internet History list to my response here ...)
On Thu, 11 Mar 2021, Henry Bent wrote:
> Perhaps a more interesting question, and one which I cannot quickly answer
> (nor am I going to go pinging huge swaths of the public internet), is are
> there any hosts in any version of HOSTS.TXT that are still on the public
> internet in the same location? Or - and perhaps there is an easy answer to
> this that I do not know - is there a repository of old WHOIS databases? I
> remember being stymied ~20 years ago that Ultrix had SRI-NIC.ARPA hardcoded
> in the whois binary and I couldn't find a hostname of the correct length
> with which to replace it...
Using 1988 SRI-NIC host table
https://github.com/ttkzw/hosts.txt/blob/master/pub/hosts/19881208/HOSTS.TXT
I don't know if at same location, but some relationship and even some
same or close names:
CS.WISC.EDU 128.105.2.6
128.135.0.0 u-chicago.uchicago.edu.
uvaarpa.virginia.edu. uvaarpa-old.virginia.edu. 128.143.2.7
jellicoe.cs.ucl.ac.uk. 128.16.3.1
honda.cs.columbia.edu. 128.59.16.16
cesd-gw.ai.sri.com. 192.12.33.1
ns0.llnl.gov. 192.12.17.1
umbc-net.umbc.edu. 130.85.0.0
net.queensu.ca. 130.15.0.0
ns.indiana.edu. 129.79.1.1
oswego-net.oswego.edu. 129.3.0.0
dorm-net0.stanford.edu. 128.12.0.0
nas-net.nas.nasa.gov. 129.99.0.0
Several others at same organizations or descendants. A lot are under
xip.io.
next prev parent reply other threads:[~2021-03-12 1:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:13 [TUHS] " Grant Taylor via TUHS
2021-03-11 17:29 ` [TUHS] [COFF] " Steffen Nurpmeso
2021-03-11 17:40 ` [TUHS] " Bakul Shah
2021-03-11 18:08 ` [TUHS] [COFF] " Warner Losh
2021-03-11 18:12 ` Clem Cole
2021-03-11 18:21 ` Jaap Akkerhuis
2021-03-11 18:21 ` Nelson H. F. Beebe
2021-03-11 20:05 ` Jan Schaumann
2021-03-11 20:30 ` Henry Bent
2021-03-11 20:42 ` Henry Bent
2021-03-11 21:20 ` Henry Bent
2021-03-11 23:46 ` Richard Salz
2021-03-12 1:15 ` Jeremy C. Reed [this message]
2021-03-12 3:27 ` George Michaelson
2021-03-11 20:44 ` Lars Brinkhoff
2021-03-11 21:05 ` Henry Bent
2021-03-12 5:53 ` Lars Brinkhoff
2021-03-11 21:12 ` Ron Natalie
2021-03-11 22:33 ` Jeremy C. Reed
2021-03-11 18:27 ` Henry Bent
2021-03-11 18:18 ` Henry Bent
2021-03-11 18:02 ` Clem Cole
2021-03-11 20:32 ` Ron Natalie
2021-03-11 21:02 ` Bakul Shah
2021-03-11 21:08 ` Ron Natalie
2021-03-11 21:15 ` Bakul Shah
2021-03-12 1:14 ` Mary Ann Horton
2021-03-11 21:20 ` Grant Taylor via TUHS
2021-03-11 18:30 Bakul Shah
2021-03-12 10:53 Paul Ruizendaal via TUHS
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.2103111844390.6117@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
--cc=henry.r.bent@gmail.com \
--cc=internet-history@postel.org \
--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).