DNS instructions depend on the product and the records displayed in your own account. These are general decision steps, not instructions to replace working DNS records blindly.
Start with a map of the services you already use
Write down who registered your domain, who hosts its DNS, where the website will live and who handles email. They may all be different companies. A domain transfer is not the same as changing nameservers, and neither is required merely to point a website. Before editing anything, export or screenshot existing A, AAAA, CNAME, MX, TXT and verification records so there is a reliable rollback reference.
Understand what changing nameservers actually moves
Nameservers determine which DNS provider answers for the entire domain. Switching them to Hostinger can be convenient when you also want DNS managed there, but existing third-party email, verification and subdomain records may need to be recreated in the new zone. A website connection that succeeds while business email stops working is not a successful migration. Check the entire record set before changing authority.
Consider an A record when you want to keep current DNS
For compatible web or cloud hosting setups, Hostinger describes an A-record method that leaves DNS management with the existing provider. Follow the exact address displayed for your website in hPanel; never copy an IP address from a blog or a different account. Review both the root domain and www records for conflicts. Email routing generally stays at the current DNS provider, but still verify it after the change.
Website Builder has a distinct DNS procedure
Hostinger Website Builder is not identical to generic web hosting. Its help center documents nameserver, CNAME and A-record options with product-specific values. If you use Cloudflare or another external DNS provider, follow the Website Builder guide, not a WordPress hosting tutorial. Record which method you chose and ensure the website has actually been published; DNS changes alone do not publish a draft website.
Protect MX, SPF, DKIM and DMARC before changing anything
MX records determine inbound mail delivery; SPF, DKIM and DMARC help authenticate mail and reduce spoofing. If your email runs through Google Workspace, Microsoft 365 or another provider, capture the records from that provider’s current instructions. Recreate and verify them when moving DNS authority. If you only change the website A record, avoid modifying email records without a specific, validated reason.
Check DNSSEC and temporary domains carefully
Hostinger’s domain-pointing guide includes a DNSSEC preflight check; DNSSEC settings must be coordinated with the authoritative nameservers to avoid resolution failures. Do not disable an existing security feature casually: follow the authoritative provider’s migration guidance. A temporary preview address is useful for testing but should not become the permanent canonical URL for a published business site.
Validate the change from the outside
Check that the root domain and www reach the intended website, that HTTPS works, and that both incoming and outgoing email still function. Review mobile loading and contact forms as well as DNS lookup results. Propagation can take time, and a cached answer can make two devices disagree briefly. Avoid repeatedly changing records while the first change is propagating; compare results against the recorded target configuration.
Keep a rollback plan and clear ownership
Record the previous and new DNS zones, the change time, an administrator contact and a rollback trigger such as email failure or a prolonged certificate error. Only edit the zone if you understand which provider is authoritative. If the current setup is working, do not migrate nameservers solely because a checklist says so; minimize changes and document their purpose.
Editorial guidance informed by the public sources below. Product features, pricing and availability may change; always verify the live offer.
Read external Hostinger feedback.
Inspect original third-party review sources in their own context. They are not SiteVoom ratings.
See source directory ↗Pick a suitable Hostinger building route.
Use our focused Hostinger plan finder, or compare alternatives in the wider provider directory.
Ready to check the official options?
Review current products and checkout terms on the official websites of the platforms covered in this guide.
Official links only — no affiliate tracking is active.