Serious Issue: Domain “fault.cloud” Registered by Someone Else Right After My Failed Registration Attempt via DreamHost

[RoidNet]

I attempted to register the domain fault.cloud through DreamHost, but the registration failed with an error saying:

Command failed; Failed due to deadline exceeded

Shortly after, I checked WHOIS and found that the domain was registered at the exact same timestamp as my attempt — with the exact same Cloudflare nameservers (mark.ns.cloudflare.com, wanda.ns.cloudflare.com) that I had already configured in my DreamHost panel prior to the registration.
This strongly suggests that the registration request was processed internally but the domain was taken and registered under a different entity while DreamHost reported the attempt as “failed”.

---

Timeline of Events​

1. I submitted a registration request for fault.cloud through my DreamHost account.
2. As usual, I waited for confirmation, knowing that DreamHost sometimes takes time to process certain TLDs.
3. I received an email from DreamHost stating that the registration failed due to timeout:
   

   Command failed; Failed due to deadline exceeded
   and that I was not charged.

4. When I checked the WHOIS record, the domain was already registered on the exact same timestamp (2025-10-22T08:04:22Z) — the same time my registration attempt occurred.
5. The WHOIS data shows Cloudflare nameservers identical to the ones I preconfigured inside DreamHost before submitting my registration.

This cannot be a coincidence. It indicates that the request reached the registry but was somehow diverted, mishandled, or possibly taken internally.

---

Evidence Provided​

• Screenshot of the Domain Information showing the domain registered at the same timestamp with the Cloudflare nameservers.
• Copy of the DreamHost failure email showing the timeout message.
• Screenshot from my DreamHost account showing the Cloudflare NS records set before the registration attempt.

---

What I Expect from DreamHost​

1. An immediate internal investigation into what happened from the moment my request was submitted until the domain got registered under another party.
2. Full log access of the registration process, including timestamps, registry communication logs, and request handling details.
3. Either the domain returned to my account, or a transparent and fair resolution explaining how this failure occurred.
4. A clear technical explanation to ensure this does not happen again.

---

---

Call for Community Input​

Has anyone here experienced a similar situation with DreamHost or other registrars where a domain registration “failed” but the domain got registered elsewhere immediately after?
What would be the most effective next step — filing with the registry directly or pursuing legal action first?
I’ll be happy to share full screenshots and email evidence privately with trusted members who can provide guidance.

---

Conclusion:
This incident is highly concerning and raises serious questions about how DreamHost handles failed registrations. Any advice or guidance from the community on escalating this matter would be greatly appreciated.

 

[RoidNet]

 

[Jannes]

To be clear, were you in fact not charged?

What do you mean by "got registered elsewhere"? Whois shows enom.com. Enom (or eNom) and DreamHost are in partnership, and .cloud domains are probably managed on Enom's backend.

 

[RoidNet]

Enom at same time that i was register
They used my nameservers that i was using while register
And the domain appear in wehsite section in dreamhost as you see in reply message

 

[RoidNet]

Why they registered it for yours at same time

 

[alcy]

if for resale this name is unsellable so thank em it's gone

if for project well sorry to hear

 

[Jannes]

It sounds to me that the domain is yours despite their email message.

Any advice or guidance from the community on escalating this matter would be greatly appreciated.

Contact their support before escalating anything.

 

[RoidNet]

 

[Altetra]

Due to slow domain registration processing time, someone else could have registered this domain!
If it failed Dreamhost refunds the money to your account as credit, next time you can buy other domain from this credit. They can't refund it back to CC, as it is possible with Paypal.
As others have suggested, get in contact with support and see where is the domain at the moment.

 

[RoidNet]

Due to slow domain registration processing time, someone else could have registered this domain!
If it failed Dreamhost refunds the money to your account as credit, next time you can buy other domain from this credit. They can't refund it back to CC, as it is possible with Paypal.
As others have suggested, get in contact with support and see where is the domain at the moment.

Please check the screenshots carefully. The issue is not a refund — the domain was registered by DreamHost using my nameservers at the exact moment I tried to buy it. How can anyone trust a company for domain purchases if this happens

 

[Altetra]

Please check the screenshots carefully. The issue is not a refund — the domain was registered by DreamHost using my nameservers at the exact moment I tried to buy it. How can anyone trust a company for domain purchases if this happens

Did you contact them? The domain may be yours already, see if you can do changes from Manage button and if they reflect as you modified!

 

[RoidNet]

Did you contact them? The domain may be yours already, see if you can do changes from Manage button and if they reflect as you modified!

Yes without replying yet

 

[Altetra]

I think I remember now, if domain fails registration you can't see it in registered domains, but it will show under your websites, can you confirm this, does it show in both places of DH backend?

 

[Daniel Owens]

Just out of curiosity go in your cloudflare figure out if it lets you manage dns. Right now it doesn't come up.. So add it to your cloudflare and see what happens. Also get in touch with support to confirm if/when you own it.

 

[alcy]

Yes without replying yet

it's not their fault