←back to thread

634 points RVRX | 2 comments | | HN request time: 0.48s | source
Show context
Animats ◴[] No.43712702[source]
That seriously devalues MarkMonitor's services. MarkMonitor claims to be a "an ICANN-accredited registrar and recognized industry leader since 1999". The whole point of paying for MarkMonitor is that they're an expensive service for valuable domains and are not allowed to screw up. GoDaddy should not be involved here at all.
replies(12): >>43712709 #>>43712833 #>>43713101 #>>43713501 #>>43713509 #>>43714082 #>>43714250 #>>43714371 #>>43715127 #>>43719584 #>>43719616 #>>43724570 #
TheDong ◴[] No.43712833[source]
MarkMonitor isn't at fault here.

If you register a ".ps" domain, it doesn't matter if you use MarkMonitor or Namecheap, they can't help you when the ongoing genocide results in the removal of Palestine as a country and ".ps" no longer is a valid country code top level domain.

Similarly, if you register a .us domain instead of a ".com", ".net", or ".org", MarkMonitor can't help you when GoDaddy inevitably screws up.

History has borne this out: .com domains are well-managed. ccTLDs like '.io', '.su', and '.fj' have all had significant security or availability issues because they're run by "eh, whoever the hell the country picks" with no standards.

Financially, a proper gTLD also can't raise prices unilaterally and weirdly, while if you pick a ccTLD, the country has free reign to arbitrarily change prices, delete your domain, take over your domain, etc etc.

Do not use a ccTLD.

replies(5): >>43713481 #>>43713485 #>>43713523 #>>43713561 #>>43746636 #
chrismorgan ◴[] No.43713485[source]
>>> 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.

That sounds like MarkMonitor is at least partly at fault here.

replies(2): >>43713562 #>>43718982 #
1. subscribed ◴[] No.43718982[source]
Mark Monitor have issued a correct request for the `serverUpdateProhibited`, but GoDaddy changed the code to `serverHold` instead.

100% on the GoDaddy staff.

replies(1): >>43719802 #
2. oarsinsync ◴[] No.43719802[source]
> Mark Monitor have issued a correct request for the `serverUpdateProhibited`, but GoDaddy changed the code to `serverHold` instead.

I’m curious about where are you seeing what Mark Monitor requested? It doesn’t appear in the official status update. Is this public information formally posted somewhere we can all see?