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 :)
The `.local` TLD exists as a zeroconf domain name for this purpose on local networks. Your homelab can advertise as `homelab.local` without setting up custom DNS servers.
This has forever been and will forever be the dumbest anti-IPv6 complaint.
How often do you really need to communicate a complete IP address manually, human to human, via voice or handwriting where you can't just copy/paste?
I mean REALLY NEED. Not just "I'm too lazy to set up DNS", not some hypothetical nonsense where you've found yourself on a network that has functional IPv6 but all autoconfiguration beyond SLAAC is disabled, etc. It just doesn't happen at a rate sufficient to justify how much people like you whine about it.
DNS works. You set it up correctly once when you provision the system, it stays working, you never need to think about a raw IP address again until it's time to deploy a new system or something weird happens like changing a NIC. If your DNS is that broken that you can't depend on it, fix that first and stop worrying about trying to remember complete addresses. If you need to tell a colleague what system you're looking at and DNS is not properly configured for that system, "the one ending in 44a1" is more than sufficient 99% of the time in the same way "the one ending in 127" was for v4 and the rest of the time you have computers and copy/paste works.
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
an easter egg in the easter egg: https://github.com/tailscale/tailscale/commit/f8ad538a3ba0b9...
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
The `.local` TLD exists as a zeroconf domain name for this purpose on local networks. Your homelab can advertise as `homelab.local` without setting up custom DNS servers.
mDNS does that. Your devices are already accessible on your network as eg āhimatas-iphone.localā with no configuration required.
We want IPs to be distinctive from domains, having real words in both would be highly confusing
dots versus ::
Maybe because IPv6 digits are hexadecimal? and we also have DNS service for that.
I don't have to imagine, in fact its even easier. I can just go to http://brother in by browser and it goes to my brother printer. Incredible!
Is there a technical reason it starts at index 2 instead of 0?
The `fd` part indicates it's a ULA, a local private ip address. (like 192.168.0.x)
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.
Almost half of traffic to Google is ipv6: https://www.google.com/intl/en/ipv6/statistics.html
Thatās because of mobile networks predominately using IPv6, correct.
Not because of home or B2B use.
This has forever been and will forever be the dumbest anti-IPv6 complaint.
How often do you really need to communicate a complete IP address manually, human to human, via voice or handwriting where you can't just copy/paste?
I mean REALLY NEED. Not just "I'm too lazy to set up DNS", not some hypothetical nonsense where you've found yourself on a network that has functional IPv6 but all autoconfiguration beyond SLAAC is disabled, etc. It just doesn't happen at a rate sufficient to justify how much people like you whine about it.
DNS works. You set it up correctly once when you provision the system, it stays working, you never need to think about a raw IP address again until it's time to deploy a new system or something weird happens like changing a NIC. If your DNS is that broken that you can't depend on it, fix that first and stop worrying about trying to remember complete addresses. If you need to tell a colleague what system you're looking at and DNS is not properly configured for that system, "the one ending in 44a1" is more than sufficient 99% of the time in the same way "the one ending in 127" was for v4 and the rest of the time you have computers and copy/paste works.
It could have easily just been "f d zero zero colon colon 1", They're just trying to be fancy with their network addresses.