Earlier quoted context omitted.
> One thing I'm not willing to do is set up a wildcard A record 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?
1. I don't want to provide multiple entry points. As an intentionally vulgar example, http://f***you.example.com would resolve if using a wildcard address. That is unacceptable. 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 instea…
Bro, just stop, you don't understand DNS. Lots of people use wildcards.