Hostinger email stopped after nameserver change: when this repair path applies
Restore Hostinger Email MX and authentication records in the DNS zone that is now authoritative. Use these steps when mail records were not copied to the active DNS provider, but first run the embedded diagnostic so the business-email DNS and mail authentication evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
Hostinger hPanel domain/DNS management, Emails and SSL sections for the service actually involved. For Hostinger email stopped after nameserver change, confirm the active nameservers and exact service owner before changing identify active nameservers. A DNS-looking screen at hostinger has no public effect when another provider is authoritative for the zone.
Evidence to save for Hostinger email stopped after nameserver change
Record the current public state for identify active nameservers, copy Hostinger mail records, remove stale MX conflicts. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Identify active nameservers — Compare the delegated nameservers with the servers that actually answer authoritatively; a record edited in a non-authoritative zone has no effect.
- Copy Hostinger mail records — Verify copy Hostinger mail records from the public Internet and compare it with the value the responsible provider says should be live.
- Remove stale MX conflicts — Read the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
- Retest — Verify retest from the public Internet and compare it with the value the responsible provider says should be live.
Repair steps in hostinger
Restore Hostinger Email MX and authentication records in the DNS zone that is now authoritative.
- 1. Identify active nameservers. After this step, check the public value tied to identify active nameservers before changing another unrelated setting.
- 2. Copy Hostinger mail records. After this step, check the public value tied to copy hostinger mail records before changing another unrelated setting.
- 3. Remove stale MX conflicts. After this step, check the public value tied to remove stale mx conflicts before changing another unrelated setting.
- 4. Retest. After this step, check the public value tied to retest before changing another unrelated setting.
Why this order matters for hostinger
The sequence begins with the provider/authority decision, then moves through identify active nameservers, copy Hostinger mail records, remove stale MX conflicts. That keeps the change scoped to the failed business-email DNS and mail authentication path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Hostinger email stopped after nameserver change
The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. Compare the same identify active nameservers and copy Hostinger mail records evidence used before the change; a repair is complete when the public result agrees, not merely when the hostinger interface reports that a save succeeded.
If hostinger and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting identify active nameservers value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Hostinger email stopped after nameserver change should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.