Tailscale's DNS IPv6 spells out "Tailscale"

morley

Is there a technical reason it starts at index 2 instead of 0?

himata4113

This makes me think about something. Why don't we support this as a standard? It would be nice if local ipv6 spelled out "local" imagine this: local::homelab in your url-bar just working edit: Yes I know DNS solves this problem, but it would be very neat non the less, making 128bits of packet overhead actually serve a purpose without any software glue.

johen8

Sound it out with your mouth: "What DNS do you use?" "One hundred one hundred one hundred one hundred" or "one hundred, 4 times" vs. "f d seven a colon one one five c colon a one e zero colon colon five three" This is just a rant but IPv6 will never be widely adopted.

DaSHacka

Related: the name for your Tailnet is randomly-generated from a list of 'tails', and a list of 'scales' in the format `<a tail>-<a scale>.ts.net`. Many puns and easter-eggs in both! Recommend giving it a quick glance, some are pretty fun. Some examples include 'fable' as a 'tail' (IE 'tale'), and 'universe' as a 'scale'. Words can be present in both lists when the entity is applicable to both a tail and a scale, so a tailnet named `koi-koi.ts.net` is theoretically possible too. Found out about it after I randomly lucked into rolling 'miku' as my 'tail' when first creating my account :) https://github.com/tailscale/tailscale/tree/main/words

ink_13

Facebook does this too: $ dig +short AAAA facebook.com 2a03:2880:f10e:83:face:b00c:0:25de

mahboi

"Nobody needs human-memorable IP addresses"

Grimeton

Yeah the "Dead Beef Cafe" has a nice IP, too. And a nice MAC...

abelleisle

I do the same thing for my homelab's ULA. My domain is `bitcicle.com`, so I use the internal ULA prefix: `fddf:b17c:1c1e::`. Makes it easier to remember.

tzs

To take it to the next level, try to get a matching IPv4 address and company phone number. It is theoretical possible because many IP address parsers accept not only a.b.c.d form of IPv4 address, but also a.b.c (8 bit a, b, 16 bit c) and a.b (8 bit a, 24 bit b). (Also a, with 32 bit a). For example on MacOS and Debian pinging these all ping the same thing: 1.0.0.1, 1.0.1, 1.1, 16777217. If your US phone number has an area code and prefix that each fit in 8 bits and the area code doesn't match one of the first bytes that has a special meaning in IPv4 then you could have phone number areacode-prefix-number also work as IP address areacode.prefix.number.