Have you recently changed your domain's nameservers or DNS records on Hostinger, but your website is still showing the old content or refusing to load? This can happen when DNS changes have not fully propagated or when your domain has an incorrect DNS configuration.
Updated: November 2026 · DNS troubleshooting guide
Quick answer: DNS propagation is automatic and usually takes up to 24 hours. If your domain is still not pointing to Hostinger, check your active nameservers, verify A and CNAME records, review DNSSEC settings, and check the updated records using a DNS lookup tool.
In this guide, you will learn how DNS propagation works, how to check whether your changes are active, and how to fix common Hostinger DNS problems without making unnecessary changes to your domain.
1. What Is DNS Propagation?
DNS propagation is the process through which updated domain information becomes available across DNS resolvers around the world.
Whenever you change your domain's nameservers or update DNS records, the new information must be discovered by DNS servers and resolvers. These systems may temporarily continue using previously cached information.
For example, suppose your domain points to an old hosting provider and you update its A record to point to Hostinger. Some DNS resolvers may begin returning the new IP address quickly, while others may temporarily return the old address.
This is why your website may work on one network but not another immediately after a DNS update.
What changes can trigger DNS propagation?
Changing domain nameservers.
Updating an A or AAAA record.
Adding or changing a CNAME record.
Updating MX records for email services.
Adding or modifying TXT records.
Moving DNS management to another provider.
Important: DNS propagation is automatic. You do not need to manually distribute your DNS records to servers around the world. Your job is to make sure the records are correct and allow the DNS system time to update.
2. How Long Does DNS Propagation Take on Hostinger?
Hostinger states that DNS propagation can take up to 24 hours. Many changes become visible within a shorter period, but the time depends on the DNS record type, caching, and the previous configuration.
In rare cases, certain DNS records may take up to 72 hours to update everywhere.
DNS Change
What It Affects
What to Expect
Nameserver change
Which provider manages your DNS zone.
Can take up to 24 hours; validation may also be required.
A record update
Which IPv4 address a hostname resolves to.
Often updates within hours, but caching can delay results.
CNAME update
Where an alias hostname points.
Depends on DNS caching and the previous TTL.
MX record update
Where incoming email is delivered.
May take time before mail servers use the new records.
TXT record update
Domain verification and email authentication.
Verification services may need time to detect the new value.
These are general expectations, not guaranteed completion times. A DNS lookup may show the new value before every network has stopped using cached information.
What is TTL and why does it matter?
TTL stands for Time to Live. It tells DNS resolvers how long they can keep a record in their cache before checking for updated information.
For example, a TTL of 14400 seconds equals four hours. A resolver that cached the old record may continue using it until its cache expires, even after you have updated the record at your DNS provider.
Remember: Lowering TTL after a change does not immediately remove records that were already cached using an earlier TTL.
3. Why Is Hostinger DNS Propagation Not Working?
If your domain is not pointing to Hostinger after making DNS changes, the problem may be related to propagation or an incorrect DNS configuration.
Common reasons include:
Incorrect nameservers: Your domain is still using the previous provider's nameservers.
Wrong A record: The domain points to an incorrect hosting IP address.
Conflicting records: Old A, AAAA, or CNAME records interfere with the intended setup.
DNSSEC problems: An outdated or incompatible DNSSEC configuration prevents DNS responses from validating correctly.
Cached DNS information: Your computer, router, browser, or DNS resolver still uses an older result.
Incorrect email records: MX or TXT records do not match the email provider's configuration.
Domain verification: The domain requires an ownership verification step.
Wrong DNS provider: You are editing records in Hostinger while another provider manages the active DNS zone.
Do not keep changing DNS records repeatedly. First identify whether the issue is propagation, nameserver configuration, DNSSEC, or an incorrect record. Repeated changes can make troubleshooting more difficult.
4. How to Check DNS Propagation
Before changing any settings, check whether your DNS records have already started updating. This helps you understand whether you should wait or investigate a configuration problem.
These tools let you check DNS records from multiple locations.
Step 2
Enter Your Domain Name
Enter your domain, such as example.com, in the search field.
Do not include a full webpage URL or an extra path. Enter only the domain or hostname you want to check.
Step 3
Select the Correct DNS Record Type
Choose the record type based on the change you made:
NS: Check nameserver changes.
A: Check IPv4 address changes.
AAAA: Check IPv6 address changes.
CNAME: Check hostname aliases.
MX: Check email routing records.
TXT: Check verification and email authentication records.
Step 4
Run the DNS Lookup
Click Search or Lookup. The tool will display the DNS results reported by its selected locations.
Step 5
Compare the Results
Compare the returned nameservers, IP address, or record value with the information you entered in Hostinger.
If some locations show the new value and others show the old value, propagation may still be in progress.
How to understand DNS checker results
Result
Meaning
What to Do
All locations show the new value
Propagation appears complete for the locations checked.
Test your website or service.
Some locations show old values
Propagation or caching may still be in progress.
Wait and check again later.
All locations show no result
The record may not exist or may not have propagated.
Verify the record and active nameservers.
Results show an unexpected IP
The active DNS record may be incorrect.
Check the A record at the authoritative DNS provider.
5. How to Fix Hostinger DNS Propagation Issues
If your domain is still not working after updating DNS, follow these troubleshooting steps in order.
Fix 1
Verify Your Domain's Nameservers
Nameservers determine which provider manages your domain's active DNS zone. If your domain uses external nameservers, DNS changes made in Hostinger may not be the active changes serving visitors.
Open your domain registrar's dashboard.
Find the domain's nameserver settings.
Check which nameservers are currently assigned.
Compare them with the exact nameservers provided in Hostinger.
If you want Hostinger to manage your active DNS zone, update the nameservers at your registrar.
Hostinger's assigned nameservers can vary by domain and setup. Always use the values displayed in your own account.
Fix 2
Check Your A and CNAME Records
Incorrect website records are a common reason a domain does not point to the correct server.
Log in to Hostinger hPanel.
Open Domains → DNS.
Select your domain.
Check the existing A and CNAME records.
Compare the values with the connection instructions for your hosting plan.
Correct any outdated or incorrect values.
For standard web hosting, the root A record should use the hosting IPv4 address shown in your Hostinger dashboard. The www hostname should use the record type and target specified by Hostinger's connection instructions.
Fix 3
Check DNSSEC Settings
DNSSEC is a security feature that helps validate DNS responses. An outdated DS record or incompatible DNSSEC configuration can prevent DNS from resolving correctly after a nameserver change.
Log in to your domain registrar.
Open DNSSEC or advanced DNS settings.
Check whether DNSSEC is enabled.
If it is enabled and Hostinger's troubleshooting instructions require it, disable it at the registrar.
Check the domain again after the DNSSEC change.
If you manage DNSSEC records manually, make sure the DS record at the registrar matches the DNS provider's current configuration. Do not remove or replace security records without understanding the setup.
Fix 4
Check Your MX Records for Email Problems
If your website works but email stops working after a DNS change, the problem may be related to MX records.
Open your active DNS management provider.
Find the MX records for your domain.
Compare them with your email provider's official configuration.
Correct the mail server values and priorities if necessary.
Check SPF, DKIM, and DMARC TXT records as well.
Do not use generic MX values. Google Workspace, Microsoft 365, Hostinger Email, and other services can have different requirements.
Fix 5
Confirm That You Are Editing the Correct DNS Zone
If your domain uses nameservers from Cloudflare or another provider, that provider manages the active DNS zone.
Hostinger allows you to prepare or edit DNS records in its dashboard in supported configurations, even when external nameservers are currently active. However, those records will not become the live records until the domain uses Hostinger nameservers.
Check your nameserver configuration before making additional edits.
Fix 6
Check Whether Your Domain Is Verified
Some newly registered domains require contact information verification. If the verification is not completed, the domain may become temporarily suspended.
Check your registered email address.
Look for a domain verification message from your registrar.
Open the verification link if one is required.
Check the domain status in your registrar's dashboard.
After verification, domain activation can take additional time.
Fix 7
Reset Your DNS Zone Only If Necessary
If the DNS zone is badly misconfigured and your domain is already pointing to Hostinger, Hostinger provides a DNS reset option for supported domains.
Open Hostinger's Domains section.
Click Manage next to your domain.
Open DNS / Nameservers.
Find the DNS reset option.
Review the warning and understand which records will be replaced.
Confirm only if you intend to restore the default DNS configuration.
For external domains, open the External domains section and manage the relevant domain if it is available there.
Before resetting DNS: Export your existing DNS records or save a copy of them. A reset can replace custom A, MX, TXT, CNAME, and other records. Your external email and connected services may stop working if their records are not recreated.
6. How to Clear Your Local DNS Cache
Sometimes DNS propagation is complete, but your computer continues to use an older DNS result. This can happen because your operating system has cached the previous address.
If you are using Windows, you can clear the local DNS cache through Command Prompt or PowerShell.
Clear DNS cache on Windows
Step 1
Open Command Prompt or PowerShell
Press the Windows key, search for PowerShell or Command Prompt, and open it. You can use a regular session for this command.
Step 2
Run the Flush DNS Command
Enter the following command:
ipconfig /flushdns
Press Enter. Windows should display a message confirming that the DNS resolver cache was successfully flushed.
Step 3
Restart Your Browser
Close and reopen your browser. Visit your website again and check whether it now loads using the updated DNS information.
Enter your administrator password if requested. The exact command can vary by macOS version.
Other things to try
Open your website in a private or incognito browser window.
Try a different browser.
Test the website using mobile data instead of your Wi-Fi connection.
Restart your router if you suspect it is caching DNS information.
Check whether your browser or network uses a custom DNS resolver.
Remember: Flushing your computer's DNS cache only clears local cached information. It does not speed up global DNS propagation or fix an incorrect DNS record.
7. How to Verify Your Hostinger DNS Records
Once you have checked nameservers and propagation, review the actual DNS records to make sure they match your hosting and email configuration.
Common records to verify
Record
What to Check
A
Check that the root domain points to the correct hosting IPv4 address.
AAAA
Check that the IPv6 address is valid and belongs to the intended service.
CNAME
Check that www or other aliases point to the correct hostname.
MX
Check the mail servers and priority values required by your email provider.
TXT
Check SPF, DKIM, DMARC, and verification values.
NS
Check that the domain uses the intended nameservers.
Where to check DNS records in Hostinger
Log in to Hostinger hPanel.
Open Domains from the sidebar.
Click DNS.
Select your domain.
Open the DNS records section.
Review the records and update incorrect entries if needed.
You can also check your domain's DNS history if you need to review previous DNS configurations or restore a supported earlier version.
8. Common DNS Errors and Their Solutions
1. Your Domain Is Not Pointing to Hostinger
This message usually appears when Hostinger cannot detect the expected nameservers or DNS records.
Check the nameservers at your registrar.
Verify the A record against your hosting plan's IP address.
Check the www record.
Allow time for DNS propagation.
2. DNS_PROBE_FINISHED_NXDOMAIN
This browser error means the requested hostname could not be resolved through DNS.
Check whether the domain is registered and active.
Verify the domain's nameservers.
Check whether the required DNS record exists.
Confirm that the hostname is typed correctly.
Flush the local DNS cache.
3. DNS_PROBE_FINISHED_BAD_CONFIG
This error can indicate a DNS configuration problem on your device or network.
Check your device's DNS settings.
Restart your router if needed.
Flush the local DNS cache.
Check whether your domain's DNS records are correct.
Test the domain using another network.
4. Website Shows the Old Hosting Provider
If your website still loads from the old server, some DNS resolvers may be using cached records or the active A record may still point to the previous IP address.
Check the A record using a DNS lookup tool and compare the result with your new Hostinger hosting IP address.
5. Website Works but Email Does Not
This usually indicates an email DNS configuration issue rather than an A record propagation problem.
Check the MX, SPF, DKIM, and DMARC records against the official settings supplied by your email provider.
6. DNS Records Look Correct but Hostinger Still Shows Connecting
Hostinger may still be waiting for DNS propagation, nameserver validation, or domain verification. Check the connection status and verify the records through an external DNS lookup tool.
If the expected values are already visible but the dashboard continues showing an error, contact Hostinger support with your domain and the DNS lookup results.
9. What to Do While DNS Is Propagating
You do not need to stop working on your website while DNS changes are being applied. Hostinger provides ways to continue preparing your website during this period.
Use the temporary preview URL
If your domain is being connected to Hostinger, you can continue working on your website through the temporary preview URL where available.
This allows you to check website content and make changes without waiting for the public domain to finish propagating.
Use a local hosts file for testing
Advanced users can temporarily edit their computer's hosts file to map a domain to the new server IP address.
This allows the computer to access the website using the new server before public DNS propagation is complete. The change only affects the computer where the hosts file is modified.
Important: A hosts-file entry is only a local testing method. It does not change public DNS records or make the website available to other visitors. Remove the temporary entry when it is no longer needed.
Still having DNS problems?
Use Hostinger's official troubleshooting guide to check nameservers, DNSSEC, DNS records, and domain connection status.
1. How long does DNS propagation take on Hostinger?
Hostinger states that DNS propagation can take up to 24 hours. Some changes become visible sooner, while certain records may take up to 72 hours in rare cases.
2. Why is my domain still not pointing to Hostinger?
Your domain may still be using old nameservers, incorrect A or CNAME records, or an incompatible DNSSEC configuration. Check the active DNS provider and verify the records against Hostinger's instructions.
3. How can I check whether DNS propagation is complete?
Use a DNS lookup tool such as What's My DNS or DNS Checker. Enter your domain, select the record type you changed, and compare the returned values with your Hostinger DNS configuration.
4. Can I use my website while DNS is propagating?
Yes. You can continue working through Hostinger's temporary preview URL where available. Advanced users can also use a local hosts-file entry to test the website on the new server.
5. Does flushing DNS cache fix propagation problems?
Flushing your local DNS cache can help your computer stop using an outdated cached result. However, it does not fix incorrect DNS records or speed up propagation across the internet.
6. Why does my website work on mobile data but not on Wi-Fi?
Your Wi-Fi network, router, or DNS resolver may still be using cached information. Try restarting the router, flushing your device's DNS cache, or testing with another DNS resolver.
7. Can DNSSEC cause Hostinger DNS propagation issues?
Yes. An outdated DS record or incompatible DNSSEC configuration can prevent DNS responses from validating correctly. Check the DNSSEC settings at your registrar and follow Hostinger's current troubleshooting instructions.
8. Why are some DNS checker locations showing the old IP address?
Different DNS resolvers may have cached the previous record for different periods. If some locations show the new IP and others show the old one, propagation or caching may still be in progress.
9. Should I reset my Hostinger DNS zone to fix propagation?
Only reset the DNS zone if you have identified a configuration problem and understand which records will be replaced. Export your existing records first because a reset can remove custom website and email settings.
10. What should I do if DNS propagation takes more than 24 hours?
Check the authoritative nameservers, DNS records, DNSSEC configuration, and domain status. If the expected values are correct but the domain still does not resolve, contact Hostinger support with your DNS lookup results.
11. Does changing nameservers affect email?
It can. When you switch nameservers, the new DNS provider becomes responsible for the active DNS zone. Make sure the correct MX, SPF, DKIM, and DMARC records are configured to keep your email working.
12. Can I edit DNS records in Hostinger while propagation is happening?
Yes, you can manage DNS records in Hostinger where an appropriate DNS zone exists. However, changes become publicly active through Hostinger only when the domain's active nameservers point to Hostinger.
Final Thoughts
DNS propagation problems can be frustrating, especially when your website is not loading after changing nameservers or DNS records. However, most issues can be resolved by checking the active nameservers, verifying A and CNAME records, reviewing DNSSEC settings, and allowing enough time for propagation.
Before making additional changes, use a DNS lookup tool to understand what the internet currently sees. If the updated records are correct but your computer still displays old information, try clearing your local DNS cache.
Most importantly, avoid resetting your DNS zone or deleting records without checking their purpose. With the correct DNS configuration and a little patience, your domain should connect to Hostinger successfully.
Editorial note: DNS propagation times, dashboard options, and troubleshooting procedures may change. Follow the current DNS instructions in your Hostinger account and verify your domain's records before making major configuration changes.
