That's going to be more than inconvenient, that is impractical. There are 300+ domain names for sale, with many removed or added every day. By having the wildcard I don't have the 300+ domains actually in the config file, I just need to point the DNS to the IP#.
What I am asking is that every subdomain, even www, is not allowed on the HTTP port, such that the wildcard recognizes example.com but returns a 404 on requests for test.example.com, ssl.example.com and mail.example.com (mail, in fact, is handled by gmail, so no MX record is really necessary, but these are "hits" and "visits" I'm finding in my statistics log for the plugin). But example.com can be visited and the template for making an offer on just that domain is shown.
Perhaps I am not asking the question right either. If someone creates 4rrzz.com79wmwww.google.example.com (which only displays said template), what harm is there? Though it could be visited again, could it actually be abused? There are no pointers in var/www/html/wp-content/ showing such a "place."
What I am asking is that every subdomain, even www, is not allowed on the HTTP port, such that the wildcard recognizes example.com but returns a 404 on requests for test.example.com, ssl.example.com and mail.example.com (mail, in fact, is handled by gmail, so no MX record is really necessary, but these are "hits" and "visits" I'm finding in my statistics log for the plugin). But example.com can be visited and the template for making an offer on just that domain is shown.
Perhaps I am not asking the question right either. If someone creates 4rrzz.com79wmwww.google.example.com (which only displays said template), what harm is there? Though it could be visited again, could it actually be abused? There are no pointers in var/www/html/wp-content/ showing such a "place."