Start for free – your first 3 months are freeSee the offer

DNS and name servers

TTL and waiting time: why DNS changes do not work straight away

Understand TTL and how long it takes before a changed DNS record or new name servers take effect – and what you can do yourself to speed it up.

3 min readUpdated

On this page
  1. How long does it take?
  2. Choose a TTL
  3. Still seeing the old page?
  4. Frequently asked questions
  5. Can Sitewig make it faster?
  6. Why does it work for me but not for my colleague?
  7. When should I contact support?

When you save a DNS change at Sitewig, it reaches our name servers within a few minutes. Even so, it can take longer before everyone sees it. The reason is TTL (time to live): the time others may remember the old answer before they ask again.

The answer is remembered in the browser, router and at the internet provider, and a timeline with a TTL of 1 hour
With a TTL of 1 hour, some people may see the old answer for up to an hour

How long does it take?

ChangeTypical waiting time
New record on a name that did not exist beforeA few minutes
Changed or deleted recordA few minutes + up to the old TTL (default 1 hour)
New target with Change targetA few minutes + up to the old TTL
New name servers at the registrarUp to 24 hours. Sitewig checks automatically every hour

Name server changes take longest because the registry for the extension (e.g. .dk or .com) also has a waiting time, which neither you nor Sitewig can change.

Choose a TTL

You choose the TTL in the Add record or Edit DNS record panel. The options are 10 minutes, 30 minutes, 1 hour, 4 hours, 12 hours and 24 hours. The default is 1 hour, which suits most people. In the DNS table, TTL is shown in seconds, e.g. 3600 s for 1 hour.

Still seeing the old page?

  1. Step 1: Clear your own cache

    Reload the page with a hard refresh, try a private window, or close and reopen the browser.

  2. Step 2: Try another network

    Turn off wifi on your phone and use mobile data. If it works there, only your own network is remembering the old answer. Restart the router if need be.

  3. Step 3: Wait out the old TTL

    If the old TTL was 1 hour, wait an hour from the change. For name server changes it can take up to 24 hours.

  4. Step 4: Check the status at Sitewig

    Open the domain under Domains → My domains. The banner at the top and the Timeline card show whether anything is missing. See Troubleshooting.

Frequently asked questions

Can Sitewig make it faster?

Our name servers have the change after a few minutes. The rest depends on how long others are allowed to remember the old answer – which is why lowering the TTL well in advance helps.

Why does it work for me but not for my colleague?

You are using different networks or devices that asked at different times. Once the TTL has expired, everyone sees the same thing.

When should I contact support?

If more than 24 hours have passed after a name server change, or more than the old TTL after a record change, and the banner on the domain page still shows an error.

Read about domains at Sitewig

Didn't find the answer?

Reply within 1 working day · Mon–Fri 8:00–17:00 CET