Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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]”.


The RFC is long obsolete. The world changed a lot since 1990.


All 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.


Some 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.


> nothing wrong with naming the webserver simply "web"

Until you have more than one webserver.


That's all well and good until you hire Web and Dev.


I'd like to welcome our newest team member, Cloud Prod!


Reminds me of https://xkcd.com/327/ and Little Bobby Tables.


A big thing that changed is that host names aren't part of email addresses anymore.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: