@Marcus Maybe @danderson can help?
-
@Marcus Maybe @danderson can help?
-
@jan @Marcus What "tailscale DNS" do you mean? Resolution for names within your tailnet happen on localhost within the tailscaled process, so there isn't really any infrastructure outage risk in the traditional sense. That's why it's not listed, it's not like there's a DNS server we run that can go down.
I suggest contacting support so they can take a look and see what might have happened.
-
@danderson @jan I've just had a response from support. Looks like I'm using the old beta.tailscale.net MagicDNS and didn't get notified of the change because I don't have an email associated.
Switching over to the new one now...(cc @thatsten )
-
@Marcus @jan @thatsten Argh, that's unfortunate, sorry One of the joys of using third party SSO exclusively, there's a variety of configurations where we have no contact info for operators. We've been nudging people to provide said info for a while, and for the beta.tailscale.net thing iirc we had a big loud banner on the admin console for a while... But that's still easy to miss if you had no reason to load the admin panel
-
@danderson One of the problems about having a service so good that it "just works" is I rarely need to ever log in to my account
I've made sure my email is added now so hopefully nothing like this in the future!
-
@Marcus It sounds like bragging, and I don't mean it that way, but... yeah, ironically there's often so little need to look at the admin panel that it's genuinely tricky to get back out of the "no contact info for this tailnet" problem At some point we toyed with shipping a notification capability in the client stuff as a last resort, but that has its own whole set of problems...