21–30 of 324 posts
Earlier quoted context omitted.
Companies pay MarkMonitor to NOT make these mistakes. So... GoDaddy failed?
Yeah I don't understand this. MarkMonitor themselves are a registry, so is the potentially a mistake in migrating from GoDaddy to MarkMonitor?
Someone in the Zoom company management forgot to update the billing credit card for that domain, I bet you $1000. Happens all the time with our clients.
Earlier quoted context omitted.
Yeah I don't understand this. MarkMonitor themselves are a registry, so is the potentially a mistake in migrating from GoDaddy to MarkMonitor?
GoDaddy operates the .us TLD, so Zoom registered the domain through Markmonitor, who acquired it from GoDaddy, who shit the bed and broke everything.
Earlier quoted context omitted.
Companies pay MarkMonitor to NOT make these mistakes. So... GoDaddy failed?
Yeah I don't understand this. MarkMonitor themselves are a registry, so is the potentially a mistake in migrating from GoDaddy to MarkMonitor?
Markmonitor and zoom are both terrible companies so I can't feel bad about this
Earlier 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.
Earlier quoted context omitted.
What does “shutting down” the domain even mean? Has to be a DNS thing, right?
It's translated through several layers of people who don't know anything. Their domain expired because at some level people made some pretty boneheaded mistakes. Whomever their actual registrar actually was (GoDaddy it seems) stopped pointing the zoom.us nameserver record (NS) at AWS Route 53 which Zoom obviously uses. % dig +short zoom.us NS ns-387.awsdns-48.com. ns-1137.awsdns-14.org. ns-1772.awsdns-29.co.uk. ns-88…
.us (and other many TLDs) uses EPP to communicate between registars (MarkMonitor here) and Registry (GoDaddy). It is probably an admin error rather than code[1], some manual approval or other human review workflow for high value domain and someone clicked/filled in the wrong value at GoDaddy or MarkMonitor would be my first guess.
[1] would have been observed and fixed long before today, transfers happen all the time after all
Earlier quoted context omitted.
GoDaddy operates the .us TLD, so Zoom registered the domain through Markmonitor, who acquired it from GoDaddy, who shit the bed and broke everything.
ah-ha! Didn't consider that GoDaddy operates the TLD (in my mind I assumed it was just Verisign). Thank you for pointing that out.
"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.