<story><title>Name.com hijacks non-existent subdomains and redirects to their servers</title><url>http://www.destructuring.net/2013/02/28/name-com-is-doing-some-really-sketchy-stuff/</url><text></text></story><parent_chain><item><author>machrider</author><text>My workaround for this was to add a TXT record for *.mydomain.com that just returns a string like &quot;Unused&quot;.  This seems to stop them from hijacking any subdomains, and it&apos;s not an A record so undefined subdomain names do not resolve, just like if you had not defined them in the first place.&lt;p&gt;(Workaround shouldn&apos;t be necessary of course, but this kind of bullshit is par for the course with cheap hosting companies.)</text></item></parent_chain><comment><author>ams6110</author><text>Just fyi, mydomain.com is a real domain, example.com is better  to use for illustrative purposes.</text></comment>
<story><title>Name.com hijacks non-existent subdomains and redirects to their servers</title><url>http://www.destructuring.net/2013/02/28/name-com-is-doing-some-really-sketchy-stuff/</url><text></text></story><parent_chain><item><author>machrider</author><text>My workaround for this was to add a TXT record for *.mydomain.com that just returns a string like &quot;Unused&quot;.  This seems to stop them from hijacking any subdomains, and it&apos;s not an A record so undefined subdomain names do not resolve, just like if you had not defined them in the first place.&lt;p&gt;(Workaround shouldn&apos;t be necessary of course, but this kind of bullshit is par for the course with cheap hosting companies.)</text></item></parent_chain><comment><author>soult</author><text>While it is probably not relevant for must users, there is a subtle difference between &quot;There exists no A record for x.example.com&quot; and &quot;There is no x.example.com&quot;.</text></comment>