Namecheap DNS Setup Guide Configure Your Domain the Right Way

Getting your domain's DNS configured correctly on Namecheap is one of those tasks that looks simple until something breaks. Whether you just registered a domain, moved hosting providers, or need to add an email service like Google Workspace or Microsoft 365, the order of operations matters. This guide walks through every major DNS scenario on Namecheap — from choosing between BasicDNS and custom nameservers, to adding individual records and verifying they've propagated properly. No fluff, just the exact steps you need.

Understanding Namecheap DNS Options

Before touching any records, you need to choose which DNS system will serve your domain. Namecheap gives you three options inside the domain management panel:

• BasicDNS (Namecheap's free DNS) — Uses Namecheap's own authoritative nameservers. Best for domains hosted on Namecheap Shared Hosting or when you want a straightforward control panel.
• Custom DNS — You supply external nameservers (your web host, Cloudflare, AWS Route 53, etc.). Namecheap's record editor is disabled; you manage records at the external provider.
• Namecheap Web Hosting DNS — Appears automatically if you have an active Namecheap hosting plan. Pre-populates common records for that plan.

The most common mistake is leaving a domain on BasicDNS while pointing it to an external host by changing only the A record — and then being confused when email breaks because the MX records are missing. Pick the right mode first, then configure records.

How to Access the Namecheap DNS Panel

1. Log in at namecheap.com and click Domain List in the left sidebar.
2. Find your domain and click the Manage button to its right.
3. Click the Advanced DNS tab at the top of the domain management page.

If you see a message saying "DNS records are managed by your nameservers" instead of a record editor, your domain is set to Custom DNS mode and you need to log into that external provider to edit records.

Switching to BasicDNS (Namecheap Nameservers)

If you want Namecheap to host your DNS records, navigate to the Domain tab (not Advanced DNS) and look for the Nameservers section. Select Namecheap BasicDNS from the dropdown and click the green checkmark. This changes your nameservers to:

Nameserver changes propagate within minutes at most registrars but can take up to 48 hours at upstream TLD registries. In practice, most people see it working within 1-4 hours.

Switching to Custom DNS (External Nameservers)

If you're using Cloudflare, SiteGround, WP Engine, or any host that provides their own nameservers, select Custom DNS from the same dropdown and enter the nameservers your provider gave you — typically two or four entries. Example for Cloudflare:

After saving, all DNS record management moves to that provider. Namecheap's Advanced DNS tab will display a notice and the record editor will be grayed out.

Adding an A Record (Point Domain to a Web Server)

An A record maps your domain or subdomain to an IPv4 address. This is what makes yourdomain.com resolve to your server. In the Advanced DNS tab under Host Records:

1. Click Add New Record.
2. Set Type to A Record.
3. Set Host to @ (for the root domain) or www for the www subdomain.
4. Set Value to your server's IP address, e.g., 203.0.113.42.
5. Set TTL to Automatic (1800 seconds) to start. Lower it to 300 if you anticipate changes soon.
6. Click the green checkmark to save.

Add a second A record with Host set to www pointing to the same IP, or use a CNAME for www (see below). Most servers expect traffic on both the bare domain and www.

Adding a CNAME Record (Aliases and Subdomains)

CNAME records map one hostname to another hostname. They're used for www, for third-party services like Shopify or HubSpot, and for SSL domain verification. Rules to remember: you cannot use a CNAME on the root (@) domain — only on subdomains. Also, a CNAME cannot coexist with any other record type for the same hostname.

1. Click Add New Record.
2. Type: CNAME Record.
3. Host: www (or shop, blog, etc.).
4. Value: The target hostname, e.g., yourdomain.wpengine.com or shops.myshopify.com. Always include the trailing dot convention if the provider specifies it, though Namecheap's interface usually handles this automatically.
5. TTL: Automatic. Save.

Adding MX Records for Email

MX records direct email for your domain. If you're setting up Google Workspace, Microsoft 365, Zoho, or any other hosted email, your provider gives you specific MX hostnames and priority numbers. Here's Google Workspace as an example:

1. Delete any existing MX records first if you're replacing them — Namecheap shows them in the Host Records section with type MX.
2. Add each new MX record with Host set to @, the Mail Server value from your provider, and the correct Priority.

Lower priority numbers are tried first. Save all records. If you see a warning about existing Namecheap mail records (like mail.privateemail.com), remove those before adding your new provider's MX entries.

Adding TXT Records for SPF, DKIM, and Domain Verification

TXT records are multipurpose. The three most common uses are domain ownership verification, SPF (Sender Policy Framework for email authentication), and DKIM (DomainKeys Identified Mail). They all follow the same process:

1. Type: TXT Record.
2. Host: @ for root-domain records like SPF and ownership verification. For DKIM, your provider gives you a specific subdomain like google._domainkey.
3. Value: The exact string from your provider — paste it carefully. For SPF it looks like:

For Microsoft 365 SPF:

Important: You can only have one SPF TXT record on the root (@). If you use multiple email services, merge them into one record:

Adding an AAAA Record for IPv6

If your server has an IPv6 address, add an AAAA record the same way as an A record, but select AAAA Record as the type and enter the full IPv6 address:

Verifying Your DNS Records

After adding records, do not assume they're working just because Namecheap shows a green checkmark. Verify from outside using command-line tools or a web-based checker.

On Linux or macOS, use dig:

On Windows, use nslookup:

To query a specific DNS server (bypassing your local cache), add the resolver address. For Google's public DNS:

If the record shows up correctly against 8.8.8.8 but not locally, you're dealing with a local cache issue — flush it with ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on macOS.

Troubleshooting Common Namecheap DNS Problems

Records Not Showing Up After Saving

If you save a record but it doesn't appear, check whether your domain is set to Custom DNS mode. In Custom DNS mode, Namecheap's editor is inactive — changes save to their interface but are never published to any authoritative server. Switch to BasicDNS if you want Namecheap to manage your records.

Website Shows Namecheap Parking Page

This usually means your A record is pointing to Namecheap's parking IP instead of your host's IP. Check the current A record value using the DNS Lookup tool and compare it to the IP address your hosting provider assigned you. Update the record and wait for TTL to expire before retesting.

Email Not Delivering After MX Change

Three things to check: (1) Old MX records still exist alongside the new ones — remove duplicates. (2) The new MX records haven't propagated yet — use dig or nslookup to query Namecheap's own nameservers directly to confirm the records are published. (3) SPF record is missing or incorrect, causing the receiving server to reject mail silently.

Querying Namecheap's nameserver directly tells you whether the record is published at the source, regardless of global propagation status.

SSL Certificate Domain Validation Failing

Many certificate authorities use CNAME or TXT records for domain control validation (DCV). If validation keeps failing, confirm the CNAME or TXT record value matches exactly what the CA provided — no extra spaces, no missing dots. Some CAs require the record to exist on a specific subdomain like _acme-challenge.yourdomain.com. In Namecheap's editor, enter only the subdomain portion in the Host field (e.g., _acme-challenge), not the full hostname.

Recommended TTL Strategy

TTL (Time To Live) tells resolvers how long to cache a record before checking again. Namecheap's default Automatic TTL is 1800 seconds (30 minutes). Here's a practical strategy:

• Normal operation: Leave at 1800 or set to 3600. Lower TTLs increase DNS query load on Namecheap's servers with no benefit when records are stable.
• Before a planned migration: Drop TTL to 300 (5 minutes) at least 48 hours before you switch. This ensures caches expire quickly when you make the change.
• After migration is confirmed working: Raise TTL back to 1800 or 3600 to reduce DNS lookup latency for visitors.

Using Namecheap's URL Redirect Records

Namecheap's Advanced DNS panel includes a URL Redirect Record type that's not a standard DNS record — it's a Namecheap-hosted redirect service. You can use it to redirect a subdomain to an external URL with 301 or 302 status codes without touching your web server. For example, redirecting blog.yourdomain.com to a Medium or Substack page. Set Host to blog, Value to the full destination URL, and choose the redirect type. Note: this only works while you're on Namecheap BasicDNS or Namecheap Web Hosting DNS.

Exporting Your DNS Zone Before Making Changes

Namecheap doesn't offer a one-click zone export, so before making bulk changes, manually document your existing records. Take a screenshot or copy the records to a text file. Alternatively, pull the zone data from the command line:

This queries Namecheap's nameserver for all record types and gives you a snapshot you can refer back to if something breaks after a change.

Final Checklist Before Going Live

• Correct nameservers confirmed at the registrar level (not just record changes)
• A record points to the correct server IP — verified with dig or nslookup
• www CNAME or A record configured
• MX records set to your email provider's values with correct priority numbers
• SPF TXT record present, properly merged if multiple senders
• DKIM TXT records added for each email service
• DMARC TXT record added at _dmarc.yourdomain.com
• SSL domain validation CNAME or TXT record added if using an external CA
• TTL lowered in advance of migration, raised again after

Namecheap's DNS interface is reliable once you understand the modes and how the record editor interacts with them. The most common failures come from mixing up BasicDNS and Custom DNS modes, or leaving stale records in place when switching providers. Work through each record type methodically, verify with live DNS queries, and you'll avoid the hours-long confusion that catches most people out.