On the Apache configuration, you need to create an extra virtualhost
container and set it up in one of the httpd.conf include files executed
after the normal virtualhost configurations load.
I see you listed a wildcard to every TLD but that is not necessary as
you could just simply put a wildcard for the server name itself (*) and
any web connections that are not by IP directly without resolution or
resolving to any existing site on your server would trigger the wildcard
site to display.
The trick under cpanel is to use the include files because if you just
simply add the wildcard DNS virtualhost to httpd.conf by itself, it
will get overwritten quickly by Cpanel and removed again.
Anyway ...
Using a wildcard virtualhost is particularly useful for trapping domains
that still resolve to your server's IP address even though you don't have
any accounts setup for those domains specifically.
You won't need to do anything in terms of DNS configuration for what
you are asking but the same technique could be applied to allow for
wildcard subdomains as long as the entry comes after your regular
virtualhosts and before this full wildcard virtualhost entry. For those
you would need to make a wildcard DNS update in the DNS of the
domains but the principle is the same.
Just for a side FYI on wildcard DNS since I mentioned it:
On Apache (httpd.conf) configuration side:
Code:
ServerName *
ServerAlias *
(Or 'subdomain.*' for wildcard subdomains as also mentioned)