enom giving Google a bad name
Many of you might be following the enom weekend fiasco: https://twitter.com/enomsupport/status/1482621466151571456 https://twitter.com/enomsupport/status/1482707275529678849 https://enomstatus.com/ Thousands of domains have been knocked out. But I just found out that Google is an enom reseller: https://help.enom.com/hc/en-us/articles/115005222367-My-Domain-was-registere... "Google handles all of the billing and renewals of your domain name, while Enom offers technical support to manage your domain." So who takes responsibility when a fiasco happens like this: Google or Enom? -Hank
On Sun, Jan 16, 2022 at 2:38 PM Hank Nussbacher <hank@interall.co.il> wrote:
Many of you might be following the enom weekend fiasco:
https://twitter.com/enomsupport/status/1482621466151571456
https://twitter.com/enomsupport/status/1482707275529678849
Thousands of domains have been knocked out.
Because they used URL redirection services, right ? Domains under management are unlikely to be affected unless the registrant needs a domain update.
But I just found out that Google is an enom reseller:
https://help.enom.com/hc/en-us/articles/115005222367-My-Domain-was-registere...
"Google handles all of the billing and renewals of your domain name, while Enom offers technical support to manage your domain."
So who takes responsibility when a fiasco happens like this: Google or Enom?
I would imagine Google only uses Enom for TLDs that they don't carry thru Google Domains, their own registrar. And Google would also use its own URL redirection services, not Enom's. Rubens
On 16/01/2022 19:57, Rubens Kuhl wrote:
On Sun, Jan 16, 2022 at 2:38 PM Hank Nussbacher <hank@interall.co.il> wrote:
Many of you might be following the enom weekend fiasco:
https://twitter.com/enomsupport/status/1482621466151571456
https://twitter.com/enomsupport/status/1482707275529678849
Thousands of domains have been knocked out.
Because they used URL redirection services, right ? Domains under management are unlikely to be affected unless the registrant needs a domain update.
From what I see enom's nameservers are down. -Hank
Because they used URL redirection services, right ? Domains under management are unlikely to be affected unless the registrant needs a domain update.
From what I see enom's nameservers are down.
"We also discovered resolution problems that impact a few hundred domains" Tucows group, which includes a few registrars including eNom, had more than 12 million domains under management by September 2021 (last set of statistics published by ICANN). So we are talking 0,01% of customers affected, tops. Rubens
On 1/16/22 11:44, Rubens Kuhl wrote:
"We also discovered resolution problems that impact a few hundred domains"
Tucows group, which includes a few registrars including eNom, had more than 12 million domains under management by September 2021 (last set of statistics published by ICANN). So we are talking 0,01% of customers affected, tops.
Assuming small values of "few", that is correct. -- Jay Hennigan - jay@west.net Network Engineering - CCIE #7880 503 897-8550 - WB6RDV
What do you mean by "takes responsibility?" When my vendor goes down, I do whatever I can to get the end user back up and running again. I take _ownership_ of the situation and work dilligently to resolve it, as best I can, within my sphere of control. However, because I cannot control how my vendor operates their business, how can I take responsiblity for its actions and operations? My option is to decide if the vendor had a bad day or if they are inept and I need to replace them. Finding them inept and NOT replacing them THEN puts the responsibility on my shoulders, IMHO. Has enom been demonstrably inept leading up to this point? Beckman On Sun, 16 Jan 2022, Hank Nussbacher wrote:
But I just found out that Google is an enom reseller:
So who takes responsibility when a fiasco happens like this: Google or Enom?
--------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com https://www.angryox.com/ ---------------------------------------------------------------------------
participants (4)
-
Hank Nussbacher -
Jay Hennigan -
Peter Beckman -
Rubens Kuhl