Sedo.com - Official Thread

[Sedo]

Hi All! :hi:

By request, we've decided to start a thread dedicated to Sedo. We're looking for invaluable insight into what domainers want and need out of our parking program (and marketplace, of course).

Questions, comments, suggestions, tips are welcome! We're hoping this will be a great discussion about what works at Sedo and what might not (please be constructive and respectful to others in your feedback) so that everyone involved can benefit and learn from it.

Looking forward to hearing your thoughts and ideas! Happy Holidays!

Always,
Keith
(on behalf of Sedo)

 

[tom365]

...

 

[Future Sensors]

@tom365

I understand that you’re experiencing several issues. From your screenshot, it appears that you are accessing Sedo from China, which might be contributing to these problems.

Regarding the name servers: while website visitors typically don’t notice them, they can be significant in China due to potential blocking mechanisms, which seems to be affecting your experience accessing Sedo.

I’ve personally switched from ns1.sedoparking.com and ns2.sedoparking.com to sl1.sedo.com and sl2.sedo.com. The new landers (#15) on this new infra do not have a captcha, and TLS (https) certificates are generated much faster. Overall, I see only benefits.

You also mentioned a 10% decrease in sales. Could you please explain how you calculated this figure, and how many sales and how many sellers were included in your analysis? Also, during what period did you perform this test and in what way?

 

[Future Sensors]

@tom365

Another factor that might be contributing to your decreased sales is the setup of a non-functional nameserver for a domain you tried to sell through NamePros. The nameserver you're using is ‘THIS.DOMAIN-IS-4-SALE-AT-DAN.COM’, it does not respond to queries and is not an official DAN nameserver.

If you are configuring your nameservers in this manner for all your domains, it’s understandable that your sales have decreased. However, this issue is not related to Sedo.

At this point, it seems like you’re placing all the blame on Sedo, but I have serious doubts about your conclusions, because you're misconfiguring things yourself for your domains.

 

[Future Sensors]

I've never used their landers. What's the difference between the 2 sets?

The main difference is that sl1.sedo.com and sl2.sedo.com are specifically created on Sedo's new infrastructure for only Sedo's sales lander #15, which is a pretty clean sales lander. When using these nameservers, there will not be a Cloudflare captcha.

You can still use the traditional ns1.sedoparking.com and ns2.sedoparking.com nameservers with Sales lander #15, but then your visitors will be bothered with a Cloudflare captcha. Also, TLS (https) certificate provisioning will be a bit slower for your landers.

If you prefer other landers than Sedo's sales lander #15, you cannot use sl1.sedo.com and sl2.sedo.com but should use the traditional ns1.sedoparking.com and ns2.sedoparking.com nameservers. Sales and parking landers can then be configured from the dashboard.

I'm now using sl1.sedo.com and sl2.sedo.com.

 

[tom365]

...

 

[Future Sensors]

It is the third DNS, and it only comes to this DNS when the first and second DNS do not respond.

Technically not true.

 

[tom365]

The main difference is that sl1.sedo.com and sl2.sedo.com are specifically created on Sedo's new infrastructure for only Sedo's sales lander #15, which is a pretty clean sales lander. When using these nameservers, there will not be a Cloudflare captcha.

You can still use the traditional ns1.sedoparking.com and ns2.sedoparking.com nameservers with Sales lander #15, but then your visitors will be bothered with a Cloudflare captcha. Also, TLS (https) certificate provisioning will be a bit slower for your landers.

If you prefer other landers than Sedo's sales lander #15, you cannot use sl1.sedo.com and sl2.sedo.com but should use the traditional ns1.sedoparking.com and ns2.sedoparking.com nameservers. Sales and parking landers can then be configured from the dashboard.

I'm now using sl1.sedo.com and sl2.sedo.com.

 

[Future Sensors]

@tom365

It is now very clear that you are giving unreliable information about Sedo at all levels. In addition, it appears that you are configuring your own domains incorrectly, and do not even understand the operation of DNS at a technical level. I will leave it at that.

 

[tom365]

...

 

[Jannes]

I have always emphasized the reason：

because No one knows what Sedo.com does, but Sedoparking is more recognizable

Sedoparking means that the domain name is available for sale when parked. We hope sedo can pay attention to these details

but now Sedoparking.com need Cloudflare captcha. It has been like this for many years, why not cancel it?

Everyone in the industry knows what Sedo does. Outside of the industry, very few people know what even Afternic does. Why don't you ask Afternic to use afternicparking nameservers?

 

[tom365]

...

 

[tom365]

...

 

[Jannes]

Are you investing in domain names to sell to industry professionals?

Do you think that end users associate 'parking' with domain names rather than cars?

 

[tom365]

...

 

[Future Sensors]

I believe some people can understand what I'm saying, if you are very professional in selling domains

 

[Jannes]

I believe some people can understand what I'm saying, if you are very professional in selling domains

I appreciate how patient you are with those of us who don't understand.

 

[Future Sensors]

It is the third DNS, and it only comes to this DNS when the first and second DNS do not respond.

Let me explain to you how this works. It's definitely not how you describe.

When a domain has multiple nameservers listed, the DNS resolver does not strictly follow a sequential order, meaning it doesn’t use the third nameserver only if the first two fail. Instead, DNS resolvers typically use a round-robin approach or select a nameserver based on factors like response time and availability. This means that the third nameserver can be queried even if the first two are functioning properly.

DNS resolvers often distribute queries among all available nameservers to balance the load. Additionally, some DNS resolvers may prefer nameservers that respond more quickly, so if the third nameserver has a faster response time, it might be queried more frequently.

Having multiple nameservers ensures redundancy, so if one or more nameservers are down, others can still respond. However, this doesn’t mean the third nameserver is only used as a last resort. Instead, it can be actively used along with the others to ensure better performance and reliability.

I wish you good luck learning the basics of domaining and DNS.

 

[tom365]

I don't think I should have shared so much experience.I have deleted the relevant proposal.

 

[tom365]

I appreciate how patient you are with those of us who don't understand.

I don't think I should have shared so much experience. I have deleted the relevant proposal

 

[tom365]

Let me explain to you how this works. It's definitely not how you describe.

When a domain has multiple nameservers listed, the DNS resolver does not strictly follow a sequential order, meaning it doesn’t use the third nameserver only if the first two fail. Instead, DNS resolvers typically use a round-robin approach or select a nameserver based on factors like response time and availability. This means that the third nameserver can be queried even if the first two are functioning properly.

DNS resolvers often distribute queries among all available nameservers to balance the load. Additionally, some DNS resolvers may prefer nameservers that respond more quickly, so if the third nameserver has a faster response time, it might be queried more frequently.

Having multiple nameservers ensures redundancy, so if one or more nameservers are down, others can still respond. However, this doesn’t mean the third nameserver is only used as a last resort. Instead, it can be actively used along with the others to ensure better performance and reliability.

thanks your share.