CLOSED

[Savage Names]

Hi all

Has anyone experienced a domain purchased through a GoDaddy expired auction not resolving correctly for an extended period?

I acquired CoffeeCash.com via GoDaddy Auctions around a month ago. Since taking ownership, the domain has never resolved properly despite multiple nameserver changes and extensive troubleshooting.

I have contacted GD support on several occasions regarding the issue, but it remains unresolved.

A few details:

• Domain is managed within my GoDaddy account.
• I’ve tested both Atom and Afternic nameservers (not working)
• Other domains in the same account are working normally.
• Resolution behaviour has been inconsistent across different devices and networks.
• GoDaddy support recently advised that the domain had been “reconciled” and later escalated the issue to their advanced team.
• My GoDaddy account shows the domain using Atom nameservers (ns1.atom.com / ns2.atom.com).
• However, public WHOIS continues to show the Name-Services nameservers.

What makes this particularly strange is that the nameservers shown in my GoDaddy account do not appear to match what is being published externally.
I’m curious whether anyone else has experienced something similar with an expired-auction acquisition, particularly involving nameserver updates, registrar synchronization issues, or domains appearing to be stuck between systems.

Any insight or similar experiences would be greatly appreciated.

 

[Future Sensors]

It currently redirects to another domain, is that yours as well?

******cup.com

 

[Future Sensors]

My GoDaddy account shows the domain using Atom nameservers (ns1.atom.com / ns2.atom.com).

This is how it's currently configured (delegated) in DNS:

CoffeeCash.com. 172800 IN NS dns1.name-services.com.
CoffeeCash.com. 172800 IN NS dns2.name-services.com.
CoffeeCash.com. 172800 IN NS dns3.name-services.com.
CoffeeCash.com. 172800 IN NS dns4.name-services.com.
CoffeeCash.com. 172800 IN NS dns5.name-services.com.

 

[Savage Names]

It currently redirects to another domain, is that yours as well?

******cup.com

No not mine

 

[Savage Names]

This is how it's currently configured (delegated) in DNS:

CoffeeCash.com. 172800 IN NS dns1.name-services.com.
CoffeeCash.com. 172800 IN NS dns2.name-services.com.
CoffeeCash.com. 172800 IN NS dns3.name-services.com.
CoffeeCash.com. 172800 IN NS dns4.name-services.com.
CoffeeCash.com. 172800 IN NS dns5.name-services.com.

Yup.

 

[Savage Names]

That’s the redirect I was seeing on some networks. The confusing part is that my GoDaddy account has shown ns1.atom.com and ns2.atom.com for several days, yet the domain still appears delegated to the Name Services nameservers externally.

 

[Future Sensors]

The domain is still registered at enom, so only (an account at) enom can change the nameservers for this domain.

 

[Savage Names]

mmm.. Are you suggesting the domain is still under eNom despite appearing in my GoDaddy account after I won it at auction? If so, that would explain why nameserver changes made in GoDaddy never reach the registry.

 

[Future Sensors]

But I get your frustration.

 

[Future Sensors]

Yes.

Domain:
Domain Name: COFFEECASH.COM
Handle: 7667454_DOMAIN_COM-VRSN
Status: client delete prohibited
Status: client transfer prohibited
Conformance: rdap_level_0
Conformance: icann_rdap_technical_implementation_guide_1
Conformance: icann_rdap_response_profile_1
Notice:
Title: Terms of Service
Description: Service subject to Terms of Use.
Link: https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml
Notice:
Title: Status Codes
Description: For more information on domain status codes, please visit https://icann.org/epp
Link: https://icann.org/epp
Notice:
Title: RDDS Inaccuracy Complaint Form
Description: URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf
Link: https://icann.org/wicf
Link: https://rdap.verisign.com/com/v1/domain/COFFEECASH.COM
Link: https://enom.rdap.tucows.com/domain/COFFEECASH.COM
Event:
Action: registration
Date: 1999-07-02T02:30:52Z
Event:
Action: expiration
Date: 2026-07-02T02:30:52Z
Event:
Action: last changed
Date: 2025-06-03T06:21:01Z
Event:
Action: last update of RDAP database
Date: 2026-06-13T17:44:41Z
Secure DNS:
Delegation Signed: false
Entity:
Handle: 48
Public ID:
Type: IANA Registrar ID
Identifier: 48
Link: http://www.enomdomains.com
Role: registrar
vCard version: 4.0
vCard fn: eNom, LLC
Entity:
Role: abuse
vCard version: 4.0
vCard tel: tel:+1.4165350123
vCard email: [email protected]
Nameserver:
Nameserver: DNS1.NAME-SERVICES.COM
Nameserver:
Nameserver: DNS2.NAME-SERVICES.COM
Nameserver:
Nameserver: DNS3.NAME-SERVICES.COM
Nameserver:
Nameserver: DNS4.NAME-SERVICES.COM
Nameserver:
Nameserver: DNS5.NAME-SERVICES.COM

 

[Future Sensors]

Or in simpler format:

Domain Name: COFFEECASH.COM
Handle: 7667454_DOMAIN_COM-VRSN
Creation Date: 1999-07-02T02:30:52Z
Expiration Date: 2026-07-02T02:30:52Z
Updated Date: 2025-06-03T06:21:01Z
Registrar: eNom, LLC
Registrar IANA ID: 48
Domain Status: client delete prohibited
Domain Status: client transfer prohibited
Name Server: DNS1.NAME-SERVICES.COM
Name Server: DNS2.NAME-SERVICES.COM
Name Server: DNS3.NAME-SERVICES.COM
Name Server: DNS4.NAME-SERVICES.COM
Name Server: DNS5.NAME-SERVICES.COM

 

[Savage Names]

GD should be the one explaining why the registry still appears to be under eNom control and fixing the discrepancy.

I've spent far too long on messaging support and emailing my "VIP Account Executive"

 

[Future Sensors]

@GoDaddy should be the one explaining why the registry still appears to be under eNom control and fixing the discrepancy.

I've spent far too long on messaging support and emailing my "VIP Account Executive"

Ah, the authentic GoDaddy experience. I wish you the strength to survive their support team.

 

[Future Sensors]

Here you can find the most actual state for the domain, to see whether anything has changed:

https://rdap.verisign.com/com/v1/domain/COFFEECASH.COM

 

[Hypersot]

I don't use GoDaddy so I don't know how auctions work there but, with other registrars', there are cases when won domains at auctions are registered at other registrars but managed through the registrar that handles the auction.
And, yes, sometimes it takes a few extra steps to get things handled properly (like eg. changing NS, getting the auth-code, etc.).
Not sure yours is also the same case, just thought I should share my experience.

 

[Future Sensors]

I don't use GoDaddy so I don't know how auctions work there but, with other registrars', there are cases when won domains at auctions are registered at other registrars but managed through the registrar that handles the auction.
And, yes, sometimes it takes a few extra steps to get things handled properly (like eg. changing NS, getting the auth-code, etc.).
Not sure yours is also the same case, just thought I should share my experience.

Thanks for the addition. I'm not really an expert on this (these auctions).

You'd think GoDaddy would know all this, but they seem to be steering @Savage Names in the wrong direction. That's pretty bad.

 

[Hypersot]

@Future Sensors ,
That's the exact reason why I don't use GoDaddy.

 

[DN_Hunter]

Or in simpler format:

Domain Name: COFFEECASH.COM
Handle: 7667454_DOMAIN_COM-VRSN
Creation Date: 1999-07-02T02:30:52Z
Expiration Date: 2026-07-02T02:30:52Z
Updated Date: 2025-06-03T06:21:01Z
Registrar: eNom, LLC
Registrar IANA ID: 48
Domain Status: client delete prohibited
Domain Status: client transfer prohibited
Name Server: DNS1.NAME-SERVICES.COM
Name Server: DNS2.NAME-SERVICES.COM
Name Server: DNS3.NAME-SERVICES.COM
Name Server: DNS4.NAME-SERVICES.COM
Name Server: DNS5.NAME-SERVICES.COM

Interesting the Expiration Date isn't another year out -- from GD Expired auctions you pay for a 1-year extension. But if the expiration date is in a couple of weeks, how did it make it to GD Expired Auctions?

Also, Client Transfer Prohibited -- is the name "locked" (regular status or 60-day lock)?

I hope you can resolve this before the Enom Expiration Date of 2026-07-02

 

[Savage Names]

It's currently locked.
Very strange. I have proof of payment on 15th May
It’s a good job I didn’t pay big $ for this name! Crazy.

 

[bmugford]

It's currently locked.
Very strange. I have proof of payment on 15th May so hopefully.. @GoDaddy you can sort this.

It’s a good job I didn’t pay big $ for this name! Crazy.

This is an odd one. The timing doesn't make sense.

The domain was not expired, so I am not sure why it would have made it to GoDaddy auctions.

7/2/2026 expiration date. May 15th auction win.

Presumably, it was listed about 10 days before the auction ended.

Are we sure it was an actual auction, and not some other type of listing like Afternic BIN via Auctions?

Can you take a screenshot of the domain listed in your GoDaddy control panel?

For all of GoDaddy's flaws, I am not sure I have ever seen a de-sync issue where a domain listed in your GoDaddy control panel is registered at some other registrar.

@GoDaddy.

Brad