Zoom outage caused by accidental 'shutting down' of the zoom.us domain
1–10 of 324 posts
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#2Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#3"This block was the result of a communication error between Zoom’s domain registrar, Markmonitor, and GoDaddy Registry, which resulted in GoDaddy Registry mistakenly shutting down zoom.us domain. "
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#4Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#5"This block was the result of a communication error between Zoom’s domain registrar, Markmonitor, and GoDaddy Registry, which resulted in GoDaddy Registry mistakenly shutting down zoom.us domain. "
Something is fishy about this. A communication error would not result in a domain being placed on hold. On hold is usually the result of a legal order or in the case of the .us TLD a nexus compliance violation. I've transferred thousands of domains from assorted dodgy registrars into MarkMonitor and can not even imagine a scenario where a miscommunication results in a domain being placed on hold.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#6Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#7"This block was the result of a communication error between Zoom’s domain registrar, Markmonitor, and GoDaddy Registry, which resulted in GoDaddy Registry mistakenly shutting down zoom.us domain. "
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#8Earlier quoted context omitted.
Something is fishy about this. A communication error would not result in a domain being placed on hold. On hold is usually the result of a legal order or in the case of the .us TLD a nexus compliance violation. I've transferred thousands of domains from assorted dodgy registrars into MarkMonitor and can not even imagine a scenario where a miscommunication results in a domain being placed on hold.
Nah, weird stuff that “shouldn’t” happen almost always happens more often than things that “should” happen.
To me a communication error implies someone followed erroneous instructions without asking the obvious, " ... but isn't this a big business that is still live and why don't I have a legal order in my hand?" In fairness this did happen recently with he.net because a sub-domain was reported but it was done intentionally even if they failed to do even basic due diligence. After Covid I would expect most people would know zoom.us would be in use by a lot of people whereas only specific groups of people would know what he.net is.
I am curious if the process has changed due to laziness and now registrars can just select any number of domains and click a button to place them on hold without management or executive approval. If so that should be in some audit trail and should require confirmation and approval by a senior leader.