Dynadot โ€” .com Transfer

Afternic - Official Thread

Spacemail by SpaceshipSpacemail by Spaceship
Watch

GoDaddy

Top Member
๐Ÿฅ‡ Best Registrar (2016-2018)
:heavy_check_mark: GoDaddy Staff
Impact
1,267
Hello NamePros!
By popular demand, we have launched a dedicated feedback thread for Afternic, the GoDaddy-owned domain name marketplace.

We have created this thread as a way for you to tell us what works, what doesn't work, and what features you'd like to see at Afternic (please be constructive with your feedback). We're looking forward to hearing from the domain investment community to help us shape the future of Afternic.

We will also be sharing Afternic product updates in this thread.

Please note that this thread is not meant for support. Please email our support team at [email protected] for assistance.
 
16
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
.US domains.US domains
Now that was Fast, 3 hours from Sold, Payment Received to Payment Scheduled

ANicDomainSale.jpg
 
13
•••
Now that was Fast, 3 hours from Sold, Payment Received to Payment Scheduled

Congrats and a great way to start the weekend!
 
4
•••
What am I missing? (I'm not desperate for $.)

Beware, someone else might be trying to list your domain. It's happened to me.

Note: I didn't see the supporting posts before I posted this.
 
Last edited:
0
•••
This was always a problem for me whenever trying to checkout at Godaddy Auctions.

Same thing happens for me too sometimes when checking out (with hand-regs), crashing the site. Using Chrome on MacOS

I caught one of the two cart-error scenarios now. The other one is a complete crash of the page, this one just reports an error in a box.

Maybe @GoDaddy can work with this info in regards to nextgen_cart

Screenshot 2025-07-18 at 21.15.51.png

Screenshot 2025-07-18 at 21.15.28.png
 
1
•••
1
•••
I'm thrilled to announce the following.

After much persistent advocacy on this forum, it's a significant relief to finally confirm that Afternic has resolved the long-standing "lame delegation" issues affecting customer domains using NS1.afternic.com and NS2.afternic.com. Public DNS zone data shows that these NS1/NS2 servers alone are authoritative for over 3.5 million Seller domains. And Afternicโ€™s complementary NS3/NS4 and NS5/NS6 clusters together handle several million more.

For years, these "preferred" NS1 & NS2 nameservers provided invalid or non-responsive Namefind.com NS records, a problem extensively documented and a source of considerable frustration for domain owners. This "lame delegation" meant that while domains appeared correctly configured on the registrar side, DNS resolvers often encountered delays or outright failures when attempting to query for NS records, leading to significantly longer lookup times, unreliable lander access, and a generally degraded user experience. Crucially, Afternic Sellers also encountered difficulties changing nameservers for certain ccTLDs, as their registries conducted strict DNS "pre-delegation" tests that failed due to the lame delegation issues at Afternic.

As of today, Afternic is now correctly serving valid NS records for millions of customer domains, meaning the long-standing workaround of using NS3/NS4 or NS5/NS6 is, in principle, no longer necessary.
 
Last edited:
40
•••
I'm thrilled to announce the following.

After much persistent advocacy on this forum, it's a significant relief to finally confirm that Afternic has resolved the long-standing "lame delegation" issues affecting customer domains using NS1.afternic.com and NS2.afternic.com. Public DNS zone data shows that these NS1/NS2 servers alone are authoritative for over 3.5 million Seller domains. And Afternicโ€™s complementary NS3/NS4 and NS5/NS6 clusters together handle several million more.

For years, these "preferred" NS1 & NS2 nameservers provided invalid or non-responsive Namefind.com NS records, a problem extensively documented and a source of considerable frustration for domain owners. This "lame delegation" meant that while domains appeared correctly configured on the registrar side, DNS resolvers often encountered delays or outright failures when attempting to query for NS records, leading to significantly longer lookup times, unreliable lander access, and a generally degraded user experience. Crucially, Afternic Sellers also encountered difficulties changing nameservers for certain ccTLDs, as their registries conducted strict DNS "pre-delegation" tests that failed due to the lame delegation issues at Afternic.

As of today, Afternic is now correctly serving valid NS records for millions of customer domains, meaning the long-standing workaround of using NS3/NS4 or NS5/NS6 is, in principle, no longer necessary.
Amazing. I thought it would never happen! Well done on continually pressing for this.
 
3
•••
I'm thrilled to announce the following.

After much persistent advocacy on this forum, it's a significant relief to finally confirm that Afternic has resolved the long-standing "lame delegation" issues affecting customer domains using NS1.afternic.com and NS2.afternic.com. Public DNS zone data shows that these NS1/NS2 servers alone are authoritative for over 3.5 million Seller domains. And Afternicโ€™s complementary NS3/NS4 and NS5/NS6 clusters together handle several million more.

For years, these "preferred" NS1 & NS2 nameservers provided invalid or non-responsive Namefind.com NS records, a problem extensively documented and a source of considerable frustration for domain owners. This "lame delegation" meant that while domains appeared correctly configured on the registrar side, DNS resolvers often encountered delays or outright failures when attempting to query for NS records, leading to significantly longer lookup times, unreliable lander access, and a generally degraded user experience. Crucially, Afternic Sellers also encountered difficulties changing nameservers for certain ccTLDs, as their registries conducted strict DNS "pre-delegation" tests that failed due to the lame delegation issues at Afternic.

As of today, Afternic is now correctly serving valid NS records for millions of customer domains, meaning the long-standing workaround of using NS3/NS4 or NS5/NS6 is, in principle, no longer necessary.

Wooooooow!!!! Really appreciate your insistence on this!

You can actually see the landers resolve faster now.
 
Last edited:
4
•••
Now that was Fast, 3 hours from Sold, Payment Received to Payment Scheduled

Show attachment 279262

Payment has been received in lass then 24 hours after the domain was sold.
I have never had a transaction complete so fast. Nice(y)(y)
 
7
•••
Is anyone else encountering issues with Afternic 2FA via phone number? It randomly tells me that the number was used too often, then I select the backup number, and it just gets stuck in verifying the code.
 
1
•••
OK. I agree, folks. Sedo won't really care or take note. It will negatively impact their sales but not such that it will impact a weekend, holiday, long lunch, afternoon nap, or maintaining a steady course to oblivion.
yes, I agree,The Sedo platform doesn't have much sales anymore, but Sedo doesn't care. They only care about holidays, working one hour a day, and the rest of the work waiting for the second day, collective retirement
 
4
•••
ns1.afternic.com
ns2.afternic.com
ns3.afternic.com
ns4.afternic.com

I have seen many people giving feedback that there are issues with the NS1 and NS2 parking pages of the Afternic domain. I am curious why you do not use NS3 and NS4 since you are aware of the issues with NS1 and NS2?

Is there any disadvantage between NS3 and NS4 compared to NS1 and NS2?
 
Last edited:
0
•••
Is there any disadvantage between NS3 and NS4 compared to NS1 and NS2?
No.

Now that ns1/ns2 have been fixed, these are the preferred Afternic.com nameservers.

All 6 nameservers will respond with the same answer. You can even combine ns3 + ns6. Or, ns1 + ns5.

I assume though, that the new ns1/ns2 servers have the latest and most reliable tech stack that can scale in the future. These two nameservers handle the vast majority of domains for Afternic sellers (currently more than 3.5 million, based on public dns zone data).
 
Last edited:
4
•••
Payment has been received in lass then 24 hours after the domain was sold.
I have never had a transaction complete so fast. Nice(y)(y)
Spill the name you sold dude wtffff
 
3
•••
Nice sale though congarts shiiii


$$$$$!
 
Last edited:
1
•••
I
Spill the name you sold dude wtffff
I don't post names of my domain sales, I haven't done that in years.
This was just a review of the Afternic process to show the speed of a sale.
 
1
•••
I don't understand what is the big deal here.

GoDaddy acquired DAN.com 3 full years ago. DAN already had a streamlined domain selling process in place: from the moment a domain was sold to its transfer and payout you were looking at mere hours, even with DAN being stationed in the Netherlandsโ€”that was the only disadvantage for US-based sellers.

So it took Afternic 3 years to get up to speed! (pun intended.)

On another note, Afternic won't fix crap such as this:
 

Attachments

  • instructions.jpg
    instructions.jpg
    123.3 KB · Views: 77
3
•••
On another note, Afternic won't fix crap such as this:
There's a strong risk all these continued emails will cause GoDaddy/Afternic to be marked as spam more often, which has a detrimental effect on all their email communications.

Maybe our liaison can step in.
 
1
•••
Now that was Fast, 3 hours from Sold, Payment Received to Payment Scheduled

Show attachment 279262
That's what we love to see, @lennco. Thanks for sharing!

I'm thrilled to announce the following.

After much persistent advocacy on this forum, it's a significant relief to finally confirm that Afternic has resolved the long-standing "lame delegation" issues affecting customer domains using NS1.afternic.com and NS2.afternic.com. Public DNS zone data shows that these NS1/NS2 servers alone are authoritative for over 3.5 million Seller domains. And Afternicโ€™s complementary NS3/NS4 and NS5/NS6 clusters together handle several million more.

For years, these "preferred" NS1 & NS2 nameservers provided invalid or non-responsive Namefind.com NS records, a problem extensively documented and a source of considerable frustration for domain owners. This "lame delegation" meant that while domains appeared correctly configured on the registrar side, DNS resolvers often encountered delays or outright failures when attempting to query for NS records, leading to significantly longer lookup times, unreliable lander access, and a generally degraded user experience. Crucially, Afternic Sellers also encountered difficulties changing nameservers for certain ccTLDs, as their registries conducted strict DNS "pre-delegation" tests that failed due to the lame delegation issues at Afternic.

As of today, Afternic is now correctly serving valid NS records for millions of customer domains, meaning the long-standing workaround of using NS3/NS4 or NS5/NS6 is, in principle, no longer necessary.
We're glad we got this completed - thanks for your patience!

There's a strong risk all these continued emails will cause GoDaddy/Afternic to be marked as spam more often, which has a detrimental effect on all their email communications.

Maybe our liaison can step in.
There is a strategy behind follow-ups; something that was developed at Uniregistry, and implemented into Afternic. This follow-up strategy has resulted in 36% of sales in 2024 coming from leads over 30 days old. Our Director of Aftermarket Sales recently wrote about the follow-up strategies, here.

We do carefully monitor key metrics of our sends. Nonetheless, we'll make sure the team sees your concerns.
 
Last edited:
0
•••
I don't understand what is the big deal here.

The big deal is that neither Dan nor Afternic exist anymore and GoDaddy is having trouble duplicating the options and features of one or both of these shuttered platforms.

Instead they're using bits and pieces of other systems to kludge together a working domain marketplace, and it's really not working.
 
Last edited:
8
•••
Spaceship
Domain Recover
DomainEasy โ€” Payment Flexibility
  • The sidebar remains visible by scrolling at a speed relative to the pageโ€™s height.
Back