On an ethical level this is closer to typo-squatting, something that there are rules against.
On an ethical level this is closer to typo-squatting, something that there are rules against.
Why not? I'm being earnest here, I'm a name.com customer and I do have such a wildcard record. Are you building a network service that relies on nonexistent subdomains being resolved at the DNS level (rather than a 404 page or a redirect to a subdomain that does exist)? Or is it more of a philosophical thing?
2. I'm in the process of setting up a self-assembling system that will need to be environment aware (public, staging, dev). If I redirect everything to a single A record I actually have to perform logic on my end. A failed request will instead mean to simply move to the next in the list. (Or that is how I am scheming for it to work anyway, not being built yet I don't know how it will turn out.)
if ($host !~ "^(example.com|beta.example.com|valid.example)$") {
rewrite ^/(.*)$ http://example.com/$1 permanent;
}
http://www.example.com/aboutor
http://fuckshit.example.com/about
becomes
This is good practice in any case, so that you're always serving up the canonical URL.