4 ms·
My 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 subdomai
by machrider 14y ago
My 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.)
- ams6110 14y agoJust fyi, mydomain.com is a real domain, example.com is better to use for illustrative purposes.
- signed0 14y agoAmusingly mydomain.com is a domain registrar. I wonder how many people stumble upon it by accident.
- 1337p337 14y agoexample.com isn't just better: it's actually specified in RFC 2606 as one of the domains "reserved for use in private testing, as examples in documentation, and the like."
- pi18n 14y agoThis is a good workaround, and I am voting you up in the hopes that others see it.
- lhnn 14y agoConfirmed to work with name.com Before: Parked page After: Bing search (thanks IE)
- soult 14y agoWhile it is probably not relevant for must users, there is a subtle difference between "There exists no A record for x.example.com" and "There is no x.example.com".
- drmonocle 14y agoA workaround for this is to make *.example.com a CNAME for something.invalid. ".invalid" is a reserved TLD guaranteed not to exist so this should force all queries for non-existent domains to come back with NXDOMAIN.
- JohnsonB 14y agoA workaround? As opposed to simply switching registrars with something decent?
- javajosh 14y agoyeah, the best workaround is namecheap.com
- EduardoBautista 14y agoI don't like being with resellers.
- moondowner 14y agoWhat do you think of http://en.gandi.net/ http://en.gandi.net/ guys? I'm on name.com as well but this thing is really bugging me.
- nicholassmith 14y agoI'm with gandi, there's a few things I don't like but overall they've been super stable with very little headaches. I think in the 3+ years I've been with them I've had one slight issue that was dealt with in <24 hours.
- nkozyra 14y agoI typically just do a *.example.com @A record to the IP address, works just as well and would fix the specific problem in the link (unless he's worried about having to extract individual subdomains to go separate places later).