A DNS change can be correct while a browser, network resolver or previous record remains cached. Website caching can create a similar symptom.

What to do

  1. Verify that you changed the records at the authoritative DNS provider rather than an unused zone.
  2. Check the exact hostname, including www, and confirm any old AAAA record is not routing visitors elsewhere.
  3. Compare from another network or device. Test in a private browser window to distinguish browser content cache from DNS behavior.
  4. Keep the previous host running until the agreed migration checks are complete. If the behavior persists, send JIJ the hostname, change time, expected destination and a screenshot.

Good to know

Propagation time depends on prior TTLs and resolver caching. There is no guaranteed universal completion time.

Related help

Reviewed October 18, 2026. Need help? Contact JIJ support.

Was this answer helpful? 0 Users Found This Useful (0 Votes)

Most Popular Articles

Before changing nameservers or DNS

DNS controls where your domain’s website and email are delivered. Changing nameservers can move...
Understand A, AAAA, CNAME, MX and TXT records

Each DNS record has a purpose. Edit records at the provider hosting your authoritative DNS; a...
Prepare for a domain transfer

Transferring a domain registration and moving a website are separate operations. A registration...
Keep Google Workspace or Microsoft 365 email when moving a website

You can host your website with JIJ while another provider handles your domain email. The website...

Powered by WHMCompleteSolution