Resolvers temporarily retain DNS responses according to the TTL. As a result, a change may not be visible everywhere immediately.
Step-by-step guide
- Open DNS management for the relevant domain name.
- Compare the current records with the values that are actually required.
- Check IPv4, IPv6 and email records where applicable.
- Save only the necessary corrections.
- Test again using an external DNS resolver and allow for the TTL.
Which value should you enter?
| Record type | DNS |
| Value | depending on the situation |
| TTL | Use the default value unless a provider specifies otherwise. |
What should you consider?
- Check whether the change is present on the authoritative name servers.
- Compare responses from different resolvers.
- Wait at least for the old TTL to expire before concluding that something is not working.
DNS changes take time
After saving, an old value may temporarily remain in cache. Therefore, check not only in your browser but also with an external DNS checker.
Frequently asked questions
When will a DNS change become visible?
This depends on the TTL and provider caches. The change is often visible within a few minutes, but old responses may be retained for longer.
Can I undo a DNS change?
Yes. Restore the previous value and save again. This correction may also temporarily be affected by DNS cache.
Do I need to change the TTL?
Usually not. For a planned migration, you can lower the TTL in advance so later changes are retrieved more quickly.
Still need help?
Email support@mosthosted.com and include your domain name, the required record and the value.