They will not remove my domains from Dan.com (1 Viewing)

I kind of agree with this, as how is Dan supposed to know the actual owner of the domains is the one making the takedown request? Imagine if they just started deleting domains from any Tom, Dick or Harry who asked.

Of course Dan should require a DNS TXT or Nameserver confirmation for ANY new domain listing, not just those that are already present on their system.

DomainRecap said:

Of course Dan should require a DNS TXT or Nameserver confirmation for ANY new domain listing, not just those that are already present on their system.

Click to expand...

The TXT verification is virtually impossible with a large portfolio, it would take forever to add that by hand.

Nameservers are easy, you can change them in bulk and then change them back one verified.

That said, changing them back will cost 25% commission.

PS. I have not used one godaddy service since they implemented the 25% nameserver rule.
I still have some larger portfolios I purchased from other domainers that are sitting at godaddy but I cherry picked the domains I wanted to keep and moved them out. The other domains are sitting there waiting to expire, mainly worthless .ca and .net extensions with a few oddball extensions mixed in. I moved out all .coms because I'm not giving them to the godaddy expired auction.

This entire space is due for a massive interruption when a new dan.com appears on the horizon. Godaddy will have to adapt if they want to retain/regain the larger bargain hunting portfolios.

Here is a good article about godaddy and their market share. I cannot see it going up further in market value charging the massive commissions and totally uncompetetive renewal prices.

https://domainnamewire.com/2023/09/12/starboard-calls-for-godaddy-to-cut-costs/

MapleDots said:

The TXT verification is virtually impossible with a large portfolio, it would take forever to add that by hand.

Click to expand...

If your registrar supports Aliases, it's as easy as pie. Just create one mule domain with DNS TXT and paste in the rest as Alias domains.

Kudos to @bmetal for outlining how to do this.

DomainRecap said:

If your registrar supports Aliases, it's as easy as pie. Just create one mule domain with DNS TXT and paste in the rest as Alias domains.

Kudos to @bmetal for outlining how to do this.

Click to expand...

Maybe he could post a quick tutorial

MapleDots said:

Maybe he could post a quick tutorial

Click to expand...

It's basically just using the same DNS data (zone file) for multiple domains... but it requires that you either run your own DNS servers or use a DNS service that supports the idea. It's a useful concept that we've used both in our hosting and our domain-dns.com service for decades.

baremetal.COM baremetal.CA baremetal.NET .ORG etc ... they all use the same configuration and life is simpler if you don't have to update all of them if there is a change, and they don't get out of sync this way.


-Tom