> For the complete documentation index, see [llms.txt](https://support.agentfire.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.agentfire.com/launch/redirects-and-dns-management/articles-1505029-what-factors-affect-dns-propagation-time.md).

# How Long DNS Changes Take (and Why)

Why DNS changes don't show up everywhere at once, how long they usually take, and what to check before waiting it out.

When a DNS change is made, like pointing your domain to your new AgentFire website or adding a record for your email, it doesn't show up for everyone at the same moment. The time it takes is called **propagation**.

## Why it takes time

Internet providers and devices save (cache) DNS answers for a while, so they don't have to look them up every time. Until their saved copy expires, they keep showing the old answer. That's why you might still see your old website while we, or a friend in another city, already see the new one.

How long a saved copy lasts depends on the record's **TTL** (time to live), a setting on each record. See Cloudflare's [explanation of TTL](https://developers.cloudflare.com/dns/manage-dns-records/reference/ttl/).

## How long it usually takes

| Change                                                                             | Usual time                            |
| ---------------------------------------------------------------------------------- | ------------------------------------- |
| Adding or changing a record (for example for email, a subdomain or a verification) | Usually minutes to a few hours        |
| Changing your domain's nameservers                                                 | Often a few hours, and up to 48 hours |

These are typical times, not guarantees. Some providers hold on to old answers longer.

## Check before you wait

Waiting only helps if the change was made correctly. If it's been more than a few hours:

* **Moving your website to AgentFire?** Log in to your registrar and check that the nameservers match exactly the ones we sent you, with no extra or old ones left. See [How to Change Your Nameservers in GoDaddy](/launch/nameservers-and-access/articles-5081746-how-to-change-nameservers-using-godaddy.md) for an example.
* **Waiting on a record?** Email <support@agentfire.com> and ask us to confirm the record is in place. See [How to Add or Change DNS Records on Your Domain](/launch/redirects-and-dns-management/how-to-add-or-change-dns-records.md).

## Common Questions

<details>

<summary>Support says my new website is live, but I still see the old one.</summary>

If your nameservers are right, your device or internet provider still has the old answer saved. Open your website in a private or incognito window, or on your phone using mobile data instead of Wi-Fi. If you still see the old site after 48 hours, email <support@agentfire.com>.

</details>

<details>

<summary>My email or CRM provider still says a record is missing.</summary>

First ask us to confirm the record was added exactly as your provider gave it. If it's there, wait a little and click **Verify** again in your provider's settings. Their check can lag behind the change.

</details>

<details>

<summary>My website or login says it doesn't exist.</summary>

Check your nameservers before waiting. Waiting won't fix wrong or extra nameservers.

</details>

<details>

<summary>Can you make the change show up faster?</summary>

Not for everyone at once. Once a change is made, each provider picks it up when its saved copy expires.

</details>

<details>

<summary>I moved my domain away from AgentFire. Why do I still see the old site?</summary>

Once your nameservers point somewhere else, your new provider controls your DNS. Give it time to update. If it still shows the old site after 48 hours, check the settings with your new provider.

</details>