How to Add DNS Records in Hostinger

How to Add DNS Records in Hostinger

Open hPanel, go to Domains, select your domain, and open DNS / Nameservers to reach the DNS Zone Editor. If the domain sits on a hosting plan, you can also reach the editor through Websites, your site’s dashboard, Advanced, then DNS Zone Editor. From there, click Add record, choose the record type, fill in the Name/Host and value fields, and click Save.

This only works while the domain uses Hostinger’s nameservers. If your DNS is hosted somewhere else, the records have to be changed at that provider instead.

How to Add DNS Records in Hostinger Step by Step

Two documented routes exist, and which one applies depends on what you bought. Accounts with hosting use the website dashboard path above. Domain-only accounts go to hPanel, Domains, Domain portfolio, select the domain, then DNS / Nameservers and DNS records. The editor is also available from a website’s dashboard sidebar, so you can open it without leaving the site view.

Before you start, confirm two things: the domain is connected to the hosting plan and it points at the correct nameservers. Hostinger keeps snapshots of your DNS zone, so a bad edit can be reverted rather than rebuilt by hand. Take a moment to note the current values of any record you plan to change.

Then follow these steps:

  1. Click Add record.
  2. Choose the record type from the list.
  3. Fill in Name/Host. Use @ for the root domain, www for www.yourdomain.com, or a subdomain name.
  4. Enter the destination IP, hostname or text string in the value field.
  5. Leave TTL at the default unless you have a reason to change it, since the default is fine for most records.
  6. Add a priority value only where the type requires one, meaning MX and SRV records, where a lower number means higher priority.
  7. Click Save.

To change or remove something later, find the record in the list, click Edit or Delete, then confirm.

Once saved, confirm the entry appears with the values you entered. To see whether the change has spread beyond Hostinger’s own nameservers, look the record up on dnschecker.org or whatsmydns.net.

The DNS Record Types You Will Actually Use

Most records you will ever touch fall into a small group. Each one carries a specific kind of routing or verification job.

Record type What it does Example
A Points a domain to an IPv4 address @ → 185.0.0.1
AAAA Points a domain to an IPv6 address @ → 2001:db8::1
CNAME Creates an alias to another domain www → yourdomain.com
MX Identifies the mail server for the domain @ → mail.hostinger.com, priority 10
TXT Holds free-text values for verification, SPF and DKIM @ → “v=spf1 include:… ~all”
NS Lists the authoritative nameservers @ → ns1.example-dns.com
SRV Locates app or protocol-specific services Service-specific values
CAA Names the certificate authorities allowed to issue for the domain @ → 0 issue “letsencrypt.org”

MX and SRV records also need a priority value, and a lower number means higher priority. NS records are usually set for you, so hand-editing them is rarely necessary.

On the root domain the A record is what serves your site, while CNAME examples in Hostinger’s documentation use the www subdomain. Keep that pattern in mind before you replace anything at the root.

Working with Email Records

An MX record names the mail server and carries a priority. If you use Hostinger Email, resist adding MX, SPF, DKIM and DMARC by hand, because the Email Domain Settings page sets all four up for you. Hand-built duplicates are a common source of conflict.

Common Mistakes When Editing DNS Records in Hostinger

Overwriting an existing A or CNAME record without checking what it does is the fastest way to take a site offline, because that record is what points the domain at the server holding your files. Note the old value first.

Mixing MX records from two providers is another frequent error. Delete the old entries before adding a new provider’s values, and keep the priority rule in mind, since a lower number wins. Adding Hostinger mail records manually when the Email Domain Settings page already configures them creates the same muddle.

Editing in hPanel while DNS lives elsewhere is a quieter mistake. When another provider’s nameservers are authoritative, changes made in the Hostinger editor are ignored.

Expecting instant global results also causes confusion. Changes can take up to 24 to 48 hours to propagate, often sooner. Caching across the wider internet is the reason, and ICANN’s documentation on the Domain Name System explains why that caching layer exists.

Finally, paste values exactly as the service gives them. Some DNS interfaces expect a trailing dot on a fully qualified name and others do not, so altering the supplied string can produce a lookup that never resolves.

What to Do If Something Goes Wrong

Work through the likely causes in order rather than changing several things at once.

If the editor will not open or shows nothing useful, check that the domain is connected to the hosting plan and uses the correct nameservers. If the domain points at another provider, move to that dashboard instead.

If the site breaks right after an edit, restore from the DNS zone snapshot to get back to the last working state. Then re-check the value you entered against the source that gave it to you.

If email stops arriving, confirm the MX records match what your mail provider issued and that no old provider’s entries remain. Where Hostinger Email is involved, run the Email Domain Settings page again so MX, SPF, DKIM and DMARC are rebuilt together.

If a saved record seems not to work, verify it exists in the list with the right value, then check propagation on dnschecker.org or whatsmydns.net rather than assuming the save failed. Allow up to 24 to 48 hours for global propagation before concluding the change is broken.

Propagation Time and TTL Settings Explained

TTL is the cache lifetime of a record in seconds, and the default is fine for most entries. Where no specific TTL is required, Hostinger’s support documentation points to a default of 14400 seconds, which is four hours.

Lowering the TTL before a planned server move shortens how long caches hold the old value, so the switch surfaces faster once you make it. Raise it again after the move settles.

Propagation follows that timer. Changes can take up to 24 to 48 hours to reach every resolver worldwide, often less, and TXT record changes alone should be given up to 24 hours. Split behavior during the window is normal, with some visitors reaching the new destination and others still hitting the cached one.

Managing DNS When Using External Nameservers

If your domain points at Cloudflare, AWS Route 53 or another provider’s nameservers, records must be managed there. hPanel may still display the editor, but Hostinger is no longer authoritative for the zone.

Hostinger nameserver pairs differ per domain, so never guess them or copy them from another guide. If the domain already uses a *.dns-parking.com pair, keep that pair. To see what is currently set, open the Nameservers section in hPanel. Moving DNS back to Hostinger means changing nameservers at the registrar first, and you will need to wait for that delegation to take effect before edits in hPanel mean anything. The steps for that switch are covered in How to Change Nameservers in Hostinger.

Connecting Third-Party Services

Verification and connection tasks often come with an exact CNAME or TXT string. Paste it character for character, including capital letters and hyphens, because the checking service validates against what it issued.

Frequently Asked Questions

Can I Undo a Bad DNS Edit?

Yes. Hostinger keeps DNS zone snapshots that can be restored to roll back a change.

Where Do I Check Whether a Record Went Live?

Look the record up on dnschecker.org or whatsmydns.net, and allow up to 24 to 48 hours for global propagation first.

Do I Need to Add Hostinger Email Records Manually?

Usually not. The Email Domain Settings page configures MX, SPF, DKIM and DMARC for you. Adding them by hand risks duplicates.

Why Is the Editor Missing or Empty?

Check that the domain is attached to the hosting plan and uses the right nameservers, and if DNS sits at another provider, edit there instead.

What This Means for Your Website Setup

The DNS Zone Editor puts routing, verification and email configuration in your hands without a support ticket. The safe habits are simple: read the existing record before you replace it, keep the default TTL unless a migration demands otherwise, and confirm with a lookup tool instead of assuming a save has gone live.

If you are still choosing where to host, the verified promotional pricing page is worth a look before you buy, and How to Add a Website in Hostinger hPanel covers the setup that comes first. For mail clients, How to Add Hostinger Email to Gmail picks up after the records are in place.

Claim Your Discounted Plan Now

This page contains affiliate links. If you purchase through the links on this page, we may earn a commission, at no extra cost to you.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top