Point Subdomain to Hostinger with Namecheap DNS

Your apex domain is running on Namecheap DNS handling production traffic or Google Workspace email, and you just need to point a single subdomain like app.domain.com or staging.domain.com to Hostinger. Changing your root nameservers to Hostinger will nuke your active MX records, break external TXT verifications, and trigger unnecessary downtime.

Don’t touch your nameservers. You only need a single A record inside Namecheap’s Advanced DNS zone editor. Here is how to configure the subdomain in Hostinger hPanel, grab the right server IP, map the DNS in Namecheap, and verify it from your terminal before issuing an SSL certificate.

Keep Namecheap BasicDNS for the Root Domain

Switching nameservers delegates authority over your entire DNS zone to Hostinger. If you manage custom Google Workspace MX records, SPF/DKIM strings, or hostnames pointing to Vercel or AWS, migrating nameservers breaks those services immediately.

Leaving Namecheap BasicDNS alone keeps your apex (example.com) and your mail records completely untouched. You just add one explicit pointer for the subdomain. It eliminates downtime, avoids re-verifying ownership on third-party platforms, and keeps your stack organized.

If you ever actually want Hostinger to manage the full DNS zone for that specific subdomain without touching the root domain, use NS records instead. I covered that setup in my guide on how to delegate a subdomain to external nameservers in Namecheap DNS. But for 95% of setups, a simple A record is faster and easier to maintain.

Find Your Hostinger Server IP Address

Hostinger runs shared clusters behind LiteSpeed, so incoming traffic needs to hit the specific server IP assigned to your hosting container.

Log in to hPanel and grab that IP address:

1. Click Websites in the top navigation bar.
2. Hit Manage next to your active hosting account or primary site.
3. In the left sidebar, navigate to Hosting > Plan Details.
4. Copy the address listed under Server IP Address (for example, 185.193.126.44).

Do not guess this IP by running dig on your apex domain if that domain points to another host. Copy the exact IP from your hPanel dashboard.

Create the Subdomain Inside Hostinger hPanel

Hostinger’s web server needs to know how to route incoming HTTP requests when the Host header matches your subdomain. If the server receives traffic for an unregistered hostname, it serves a 404 or dumps visitors onto a generic Hostinger landing page.

You have two ways to add the hostname in hPanel: as a standard subdomain under an existing site, or as an independent website. If it shares your main hosting container, use the Subdomains menu. If you want separate directories and isolated FTP access, add it as a standalone site.

Option A: Adding via Subdomains Menu

In hPanel, head to Domains > Subdomains. Enter your prefix (like staging or portal). Leave the document root box checked to generate public_html/staging automatically, or name a custom folder. Click Create.

Option B: Adding as an Independent Website

If you want isolated file permissions, separate FTP accounts, or cleaner staging workflows, go to Websites > Add Website. Pick Other, enter the full hostname (e.g., portal.example.com), and skip the auto-installer. This keeps the web root isolated at public_html/ for that standalone entry.

If you’re spinning up a WordPress test environment, read our walkthrough on how to set up WordPress staging on Hostinger, which uses this exact isolation method.

Configure the A Record in Namecheap Advanced DNS

Now that Hostinger is ready to receive requests, jump into Namecheap to point your traffic to that IP address.

1. Log in to your Namecheap Dashboard.
2. Find your root domain in the Domain List and click Manage.
3. Under the Nameservers section, verify it says Namecheap BasicDNS or Namecheap Web Hosting DNS. Do not select Custom DNS.
4. Click the Advanced DNS tab at the top.
5. Scroll down to Host Records and click Add New Record.

Enter these values:

• Type: A Record
• Host: Enter the subdomain prefix only. If your subdomain is staging.example.com, type staging. Never enter the full domain here.
• Value: Paste your Hostinger server IP (e.g., 185.193.126.44).
• TTL: Select 1 min so changes propagate quickly while testing (or leave it on Automatic).

Click the green checkmark to save. If you already have an existing CNAME or URL Redirect on that same host prefix, delete it first. IETF RFC 1034 prevents an A record and a CNAME from coexisting on the same host label.

Verify DNS Propagation Using the Terminal

Don’t rely on your browser to check propagation. Browsers cache DNS aggressively and can mislead you into thinking your setup failed. Query resolvers directly from your terminal.

On macOS, Linux, or WSL, run dig against Google’s public resolver:

dig +short staging.example.com @8.8.8.8

If the record has propagated, you’ll see your Hostinger IP in the answer section. You can also query Namecheap’s nameservers directly to confirm their authoritative servers processed your edit:

dig A staging.example.com @dns1.registrar-servers.com +noall +answer

On Windows systems without dig, use nslookup:

nslookup staging.example.com dns1.registrar-servers.com

Once your Hostinger IP appears in the output, your DNS is working. You can also spot-check global edge nodes on whatsmydns.net.

Issue a Free Let’s Encrypt SSL Certificate in hPanel

Do not try to issue an SSL certificate before your DNS resolves to Hostinger. Hostinger uses an automated Let’s Encrypt HTTP-01 challenge over port 80. If the subdomain doesn’t point to Hostinger yet, Let’s Encrypt can’t verify the token in the .well-known/acme-challenge/ directory and fails immediately.

Once dig returns your Hostinger IP:

1. Head back to hPanel.
2. Go to Security > SSL.
3. Locate your new subdomain in the list.
4. Click Install SSL.

Hostinger verifies the record and deploys the certificate automatically. Toggle Enforce HTTPS so unencrypted HTTP requests redirect to HTTPS.

If you’re deploying code directly from a repository after SSL is ready, check out our guide on setting up Git auto-deployment for WordPress in Hostinger.

Common Pitfalls and How I Fixed Them

Setting up split DNS between Namecheap and Hostinger is straightforward, but two common bugs often trip people up.

1. The Subdomain Shows the Default Hostinger Parking Page

I ran into this on my first attempt. DNS resolved to the Hostinger IP, but loading the site pulled up Hostinger’s default parking page. The issue was an unmapped virtual host: I had typed stage in Namecheap but staging in hPanel’s Subdomain tool.

Because LiteSpeed couldn’t find a virtual host matching the incoming Host header, it served the generic catch-all pool. Make sure the Host field in Namecheap matches the subdomain prefix in Hostinger character-for-character.

2. The SSL Installation Fails with an ACME Timeout

If you hit Install SSL right after saving the Namecheap A record, Let’s Encrypt will likely query an old IP or hit an NXDOMAIN response due to caching. ACME resolvers cache negative lookups aggressively. If it fails, wait 10 to 15 minutes, confirm resolution with dig, and then retry the install inside hPanel.

Frequently Asked Questions

Can I use a CNAME record instead of an A record?

Yes, you can use a CNAME if Hostinger gives you a target hostname (like a staging URL). But an A record pointing straight to your assigned server IP is cleaner and cuts out an extra DNS lookup hop, giving you a slightly faster time-to-first-byte (TTFB).

Will pointing my subdomain to Hostinger break my Namecheap Private Email?

No. Your mail records (MX, SPF, DKIM) are tied to your root domain or mail host labels. As long as you don’t edit your MX records in Namecheap and leave your nameservers on Namecheap BasicDNS, your mail continues without interruption. If you ever need to rebuild those records, check our walkthrough on how to set up Namecheap Private Email MX records.

How long does Namecheap DNS propagation take for subdomains?

With Namecheap BasicDNS, new A records usually propagate within 5 to 15 minutes. If you modified an existing record rather than creating a brand-new one, propagation depends on the TTL of that previous record, which defaults to 30 minutes unless you lowered it earlier.

Do I need to add a “www” record for my subdomain?

Almost never. Nobody types www.app.example.com. But if you specifically want that format to resolve, add a secondary CNAME in Namecheap with www.app as the Host pointing to app.example.com, and add the alias in hPanel.

Next Steps

Your subdomain now points cleanly to Hostinger, and your root DNS records on Namecheap remain completely untouched. If you decide to put a caching layer in front of your Hostinger app down the road, check out our guide on how to deploy a static landing page on Hostinger with Namecheap and CDN caching.