(Workaround shouldn't be necessary of course, but this kind of bullshit is par for the course with cheap hosting companies.)
Before: Parked page
After: Bing search (thanks IE)
I'll say the same thing I said then:
As an anecdotal counterpoint, I'm an extremely happy Name.com customer. I transfered several domains to them a year or so ago from GoDaddy. They support two-factor authentication, their interface is uncluttered, I pay them less money than I paid GoDaddy, and I haven't had a single issue. I would highly recommend them to anyone looking for a registrar.
That being said, I don't use them for DNS. If this is a feature of their nameservers, I do find it strange that they don't offer a way to opt out (other than using alternative nameservers).
I am still an incredibly happy Name.com customer and would recommend them as a registrar to anyone who asks. I just would point them somewhere else for DNS hosting.
I do mind the idea of them treating ever possible 3LD as a parked domain, when my domain is not parked (and configured using their Name Servers).
If you've never done it, it is a couple of hours of reading and fiddling, but very quick if you have set up DNS before. I'm actually a bit curious about why people (even some sysadmins!) tend to spend time clicking on some clunky web interface to update records manually when it's actually easier to do it yourself. (Mail servers, on the other hand...)
Personally, I got Bind installed on all my machines, both for DNS zones and resolving. The only exception is my phone, and that is only because I couldn't find a package for it.
For those that do not want to deal with config files, there is also GUIs like gadmin-bind.
Of course, it would be better for them to simply charge a bit more and get rid of it altogether, especially since it breaks standards.
Still using NameCheap here.
(OK, maybe I would)
EDIT: I really don't understand your thinking; I am the opposite. I respect name.com for being forward about it and not acting like a politician (treating me like a child).
I respect them for sharing their reasons. I think it is professional.
My issue is two fold:
- This kind of activity "breaks the internet" on the purest sense possible. It is against spec' for a very good reason, IT IS STUPID. Going to a null domain should give you a null reply. It breaks software and it breaks user's expectations (e.g. if you hit that page because you typo-ed the domain you might assume the domain has gone out of business or been "hacked").
- Their work-around(s) are silly. They are essentially "then use someone else" or "register every single possible sub-domain." No opt-out.
They might be very good at business and marketing but they fail on every technological ground you can fail. Someone who fails that badly at understanding the internet isn't someone I want running my DNS of all things...
"Use someone else" is the opt-out, whether you take it to mean "use another registrar" or use "other, non-gratis DNS services.
Your other option is to use a wildcard, as I think you understand (though your "register every single possible sub-domain" is a bit misleading).
This behavior sucks, but if it's something that bothers you, you're probably the type that should be using a better DNS provider, anyways. That said, I'm a happy customer of name.com.
If your server falls off of the net your DNS goes boom too and you have no shot of redirecting people to a landing page or similar "oh shit" activities.
Now you could re-point your nameserver records but in my experience that takes longer to propagate than a new A record with a short TTL.
 IMO, the use of wildcard certs is a dangerous practice made obsolete by SNI.
 If the cert gets stolen from one server, the thief can impersonate any server on that domain.
Personally, I use a third-party dns service. Seen too many registrars play with DNS. Don't know why anyone would trust them.
I don't know about you, but i give everyone the benefit of doubt and unless someone violates this trust, i'd think most people do too.
Also, at least i tend to think of registrars as some kind of neutral entity that i, indeed, can trust - guess there are some exceptions to the rule.
How many years and years of abuse has it taken for people to notice what GoD*ddy has been doing all that time and finally cause some sort of mass-defect to other registrars..
Hopefully, the level of tolerance for this behavior is of an all-time low so registrars simply can't afford to abuse the trust of their customers any longer.
True.. and I used to trust registrars to manage my DNS.. but over the years, this is at least the 3rd or 4th time this has happened with a registrar I am on (yes, I have domains at name.com).
Since I don't have time to interrogate every registrars DNS server when I sign up, I just assume it's useless these days. + I end up having to pay for a DNS service anyway, to avoid the bad registrars DNS.. so it's easier to use a single DNS service for all of the domains.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, firstname.lastname@example.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
All domain names registered via Name.com will automatically be provided a Parked Domain Service. All domains will default to our name servers unless and until you modify your default settings. At any time, you may disable the placeholder page by updating, modifying or otherwise changing the name servers for the relevant domain name.
Domain names using our Parked Domain Service may display a placeholder page for your future website. These placeholder pages may include contextual and/or other advertisements for products or services. Name.com will collect and retain any and all revenue acquired from these advertisements, and you will have no right to any information or funds generated via the Parked Domain Service.
You agree that we may display our logo and links to our website(s) on pages using the Parked Domain Service.
Name.com will make no effort to edit, control, monitor, or restrict the content displayed by the Parked Page Service. Any advertising displayed on your parked page may be based on the content of your domain name and may include advertisements of you and/or your competitors. It is your responsibility to ensure that all content placed on the parked page conforms to all local, state, federal, and international laws and regulations.
It is your obligation to ensure that no third party intellectual or proprietary rights are being violated or infringed due to the content placed on your parked page. Neither Name.com nor our advertising partners will be liable to you for any criminal or civil sanctions imposed as a direct or indirect result of the content or links (or the content of the websites to which the links resolve) displayed on your parked pages.
As further set forth above, you agree to indemnify and hold Name.com and its affiliated parties harmless for any harm or damages arising from your use of the Parked Domain Service.
Oh, and don't use name.com, they hijack DNS. :)
A previous series of support emails:
I own the joshka.net domain registered with name.com.
When I attempt to resolve a subdomain that does not exist I expect this to
return a NXDOMAIN result.
Instead, the name.com name servers return an IP address of spammers.
How can I setup my account to return NXDOMAIN for this domain?
I have set your domain to a wildcard 'A' record, that accepts any
subdomain, and points it to your hosting IP address. I ran a 'dig' [ping]
command on 'stuff.joshka.net' as a test, please see the results below:
I think we have a slight misunderstanding. I do not want a wildcard A record
(and have removed the record that was setup).
Resolving any subdomain that I have not explicitly created a DNS record
should return a NXDOMAIN result.
This expectation is in line with ICANN's memorandum titled "Harms and
Concerns Posed by NXDOMAIN Substitution (DNS Wildcard and Similar
Technologies) at Registry Level" at
Providing this default wildcard service where it is not requested or
required is a disservice. I can't imagine why I would want or need this.
I apologize for the misunderstanding with the wildcard DNS record. We have had multiple customers request this in the past, and this feature was used with success in those cases. I have consulted our management team to see if there is a different option that we can provide you. Please look for a response concerning this issue tomorrow.
I'll look forward to hearing from you.
It's not the wildcard DNS itself that I couldn't see the use of. I
understand why that would be useful in narrow situations.
What I don't understand is why name.com provide the default wildcard A
record redirecting to a site full of advertising. I don't know how this
would be useful to any business or entity that does not want to use wildcard
subdomains of their own.
I understand that section 19 of the registration agreement seems to cover
this use of wildcards (though the wording is fairly vague), but it also
states "At any time, you may disable the placeholder page by updating,
modifying or otherwise changing the name servers for the relevant domain
Thanks for getting back with us. Yes you are correct, by changing the DNS or name servers for this domain, it will no longer point to the parking page.
I have discussed all options for allowing this wording to show, with our support management team, and the systems administration group. We sincerely apologize, however our DNS servers are not able to show the 'nxdomain' that you mentioned.
This option is possible should you wish to use your own custom name servers for this domain. Should you wish to setup your own name servers, here are instructions for registering these name servers from within your Name.com account
They support two-factor auth (almost no one else does), and have nicely scoped cookies (HTTP only, Secure flag, etc.).
Now, if one of your authenticated users visits the wrong subdomain, they are directed to a server of name.com's choice.
Thanks for the correction.
GoDaddy is the absolute devil though. We all know that.