← Back to Learning Hub

DNS Records • Intermediate • 6 min read

How to Find a DNS Record's TTL (Current Value)

Find the TTL currently set on a DNS record: read the TTL column in dig and nslookup, tell the authoritative TTL from a resolver's countdown, and confirm a change.

The TTL (time to live) on a DNS record is just a number of seconds, and finding the value currently set on a record is a mechanical task: look it up and read the right column. The catch is that there are two different TTLs you can see for the same record. One is the authoritative TTL, the value actually configured in your zone, which you get by asking the nameservers that own the record. The other is the countdown TTL that a recursive resolver reports, which is whatever is left on its cached copy and keeps shrinking toward zero. Confusing the two is the most common reason people think a TTL change has not taken effect when it has. This guide shows how to read the TTL in dig and nslookup, how to be sure you are reading the authoritative value, and how to confirm a lowered TTL is live before a migration.

Where the TTL appears in a lookup

In dig, the TTL is the integer column in the answer section, sitting between the record name and its class. Run a plain query and read that number:

$ dig example.com A

;; ANSWER SECTION:
example.com.    3600    IN  A   203.0.113.10

Here the TTL is 3600, meaning one hour. The columns are name, TTL, class (IN), type (A), and value. To cut the noise and see only the answer line, use the short form:

$ dig example.com A +noall +answer
example.com.    3600    IN  A   203.0.113.10

Every record type works the same way. Ask for the type you care about, whether that is MX, TXT, CNAME, or NS, and read the second column. Each record set carries its own TTL, so the A record and the MX record on the same name can differ.

Authoritative TTL versus the resolver countdown

This is the part that trips people up. When you query a public recursive resolver such as 8.8.8.8, the TTL it returns is not the configured value, it is the time remaining on the copy that resolver cached. Query it again a few seconds later and the number is lower:

$ dig example.com A @8.8.8.8 +noall +answer
example.com.    1784    IN  A   203.0.113.10

$ dig example.com A @8.8.8.8 +noall +answer
example.com.    1771    IN  A   203.0.113.10

That descending number (1784, then 1771) is a countdown, not the real TTL. When it hits zero the resolver discards the cached copy and fetches a fresh one, at which point the number jumps back up to the full configured value. To read the actual TTL set in the zone, ask an authoritative nameserver for the domain directly, because an authoritative server always returns the full configured value and never a countdown:

$ dig example.com NS +short
ns1.yourhost.com.
ns2.yourhost.com.

$ dig example.com A @ns1.yourhost.com +noall +answer
example.com.    300     IN  A   203.0.113.10

In this example the authoritative TTL is 300 (five minutes), even though a recursive resolver might show any number up to 300 depending on how long ago it cached the record. The rule is simple: a steady number that does not shrink on repeat queries is the authoritative TTL; a number that counts down is a resolver's cache.

SignalAuthoritative TTLResolver countdown TTL
Source queriedThe zone's own nameserverA recursive resolver
Behavior on repeat queriesStays the sameDecreases each time
What it tells youThe value configured in the zoneTime left before the cache refreshes
Use it toConfirm the real settingJudge how long a cached copy survives

Reading the TTL on Windows with nslookup

Plain nslookup hides the TTL, so turn on debug output to reveal it. The TTL appears on its own line in the record detail:

> nslookup -debug -type=a example.com
...
    ANSWERS:
    ->  example.com
        internet address = 203.0.113.10
        ttl = 300 (5 mins)

As with dig, if you point nslookup at a recursive resolver you get the cached countdown. Set the server to an authoritative nameserver first with server ns1.yourhost.com to read the configured value.

Confirming a lowered TTL before a migration

The usual reason to check a TTL is to lower it ahead of a move so cached copies expire quickly and the real cutover propagates in minutes. Lowering the TTL is itself subject to the old TTL: resolvers that cached the record under the old, higher value keep serving it until that old value expires. So there is a specific sequence to confirm the change is truly in effect everywhere.

  1. Change the TTL in your zone, for example from 3600 to 300.
  2. Query an authoritative nameserver directly and confirm it now returns 300. This proves the new value is live at the source.
  3. Wait at least the old TTL (3600 seconds here) so every resolver's cached copy under the old value has expired.
  4. Query public resolvers in several regions. Once they refetch, their countdown ceiling is now 300, confirming the lower TTL has taken hold.
  5. Only then schedule the record change itself, knowing it will propagate within the new short TTL.

The Valla DNS lookup tool queries authoritative servers and surfaces the configured TTL for each record type, so you can read the real value without untangling a resolver's countdown by hand. That makes it easy to confirm a lowered TTL is live at the source before you rely on it for a cutover.

Frequently asked questions

How do I find the current TTL on a DNS record?

Run dig example.com A +noall +answer and read the number between the record name and the class; that is the TTL in seconds. For the true configured value rather than a cached copy, direct the query at one of the domain's authoritative nameservers.

Why does the TTL change every time I check it?

You are querying a recursive resolver, which reports the time remaining on its cached copy. That number counts down until the cache expires, then resets to the full value. Query an authoritative nameserver instead to see the steady, configured TTL.

How do I read the authoritative TTL rather than a cached one?

Find the domain's nameservers with dig example.com NS +short, then query one of them directly, for example dig example.com A @ns1.yourhost.com. An authoritative server always returns the full configured TTL, never a countdown.

Does nslookup show the TTL?

Not by default. Add the debug flag, as in nslookup -debug -type=a example.com, and the TTL appears on its own line in the record detail. Point it at an authoritative server first if you want the configured value.

How do I know a lowered TTL has actually taken effect?

Confirm the authoritative server returns the new lower value, then wait at least the length of the old TTL so cached copies under the old value expire. After that, public resolvers will refetch and cap their countdown at the new value, which confirms the change has propagated.

Planning a migration? Read the real configured TTL per record type with the Valla DNS lookup tool before you lower it, so your cutover lands inside the window you expect.

Troubleshooting box

If results look inconsistent, compare authoritative nameservers first, then recursive resolvers by region. Capture snapshots every 10 minutes for deterministic incident timelines.

Try VallaDNS free →

Intermediate • 7 min

How to Check If Nameservers Have Propagated

Nameserver changes live at the parent TLD and follow the registry NS TTL, not your zone. Check the parent delegation and confirm the new NS set worldwide.