Understand DNS propagation and TTL on OneNet Servers
Applies to: Nameserver changes and DNS record updates for domains that use OneNet Servers or any external DNS authority.
DNS changes do not appear everywhere at the same moment. The delay is usually not a fault in OneNet Servers. It is the normal effect of caches, TTL values, and registry or resolver update timing.
Before you start
- Know whether you changed nameservers or only a DNS record.
Steps on OneNet Servers
- Check what you actually changed: nameservers, an A record, an MX record, or another record type.
- Allow time for resolvers and browsers to stop serving the old cached answer.
- If you are planning a major DNS move, lower the TTL before the change whenever you can do that safely.
- Use more than one network or DNS lookup tool before you decide the change failed.
What you should see next
- Small record changes can appear quickly in some places while other resolvers still show the old answer.
- Nameserver changes often feel slower than normal record edits because more layers are involved.
Common issues
- A local browser or device can show the old result even when the new result is already live elsewhere.
- External DNS providers, registries, and recursive resolvers all cache differently, so two people can see different answers at the same time.
What affects propagation most
- The TTL value on the old record.
- Resolver cache behaviour on the network you are using.
- Whether you changed a record inside the same DNS authority or moved the nameservers entirely.
Next steps on OneNet Servers
When to contact support: Contact support if the change was made correctly and still shows no sign of moving after a reasonable propagation window for the record type involved.
