How to Add a Subdomain in GoDaddy (Step-by-Step Guide)
Adding a subdomain in GoDaddy is a straightforward DNS task once you understand what subdomains are and how GoDaddy's control panel handles them. Whether you're setting up a staging environment, a blog, a store, or a separate app, the process follows the same core path — with a few variables that change based on your specific setup.
What Is a Subdomain?
A subdomain is a prefix added to your root domain that creates a separate, addressable web location. For example:
blog.yourdomain.comshop.yourdomain.comstaging.yourdomain.com
The part before the first dot is the subdomain. It's treated as a distinct address by browsers and servers, but it lives under your existing domain — no new domain registration required.
Subdomains are used to organize different sections of a website, host separate applications, point to different servers, or create test environments without touching the main site.
Where Subdomain Management Lives in GoDaddy
GoDaddy handles subdomains through DNS records, not a dedicated "subdomains" panel. You're creating a DNS record — typically an A record or CNAME record — that maps your subdomain prefix to an IP address or another hostname.
This distinction matters. Some hosting dashboards (like cPanel) have a visual "Subdomains" tool, but GoDaddy's primary interface routes you through the DNS Manager.
How to Add a Subdomain in GoDaddy 🖥️
Step 1: Log In to Your GoDaddy Account
Go to godaddy.com and sign in. From your account dashboard, navigate to My Products.
Step 2: Access Your Domain's DNS Settings
Find the domain you want to add a subdomain to. Click the three-dot menu or Manage DNS next to that domain. This opens the DNS Management page for that domain.
Step 3: Add a New DNS Record
Click Add New Record. You'll be prompted to choose a record type. The two most common for subdomains are:
| Record Type | When to Use |
|---|---|
| A Record | Point your subdomain to a specific IP address (e.g., a VPS or dedicated server) |
| CNAME Record | Point your subdomain to another hostname (e.g., a third-party service or another domain) |
Step 4: Fill In the Record Details
For an A Record:
- Type: A
- Name: Enter only the subdomain prefix (e.g.,
blog— not the fullblog.yourdomain.com) - Value: The IP address of the server where this subdomain should point
- TTL: Can stay at the default (usually 1 hour) or be adjusted
For a CNAME Record:
- Type: CNAME
- Name: Your subdomain prefix (e.g.,
shop) - Value: The target hostname (e.g.,
shops.myplatform.com) - TTL: Default is fine for most uses
Step 5: Save and Wait for Propagation
Click Save. GoDaddy will apply the record. DNS changes typically propagate within 30 minutes to a few hours, though full global propagation can take up to 48 hours in some cases. During this window, the subdomain may not resolve consistently across all networks.
Common Use Cases and What Changes Between Them
Not every subdomain setup is identical. The DNS record is just one part — where things differ is what happens after the DNS resolves.
Pointing to a hosting account you control: If your subdomain should load a website hosted on the same GoDaddy hosting plan as your main domain, you may also need to create a subdomain directory inside your hosting control panel (cPanel or Plesk). The DNS record gets traffic to the server; the hosting config tells the server what to show.
Third-party services (email tools, CDNs, e-commerce platforms): Many platforms like Shopify, Mailchimp, or Fastly provide a specific CNAME target. You'll enter that as the value in your CNAME record. The platform handles the rest.
Separate servers or VPS instances: Use an A record pointing to the server's public IP. The server itself needs to be configured to respond to that subdomain — a virtual host entry in Apache or Nginx, for example.
Wildcard subdomains: GoDaddy supports wildcard DNS records using * as the name (e.g., *.yourdomain.com). This routes any subdomain to one destination, useful for multi-tenant apps. However, your server or application needs to handle the wildcard routing logic on its end.
A Few Things Worth Knowing 🔍
GoDaddy-hosted vs. externally hosted domains: If your domain's nameservers are pointed away from GoDaddy (to Cloudflare, AWS Route 53, or another provider), you won't manage DNS in GoDaddy's panel — you'll do it wherever the nameservers are set. You can check nameserver settings on the same DNS Management page.
SSL certificates for subdomains: A standard SSL certificate covering your root domain does not automatically cover subdomains. You'll need either a wildcard SSL certificate or a separate certificate for each subdomain, depending on your hosting environment and certificate provider.
Subdomain vs. subdirectory: A subdomain (blog.yourdomain.com) and a subdirectory (yourdomain.com/blog) are different structures. Subdomains are technically separate from the root domain in terms of DNS and hosting configuration. For SEO and site architecture, the choice between them depends on whether the content is meant to feel like a separate property or an integrated section of the same site.
The Variable That Determines Your Next Step
The DNS record creation in GoDaddy is consistent across setups. What varies significantly is what needs to happen on the server or platform side once DNS is pointed correctly — and that depends entirely on where your subdomain is meant to go, what software is running there, and how your hosting environment is structured.
The gap between "DNS record saved" and "subdomain fully working" is almost always filled by server-side configuration — and that part of the process looks meaningfully different depending on your stack.