Hacker News Reader

Comment by TheRealDunkirk | Hacker News Reader

I like tying the scheme to the domain. For instance, mine has always been starfleet.mil. Forever non-public domain. Lots of options for host names. (I've never been able to figure out a cohesive way to do this for Star Wars.)

If you were going for deities, maybe olympus.<something> for Greek gods. Wherever the pantheon is supposed to be homed. Hinduism would give you more host names than you could (probably) ever use...

View on HN

Your mentioning the pantheon gave me a flashback to how one of my old companies named their non-prod environments. The dev environment services were named after all the Greek gods, and the QA/demo environment services after the Roman gods. It was so horribly confusing…

Yeah... I've seen this too. You really have to know your mythology to keep those 2 straight. I'd have made one of them Norse. ;-)

.mil is an valid (restricted) tld [0], and has been for a long time. And while starfleet.mil is still currently unregistered, I wouldn’t be surprised if they changed given recent trends [1]…

0: https://en.m.wikipedia.org/wiki/.mil

1: https://www.spaceforce.mil/

I'm sure it works fine, but .mil is a real TLD and someone (like the new Space Force or whatever they call themselves) could register it and use it publicly tomorrow.

The ".home.arpa" domain is explicitly set aside for 'home' non-public networks in https://datatracker.ietf.org/doc/html/rfc8375.

Before I started using zfs and drive names stopped mattering, I'd name my personal storage drives after heroes from the Iliad, and the corresponding backup drives after the heroes' wives.

Hmm, a similar scheme we used at a previous workplace - lots of references to ancient Greek philosophers, historians and of course deities.

I wanna try ancient Carthaginians: Hanno, Hamilcar, Hanno, Hannibal, Hanno, Hasdrubal, Hannibal, Hanno, Hannibal, Hanno, Hanno, and of course Hanno

Reply on news.ycombinator.com