From Netlify Subdomain to Custom Domain: My Journey with GoDaddy
Introduction
I recently found myself in a common situation: I had my portfolio site live on Netlify at sheetalssr.netlify.app, and I'd just purchased a custom domain (sheetal.me) from GoDaddy. This post documents my journey through the process and the interesting things I learned about web hosting and DNS along the way.
Understanding Web Hosting
Types of Hosting
- Shared Hosting: Multiple sites share server resources. Cost-effective but performance can be inconsistent.
- VPS (Virtual Private Server): Dedicated virtual machine resources on a shared physical server.
- Dedicated Hosting: Your own physical server. Maximum control but requires technical expertise.
- Cloud Hosting: Distributed across multiple servers for better scalability and reliability.
- Serverless Architecture: Pay-per-use model where the cloud provider manages the infrastructure.
Where Netlify Fits In
Netlify specializes in static site hosting with a serverless approach. It's perfect for:
- Portfolio websites
- Blogs
- Marketing sites
- Documentation
The DNS Connection
How DNS Works
Think of DNS as the internet's phonebook. When someone types sheetal.me:
- Their browser asks a DNS resolver for the IP address
- The resolver checks with root nameservers
- The request is directed to GoDaddy's nameservers
- The IP address is returned and the site loads
Connecting GoDaddy to Netlify
Step 1: Set Up in Netlify
- Log into your Netlify dashboard
- Go to Site settings > Domain management
- Add your custom domain (
sheetal.me) - Netlify will provide DNS records to verify ownership
Step 2: Configure GoDaddy DNS
- Log into your GoDaddy account
- Navigate to your domain's DNS settings
- Add Netlify's provided records:
- A record:
@points to Netlify's IP - CNAME:
wwwpoints to your Netlify URL
- A record:
Step 3: Choose Your Redirect Type
Netlify offers three options:
- Permanent (301): Best for permanent moves (recommended)
- Temporary (302): For testing or temporary redirects
- Forward with masking: Hides the destination URL
The Waiting Game
DNS changes can take up to 48 hours to propagate globally. Here's why:
- DNS records are cached by ISPs
- TTL (Time To Live) settings affect how long old records persist
- Some users might see changes before others
Troubleshooting Tips
If your site isn't loading:
- Double-check DNS records for typos
- Verify Netlify's SSL certificate is active
- Use whatsmydns.net to check propagation
- Clear your browser cache or try incognito mode
Final Thoughts
Connecting a GoDaddy domain to Netlify is straightforward once you understand the DNS handshake. The key is patience while changes propagate. Now, when someone visits sheetal.me, they'll see my portfolio hosted on Netlify!
