Home / WordPress / How to Point a Domain to Hostinger: Complete DNS & Nameserver Guide
devmohsin143

If you have purchased a web domain from an external registrar like Namecheap, GoDaddy, or Google Domains/Squarespace and want to host your WordPress website on Hostinger, you will need to point domain to Hostinger so visitors can reach your site. Connecting an external domain to a new host is one of the most vital steps when launching or migrating a WordPress website.

Fortunately, Hostinger’s proprietary hPanel makes this process straightforward. In this comprehensive step-by-step tutorial, you will learn the exact steps required to point your domain to Hostinger using both nameserver updates and A record configurations, preserve critical email settings, and troubleshoot common DNS propagation and SSL certificate issues.

Nameservers vs. A Records: Which Method Should You Choose?

Before modifying any settings at your domain registrar, it is essential to understand where your domain’s DNS zone will be managed. When connecting an existing domain to Hostinger, you have two primary options: changing your domain’s nameservers or updating your domain’s A record.

Feature / ComparisonMethod 1: Hostinger NameserversMethod 2: A Record Pointing
DNS Zone ManagementManaged inside Hostinger hPanelManaged at external registrar / Cloudflare
Setup ComplexityVery easy (change 2 nameserver entries)Moderate (requires adding/editing A records)
Email Routing ImpactDNS zone moves to Hostinger; email records must be manually re-addedEmail records remain untouched at current provider
Best Used ForNew sites or total migration to Hostinger hosting and emailSites keeping third-party email (e.g., Google Workspace, Microsoft 365)

Therefore, if you want Hostinger to handle all web traffic, subdomains, and DNS settings automatically, changing your nameservers is usually the best approach. However, if you already rely on external email providers like Google Workspace or Microsoft 365 and do not want to risk disrupting business email flow, pointing your A record while leaving nameservers at your registrar is often the safer alternative.

Step 1: Locate Your Hostinger DNS Details in hPanel

Regardless of which method you choose, your first step is to log into Hostinger and gather your hosting server’s specific IP address and assigned nameservers.

  1. Log in to your Hostinger hPanel account.
  2. Navigate to the Websites section from the top navigation bar.
  3. Click Manage next to the domain or website you are configuring.
  4. On the left sidebar menu, look under Hosting and select Plan Details (or navigate to Advanced > DNS Zone Editor).

Here you will see two critical pieces of information required to point domain to Hostinger:

  • Hostinger Nameservers: Usually formatted as ns1.dns-parking.com and ns2.dns-parking.com (or custom nameservers assigned to your account such as ns1.hostinger.com and ns2.hostinger.com).
  • Hostinger Server IP Address: A unique IPv4 address (e.g., 185.185.185.185) listed under Website IP or Server Details.

Note: Always verify your actual nameservers inside your own hPanel account rather than copying static examples, as Hostinger assigns specific nameserver clusters based on your hosting location and server setup.

Method 1: Point Domain to Hostinger via Nameservers (Recommended)

Changing your domain’s nameservers transfers full authority over your domain’s DNS settings to Hostinger. This allows Hostinger’s automatic tools to generate proper DNS records for subdomains, SSL certificates, and web hosting without manual record updates.

Step-by-Step Nameserver Update Procedure:

  1. Copy the two nameservers listed in your Hostinger hPanel dashboard.
  2. Log in to the account where your domain was originally purchased (e.g., Namecheap, GoDaddy, Cloudflare, or Google Domains/Squarespace).
  3. Find your domain management menu or DNS / Nameserver settings page.
  4. Change the nameserver option from “Default / Standard” to Custom DNS or Custom Nameservers.
  5. Paste the Hostinger nameservers into the primary and secondary fields:
    • Nameserver 1: ns1.dns-parking.com (or your assigned Hostinger NS1)
    • Nameserver 2: ns2.dns-parking.com (or your assigned Hostinger NS2)
  6. Save or confirm your changes at the registrar.

Additionally, if you are using WordPress site management tools or migrating an existing site, changing nameservers makes adding addon domains and installing Hostinger Auto-SSL seamless.

Method 2: Point Domain to Hostinger via A Records

If you prefer to keep your DNS zone managed at your current registrar or Cloudflare—particularly to maintain active email routing without interruption—you can point domain to Hostinger using an A record instead.

Step-by-Step A Record Setup Procedure:

  1. In your registrar’s DNS management panel, locate your existing A Records.
  2. Find the A record with the Host/Name value set to @ (which represents your primary domain root).
  3. Edit the record and change the Value / Points to field to your Hostinger Server IP address.
  4. Set the TTL (Time To Live) to 3600 seconds (or Automatic / Default).
  5. Look for a second A record or CNAME record for www:
    • If using an A record for www, point its value to the same Hostinger Server IP address.
    • If using a CNAME record for www, point its target value to your root domain (e.g., yourdomain.com).
  6. Save all updated records.

Crucial Step: Preserving Email Records (MX, SPF, DKIM)

One common mistake webmasters make when attempting to point domain to Hostinger is losing access to active email accounts hosted externally.

If you choose Method 1 (Nameservers), your old registrar’s DNS zone becomes inactive, and Hostinger’s DNS Zone Editor takes over. Consequently, active email services (such as Google Workspace, Titan Email, or Microsoft 365) will stop receiving mail unless you re-create your email records inside hPanel.

Before changing nameservers, copy your existing DNS records from your registrar and re-enter them inside Hostinger hPanel under Advanced > DNS Zone Editor:

  • MX Records: Points email traffic to your email provider (e.g., ASPMX.L.GOOGLE.COM).
  • TXT / SPF Records: Verifies sending authorization (e.g., v=spf1 include:_spf.google.com ~all).
  • DKIM & DMARC Records: Ensures cryptographic validation and prevents spam flagging.

Meanwhile, if you choose Method 2 (A Record), your MX, SPF, and DKIM records remain untouched at your domain registrar, ensuring uninterrupted email operations during the website DNS switch.

Step 3: Verify Destination and Test DNS Propagation

Once you complete the update, DNS changes do not happen instantly worldwide. Global DNS caching servers update incrementally in a process known as DNS propagation, which generally takes anywhere from 15 minutes to 24 hours.

You can verify whether your domain correctly points to Hostinger using online propagation tracking tools:

  • WhatIsMyDNS: Enter your domain name and select A or NS to check global propagation across global nodes.
  • DNSChecker.org: View real-time status across multi-region DNS servers.
  • Command Line Lookup: Run nslookup yourdomain.com in Terminal or Windows Command Prompt to check your local network resolution.

Troubleshooting Propagation Delays and SSL Errors

Even after correctly configuring Hostinger DNS settings, you might encounter minor roadblocks. Here is how to troubleshoot the most common issues:

1. Domain Points to IP, But Shows “Default Website” or 404 Page

This typically occurs if the domain name has not been formally added inside Hostinger hPanel. Ensure that under Websites > Add Website, you have added the exact domain name matching your external registrar setup.

2. “Your Connection is Not Private” / SSL Certificate Error

Hostinger provides free Unlimited SSL certificates via Let’s Encrypt. However, Hostinger cannot issue an SSL certificate until DNS propagation reaches their servers.

  • Wait until propagation completes globally.
  • In hPanel, go to Security > SSL.
  • Click Install SSL or Re-install SSL next to your domain name.

3. Local Browser Caching Issue

If DNS tools show the correct Hostinger IP address but your computer still opens the old hosting site, clear your browser cache or run the local DNS flush command:

On Windows Command Prompt:

ipconfig /flushdns

On macOS Terminal:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Frequently Asked Questions

How long does it take to point domain to Hostinger?

While A record updates can take effect within 15 to 60 minutes, changing nameservers across global TLD registries usually takes between 2 to 24 hours to fully propagate worldwide.

Will pointing my domain to Hostinger cause website downtime?

If you migrate your WordPress database and website files to Hostinger before updating your DNS settings or nameservers, your site visitors will experience zero downtime during propagation.

Can I transfer my domain registration to Hostinger instead?

Yes. In addition to pointing your DNS, Hostinger allows complete domain transfers under Domains > Transfer Domain in hPanel using an EPP transfer code provided by your registrar.


By following these clear steps, you can confidently point domain to Hostinger, ensure seamless DNS routing, protect your essential email records, and launch your WordPress site with optimal speed and security.

Related Blogs

Learn how to improve WordPress website speed safely. Actionable guide covering image optimization, caching, database cleanup, and hosting without breaking your site.
Confused by speed test scores? Learn how to accurately interpret website speed test results, analyze Core Web Vitals like LCP, INP, CLS, and TTFB, and fix bottlenecks efficiently.
Master the exact workflow for testing WordPress website speed. Learn how to use PageSpeed Insights, GTmetrix, and Core Web Vitals to accurately diagnose performance bottlenecks.