Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
When it comes to DNS WildCards, you’ll need to set them up using an A entry, which would look like:
A * DROPLET_IP
or
A *.m DROPLET_IP
The first DNS entry catches anything at the first level – www, test, forum.domain.com, etc. The second works much like the first, though it catches anything targeting m.domain.com, so:
test01.m.domain.com
test02.m.domain.com
etc
With NGINX, you would then specify the WildCard in the server_name, for example:
server_name domain.com www.domain.com *.domain.com
or
server_name m.domain.com www.m.domain.com *.m.domain.com;
The * entry tells NGINX to handle the WildCard requests, but it will only do so if the DNS is properly setup as noted above. Without the WildCard DNS, NGINX won’t handle the requests as expected.