After you change nameservers or DNS records, the result is not visible everywhere immediately. This is normal: DNS information is cached by resolvers (your ISP, office network, mobile operator) and by your device.
What typically changes “slowly”
- Nameserver change at the registrar (for example to
ns1.garmtech.com, ns2.garmtech.com, ns3.garmtech.com).
- DNS record change (A/CNAME/MX/TXT) for a domain that already uses GARMTECH nameservers.
How long does propagation take?
- Most changes are visible in minutes to a few hours.
- In some networks it can take up to 24 hours (occasionally longer) due to caching and TTL values.
Tip: Nameserver changes usually take longer than editing a single DNS record.
How to check what the Internet currently sees
- Check your source of truth:
- If the domain uses GARMTECH nameservers, check the DNS zone in Plesk: Websites & Domains → DNS Settings.
- If the domain does not use GARMTECH nameservers, check DNS where your nameservers point (your external DNS provider or registrar DNS).
- Check nameservers (NS) from any computer:
nslookup -type=ns example.com
dig NS example.com +short
- Check a specific record (example A-record):
nslookup example.com
dig A example.com +short
- Compare from different networks (mobile data vs Wi‑Fi). If one shows the new data and the other doesn’t, you are seeing cache differences.
Common issues and fixes
- Old website still opens: clear your browser cache and test in an incognito/private window.
- Wrong server shown in email or website checks: confirm that the domain’s NS records are exactly
ns1.garmtech.com, ns2.garmtech.com, ns3.garmtech.com (if you intended to use GARMTECH DNS).
- “DNS_PROBE_FINISHED” errors: flush local DNS cache and restart the router (home routers sometimes cache DNS too).
- You changed records in Plesk but nothing changes: ensure the domain really uses GARMTECH nameservers. If nameservers point elsewhere, Plesk DNS edits are not used on the Internet.
Good practice for planned DNS changes
- Lower the TTL 24 hours before the change (for example to 300 seconds), then change the record, and later return TTL to normal.
- Keep the old service working for a short period if possible (useful for website migrations).
