Connecting a domain name to a Hostinger hosting account requires the domain's DNS configuration to point to the correct hosting service. One of the most common methods is to change the domain's nameservers.

This guide explains what Hostinger nameservers are, how nameservers work, how to find the correct Hostinger nameservers, how to configure them when your domain is registered with another company, how DNS propagation works, how nameservers affect email, and how to troubleshoot common DNS problems.

What Is a Nameserver?

A nameserver (NS) is a specialized DNS server responsible for telling the internet where the authoritative DNS records for a domain are located.

For example, when someone enters:

www.example.com

into a browser, DNS infrastructure is used to determine where that domain should be resolved.

Nameservers identify the DNS provider responsible for records such as:

• A records
• AAAA records
• CNAME records
• MX records
• TXT records
• SPF records
• DKIM records
• DMARC records
• SRV records
• CAA records

Changing nameservers therefore does much more than simply change the website's IP address. It effectively changes which DNS provider controls the authoritative DNS zone for the domain.

What Are Hostinger Nameservers?

If a website is hosted with Hostinger, the domain can normally be connected to the hosting service by pointing its nameservers to the nameservers specified by Hostinger.

Historically, commonly documented Hostinger nameservers have included:

ns1.dns-parking.com
ns2.dns-parking.com

However, do not assume these are necessarily the correct nameservers for every Hostinger account or domain.

Hostinger may provide different nameservers depending on the domain, hosting product, account, infrastructure, or service configuration.

Recommended practice

Always obtain the nameservers directly from your own Hostinger hPanel before modifying the domain.

Do not rely solely on nameserver values copied from an old article, forum post, video, or another Hostinger customer's account.

How to Find the Correct Hostinger Nameservers

Log in to your Hostinger account and open hPanel.

Depending on the current Hostinger interface and hosting product, the information may be available under areas such as:

Websites → Your Website → Check Guide

or:

DNS / Nameservers

or within the domain/website management section.

Hostinger will display the nameservers that should be configured for your domain.

Copy them exactly.

For example, you might see values similar to:

Nameserver 1: ns1.dns-parking.com
Nameserver 2: ns2.dns-parking.com

Your actual values may be different.

Do I Need the Nameserver IP Addresses?

Usually, no.

Most domain registrars require only names such as:

ns1.dns-parking.com
ns2.dns-parking.com

and automatically resolve the corresponding IP addresses.

Some systems, especially certain registrars or configurations involving custom/private nameservers, may also request IP addresses.

Hostinger has previously documented these addresses for its dns-parking.com nameservers:

ns1.dns-parking.com    162.159.24.201
ns2.dns-parking.com    162.159.25.42

Important

IP addresses associated with provider infrastructure can change.

Therefore, never treat an IP address found in an old article as permanently valid.

If your registrar specifically requests nameserver IP addresses, verify the current values from Hostinger before entering them.

Method 1: Point a Domain to Hostinger Using Nameservers

This is generally the simplest method when you want Hostinger to manage the DNS zone.

Suppose:

Domain Registrar: Another company
Web Hosting: Hostinger
DNS Management: Hostinger

You would normally change the nameservers at the company where the domain is registered.

Step 1: Add the Domain or Website to Hostinger

Before changing anything at your registrar, make sure the domain has been properly added to the appropriate Hostinger hosting plan.

This is important because changing nameservers before the hosting account is ready can cause temporary website or email disruption.

Step 2: Find the Required Nameservers

Open Hostinger hPanel and locate the connection instructions for the website/domain.

Copy the exact nameservers displayed by Hostinger.

Step 3: Log In to Your Domain Registrar

The nameserver change must normally be performed at the company where the domain is registered.

For example, if the domain was purchased from another registrar but the website is hosted at Hostinger, log in to the domain registrar, not merely the Hostinger hosting account.

Look for an option such as:

• Nameservers
• Change Nameservers
• DNS Settings
• Manage DNS
• Custom Nameservers
• DNS Management
• Domain Management

The terminology differs between registrars.

Step 4: Select Custom Nameservers

If the registrar currently uses its default nameservers, select an option similar to:

Use Custom Nameservers

Then remove the old nameservers and enter the Hostinger nameservers shown in your hPanel.

Example:

Nameserver 1: ns1.dns-parking.com
Nameserver 2: ns2.dns-parking.com

Again, these are examples. Use the actual values provided for your domain.

Step 5: Save the Configuration

Save or submit the changes.

Some registrars may ask you to:

• confirm your password;
• approve an OTP;
• verify the change by email;
• disable registrar lock-related protection;
• confirm a security prompt.

Complete any required verification.

What Happens After Changing the Nameservers?

The change is not necessarily visible everywhere immediately.

DNS information is cached by:

• ISPs
• recursive DNS resolvers
• operating systems
• routers
• browsers
• corporate networks
• security appliances
• CDN infrastructure

It takes time for the new DNS information to become visible throughout the internet.

This process is known as DNS propagation.

Hostinger advises allowing up to approximately 24 hours for DNS changes to propagate globally, although changes often become visible much sooner.

During propagation, it is possible for:

• one internet connection to show the new website;
• another connection to show the old website;
• mobile data to behave differently from office broadband;
• email to behave inconsistently;
• some DNS checkers to show the new nameserver while others still show the old one.

This does not automatically mean the configuration has failed.

How to Check Whether Nameservers Have Changed

You can verify nameservers using several methods.

Windows Command Prompt

Open Command Prompt and run:

nslookup -type=NS example.com

Replace example.com with your actual domain.

You can also use:

nslookup example.com

to check the resolved IP address.

PowerShell

Run:

Resolve-DnsName example.com -Type NS

For an A record:

Resolve-DnsName example.com -Type A

For MX records:

Resolve-DnsName example.com -Type MX

For TXT records:

Resolve-DnsName example.com -Type TXT

These commands are particularly useful for administrators troubleshooting website and email DNS configurations.

Flush the Windows DNS Cache

If DNS has changed but your Windows PC continues to open the old server, clear the local DNS resolver cache.

Open Command Prompt as Administrator and run:

ipconfig /flushdns

You should receive a message similar to:

Successfully flushed the DNS Resolver Cache.

Then close and reopen the browser.

Nameserver Change vs A Record Change

These two approaches are often confused.

Nameserver Method

Changing nameservers means:

"Use this DNS provider to manage my domain's DNS."

For example:

Registrar
    ↓
Hostinger Nameservers
    ↓
Hostinger DNS Zone
    ↓
Website / Email / Other Services

Hostinger becomes responsible for the authoritative DNS zone.

A Record Method

Changing an A record means:

"Keep my existing DNS provider but send this hostname to a particular IPv4 address."

For example:

Registrar / Existing DNS Provider
    ↓
A Record
    ↓
Hostinger Server IP

DNS management remains with the existing provider.

Which Method Should You Use?

Use Hostinger nameservers when:

• Hostinger hosts your website;
• you want Hostinger to manage DNS;
• you want simpler centralized DNS management;
• you do not need another provider to remain authoritative for DNS.

Consider the A record method when:

• DNS must remain with another provider;
• you use an external DNS service;
• you use a specialized email/DNS configuration;
• organizational policy requires DNS to remain elsewhere;
• changing nameservers would disturb an existing complex DNS zone.

Critical Warning: Nameserver Changes Can Affect Email

This is one of the most important considerations.

Changing nameservers changes which DNS zone becomes authoritative.

Suppose your current DNS provider contains:

Website records
MX records
SPF
DKIM
DMARC
Verification TXT records
Subdomains
Autodiscover
Other application records

If you change the nameservers without recreating the required records at the new DNS provider, some services may stop working.

This is particularly important when your email is hosted by:

• Google Workspace
• Microsoft 365
• Zoho Mail
• another business email provider
• a third-party mail server

Example: Hostinger Website + Google Workspace Email

Suppose you want:

Website → Hostinger
Email   → Google Workspace

You can still use Hostinger nameservers.

However, after Hostinger becomes your DNS provider, the DNS zone at Hostinger must contain the appropriate Google Workspace records.

That may include:

• Google MX records
• SPF TXT record
• DKIM TXT record
• DMARC TXT record
• Google verification records

Do not assume that changing the nameservers will automatically preserve third-party email settings.

Example: Hostinger Website + Microsoft 365

The same principle applies to Microsoft 365.

The Hostinger DNS zone may need Microsoft-specific:

• MX
• TXT
• CNAME
• SRV

records according to the services being used.

If these records are missing or incorrect, Outlook or Microsoft 365 email services can be affected even though the website works normally.

Recommended Procedure Before Changing Nameservers

Before modifying nameservers on an active business domain, make a complete record of the existing DNS zone.

Record or export:

A
AAAA
CNAME
MX
TXT
SRV
CAA
NS

Also document:

• SPF
• DKIM
• DMARC
• email verification records
• Microsoft 365 verification
• Google verification
• subdomains
• application records
• third-party service verification records

Taking screenshots or exporting the DNS zone can make rollback and troubleshooting significantly easier.

DNSSEC Considerations

DNSSEC adds cryptographic validation to DNS.

If DNSSEC is enabled at the existing provider and you change authoritative nameservers incorrectly, a DNSSEC mismatch can result in DNS resolution failures.

Symptoms can include:

• website inaccessible;
• DNS lookup failures;
• domain working on some systems but not others;
• SERVFAIL responses.

When migrating DNS providers, verify the DNSSEC configuration carefully.

Do not copy old DS/DNSSEC information blindly to a new provider.

Common Problems After Changing Hostinger Nameservers

1. Website Still Opens the Old Server

Possible reasons:

• DNS propagation is incomplete;
• ISP DNS cache;
• Windows DNS cache;
• browser cache;
• old nameservers are still active;
• the domain was modified at the wrong registrar account.

Check:

nslookup -type=NS example.com

and:

nslookup example.com

2. Website Stops Working Completely

Check:

• domain is active;
• hosting plan is active;
• domain has been added to Hostinger;
• nameservers are correct;
• Hostinger DNS zone contains the correct website records;
• DNSSEC is not causing validation errors.

3. Website Works but Email Stops

This usually indicates a DNS mail configuration problem.

Check:

nslookup -type=MX example.com

Then verify:

• MX records;
• SPF;
• DKIM;
• DMARC;
• mail-provider verification records.

The website and email can use completely different service providers.

4. www Works but the Root Domain Does Not

For example:

www.example.com     → Works
example.com         → Does not work

Check the DNS records for both the root domain and www.

5. Root Domain Works but www Does Not

This usually indicates a missing or incorrect www DNS record.

Check:

nslookup www.example.com

and compare it with:

nslookup example.com

6. SSL Certificate Error After DNS Change

An SSL certificate is associated with the website/server configuration, not simply the registrar.

After DNS changes, the hosting platform may need time to:

• detect the domain;
• validate DNS;
• issue an SSL certificate;
• install or activate the certificate.

Do not immediately assume the nameserver configuration is incorrect solely because HTTPS is not available immediately after migration.

7. DNS_PROBE_FINISHED_NXDOMAIN

This browser error generally indicates that DNS resolution failed.

Check:

nslookup example.com

Possible causes include:

• incorrect nameservers;
• domain expiration;
• missing DNS records;
• incomplete propagation;
• DNSSEC problems;
• incorrect domain configuration.

Hostinger Nameservers vs Cloudflare

A common configuration is:

Domain Registrar
      ↓
Cloudflare Nameservers
      ↓
Cloudflare DNS
      ↓
Hostinger Server

In this arrangement, do not replace Cloudflare nameservers with Hostinger nameservers unless you deliberately want to stop using Cloudflare as the authoritative DNS provider.

Instead, keep the Cloudflare nameservers and configure the required Hostinger destination records inside Cloudflare.

The important principle is:

DNS records must normally be managed at the provider whose authoritative nameservers are currently assigned to the domain.

Does Changing Nameservers Transfer the Domain?

No.

Changing nameservers does not transfer domain ownership or domain registration.

For example:

Registrar: Company A
Nameservers: Hostinger
Website: Hostinger

The domain remains registered with Company A.

Only DNS authority has been pointed elsewhere.

A domain transfer and a nameserver change are separate operations.

Does Changing Nameservers Move Website Files?

No.

Nameservers do not copy:

• website files;
• databases;
• WordPress installations;
• PHP files;
• email messages;
• SSL certificates;
• backups.

They only control DNS resolution.

Website migration must be completed separately.

Does Changing Nameservers Change Email Automatically?

It can affect email because MX and related DNS records are controlled by the authoritative DNS provider.

Therefore, always verify email configuration before changing nameservers on a production domain.

For business environments, DNS migration should be treated as both a website and email change-management task.

Recommended Safe Migration Procedure

For an important production domain, use this sequence:

1. Back up the website.
2. Back up databases.
3. Record the existing DNS zone.
4. Record MX records.
5. Record SPF.
6. Record DKIM.
7. Record DMARC.
8. Record all subdomains.
9. Add and configure the website at Hostinger.
10. Verify the destination hosting configuration.
11. Obtain the exact Hostinger nameservers from hPanel.
12. Recreate required third-party DNS records where necessary.
13. Change the nameservers at the registrar.
14. Monitor DNS propagation.
15. Test the root domain.
16. Test www.
17. Test HTTPS.
18. Test incoming email.
19. Test outgoing email.
20. Verify SPF, DKIM and DMARC after migration.

This greatly reduces the risk of unexpected downtime.

Useful Windows DNS Diagnostic Commands

Display configured DNS servers

ipconfig /all

Flush local DNS cache

ipconfig /flushdns

Check domain resolution

nslookup example.com

Check nameservers

nslookup -type=NS example.com

Check mail servers

nslookup -type=MX example.com

Check TXT records

nslookup -type=TXT example.com

PowerShell nameserver lookup

Resolve-DnsName example.com -Type NS

PowerShell MX lookup

Resolve-DnsName example.com -Type MX

These commands are useful when diagnosing DNS migration, website connectivity and email-delivery problems.

Frequently Asked Questions (FAQ)

1. What are Hostinger nameservers?

They are authoritative DNS servers used to manage DNS records for domains configured to use Hostinger DNS services.

2. What are Hostinger's nameserver addresses?

Hostinger has historically documented nameservers such as:

ns1.dns-parking.com
ns2.dns-parking.com

However, Hostinger currently recommends using the exact nameservers displayed in your hPanel because values can vary.

3. Do I need nameserver IP addresses?

Usually not. Most registrars require only nameserver hostnames.

4. How long does a nameserver change take?

DNS changes may become visible quickly, but full worldwide propagation can take up to approximately 24 hours.

5. Will changing nameservers delete my website?

No. It does not delete website files. It changes DNS authority.

6. Can changing nameservers cause website downtime?

Yes, particularly if the new DNS zone or hosting configuration is incomplete.

7. Can changing nameservers affect email?

Yes. Incorrect or missing MX, SPF, DKIM or other mail-related records can interrupt email.

8. Can I use Hostinger hosting with Google Workspace?

Yes. Configure the required Google Workspace DNS records at the authoritative DNS provider.

9. Can I use Hostinger hosting with Microsoft 365?

Yes. Microsoft 365 DNS records can coexist with a website hosted at Hostinger.

10. Can my domain remain registered elsewhere?

Yes. Your registrar and hosting provider can be different companies.

11. Is changing nameservers the same as transferring a domain?

No. A nameserver change modifies DNS authority. A domain transfer changes the registrar.

12. Should I change nameservers or the A record?

Use nameservers when you want Hostinger to manage DNS. Use an A record when you want to keep DNS management with the existing provider.

13. Why does my old website still appear after changing nameservers?

DNS caching and propagation can temporarily cause users to reach the old server.

14. Why does the website work on mobile data but not office broadband?

Different networks may use different DNS resolvers and cached DNS information.

15. Should I delete my old hosting immediately?

No. Keeping the old hosting operational during DNS migration provides a useful safety window.

16. Should I disable DNSSEC before changing nameservers?

DNSSEC must be handled carefully during DNS-provider migration. An incorrect DS/DNSSEC configuration can cause resolution failures.

17. Why does my website work but email does not?

Website DNS and mail DNS are separate. Your A/CNAME records may be correct while MX or other mail-related records are incorrect.

18. Can I use Cloudflare with Hostinger?

Yes. Cloudflare can remain the authoritative DNS provider while the website points to Hostinger.

19. Where should DNS records be edited?

Normally at the provider whose authoritative nameservers are currently assigned to your domain.

20. How can I check the current nameservers from Windows?

Run:

nslookup -type=NS example.com

or:

Resolve-DnsName example.com -Type NS

Final Recommendation

Changing nameservers is technically simple, but on an active business domain it should not be treated as merely replacing two text values.

Before making the change, identify:

Domain Registrar → Authoritative DNS Provider → Website Hosting Provider → Email Provider

For example:

Registrar:        Domain Registrar
DNS:              Hostinger
Website Hosting:  Hostinger
Email:            Google Workspace

Once this structure is clear, DNS configuration becomes much easier to understand and troubleshoot.

Most importantly, always copy the current nameservers shown in your own Hostinger hPanel rather than relying permanently on nameserver or IP values published in older documentation.

Disclaimer

Hostinger's interface, infrastructure, nameservers, IP addresses, DNS procedures and service configuration may change over time. Always verify current values in your Hostinger hPanel and official Hostinger documentation before making DNS changes.

DNS modifications can affect websites, email and other domain-based services. For production or business-critical domains, record or back up the existing DNS configuration before making changes.