Name.com hijacks non-existent subdomains and redirects to their servers
21–30 of 93 posts
Re: Name.com hijacks non-existent subdomains and redirects to their servers
#22My workaround for this was to add a TXT record for *.mydomain.com that just returns a string like "Unused". This seems to stop them from hijacking any subdomains, and it's not an A record so undefined subdomain names do not resolve, just like if you had not defined them in the first place. (Workaround shouldn't be necessary of course, but this kind of bullshit is par for the course with cheap hosting companies.)
Re: Name.com hijacks non-existent subdomains and redirects to their servers
#23My workaround for this was to add a TXT record for *.mydomain.com that just returns a string like "Unused". This seems to stop them from hijacking any subdomains, and it's not an A record so undefined subdomain names do not resolve, just like if you had not defined them in the first place. (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)
Re: Name.com hijacks non-existent subdomains and redirects to their servers
#24The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@destructuring.net 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.
Re: Name.com hijacks non-existent subdomains and redirects to their servers
#25My workaround for this was to add a TXT record for *.mydomain.com that just returns a string like "Unused". This seems to stop them from hijacking any subdomains, and it's not an A record so undefined subdomain names do not resolve, just like if you had not defined them in the first place. (Workaround shouldn't be necessary of course, but this kind of bullshit is par for the course with cheap hosting companies.)
Just fyi, mydomain.com is a real domain, example.com is better to use for illustrative purposes.
Re: Name.com hijacks non-existent subdomains and redirects to their servers
#26Re: Name.com hijacks non-existent subdomains and redirects to their servers
#27By default, every 404 page hosted with HostGator puts an advertisement for HostGator hosting on your site.
Re: Name.com hijacks non-existent subdomains and redirects to their servers
#28My workaround for this was to add a TXT record for *.mydomain.com that just returns a string like "Unused". This seems to stop them from hijacking any subdomains, and it's not an A record so undefined subdomain names do not resolve, just like if you had not defined them in the first place. (Workaround shouldn't be necessary of course, but this kind of bullshit is par for the course with cheap hosting companies.)
Re: Name.com hijacks non-existent subdomains and redirects to their servers
#29It's really not that hard to run your own nameserver. While I obviously disagree with what they're doing, I think you should have been running your own in the first place.
It's really not hard at all. I wrote a blog post about my setup a few months ago[1]. To summarize: djbdns + a few VPS instances which can be very tiny + puppet. [1]: https://bugsplat.info/2012-12-31-how-i-run-my-own-dns.html
Re: Name.com hijacks non-existent subdomains and redirects to their servers
#30http://www.name.com/blog/general/domains/2012/01/pro-tip-how...
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.