6 ms·
MagicDNS is generally available
- ews 4y agoGreat idea, however, I had to disable MagicDNS in few of my machines as tailsscale changed my local DNS with 100.100.100.100 on my resolv.conf filet, yet for some reason that address was impossible to reach internally.
- syats 4y agoWhat is tailscale? I don't like the world where every time someone launches a feature on their product they get to top of HN by calling it "generally available".
- simonw 4y agoIn this particular case I think Tailscale has been discussed thoroughly enough on Hacker News in the past that it's OK that they didn't include the "what is Tailscale" bit (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=tailscale%20points%3E100&sort=byDate&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...) - but I agree, it's always better to start a blog entry with a reminder. Fly.io are great at this, e.g. https://fly.io/blog/introducing-litefs/ https://fly.io/blog/introducing-litefs/
- jrootabega 4y agoa dynamic peer-to-peer layer on top of wireguard
- natpunk 4y ago
- rs_rs_rs_rs_rs 4y agoYou already know the comments on this posts, but that's for a reason, Tailscale is that good people won't shut up about it.
- naikrovek 4y ago
- afturner 4y agoReally? > You already know the comments on this posts Without looking at the comments, you will already know what they say. > but that's for a reason, Tailscale is that good people won't shut up about it. Because this person is suggesting that Tailscale is so good, people will rave about it whenever it's mentioned. Pretty easy to understand.
- remram 4y agoAll the comments here are about drawbacks and limitations. The upvotes on the submission might be explained by quality of the product, but the comments not so much.
- naikrovek 4y ago
- tiagod 4y agoMeaning can be also inferred from context. Even in your example, the conversation context and follow-up statements could home in on the context. Sure, maybe it would be better if everyone just wrote in a non-ambiguous way, but you're on an international forum where many people don't have a native understanding of the language (me included). I understood what he meant immediately. I also don't agree with the comment, but that's another subject.
- Melatonic 4y agoThis is cool but.....don't tons of DNS software already do this and for many many years?
- erdaniels 4y agoIt is! But the usual thing with Tailscale is that this just works out of the box. Any new person starting where I work has Tailscale installed by default. Once they log in, they can access any of our pis/servers that are setup with names like rpi1. Furthermore, you've got ACLs + Tailscale SSH. That means you can start day 1 and do ssh root@rpi1 and it just works. It's amazing and worth so much money. Edit: I just really wish they would allow more than being tied to Google SSO. I want to invite people outside of my domain easily :o)
- xena 4y agoI wrote a giant diatribe about this here: https://tailscale.com/blog/magicdns-why-name/ https://tailscale.com/blog/magicdns-why-name/ It's not just a DNS server, it's everything _around_ the DNS server.
- VTimofeenko 4y agoYeah, it's totally possible to configure a stack like that. I roll my own stack of unbound+nsd as adblocking split-horizon DNS for LAN, roaming and management WG network. Tailscale value prop as I understand it - they can manage this whole thing for you.
- tinalumfoil 4y agoWhile this is cool I've had luck just purchasing a domain (not that expensive), and manually setting up DNS through that. Some advantages that this doesn't look like this would replicate, (1) I can have multiple domains for the same device, say gitea.mytsnetwork.com and netxcloud.mytsnetwork.com can go to the same device (2) I can get real HTTPS certificates for those domains which I consider necessary nowadays if only just to prevent errors (3) it's "real" DNS so when my browser decides to ignore my system settings and use DNS-over-HTTPS instead everything still works. EDIT: It looks like (2) is solved by the tailscale cert command. I'd replace that point by saying owning the domain is important to controlling the certificate for me. All that said, the more I read into this, this looks like a really well thought-out feature.
- mynameisvlad 4y agoTailscale has supported real certificates via LE for over a year now: https://tailscale.com/blog/tls-certs/ https://tailscale.com/blog/tls-certs/
- mholt 4y agoJust wait'll you see what's possible with Caddy+Tailscale (currently, and coming soon)!
- michael_j_ward 4y ago> (1) I can have multiple domains for the same device, say gitea.mytsnetwork.com and netxcloud.mytsnetwork.com can go to the same device I tried setting up caddy on a machine and then using caddy to reverse-proxy requests to each service i.e. `grafana.my-machine.tail-hex.ts.net` and `controller.my-machine.tail-hex.ts` Obviously, `caddy` has no problem with the reverse proxy bit, but I did fail at being able to point multiple routes or subnet routes at the same machine via tailscle / magic-dns. I'm sharing because it feels like something I should be able to do, and feel dumb not being able to figure it out.
- xena 4y agoThis is exactly what we've been working on. Stay tuned ^^
- donatj 4y agoVery exciting news. I have been using Tailscale for about two weeks now and I am SOO happy with it. It's genuinely joyful software like I haven't used in years. A modern version of the old Hamachi.
- atonse 4y agoGlad to see someone else remembers Hamachi :) Tailscale feels as magical as Hamachi did.
- kosikond 4y agoOut of curiosity, would any Tailscaler please answer why the exisiting $tailnet.beta.tailscale.net weren't just shortened to $tailnet.ts.net ? (Some of us have had luck on beatiful DNS notations early)
- bradfitz 4y agoCouple reasons. 1. We want you to be able to get HTTPS certs for these too without having to manage multiple names, but HTTPS cert names go on the CT log. See https://tailscale.com/blog/tls-certs/ https://tailscale.com/blog/tls-certs/ and https://tailscale.com/kb/1153/enabling-https/ https://tailscale.com/kb/1153/enabling-https/ . So having your email address in your DNS name (and thus the CT log) from the old beta.tailscale.net forms isn't great. 2. We want you to be able to have multiple separate tailnets per org/account in the future.
- mdeeks 4y agoMagicDNS 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.
- cschmatzler 4y agoThe way I have it set up is my Tailscale pod redirecting all requests to an ingress controller, and then all subdomains CNAMEd to the Tailscale DNS. That way, all requests are going Tailscale pod -> nginx ingress controller -> service, no matter which node everything is running on.
- pshirshov 4y agoIt breaks things and you have little control over it. It replaces default search domain with its own. Also it does't keep your DNS servers in your resolv.conf nor tries to forward your query to them when it fails to resolve it. So, you may experience a loss of connectivity for short hostnames w/o tailscale (host instead of host.my.domain) or get unnecessary overhead for TS-enabled hosts within your local network.
- diegs 4y agoIs this still incompatible with split horizon DNS? Whenever I'm connected to my corporate tailnet I can no longer resolve hostnames that are registered on my personal, DHCP-assigned DNS server, breaking access to my home network. This also leads me to believe that all my DNS requests are being routed through the magic DNS server which is not cool IMO.
- bradfitz 4y agoMost of the Split DNS issues should be fixed now. If you're on Linux, you want systemd-resolved, as it's the only Linux DNS resolver that's really any good, regardless of your opinions on systemd overall (See https://tailscale.com/blog/sisyphean-dns-client-linux/ https://tailscale.com/blog/sisyphean-dns-client-linux/) In any case, file a bug with details and we'll fix it up if there are still issues.
- trashburger 4y agoYou're right for most setups, but when Docker also comes into play, systemd-resolved+Tailscale+Docker interacts really badly and containers cannot resolve anything anymore. This caused some serious hair-pulling at work a few months ago.
- sally_glance 4y agoHow did you solve it? I want to be prepared if it happens, spent too much time figuring out weird Docker - DNS/network interactions on hotel wifis and the like...
- trashburger 4y agoThe only proper solution I could find is disabling systemd-resolved entirely. There doesn't seem to be any way to make it use something other than 127.0.0.1 as its listen address (it's actually hardcoded in systemd-resolved) which means that Docker containers which inherit /etc/resolv.conf rules can't resolve DNS anymore.
- 4y ago
- tosh 4y agorite of passage https://en.m.wikipedia.org/wiki/Right_of_passage https://en.m.wikipedia.org/wiki/Right_of_passage edit: fixed
- jadbox 4y agoCould this be used for DDNS for exposing a public web server?
- rrix2 4y agoa cool thing you can do with MagicDNS: Set your "global nameserver" to a host within your tailnet and run your own resolver accessible "anywhere". It's easy enough to set up pi-hole.net on a machine on your LAN and configure your home router to hand out DHCP records that will instruct LAN machines to use it, but if I wanted to have DNS-based ad-blocking at the coffee shop or library or elsewhere I previously had my pi-hole listening on a public IPv4's port 53 and deal with resolve.conf etc... and boy howdy does running an internet-accessible DNS resolver suck! My server would receive millions of requests, weird reflection attacks like [1], probes, the whole nine, it made the dashboarding useless for personal tracking. But now my pi-hole only listens on my LAN network and its tailnet address, and any machine connected to the tailnet including my phone will use the pi-hole without configuration on any network via MagicDNS. [1]: https://www.linuxquestions.org/questions/linux-newbie-8/there-are-many-query-this-website-on-my-dns-server-4175676097/ https://www.linuxquestions.org/questions/linux-newbie-8/ther...
- kinduff 4y agoI have a similar setup but deployed my PiHole in Fly.io using a custom Docker image behind Tailscale. This way I can just connect to Tailscale and I have ad blocking automatically using their custom DNS servers. Very useful and I use it all the time on my mobile devices including my laptop when I'm using guest wifis.
- techsupporter 4y agoCompletely off-topic but a continuously-looping very large GIF smack in the middle of the feature post is really distracting. I appreciate that GIFs are supposed to be animated loops, this one is just too large and moves around too much. (Side note: setting image.animation_mode = none in Firefox stops the animation.)
- deleted 4y ago[deleted]
- ethanpil 4y agoAs a long time ZeroTier user I want to point out that they have some interesting DNS solutions as well.[1] (Personally, have not felt the need to change something that has a great free tier, self hosting controllers, etc, and has been working reliably for years... Tailscale looks cool though) [1]https://www.zerotier.com/2022/04/11/the-zerotier-dns-story/ https://www.zerotier.com/2022/04/11/the-zerotier-dns-story/
- imagine99 4y agoI 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. Zerotier has had all of that figured out for years, in the meantime Tailscale just locked the thread requesting multiple connection support as "too heated" (after >2 years of no progress). And putting access to our corporate networks in the hands of Google & 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. I can follow their arguments to some extent, I just don'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's why you won'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. 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'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't imagine them? Sorry for the rant, again, I want to love TS, it'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. 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 "best practice" 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.
- BrightOne 4y agoMy tailnet is set up using a GitHub organization, without using Google at all. I have sufficient security (2FA with security keys, etc.) enforced for it. I think that hand-rolling their own auth would not be a great idea just yet, while they are still ironing out other features.
- SergeAx 4y agoWhile this looks fun, I still prefer to register a short domain (used free *.net.ru before war) and auto-populate DNS with Terraform/Ansible on a provision stage.
- artdigital 4y agoLove tailscale! Set it up a couple weeks ago and it’s very fun to use. MagicDns is great! I can go http://macmini http://macmini anywhere and it just works Just wish they offered more subnet routers. I’m as much hobby as hobby can be, and already hit the limit (one on my mini k8s cluster, one at home, that’s it. They don’t allow you to have more). Been stuffing the sidecar awkwardly into everything to get around it If someone from tailscale is reading this - please consider upping the limit of subnet routers. I’ll have to switch to ZeroTier once I want another one which doesn’t have those restrictions. Even paying for the hobby pro plan is just upping it from 1 -> 2
- xena 4y agoTailscalar here. For what it's worth there's no hard limit on subnet routers at this time. My personal tailnet is using 8 of them.
- dfcarney 4y ago(co-founder here) To xena's point, we're not currently enforcing the limits :) We've been very cautious about that since, as I mentioned in a comment elsewhere, the limits have always been an experiment.
- artdigital 4y agowow TIL! That makes me less anxious about that hobby pro restriction. Gonna get another subnet router deployed later :)
- chipsa 4y agoThe Github team org plan (for connecting friends and family) had a subnet router limit of 5, if you want to legitly get a higher limit rather than just ignoring the limit that they don't check.
- artdigital 4y agoOh what, is the limit not being enforced? I didn’t even bother trying to spin up another one because everything goes through that admin console, so I was sure there’d be a “you hit your limit” message Dang now I know what I’ll be doing tonight
- S0und 4y agoPSA: Zerotier can do the same thing, just set a hostname for a client in the control center.
- midislack 4y agoWOW, this changes EVERYTHING! Thanks for this important message, OP!
- jrootabega 4y ago"[[Tailscale automatically assigns IP addresses for every unique device in your network | https://tailscale.com/kb/1033/ip-and-dns-addresses/ https://tailscale.com/kb/1033/ip-and-dns-addresses/ ]], giving each device an IP address no matter where it is located." That phrasing is a little off. It implies there are situations where your location will affect whether or not you get an IP address. Reading the link makes it clear: it assigns IP addresses that are independent of the device's location. The same device will keep the same IP address even when it moves to another network location, which is not surprising when you are familiar with wireguard configuration.
- edumucelli 4y agoIf anyone at Tailscale read this: your product is insanely good. I use it and it is delight to set up.
- vczf 4y agoI hadn't heard of tailscale before this, but this system is what I have always wanted for my devices. I just finished setting this up and it works amazingly well. Now I've got samba/nomachine/syncthing restricted to the tailscale network with aesthetically pleasing device names. Better security and I can roam now. This is awesome stuff.