Zoom outage caused by accidental 'shutting down' of the zoom.us domain
151–160 of 324 posts
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#152Earlier quoted context omitted.
That’s because you are maybe not in the market for MarkMonitor. If you check the whois for any global brands chances are they are held by MarkMonitor. Just like you don’t use EY as your tax advisor.
Genuinely, I don’t understand how anything other than uptime matters for a domain registrar. What services are they offering that makes them attractive to corporations?
What MarkMonitor can provide is things like facilitating RegistryLock, which makes it even harder for changes to be made. And account reps that know what's going on. I hate working with account reps, but if they're knowledgable and easy to work with, it's ok.
They do some trademark monitoring (thus the name), if you want to get your own related app taken down from Google Play :p (I'm not bitter, it was amusing). And presence services if you need to hold a domain in a weird location that wants a presence, they can probably arrange it, which is handy at times.
I'd love to know more details on this incident, MarkMonitor had a bulletproof reputation as a registrar that won't fuck up. Godaddy doesn't, but then I didn't realize they had taken over the contract for .us
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#153Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#154Earlier quoted context omitted.
It wouldn't be the first time a ccTLD has been retired after its country ceased to be, though it would be the most disruptive given how popular it is, hence the uncertainty as to what they'll do this time.
If I were Mauritius, I would be hitting tech companies left and right to secure a permanent income stream. You guys want to kick indigenous people off their land for military bases? Enjoy your new bill for .io domains.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#155Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#156Amazing how many service outages are caused by doing business with GoDaddy.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#157Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#158A few years ago I had a .us TLD. I eventually decided that I probably shouldn't be reliant on a country code for my domain, it's the same reason why I don't use .io I'm not saying that this couldn't have happened with a gTLD But why put your brand at the mercy of a government like that?
> But why put your brand at the mercy of a government like that? I tend to trust my government (Canada) and I appreciate that WHOIS information is hidden by default for .ca domains. I live here and always will so it seems fit to use the national TLD for representing myself and my work.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#159Earlier quoted context omitted.
It's possible, but MarkMonitor is Zoom's registrar, so there are plenty of other ways for a miscommunication between MarkMonitor and GoDaddy to cause this. Copyright complaints would be a more reasonable theory if MarkMonitor were mentioned and didn't have any other involvement.
I guess but if MarkMonitor accidently suspended it, it would be ClientHold but it was widely reported it was showing as ServerHold. ServerHold is used with Registry (GoDaddy in this case) is disabling vs ClientHold is when registrar is pulling the plug (MarkMonitor) So what would have MarkMonitor said to GoDaddy to cause them to ServerHold a domain?
It turns out that they had typo’d 12 into the request type field instead of 1, and type 12 was “Covid lockdown protocol with security enforcement” leftover from 2020 and latent in their systems.
Depending on MarkMonitor have chosen to integrate with each other to handle the sort of trademark management that is MarkMonitor’s premium offering, either or both parties could have simply been off-by-one or typo’d in a transaction to cause this. It’s absolutely plausible to create a confusing nightmare outcome with a one-byte error. (And we’re having quite incredible cosmic rays today, so I hope they’re using ECC RAM!)
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#160A few years ago I had a .us TLD. I eventually decided that I probably shouldn't be reliant on a country code for my domain, it's the same reason why I don't use .io I'm not saying that this couldn't have happened with a gTLD But why put your brand at the mercy of a government like that?
> it's the same reason why I don't use .io Dodged a bullet there given that .io is at risk of being discontinued altogether. It hasn't been decided yet, but better to not have that dangling over your head.