Hostinger domain points to old website: when this repair path applies
Update only the stale website endpoints and check for a forgotten AAAA record. Use these steps when A/AAAA records still target the old host, but first run the embedded diagnostic so the DNS resolution and delegation 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 domain points to old website, confirm the active nameservers and exact service owner before changing confirm current hosting IP. A DNS-looking screen at hostinger has no public effect when another provider is authoritative for the zone.
Evidence to save for Hostinger domain points to old website
Record the current public state for confirm current hosting IP, compare A and AAAA, update stale values. 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.
- Confirm current hosting IP — Verify confirm current hosting IP from the public Internet and compare it with the value the responsible provider says should be live.
- Compare A and AAAA — Compare IPv4 and IPv6 separately. A healthy A record can hide a broken AAAA path that affects only visitors whose network prefers IPv6.
- Update stale values — Verify update stale values from the public Internet and compare it with the value the responsible provider says should be live.
- Wait according to TTL then retest — Compare independent resolvers or regional probes together with TTL. Different answers are evidence of cache/authority differences, not a reason to claim a fixed global propagation time.
Repair steps in hostinger
Update only the stale website endpoints and check for a forgotten AAAA record.
- 1. Confirm current hosting IP. After this step, check the public value tied to confirm current hosting ip before changing another unrelated setting.
- 2. Compare A and AAAA. After this step, check the public value tied to compare a and aaaa before changing another unrelated setting.
- 3. Update stale values. After this step, check the public value tied to update stale values before changing another unrelated setting.
- 4. Wait according to TTL then retest. After this step, check the public value tied to wait according to ttl then retest before changing another unrelated setting.
Why this order matters for hostinger
The sequence begins with the provider/authority decision, then moves through confirm current hosting IP, compare A and AAAA, update stale values. That keeps the change scoped to the failed DNS resolution and delegation path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Hostinger domain points to old website
Authoritative DNS should publish the intended record and independent resolvers should converge on that answer as their previous cached TTLs expire. Compare the same confirm current hosting IP and compare A and AAAA 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 confirm current hosting IP 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 domain points to old website 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.