4 ms·
A rare gem. Now cue all the people, not having read it, chiming in with comments of the form “What I use is… [something which the RFC recommends against doing]
by teddyh 3y ago
A rare gem. Now cue all the people, not having read it, chiming in with comments of the form “What I use is… [something which the RFC recommends against doing]”.
- deleted 3y ago[deleted]
- dale_glass 3y agoThe RFC is long obsolete. The world changed a lot since 1990.
- teddyh 3y agoAll the things which the RFC recommends against are still all bad practices, for reasons which have not changed. Modern server “cattle” style naming, which I assume you have in mind, is actually explicitly mentioned as a reasonable idea in the RFC text.
- dale_glass 3y agoSome can be ignored in modern times. Eg, nothing wrong with naming the webserver simply "web". Particularly in modern times where it's going to be a VM/container, and never do anything else. Also nothing wrong with naming your laptop after yourself. Laptops weren't much of a thing in 1990, these days everyone at my company has their own. And seeing a login or packets on tcpdump from "bob.example.com" is very much helpful.
- NoZebra120vClip 3y agoThat's all well and good until you hire Web and Dev.
- JohnFen 3y ago> nothing wrong with naming the webserver simply "web" Until you have more than one webserver.
- mcv 3y agoA big thing that changed is that host names aren't part of email addresses anymore.