DNS
Why DNS changes are not visible
DNS changes may take time because of cache, TTL, the wrong zone, inactive changes or incorrect records. Saving is not always the same as publishing.
Reviewed:
It is not always instant
A DNS change can be correct and still not visible from your computer yet.
DNS is cached in many places. Some users may see the change before others.
Common causes
If you do not see the change, it may be due to:
- DNS cache;
- TTL still active;
- change made in a DNS zone that is not active;
- record name or value written incorrectly;
- change saved but not activated;
- browser or local network using old information.
At PRIMARI.NET
At PRIMARI.NET, after editing primary DNS, press Activate changes.
If you only save a record but do not activate changes, the configuration is not published to DNS servers.
What to check
Check that the domain uses the DNS you are editing, that the record name is correct and that the change has been activated.
You can also wait a while and test from another connection.
When to contact PRIMARI.NET
Contact PRIMARI.NET if the change is still not visible after waiting, if you do not know which DNS zone is active or if the change affects production email or web.