# Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation")

**Code:** `Domain still resolves to the old IP (DNS propagation/cache)` · **Category:** Networking · **Seen on:** Linux, Windows, Networking

You updated a DNS record, but resolvers and devices keep serving the old answer until its TTL expires.

## Meaning

There's no real propagation: each resolver caches the old record for the previous TTL. Query the authoritative server directly (`dig @ns1.provider.com example.com`) to confirm the change, lower the TTL before planned migrations, flush local caches (`ipconfig /flushdns`, `resolvectl flush-caches`) and wait out the TTL.

## Common causes

- High TTL on the old record
- Resolver or ISP cache
- OS or browser DNS cache
- Changed the record in the wrong zone/nameserver
- Negative caching of an earlier NXDOMAIN

## Quick fix

1. Check authoritative: `dig @ns1.provider.com example.com A +short`
2. Flush local DNS caches
3. Lower the TTL (300 s) a day before migrations

## Detailed fix by platform

### Linux

1. 

```bash
dig @ns1.provider.com example.com A +noall +answer
sudo resolvectl flush-caches
```


## How to diagnose

1. **Authoritative answer** — New IP?
2. **TTL** — Remaining?
3. **Local cache** — Flushed?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/networking/dns-old-record-propagation-cache)