Point Namecheap DNS to Hostinger Without Breaking Email

Switching your website hosting while preserving an active email inbox is one of those tasks where a single wrong click takes down communications for hours. When you switch your domain’s nameservers at Namecheap directly to Hostinger’s default nameservers, you wipe out active MX, SPF, and DKIM records stored in your registrar zone.

You will configure your Namecheap DNS records to route web traffic directly to your Hostinger web server IP while leaving your email services on Google Workspace, Namecheap Private Email, or Microsoft 365 completely uninterrupted.

Why changing nameservers kills your existing email

DNS nameservers act as the authority for your entire domain. If your domain uses Namecheap BasicDNS, Namecheap’s servers resolve queries for your website (A and CNAME records), your email routing (MX records), and your domain verification keys (TXT records).

When you replace Namecheap nameservers with Hostinger nameservers (like ns1.dns-parking.com), the global DNS system stops asking Namecheap where your mail should go. Unless you manually duplicated every MX and TXT record inside Hostinger’s hPanel prior to the change, incoming mail servers receive a non-existent domain response (NXDOMAIN) or drop messages into a retry queue.

You have two reliable options to solve this:

• Method 1 (Recommended): Keep Namecheap BasicDNS. Update only the root A record and www CNAME to point to Hostinger. Email records stay untouched on Namecheap.
• Method 2: Copy all existing MX, SPF, and DKIM records into Hostinger hPanel first, then switch nameservers at Namecheap.

Method 1 offers zero risk to your mail flow because your email records never move. If you also manage separate outbound servers, see our guide on how to configure and verify DNS records for multi-service environments.

Find your Hostinger server IP address

To point Namecheap records to Hostinger without touching nameservers, you need your Hostinger server’s dedicated or shared IPv4 address. Hostinger assigns this per hosting account.

1. Log in to your Hostinger hPanel dashboard.
2. Navigate to Websites and click Manage next to your target site.
3. Look at the left sidebar and click Hosting details (or check the Plan details panel on your dashboard).
4. Copy the value listed next to Server IP address (for example, 185.185.185.185).

Keep this IP address handy in a scratchpad. You will also want to verify whether your plan uses an IPv6 address (AAAA record), though IPv4 is sufficient for basic web routing.

Audit your existing Namecheap email records

Before editing anything inside Namecheap, run a quick terminal audit to record your live mail setup. This step ensures you do not overwrite any critical TXT or MX records by accident.

Open your local terminal and run dig against your domain to list your active mail exchangers:

dig +short MX yourdomain.com
dig +short TXT yourdomain.com

If you prefer a browser interface, check the official Namecheap Advanced DNS documentation while reviewing your current records tab.

You will typically see records pointing to Google, Microsoft, or Namecheap Private Email:

• Google Workspace: 1 smtp.google.com (or older 5-record setups like aspmx.l.google.com).
• Namecheap Private Email: mail.privateemail.com.
• Microsoft 365: yourdomain-com.mail.protection.outlook.com.

Confirm these records exist inside Namecheap under Domain List > Manage > Advanced DNS before proceeding.

Method 1: Point A records in Namecheap (Zero Email Downtime)

This is the cleanest approach. You keep Namecheap as your DNS host and modify only web traffic pointers.

Step 1: Open Advanced DNS in Namecheap

Log into Namecheap, open your Domain List, find your domain, and click Manage. Click the Advanced DNS tab at the top.

Step 2: Update the Root A Record

Locate the Host Records table. Look for an existing A Record with the Host set to @.

• If an A Record with Host @ exists, click its value field and replace the old IP with your Hostinger Server IP.
• Set the TTL to Automatic or 1 min (if you plan to test immediately).
• Click the green checkmark to save.

Step 3: Update the WWW Record

Look for a record with the Host set to www. You can configure this as an A Record or a CNAME:

• Option A (CNAME): Type CNAME Record, Host www, Target yourdomain.com., TTL Automatic.
• Option B (A Record): Type A Record, Host www, Value [Hostinger Server IP], TTL Automatic.

Delete any default Namecheap Parking Page records (such as parkingpage.namecheap.com) under Host Records. Leave every MX Record, TXT Record (SPF, DKIM), and CNAME associated with email untouched.

Method 2: Migrate DNS Zone to Hostinger Before Nameserver Switch

If you prefer managing all DNS records directly inside Hostinger hPanel, you must recreate all existing email routing records inside Hostinger before changing nameservers at Namecheap.

Step 1: Open the DNS Zone Editor in Hostinger

1. In hPanel, go to Advanced > DNS Zone Editor.
2. Scroll down to the Manage DNS records section.

Step 2: Recreate Your MX Records

If your email runs on Google Workspace, refer to the Google Workspace MX setup guide to get the exact priority values. Add each record in Hostinger:

• Type: MX
• Name: @
• Points to: smtp.google.com (or your mail server hostname)
• Priority: 1
• TTL: 3600

Step 3: Copy SPF and DKIM TXT Records

Find your SPF record in Namecheap (usually starts with v=spf1) and add it into Hostinger’s DNS Zone Editor:

Type: TXT
Name: @
TXT Value: v=spf1 include:_spf.google.com ~all
TTL: 3600

If you use dedicated subdomains for marketing tools, review our guide on setting up email subdomains on Cloudflare for comparative architecture.

Step 4: Update Nameservers at Namecheap

Once all records match inside Hostinger, go back to Namecheap:

1. Click Domain List > Manage.
2. Under the Nameservers dropdown, select Custom DNS.
3. Enter Hostinger’s nameservers per the Hostinger official nameserver guide:
   • ns1.dns-parking.com
   • ns2.dns-parking.com
4. Click the green checkmark to save.

Verify DNS Propagation and SPF/DKIM Integrity

DNS changes take anywhere from 5 minutes to 24 hours to propagate worldwide. You can track this in real-time from your terminal without waiting blindly.

Query your web resolution to confirm it points to the Hostinger IP:

dig +short A yourdomain.com @8.8.8.8

Next, confirm that your mail server routing remained intact and did not drop back to default values:

dig +short MX yourdomain.com @1.1.1.1
dig +short TXT yourdomain.com @1.1.1.1

If the MX query returns your Google or Private Email servers and the A record returns your Hostinger IP, your migration succeeded without email downtime.

Gotchas: Domain Verification, SSL, and TTL Caching

When running this configuration, I hit three common edge cases that can cause confusion.

1. Hostinger “Domain Not Pointing” Warning

Hostinger’s hPanel often displays a yellow banner: “Domain is not pointing to Hostinger”. If you used Method 1 (A records), Hostinger shows this warning because its system checks for Hostinger nameservers, not custom A records. As long as your dig queries return the correct IP and your site loads over HTTP/HTTPS, you can safely ignore this banner.

2. Let’s Encrypt SSL Validation Failure

Hostinger issues free Let’s Encrypt SSL certificates automatically. If you initiate SSL installation before the A record propagates fully, the ACME HTTP-01 challenge will fail. Wait until your A record resolves globally before clicking Install SSL inside hPanel.

3. Conflicting Default Records

Namecheap often includes a default wildcard (*) or URL Redirect record pointing to its parking page. If your site redirects to a parking page even after updating the root A record, delete any URL Redirect Record in the Namecheap Advanced DNS panel. When working across multiple providers, checking how other systems handle domains—such as connecting external domains to web builders—helps troubleshoot stubborn caching issues.

Frequently Asked Questions

How long does it take for Namecheap DNS changes to reach Hostinger?

If you edit A records on Namecheap BasicDNS with TTL set to Automatic or 1 min, changes typically propagate in 5 to 30 minutes. If you switch full nameservers, propagation can take between 2 and 24 hours.

Will my existing emails be deleted if I make a mistake?

No. Your emails are stored on your mail provider’s servers (Google, Microsoft, or Namecheap Private Email). A DNS mistake only interrupts new incoming messages, causing sending servers to retry or bounce. Your stored inbox data remains safe.

Do I need to pay for Hostinger Email if I keep my current mail?

No. You do not need to activate or pay for Hostinger email services. As long as your MX records point to your third-party mail provider, all mail traffic bypasses Hostinger completely.

Can I use Cloudflare between Namecheap and Hostinger without breaking email?

Yes. You point Namecheap nameservers to Cloudflare, proxy your web records (orange cloud for A/CNAME), and leave your MX and mail-related TXT records unproxied (grey cloud). If you are building automated funnels or mail triggers alongside this, see our walkthrough on setting up dedicated email sending domains.

Next Steps for Your Setup

Now that your domain resolves to Hostinger and your email flow is protected, install your SSL certificate in hPanel under Security > SSL. Once the lock icon shows green, test sending and receiving an email from an external account like Gmail to confirm that your DKIM signatures and SPF checks still pass inspection headers.