Donaldson R F
DNS, Security & Integrations
Configure Subdomain
Set up a new subdomain for your project, app, or service, pointed correctly from the start.
The Problem
You need a subdomain (like app.yourdomain.com or blog.yourdomain.com) set up and pointed at the right place, and getting the record type and target wrong means it either doesn't resolve or serves the wrong content.
About this problem
Subdomains let you run separate services or sections under the same root domain without buying a new domain — a blog, an app, a staging environment, an API. Each one needs its own DNS record (usually an A or CNAME, depending on what it's pointing to), and whether it needs its own SSL certificate depends on how it's hosted.
This typically comes up when launching a new section of a site, connecting a third-party tool that needs its own subdomain, or separating a staging/testing environment from the live site.
What's Included
- Confirming what the subdomain needs to point to (an IP, another hostname, or a specific platform)
- Creating the correct DNS record for that subdomain
- Checking SSL coverage for the new subdomain if it's served over HTTPS
- Verifying the subdomain resolves and loads correctly
What's NOT Included
- Building or hosting whatever the subdomain actually serves
- SSL certificate issuance if it needs a separate process from your main domain's certificate
- Ongoing content or application management on the subdomain
How It Works
- Confirm exactly what the subdomain should point to and what it's for.
- Choose the correct record type (A for a direct IP, CNAME for another hostname).
- Create the DNS record for the subdomain.
- Check whether the subdomain needs its own SSL certificate or is covered by an existing wildcard certificate.
- Verify resolution and that the subdomain actually serves the intended content once live.
In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.
Frequently Asked Questions
- What is a subdomain and why would I need one?
- A subdomain is a prefix added to your domain (like shop.yourdomain.com) that can point to a completely separate server or service, useful for running multiple projects under one domain.
- Does a subdomain need its own SSL certificate?
- Often yes, unless your main domain's certificate is a wildcard certificate that covers all subdomains — this gets checked and sorted out as part of the setup.
- Can a subdomain have different hosting than my main website?
- Yes, that's one of the main reasons to use subdomains — each one can point to entirely different infrastructure.
- How many subdomains can I create?
- Practically unlimited from a DNS perspective, though your hosting setup for each one is a separate consideration.
- Will creating a subdomain affect my main website?
- No, a correctly configured subdomain is independent and won't affect your root domain's existing configuration.
- Can I use a subdomain for email, like mail.yourdomain.com?
- Yes, though that's typically done via MX records on the subdomain itself rather than a simple A/CNAME, and is a slightly different setup — mention this upfront if that's your goal.