MagicDNS is generally available
I really want to like and recommend Tailscale more (and MagicDNS is another bonus) but with the forced use of Google auth and still no support for fast user switching and connections to multiple networks, it just has too many dealbreakers for me and many colleagues.<p>Zerotier has had all of that figured out for years, in the meantime Tailscale just locked the thread requesting multiple connection support as &quot;too heated&quot; (after &gt;2 years of no progress).<p>And putting access to our corporate networks in the hands of Google &amp; Co. and their trigger-happy account-blocking algos means that TS gets an automatic thumbs down from compliance officers at several of our clients. We can read stories on HN every week why such authentication systems are a bad idea, and steadfastly refusing to roll your own account system (all the while justifying it with handwavy security concerns) just seems lazy to me.<p>I can follow their arguments to some extent, I just don&#x27;t understand why the TS people insist on exclusionary features rather than letting the user choose. You believe multiple simultaneous connections are somewhat insecure and that&#x27;s why you won&#x27;t implement it? Okay, slap a warning sign on it if you want, by all means, but who cares about this if all I want is to connect to 5 branch offices at the same time.<p>You believe forcing users to use their private, everyday Google or Github accounts for authentication is safer than using a special account registered on TS with safe, unique credentials not used for any other purpose to minimze collateral damage (if the Google or Github credentials get compromised you&#x27;d get their emails or a bit of source code, but not access to the WHOLE corporate network)? How about letting the user choose and show some flexibility to use-cases that exist even if you can&#x27;t imagine them?<p>Sorry for the rant, again, I want to love TS, it&#x27;s UX is pretty neat, but something about their supercilious attitude with which they justify their (non-)features just rubs me the wrong way, I guess.<p>At the risk of downvotes (because I know TS has - rightfully - many fans), if anyone from TS is reading this, I do implore you to be more open-minded and give your users a choice rather than patronising them on multiple fronts when using your product. Feel free to recommend a &quot;best practice&quot; but understand that many users who might love your product will want and have to use it in a slightly different way than you intended - and that should be okay.