Table of Contents
- Navigating Your Namecheap DNS Dashboard
- Understanding Core DNS Records
- Pointing Your Domain to a Web Host
- Creating the Main A Record
- Handling the WWW Subdomain
- Setting Up Subdomains and Third-Party Tools
- Connecting a Subdomain to Another Platform
- Verifying Your Domain with Third-Party Services
- Confirming Your DNS Changes Are Live
- Using Online Tools to Check Propagation
- Finalizing Your Site Security
- How to Fix Common Namecheap DNS Errors
- The Typo and Conflict Check
- SSL and Email Delivery Problems
- Common Questions About Namecheap DNS Setup
- How Long Does It Take for Namecheap DNS Changes to Work?
- Can I Have Multiple A Records for My Main Domain?
- What Is the Difference Between an A Record and a CNAME Record?
- Do I Need to Change My Nameservers?

Related Posts
blog_related_media
blog_topic
blog_related_activities
blog_niche
blog_related_tips
unique_blog_element
Configuring your DNS records in Namecheap is how you tell the internet where to send traffic for your domain. Think of it like updating the post office with your new address. You’ll log into your account, head over to the "Advanced DNS" section for your domain, and create a few specific records—like an A record—that point to your website’s host. This is the bedrock for getting your domain online and working properly.
Navigating Your Namecheap DNS Dashboard
Before you can point your domain to Feather, you first need to get your bearings in the Namecheap control panel. I like to think of the Advanced DNS dashboard as the central switchboard for a domain. It's the one place where you direct all incoming traffic, whether it's for your main website, a new subdomain, or your email accounts. Getting this right is the difference between a smooth launch and a frustrating one.
Right off the bat, you'll have a choice: use Namecheap's default nameservers or use custom ones from a third party, like your web host. Honestly, for most people, just stick with Namecheap BasicDNS. This keeps everything under one roof, so you're not juggling logins across different platforms just to make a DNS change. It makes troubleshooting so much easier down the line. It's no wonder that over 3.8 million websites trust Namecheap DNS—its simplicity is a huge draw. You can dig into Namecheap's market share on Similarweb if you're curious.
Understanding Core DNS Records
Once you click into the Advanced DNS tab, you'll be looking at a list of your domain's records. These are simply instructions that guide traffic across the internet. While there are a bunch of different types, you'll probably only ever touch a few key ones for a standard setup.
To help you get started, here's a quick rundown of the most common DNS record types you'll be managing inside Namecheap.
Record Type | What It Does | Common Use Case |
A Record | Points a domain name to a specific IP address. | Pointing yourdomain.com to your web host’s server. |
CNAME Record | Points a subdomain to another domain name (not an IP). | Making www.yourdomain.com point to yourdomain.com. |
MX Record | Directs your domain's email to a mail server. | Setting up Google Workspace or another email provider. |
TXT Record | Lets you add arbitrary text, used for verification. | Proving domain ownership for Google Search Console. |
This table covers the essentials, giving you a solid foundation for what each record does and why you might need it.

This flowchart nails the simple, three-step path you'll take to get to the right screen. It's a great visual reminder that accessing these settings is less intimidating than it sounds: Login -> Domain List -> Advanced DNS.
One last setting you'll bump into is TTL, which stands for Time to Live. This number, measured in seconds, tells DNS servers around the world how long they should "remember" or cache your settings. A lower TTL makes your changes show up faster, which is super helpful when you're actively making updates. For most situations, leaving it on "Automatic" or setting it to 30 minutes (1800 seconds) is a safe bet.
Pointing Your Domain to a Web Host
Alright, let's get to the main event. This is why most people find themselves staring at a DNS settings page: getting their website live. It's that crucial step where you finally connect your shiny new domain name to the server that holds all your website's files.
We'll walk through exactly how to create the records you need to make this happen. Once you see where the values go, you'll realize it's less complicated than it sounds.
The goal here is simple. We need to tell the internet, "When someone types
mydomain.com, send them over to this specific server." This magic happens with something called an A record, which stands for Address record. It’s the most direct way to map your domain name to your hosting server's numerical IP address.
Creating the Main A Record
First things first, you need the IP address from your web host. Whether you're using Feather, SiteGround, or another provider, this number will be waiting for you in your hosting dashboard. It's usually under a section called "Details" or "Server Information" and looks something like
192.0.2.1.Got it? Great. Now, head back to your Namecheap dashboard and click on the Advanced DNS tab for your domain.
You’re going to add a new record with these settings:
- Type: A Record
- Host: @
- Value: Your server's IP address
- TTL: Automatic (or 30 minutes is fine)
That
@ symbol in the 'Host' field is just a universal shortcut that means "my main domain." So, this record tells browsers where to go for yourdomain.com.Handling the WWW Subdomain
Next up, we need to make sure people who type
www.yourdomain.com also end up on your website. It’s a small detail, but it prevents frustrating "site not found" errors and makes for a much smoother experience.Instead of creating another A record, the best way to handle this is with a CNAME record.
A CNAME (or Canonical Name) record is basically an alias. It points one name to another. Here, we'll point the
www subdomain to your main (or "root") domain. This is way more efficient because if your server's IP address ever changes down the line, you only have to update the one A record, and the CNAME will automatically follow suit.Here’s what to add:
- Type: CNAME Record
- Host: www
- Value: yourdomain.com (or just @)
- TTL: Automatic
Once you've created both of these records, you've set up the two most important pathways for visitors to find your site. The process is pretty similar no matter which registrar you use. In fact, if you've used other platforms before, our guide on the GoDaddy domain setup might look familiar.
After you save your changes, the last step is to just wait. It takes a little while for these new instructions to spread across the internet, a process we call propagation.
Setting Up Subdomains and Third-Party Tools
Your main domain is a fantastic start, but the real flexibility of a Namecheap DNS setup kicks in when you start using subdomains. This is how you can tie together your entire online world—your main website, a separate blog, a portfolio, and even a Shopify store—all under your one branded domain.
Think of subdomains as different rooms in your main office. For instance,
blog.yoursite.com could point directly to your Feather blog, while shop.yoursite.com sends visitors to your e-commerce platform. The good news? Setting this up is a lot like pointing your main domain.
Connecting a Subdomain to Another Platform
Let’s walk through a common scenario: you want to launch a blog using a service built on Notion. Platforms like this almost always give you a CNAME value or an IP address to link up your custom subdomain. It’s a super effective way to expand your site’s functionality without touching your main website.
The process is nearly identical to what you’ve done before. You'll add a new record in your Advanced DNS dashboard, but the key change is in the Host field.
- For a CNAME record: The Host would simply be
blog(orportfolio,shop, etc.), and the Value would be the target domain the service provides (likecname.service.com).
- For an A record: Again, the Host is
blog, and the Value is the specific IP address the platform gives you.
This one simple record tells the internet's traffic controllers to route anyone visiting
blog.yoursite.com over to that other service, all while your main website stays right where it is.Verifying Your Domain with Third-Party Services
Moving beyond subdomains, another task you'll definitely encounter is domain verification. Services like Google Search Console, your email marketing provider, or even social media platforms often need you to prove you own your domain before they’ll unlock their tools for you.
Their go-to method for this is asking you to add a TXT record to your DNS settings.
A TXT record is just a small snippet of text that you place in your domain’s DNS file—something only the true domain owner can do. The whole thing usually takes less than a minute.
- The service (let's say Google) will generate a unique string of characters for you.
- You'll log back into your Namecheap account and create a new TXT record.
- Just paste their unique string into the Value field. The Host is typically
@, which just means it applies to your main domain.
After you save the record, the service can scan your DNS, spot the unique code, and instantly confirm you're the owner.
Confirming Your DNS Changes Are Live
Once you've saved your new A or CNAME records, you’ve officially done your part. Now, it's the internet's turn to catch up. This next phase is called DNS propagation, which is basically the time it takes for your new settings to spread across servers all over the globe. Think of it like sending out a mass text with a new address—it takes a little while for every server in the world to get the message and save it.
I know you're eager to see your new site live, but propagation isn't instant. While it often happens within 30 minutes, it can technically take up to 48 hours for your changes to be fully visible everywhere. This isn't a Namecheap thing; it's just how the massive, decentralized Domain Name System works.

Using Online Tools to Check Propagation
So, how do you know when it's all done? Just sitting there and hitting refresh on your browser isn't the most reliable method. Your own computer and internet provider might be the last to see the update because of something called a local cache.
A much better way to check is to use an online DNS propagation checker. Tools like
whatsmydns.net or dnschecker.org are perfect for this. You just pop in your domain name, and they'll ping servers from Tokyo to Toronto to see what IP address they're detecting for your domain.You'll see a list of locations with little green checkmarks. When most of them show your new Feather IP address, you can be pretty confident your Namecheap DNS setup was a success and the changes are live for most of the world. It’s a great way to get a real-time, global status report without just guessing.
Finalizing Your Site Security
Once you've confirmed your domain is pointing to the right place, there's one last, crucial step: locking it down. With your DNS records live, you can now generate and install an SSL certificate. This is what puts the little padlock icon in the browser bar and enables
https, protecting your visitors' data and giving your SEO a nice boost.If you need a hand with this part, our walkthrough on how to install an SSL certificate breaks down the entire process. Getting this done finalizes the technical side of your site launch, ensuring you have a secure and professional presence online from day one.
How to Fix Common Namecheap DNS Errors
Even with the most careful setup, you can sometimes hit a snag with your Namecheap DNS. Seeing that dreaded "This site can’t be reached" error is enough to spark a moment of panic, but the fix is almost always something small. Think of this as your go-to guide for troubleshooting the usual issues that pop up after you hit "Save".
The vast majority of problems boil down to a few usual suspects. Before you start spiraling and thinking about complex server issues, take a deep breath and run through this quick diagnostic checklist. It’s surprising how often a simple typo is the real culprit.
The Typo and Conflict Check
Your first stop should always be a careful review of the records you just created. It's so easy to miss tiny mistakes when you're moving fast, so slow down and look closely.
- Check the Host Field: Did you use
@for your root domain? For a subdomain likeblog.yoursite.com, did you correctly enter justblog? A common mistake is putting in the full subdomain, which Namecheap doesn't need.
- Verify the Value: Double-check your server's IP address or the CNAME value you were given. Copy and paste it again just to be absolutely sure there are no sneaky extra spaces or transposed numbers.
- Look for Conflicts: This one is a big deal. You should never have more than one A record for the same host (like
@). If you added a new A record for your site but forgot to delete Namecheap’s default parking page record, your traffic will get confused, causing unpredictable connection errors for visitors.
SSL and Email Delivery Problems
Sometimes the main site loads, but other crucial services break. An SSL certificate that won't validate or emails that suddenly stop arriving are classic signs of DNS misconfigurations that go beyond a simple A record.
For SSL issues, the problem is often just a matter of timing. Your SSL provider (like Let's Encrypt) can't issue a certificate until it can "see" your new A record live on the internet. If you try to generate the certificate too soon after changing your DNS, it’ll fail. The solution here is simple: patience. Give it an hour, then try again.
Email delivery failures, on the other hand, usually point directly to missing or incorrect MX records. When you point your domain to a new host, your email settings don't automatically come along for the ride. You'll need to manually add the correct MX records from your email provider (like Google Workspace or Zoho) in your Namecheap Advanced DNS panel to get mail flowing again. Without those records, other mail servers have no idea where to deliver your messages.
Common Questions About Namecheap DNS Setup
Getting your DNS settings just right can feel a bit like detective work, especially the first time. It’s totally normal to have questions pop up along the way.
We've been there, and we've helped countless others navigate this process. So, we've put together answers to the most common questions we hear. Think of this as your go-to guide for those "wait, what about...?" moments.
How Long Does It Take for Namecheap DNS Changes to Work?
This is the big one, and the short answer is: it varies. DNS changes aren't instant. While you might see your site come online in as little as 30 minutes, it can sometimes take up to 48 hours for the changes to spread across the entire internet.
This delay is called DNS propagation, and it's just how the internet works—it's not a Namecheap-specific issue. Every server around the globe needs time to catch up with your new settings. So, if your site doesn't load right away, don't panic. Grab a coffee, give it an hour, and then check again before you start troubleshooting.
Can I Have Multiple A Records for My Main Domain?
For your main domain (the one represented by the
@ host), you should only have one A record. It’s a hard and fast rule.Think of it like this: an A record tells the internet the specific street address (IP address) for your website. If you provide two different addresses for the same domain, servers get confused. They won't know which one to send visitors to, which means your site will load for some people and not for others—or not at all. It's a recipe for inconsistent, unpredictable results.
What Is the Difference Between an A Record and a CNAME Record?
Getting the hang of this difference is key to a clean DNS setup. It's actually pretty simple when you break it down:
- An A Record points a domain name (like
yoursite.com) directly to a numeric IP address. It's like a direct map to a physical server.
- A CNAME Record (or Canonical Name) points a name (like
www.yoursite.com) to another domain name (likeyoursite.com). It's basically an alias or a nickname.
You'll almost always use an A record for your main "root" domain. For subdomains like
www or blog, a CNAME is often the cleaner, more efficient choice.Do I Need to Change My Nameservers?
This all comes down to where you want to manage your DNS records.
If you plan on using Namecheap's Advanced DNS editor (which is what our guide covers), your nameservers must be set to
Namecheap BasicDNS.If your nameservers are pointing somewhere else—like your old host (Bluehost, SiteGround, etc.)—then all your DNS changes need to be made over there, not in Namecheap. To keep things simple and all in one place, we usually recommend sticking with Namecheap's nameservers.
Ready to turn your Notion pages into a lightning-fast, SEO-optimized blog? Feather makes it effortless to launch a professional website with your custom domain.
