3 ms·

I use name.com, and will never register another domain with them, nor recommend them to anyone. It's barely acceptable for a mostly unused vanity domain, but if

by jsnell 14y ago

I use name.com, and will never register another domain with them, nor recommend them to anyone. It's barely acceptable for a mostly unused vanity domain, but if I were using the domain in any serious way I'd transfer it away in a heartbeat. The problem: If you use their name servers, they install a wildcard record for the domain pointing at a crummy adspam page. You can override the wildcard record with your own, but not disable it completely, which is completely unacceptable. Their explicitly stated reason for fucking over their customers is "we make more money this way". Which would be fine, but there's actually no way they'd be making even pennies on my domain, and they are actively reducing its utility by a much larger amount.

agwa 14y ago
Oh please. While I agree that's undesirable, it's a problem with their DNS hosting service (which is free) and not their registrar service (which you pay for). By all means warn people away from their free DNS hosting, but it's not fair to trash the whole company.
- jsnell 14y ago
  That's a very strange view. It's clearly not a free service, but part of what you pay for. In fact is a large part of what you pay for -- very few organizations are going to be hosting their own name servers these days. But more importantly, I don't see how this can possibly be an unfair criticism. They are providing a uniquely crappy service, and have shown what I consider to be a flagrant disregard for their customers by degrading their service for no benefit at all to name.com. It's stupid, it's evil, and it's bad business. Why in the world would I trust or recommend them? (Just to be clear: I'm not complaining that there's a wildcard DNS record by default. Parking domains by default seems to be how everyone in the business works. I'm complaining about the fact that the wildcard DNS record stays in effect even after you configure the comain, and can only be disabled by defining your own bogus wildcard record instead. Basically it turns every user of their service into an unintentional typosquatter.)

by jsnell 14y ago

agwa 14y ago

Oh please. While I agree that's undesirable, it's a problem with their DNS hosting service (which is free) and not their registrar service (which you pay for). By all means warn people away from their free DNS hosting, but it's not fair to trash the whole company.

jsnell 14y ago
That's a very strange view. It's clearly not a free service, but part of what you pay for. In fact is a large part of what you pay for -- very few organizations are going to be hosting their own name servers these days. But more importantly, I don't see how this can possibly be an unfair criticism. They are providing a uniquely crappy service, and have shown what I consider to be a flagrant disregard for their customers by degrading their service for no benefit at all to name.com. It's stupid, it's evil, and it's bad business. Why in the world would I trust or recommend them? (Just to be clear: I'm not complaining that there's a wildcard DNS record by default. Parking domains by default seems to be how everyone in the business works. I'm complaining about the fact that the wildcard DNS record stays in effect even after you configure the comain, and can only be disabled by defining your own bogus wildcard record instead. Basically it turns every user of their service into an unintentional typosquatter.)