DNS Setup
Sending a Subdomain to a Different Server Entirely
A subdomain doesn't have to live on the same server as your main site — an A record or CNAME can send shop., blog., or app. anywhere else on the internet.
2
Record types used: A record or CNAME
1
Subdomain record needed, independent of the root domain
24-48h
Typical worst-case propagation window for a new record
24/7
Human support for DNS record setup
In short
To point a subdomain to another server, add a new DNS record for that subdomain in the domain's DNS zone: use an A record with the target server's IP address if you have a fixed IP, or a CNAME record pointing at a hostname if the destination is an external service that provides one, such as a SaaS platform or a separately hosted blog. The main domain's own records stay untouched.
This is how a site commonly runs shop.example.com on an ecommerce platform, blog.example.com on separate blogging software, or app.example.com on a different server, all while example.com itself keeps pointing at its original hosting.
A subdomain is a fully independent DNS entry once it's created — nothing requires shop., blog., app., or any other subdomain to resolve to the same server as the root domain, even though that's the default when a subdomain is simply created inside the same hosting's cPanel. Plenty of legitimate setups deliberately split things apart: a marketing site on one host, a separately hosted blog or knowledge base, a SaaS dashboard running on its own infrastructure, or an ecommerce storefront built on a dedicated platform.
The mechanism for all of these is the same two DNS record types used for any domain: an A record maps a name directly to an IP address, and a CNAME record maps a name to another hostname instead, letting DNS follow that alias to wherever it currently points. Which one to use depends entirely on what the destination server or service asks for.
A Record: Pointing a Subdomain at a Fixed IP
Use an A record when the destination server has a known, fixed IP address — a VPS, a dedicated server, or any other hosting where the provider gives an IP to point at. In the domain's DNS zone, add a new A record with the host field set to the subdomain (such as 'shop' for shop.example.com) and the value set to the destination server's IP address.
Because an A record points directly at an IP, it's the right choice whenever the destination is infrastructure you or the service explicitly identify by IP rather than by a hostname the destination manages on its own — a straightforward, direct mapping that doesn't depend on anything at the target end changing later.
CNAME: Pointing a Subdomain at Another Hostname
Use a CNAME record when the destination is an external service that provides a hostname to point at rather than a fixed IP — common with SaaS platforms, help desk tools, landing page builders, or any service where the underlying server IP might change without notice on their end. Add a CNAME record with the host set to the subdomain and the value set to the hostname the service provides, exactly as given.
A CNAME follows that alias at lookup time, so if the destination service changes its own underlying IP address later, the subdomain keeps working without any DNS change needed at your end — that indirection is the entire advantage of a CNAME over hardcoding an A record for a service you don't control.
Setting It Up Without Disrupting the Root Domain
Adding a subdomain record is additive — it doesn't touch the root domain's own A record, MX records, or any other existing entries in the zone, since it's simply a new, separate name being added alongside them. In cPanel-style DNS management or a registrar's DNS editor, locate the DNS zone editor, add a new record, choose A or CNAME as appropriate, enter the subdomain as the host and the destination as the value, and save.
If the subdomain was previously created and hosted on the same account as the main site, that existing record needs removing or overwriting first — trying to add a conflicting record for the same subdomain without removing the old one is a common source of an unexpected old page still loading instead of the new destination.
Confirming the Subdomain Actually Reaches the New Destination
After saving the new record, use a DNS lookup tool to confirm the subdomain resolves to the correct IP (for an A record) or hostname (for a CNAME), keeping in mind that propagation follows the record's TTL and can take anywhere from minutes up to the usual 24-48 hour worst case for a brand-new or recently changed record.
Once it resolves correctly, load the subdomain in a browser to confirm the destination server or service is actually serving the expected content there, and verify SSL is issued and valid for that specific subdomain — an external SaaS platform typically handles its own certificate, while a subdomain pointed at your own separate server needs its own SSL configured there just like any other hostname.
One Domain, Multiple Servers, No Conflict
Splitting shop., blog., or app. off to different infrastructure is a normal, supported setup — it just needs the right DNS record type for whatever the destination expects.
Hosting Cheap's cPanel-style DNS editor makes adding an A or CNAME record for any subdomain straightforward, whether the destination is a separate server here or an outside service.
- cPanel-style DNS zone editor for A and CNAME records
- Existing subdomain records easy to locate and remove or update
- Free auto-renewing SSL for subdomains hosted with us
- 24/7 human support for subdomain DNS setup
Why Hosting Cheap
What you get
Straightforward DNS zone editor
Add A or CNAME records for any subdomain without needing separate DNS software.
Root domain stays untouched
Point a subdomain elsewhere without affecting the main domain's existing records.
Free auto-renewing SSL
Subdomains hosted with us get a certificate issued automatically, no manual renewal needed.
NVMe SSD + LiteSpeed
Any subdomain kept on our hosting loads from fast NVMe storage and LiteSpeed's stack.
24/7 human support
Get help choosing between an A record and a CNAME for a specific destination service.
Free managed migration
Get help moving a subdomain's existing content over if it's changing servers, not just DNS.
How It Works
Get set up in a few steps
Get the destination's IP or hostname
Find out whether the target server or service expects an A record (IP) or a CNAME (hostname).
Add the record in the DNS zone
Create the new A or CNAME record for the subdomain, removing any conflicting existing record first.
Verify resolution and SSL
Confirm the subdomain resolves correctly and that SSL is valid for it once propagation completes.
Included
Everything you need, on every plan
- Destination server's IP address or hostname confirmed before starting
- Correct record type chosen: A for an IP, CNAME for a hostname
- Any pre-existing conflicting record for the subdomain removed first
- New record's host field set to just the subdomain, not the full domain
- DNS lookup checked to confirm the subdomain resolves correctly
- Destination server or service confirmed as actually serving the right content
- SSL confirmed valid for the specific subdomain once live
- Root domain and other subdomains checked to confirm they're unaffected
FAQ
Frequently asked questions
How do I point a subdomain to a different server than my main site?
Add a new A record in the domain's DNS zone with the host set to the subdomain and the value set to the other server's IP address, or a CNAME if the destination provides a hostname instead. The root domain's own records stay exactly as they were.
Should I use an A record or a CNAME for a subdomain?
Use an A record when you have a fixed IP address to point at, such as your own VPS or dedicated server. Use a CNAME when an external service gives you a hostname to point at instead, since that lets their end change IPs without breaking your subdomain.
Will pointing a subdomain elsewhere break my main domain?
No, a subdomain's DNS record is separate from the root domain's records, so adding or changing one doesn't affect the other. The only risk is accidentally editing the wrong record, so double-check the host field before saving.
How long does it take for a new subdomain record to work?
Most new records resolve within minutes to a few hours, though a full worldwide propagation can take up to the usual 24-48 hour worst case depending on the record's TTL. Testing from a DNS lookup tool gives a clearer picture than just refreshing a browser.
Can I point a subdomain to a SaaS platform like a help desk or landing page tool?
Yes, most such platforms provide a CNAME target hostname specifically for this purpose. Add that as a CNAME record for the subdomain, and the platform's own infrastructure handles the rest, including its own SSL in most cases.
What happens to an old subdomain record if I don't remove it first?
A leftover conflicting record can cause the subdomain to keep resolving to the old destination, or cause unpredictable behavior depending on the DNS zone editor. Removing or overwriting the old record before adding the new one avoids that confusion.
Ready to Split a Subdomain Off to Its Own Server?
Get cPanel-style DNS management and NVMe hosting for whatever stays on our end, from $2.09/mo.
Get Started