Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →To change a domain’s DNS records in Hostinger, first confirm that Hostinger nameservers serve its live DNS zone. Then open the DNS Zone Editor, add or update only the record your destination service requires, and verify the result after DNS caches have had time to refresh. If the domain uses another provider’s nameservers, make the change at that provider instead.
First confirm where the live DNS zone is managed
Nameservers determine which provider’s DNS records are authoritative. Check the domain’s current nameservers before editing anything. If Hostinger nameservers are active, use Hostinger’s DNS Zone Editor. If another provider’s nameservers are active, update the records in that provider’s DNS controls. Hostinger may allow you to prepare edits in its dashboard while external nameservers are set, but those edits will not take effect unless the domain’s nameservers point back to Hostinger. See Hostinger’s DNS Zone Editor guide and DNS records management guide.
As an Amazon Associate I earn from qualifying purchases.
Open the DNS Zone Editor
The documented route depends on whether you have a site on a hosting plan or a domain-only account:
- With hosting: In the dashboard, go to Websites, select the site, then choose Advanced → DNS Zone Editor.
- Domain only: Choose DNS in the dashboard sidebar and select the domain.
Dashboard labels can change. If the editor is missing, check that the domain is connected to the hosting plan and uses the correct nameservers. Hostinger documents these access paths in its DNS Zone Editor guide.
#1 Best Overall
Choose the record that matches the task
Get the exact record name, destination, and any priority or other fields from the service you are connecting. The record form includes a type, name, destination or content, and TTL; additional fields depend on the record type. The supported record types include A, AAAA, CNAME, MX, TXT, SRV, CAA, and NS.
| Record | What it does | Target or value | Key caution |
|---|---|---|---|
| A | Points a name to an IPv4 address. | An IPv4 address; use @ for the root in Hostinger’s A-record example, or the subdomain label for a subdomain. |
Check for conflicting or outdated A and AAAA records. Before changing the root A record, disable Hostinger CDN as its A-record guidance instructs. |
| AAAA | Points a name to an IPv6 address. | The IPv6 address supplied by the destination service. | Do not substitute an IPv4 address or guess a value. |
| CNAME | Makes one hostname an alias of another hostname. | A destination hostname, not an IP address. Enter the host label without repeating the domain suffix; for example, www can point to the root domain. |
Use the exact hostname supplied by the service. |
| MX | Routes email for the domain to mail servers. | Mail server hostname and priority from the email provider. | Lower priority numbers mean higher priority in Hostinger’s explanation. Ensure the active MX records match the intended email service. |
| TXT | Stores text used for verification and email configuration. | The exact text supplied by the verification or mail service. | Do not invent or casually concatenate SPF, DKIM, or verification values. Hostinger’s guidance describes one SPF record and one DKIM record; follow your email provider’s current setup instructions. |
| SRV | Locates a particular service. | Service, protocol, port, target, priority, and weight, as supplied by the service. | Use only when the service calls for an SRV record. |
| CAA | Controls which certificate authorities may issue certificates for the domain. | The certificate authority policy values required by your setup. | Use only when your certificate or DNS configuration calls for it. |
| NS | Relates to DNS delegation and nameservers. | The nameserver values required for the delegation. | Changing delegation affects where DNS is managed; do not treat an NS change like an ordinary website record edit. |
Hostinger’s explanations of record types and A and CNAME formatting are in its supported DNS record types, A-record guide, and CNAME guide.
Rank #2
Add or edit the required record
- Open the correct domain’s editor. Use the hosting or domain-only dashboard route, and confirm that its nameservers serve the live zone.
- Choose the record type and name. Match the service’s instructions. For the root A-record example, Hostinger uses
@; for a subdomain, enter its label. For a CNAME, enter the host label without appending the domain suffix again. - Enter the exact destination and any required fields. Use an IPv4 address for A, IPv6 address for AAAA, hostname for CNAME, or the provider’s mail server and priority for MX. Copy TXT and service-specific values exactly.
- Set the TTL. If the destination service does not specify one, Hostinger’s A- and CNAME-record help pages cite 14400 seconds (four hours) as a default. TTL is a resolver’s cache duration, not a guarantee that every network will display a change after exactly that interval.
- Review existing records before saving. Remove conflicting or outdated A or AAAA records only where the change requires it. For a root A-record change, account for Hostinger’s CDN warning before proceeding.
- Save the change. Recheck the record name, value, and any priority against the destination service’s instructions before leaving the editor.
For A records, consult Hostinger’s A-record instructions; for CNAME entries, consult its CNAME instructions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Allow for DNS caching and verify the result
Hostinger advises that DNS changes can take up to 24 hours to propagate globally. The actual time a resolver shows a new value can depend on caching; a 14400-second TTL is not a promise of a uniform four-hour update. After saving, compare the record in the editor with the destination service’s requested name and value, then allow time for cached answers to expire before repeatedly editing the record. The timing guidance is in Hostinger’s DNS Zone Editor guide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Back up the zone before bulk changes
For multiple records, the editor supports bulk actions and BIND zone-file import and export. Exporting a zone file can preserve a portable copy before edits. When importing, Append adds records; Replace overwrites the existing records, so treat Replace as a full-zone overwrite. DNS history can also restore a previous snapshot, but restoring it replaces the current zone after confirmation. Review the file or snapshot carefully before applying it. See Hostinger’s DNS records management guide and DNS Zone Editor guide.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
