A wildcard subdomain lets DNS answer for multiple names without creating a separate record for each one. For example, *.example.com can support an application with several workspaces. Use this for a defined requirement: it does not automatically redirect visitors or make every address work over HTTPS.
Define the names and expected behavior
For a few known subdomains, individual records are often easier to control. Before using a wildcard, identify the allowed names, the website or application to display, and what should happen for an unknown name. The application must recognize incoming names and reject those that do not match an authorized workspace.
A DNS wildcard does not replace the record for the main domain, example.com. Existing names, delegations and the zone structure limit where it applies. It can also answer for some deeper names, so do not assume that it always covers only one level. Check Cloudflare’s DNS wildcard rules if that provider manages your zone.
Prepare the destination in cPanel
- Confirm the hosting account and retain its current settings. Check that your service and application support the intended setup.
- If available, open Domains, then Create A New Domain, and enter
*.example.com, replacing the example domain. - Select the document root for the intended content. Sharing the main website’s directory can expose that same website under other names. An application may require additional web-server or routing configuration.
Available options depend on your account. If the name is rejected or the destination is unclear, have the configuration checked before proceeding. The official cPanel procedure describes creation through the current interface.
Update the authoritative DNS zone
Make the change with the provider that actually hosts your DNS. A record added in cPanel will not be used publicly when another provider is authoritative. Retain the previous values and email records, then check the complete record name before saving.
- A: a confirmed IPv4 address for the service.
- AAAA: an IPv6 address only when the service actually supports it.
- CNAME: a target hostname, without
https://or a path. It is not an HTTP redirect and must not coexist with other record data at the same name.
Use our guide to identify your hosting address, rather than copying an example address or your own Internet connection’s IP. The name to enter, often * or *.example.com, depends on the DNS editor.
Check HTTPS and the website separately
A certificate for *.example.com covers names such as app.example.com, but by itself covers neither example.com nor a.app.example.com. This TLS rule differs from DNS wildcards. With Let’s Encrypt, a wildcard certificate requires DNS-01 validation. Automatic issuance and renewal depend on the available integration. If you use a proxy, also check its HTTPS connection to the origin server.
After DNS caches update, test the intended names, an unknown name, content, application sign-in and the certificate. A correct DNS answer does not prove that the website works. Avoid a universal landing page that unintentionally publishes the same content under unwanted names.
To validate routing, HTTPS coverage or an application with multiple workspaces, contact Nuagerie with the affected names and expected behavior. Do not send passwords or DNS tokens.
