6 ms·
Before the DNS: how yours truly upstaged the NIC's official HOSTS.TXT (2004)
- gmiller123456 7y ago>I would then telnet or ftp to these nameless hosts and see what host name the operating system login prompt gave me or what host name the ftp server announced in its greeting. I would then plug this information into my systems host table. So, you removed what little security there was at the time to make sure that the machine pointed to by a host name actually had some connection to what the hostname implied. This is just one step below making the HOST.TXT file world editable. The NIC had a good reason for not adopting your method.
- flingo 7y agoWhat're you implying? That someone would change their hostname to take over someone else's site?
- Ayesh 7y agoYes.
- gmiller123456 7y agoNot really "taking over", more like password harvesting. You just report a hostname at login that you don't own, the maintainer will update the hosts file to point to your system. People will gladly connect to your system and type in their usernames and passwords.
- fanf2 7y agoRemember at the time this was a closed network of less than a thousand computers, and there was no secrecy about what was connected to the network. For example, knowledgable users were able to identify where a computer was from its name, because sites had distinctive naming schemes https://elists.isoc.org/pipermail/internet-history/2020-February/005781.html https://elists.isoc.org/pipermail/internet-history/2020-Febr...
- flomo 7y agoKeep in mind these hostnames were generally quite descriptive of their network location, and people could vouch for that. There was no typo squatting or fishing going on. This guy's host file became popular mostly because local sysadmins were too lazy to add their own hosts.
- Ayesh 7y agoAuthor clearly says it was for their own use, and the rest of the Net just decided to prefer it.
- bradknowles 7y agoAnd in 1995, when the Defense Information Systems Agency was building the classified SIPRnet, the principal network manager wanted to use HOSTS.TXT tables instead of the DNS, because they thought it would be easier. They also wanted to use random network numbers pulled out of their ass, for the same reason. Fortunately, I got wind of this, and as the DISA.MIL Technical POC, I had a meeting with them. Ultimately, I was able to convince them of the folly of their ways, and to use real DNS servers as registered from the NIC, and to use real network numbers as registered from the NIC. The kicker was that I knew they ultimately wanted to be able to connect the classified SIPRnet to the “unwashed masses”, through a mythical “multi level secure gateway” that the NSA was supposedly building which would theoretically keep the truly classified stuff from touching the unclassified stuff. But how would you route packets from one side to the other, if you had colliding network numbers because one side just pulled random numbers out of their ass? How would you connect through to the unclassified side, if you weren’t using the “real” DNS? Yes, this was 1995, and they still thought HOSTS.TXT files were a good idea. To those of you who have used SIPRnet, you’re welcome.
- paranoidrobot 7y agoThere are, unfortunately, people who still think this way. I worked for someone a few years ago who wanted me to build tooling manage the hosts file across several hundred devices. When I said no that that's exactly what DNS servers are for, they got shitty and went on about how DNS was unreliable and the cause of so many outages.
- geofft 7y agoI wish I had a term for this sort of confusion. On the one hand, yes, DNS is the cause of many outages, and yes, in particular uncommon circumstances ("small networks" and "having an unusually good system for syncing text files that you're already keeping at five nines", etc.), syncing a hosts file might be reasonable. But most DNS outages aren't about DNS itself as a protocol, and won't be addressed by syncing the hosts file - they're about stale information in DNS, or incorrect information being stored in DNS, or something else like that. Whatever system you build to replace DNS is going to be prone to the same problems. I have seen the same line of thinking in many other contexts - "Why don't we just replace problematic component X with other component Y" where X is, genuinely, not great but Y would need to be shaped just like X and our problems with X are actually its shape, and if you were able to reshape Y, you might as well just reshape X and not bother deploying Y. But I'm not sure this fallacy has a name.
- oldandcold 7y agoAs a one-time DNS dev, this story is at once heartwarming and terrifying. Still the best thing I've read in a while! LOL!
- JohnFen 7y agoI am part of a group that runs a small "private internet" -- that is, a tcp/ip network that adheres to most internet RFCs and provides most of the same services as are available on the internet, but operates independently of the internet itself. Right now, we don't run a DNS -- we go old-school with a master hosts file as was done before DNS existed on the internet. For our situation, it's the easiest solution and is entirely manageable, since there aren't a ton of domain names and the hosts file rarely needs updating. But it's clear that eventually this will no longer be sustainable. Kudos and thanks to the author for blazing this trail for us. It will make the eventual shift to a private DNS much easier.
- DonHopkins 7y ago>This was easy because in those early days the Network Control Program known as NCP (this was before TCP/IP) would broadcast messages called RSTs to every possible host address on the network when they booted. Note that NCP used 8 bit host addresses, so it wasn't as if you couldn't write a program to connect to all 256 possible addresses and see if a computer answered. But that would be rude. https://en.wikipedia.org/wiki/Network_Control_Program https://en.wikipedia.org/wiki/Network_Control_Program The author's top level web page says: https://iconia.com/ https://iconia.com/ >from the keyboard of geoff goodfellow I'm glad to learn that Geoffrey has finally upgraded his tty to a real keyboard! He used to always use this From address: https://iconia.com/TELECOMDigestV2.33.txt https://iconia.com/TELECOMDigestV2.33.txt From: the tty of Geoffrey S. Goodfellow