MagicDNS is really cool, but it seems like it is only a useful for ssh-ing into hosts or for tiny home networks where you run a service on a single box. And may

MagicDNS is really cool, but it seems like it is only a useful for ssh-ing into hosts or for tiny home networks where you run a service on a single box. And maybe that is totally fine! I just don't see how to use it in a larger environment beyond `ssh <hostname>`. In larger environments we never have any kind of internal web site or service running on one host so we can't really have MagicDNS short names for things. It would be nice for users to just be able to type `https://deploy https://deploy` to get to our deployment tool for example. But that web interface runs across many nodes behind a load balancer so there is no way to use MagicDNS here. I wonder if some day we can register duplicate hostnames and have it do DNS load balancing? I'm not sure how that would work with the tailscale cert command either. Each node would need the private key. Anyway, we'll probably start using it but the only real use cases I see right now are for ssh and for users accessing their remote dev boxes.