A wildcard DNS record (for example, *.example.com) sends all subdomains that do not have their own record to the same target (IP address or hostname).
This is useful for platforms that automatically create subdomains (for example, client1.example.com, client2.example.com) or for development environments.
Important limitations
- A wildcard DNS record does not automatically create a website in Plesk. It only resolves DNS. Your web application must be able to handle dynamic subdomains, or you must create the required subdomains in Plesk.
- The wildcard record will not override an existing record. If you create
blog.example.com later, it will have priority over *.example.com.
Before you start
- This guide applies if your domain uses GARMTECH nameservers:
ns1.garmtech.com, ns2.garmtech.com, ns3.garmtech.com.
- If your DNS is managed elsewhere (for example, Cloudflare), create the wildcard record there instead.
Create a wildcard record in Plesk DNS
- Log in to Plesk (you can open it from My.GARMTECH).
- Go to Websites & Domains and click your domain (for example,
example.com).
- Open DNS Settings.
- Click Add Record and choose one of the common options:
Option A — Wildcard A record (recommended for most cases)
- Record type: A
- Domain name:
*
- IP address: your hosting server IP address (find it in My.GARMTECH service details or in Plesk)
Option B — Wildcard CNAME record (if you want to follow another hostname)
- Record type: CNAME
- Domain name:
*
- Canonical name: for example,
example.com (or another hostname you control)
After adding the record, click Update to apply changes.
Propagation and testing
- DNS changes may take time to propagate (depends on TTL and resolver cache).
- You can test a random subdomain in a browser, for example:
https://test123.example.com.
Next step: website configuration (if needed)
If you need Plesk to serve a separate website for a subdomain, create the subdomain in Plesk (Add Subdomain) and deploy the content to its document root.
