Afternic - Official Thread

[GoDaddy]

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.

 

[Future Sensors]

@fka Your post confuses me because you observe the same thing as I do, but at the same time ask me, "Are you sure?"

 

[fka]

@fka Your post confuses me because you observe the same thing as I do, but at the same time ask me, "Are you sure?"

Sorry, I wasn't clear.

A nameserver that doesn't respond is skipped by clients, we specify multiple nameservers so that if some are down, the others can still respond, e.g: if ns1.afternic.com then the client will talk to ns2.afternic.com instead.

If verification-*.ns101.verify.hn is responding to requests on port 53 that would be bad because it isn't the intended authoritative nameserver, it doesn't know which records to serve. If verification-*.ns101.verify.hn isn't responding then it'll be skipped and the actual nameservers will respond which is good.

 

[Future Sensors]

@fka In the past, the 3rd (per seller) unique verification NS always responded to DNS queries. It's not a TXT record. When such a 3rd NS is present, it should act like any other NS, and simply work as intended. A dead NS always causes delays and failures. Sure, the other NSs get tried afterward, but only after timing out.

It seems we may have different views on what constitutes a proper networking setup.

 

[Future Sensors]

So @fka, okay the 1/3 is a bit too strong. But at the same time, Afternic should improve monitoring their infra. This is not the first time, isn't it?

https://www.namepros.com/threads/afternic-ns1-ns2-lame-delegation-finally-resolved.1358059/

My recommendation to remove the 3rd verification nameserver remains unchanged.

 

[fka]

@fka In the past, the 3rd (per seller) unique verification NS always responded to DNS queries.

Ah, I wasn't aware of that. I figured it worked as a no-op nameserver because a no-op nameserver seems like the right implementation. As I understand it, the purpose of the verification nameserver is as a value that the system can match by doing a whois lookup (e.g: the system does a whois lookup for the domain and checks if the verification server appears in the list of nameservers).

 

[Future Sensors]

All good.

Now fix your things @GoDaddy.

 

[TonnyDomains]

All good.

Now fix your things @GoDaddy.

I am certain that you have to speak louder to catch the attention of GoDaddy

 

[Future Sensors]

@fka Some background. The .hn TLD was selected specifically to bypass some checks done by ccTLD registries that enforce pre‑delegation checks on auths, and strict hostname or delegation constraints. Some registrar panels (and registries) won't accept all these unique Afternic verification NS auths under all TLDs. AFAIK, the .hn TLD still has issues for some ccTLDs (I believe .de and friends), so sometimes the .is TLD is used by other marketplaces.

The previously mentioned lame delegation issues on ns1 & ns2 (now resolved) also contributed to certain ccTLD registries rejecting even ns1 and ns2. But that behavior is no longer occurring.

 

[Future Sensors]

I am certain that you have to speak louder to catch the attention of GoDaddy

Maybe. But it's weekend. Afternic nameservers are only required to respond Monday through Friday.

 

[wwwweb]

Sorry, I wasn't clear.

A nameserver that doesn't respond is skipped by clients, we specify multiple nameservers so that if some are down, the others can still respond, e.g: if ns1.afternic.com then the client will talk to ns2.afternic.com instead.

If verification-*.ns101.verify.hn is responding to requests on port 53 that would be bad because it isn't the intended authoritative nameserver, it doesn't know which records to serve. If verification-*.ns101.verify.hn isn't responding then it'll be skipped and the actual nameservers will respond which is good.

For some reason, I have 0 new leads at afternic today, I do use the 3rd verification server, and I have had multiple leads every single day going back over a year.