This is so cringe. I feel like software engineers are just overgrown toddlers stuck in kindergarten: "We named our servers with boy and girls names and hired an artist to draw their personalities as ninjas!!@!111". I mean, whats wrong with a plain old 4 character hash or whatever?
I hinted there how the NS chain of lookups works from . to your domain. The point is that we wanted to be able to move name servers around the ip addresss, but that wouldn't work for many domains. So - in some contexts moving IP's rapidly is possible, in some it's not. Fun.
Vatican server names sounded somewhat interesting too: Michael, Gabriel, and Raphael. They set up their own ISP and cloud hosting since then, but it was a funny gig they did in the past.
I started on a new team once and I was integrating some CloudFlare services, I hooked a domain name and I was assigned a nameserver with my lastname and one with my new manager's lastname... nobody ever believed I did not picked those, people still joke about a love story that involves a manager, myself and CloudFlare.
> One side note on this point: we once had someone write in to support criticizing us based on the fact that our name server convention is hetro-normative. I will simply say that just because you get two name servers doesn't mean they're in any kind of relationship.
I mean, you could add 50 gender-neutral names to try to balance it out...
There are infinite genders though, so it's not really fair to go beyond that.
11 comments
[ 3.5 ms ] story [ 30.4 ms ] threadhttps://blog.cloudflare.com/tld-glue-sticks-around-too-long/
I hinted there how the NS chain of lookups works from . to your domain. The point is that we wanted to be able to move name servers around the ip addresss, but that wouldn't work for many domains. So - in some contexts moving IP's rapidly is possible, in some it's not. Fun.
I mean, you could add 50 gender-neutral names to try to balance it out...
There are infinite genders though, so it's not really fair to go beyond that.