Common DNS Mistakes When Pointing a New Domain to Hostinger

Updated 2026-05-25 · Hosting Reviews

When you buy a fresh domain and want to host it on Hostinger, a handful of DNS slip‑ups can keep your site offline or break your business email. Below we walk through the most common DNS mistakes pointing new domain hostinger users make, and give you a clear, inexpensive path to get a live website and professional email up and running.

1. Not Having the Right Pieces Before You Start

Before you dive into DNS records, make sure you have three basics covered:

• Domain name: Register it through Hostinger or another registrar. Choose a name that matches your brand and is easy to spell.
• Hosting plan: For most beginners, Hostinger’s shared hosting ($3‑$15 / month) is more than enough. If you expect high traffic or need root access, consider a cloud or VPS plan.
• Platform: WordPress is the most popular CMS and works great with Hostinger’s one‑click installer. If you prefer drag‑and‑drop, Hostinger’s website builder is also available.

Having these three items ready means you can focus on DNS instead of hunting for missing pieces.

2. Forgetting to Update the Nameservers

The most frequent error when pointing a new domain to Hostinger is leaving the default registrar nameservers active. If the nameservers still point to the old registrar, any DNS changes you make in Hostinger’s dashboard won’t affect your site.

Solution:

1. Log in to the registrar where you bought the domain.
2. Locate the “Nameserver” or “DNS” settings page.
3. Replace the existing nameservers with Hostinger’s: ns1.dns-parking.com and ns2.dns-parking.com (or the ones shown in your Hostinger account).
4. Save the changes. Propagation can take 1‑48 hours, but most updates resolve within a few hours.

Once the nameservers point to Hostinger, the DNS zone you edit there will control both your website and business email.

3. Misconfiguring the A Record

The A record tells the internet the IP address of your website. A common mistake is pointing the A record to the wrong IP—often the IP of a placeholder page or an old server.

To avoid this:

• In your Hostinger control panel, go to DNS Zone → A Record.
• Copy the IP address shown under “Host Account IP.”
• Set the A record for the root domain (@) and the www sub‑domain to that exact IP.

If you’re using a CDN or a third‑party site builder, use the CNAME record they provide instead of an A record.

4. Overlooking MX Records for Business Email

Many beginners focus on getting the website live and forget the MX (mail exchange) records that route email. Without correct MX records, emails sent to you@yourdomain.com will bounce.

Steps to set up a professional email with Hostinger:

1. Activate Hostinger’s “Business Email” add‑on (often included with premium plans).
2. In the DNS Zone, locate the MX section.
3. Enter the MX host provided by Hostinger, usually something like mx1.hostinger.com with priority 10, and mx2.hostinger.com with priority 20.
4. Add the required SPF and DKIM TXT records (Hostinger lists them under “Email Authentication”).

After saving, give the records 1‑2 hours to propagate, then test by sending a message to your new address.

5. Ignoring CNAME and TXT Records for Services

Beyond the basics, you may need additional records for Google Workspace, verification with Google Search Console, or a CDN like Cloudflare. A common slip is adding a CNAME for www but also leaving an A record that conflicts, causing “Site not found” errors.

Best practice:

• Use a CNAME for www that points to your root domain (yourdomain.com) or to the service’s URL.
• Keep the root A record pointing to your Hostinger IP.
• Add any required TXT records exactly as the service instructs—no extra spaces or missing quotes.

This tidy setup prevents duplicate records and makes troubleshooting easier.

6. Not Securing the Site with SSL Early

Even after the DNS is correct, visitors will see a “Not Secure” warning if you don’t enable HTTPS. Hostinger provides a free SSL certificate that can be activated with one click once your domain resolves to the server.

Action steps:

1. In Hostinger’s dashboard, go to SSL → Free SSL.
2. Select your domain and click “Install.”
3. After installation, force HTTPS in your WordPress settings or .htaccess file.

With SSL active, you gain better SEO rankings, data encryption, and visitor trust.

Quick Checklist to Avoid Common DNS Mistakes Pointing New Domain Hostinger

1. Change registrar nameservers to Hostinger’s.
2. Set the root A record (or CNAME) to the correct Hostinger IP.
3. Configure MX records for business email and add SPF/DKIM.
4. Use a single CNAME for www and avoid duplicate A records.
5. Add any required TXT records for verification or third‑party services.
6. Activate the free SSL certificate as soon as DNS resolves.

Follow this list and you’ll cut down on the guesswork that leads to downtime.

FAQ

Do I need a separate hosting account for my business email?

No. Hostinger bundles email hosting with most of its shared and cloud plans, so one account handles both the website and professional email.

How long does DNS propagation really take?

It varies by registrar, but most changes propagate within a few hours. The full 48‑hour window is rare; during that time, some visitors may see the old site while others see the new one.

Can I switch from shared hosting to a VPS without moving my domain?

Yes. After upgrading in Hostinger, simply update the A record to the new VPS IP. The nameservers stay the same, so your DNS configuration remains intact.