I would like to see the Time-To-Live (TTL) value for a CNAME record.

I have access to dig (on Apple Mac OS X), which gives me an answer like this:

% dig host.example.gov
host.example.gov.       43200   IN  CNAME   host1.example.gov.
host1.example.gov.      43200   IN  A

Is the value '43200' the TTL for this DNS record?

4 Answers 4


Yes, the number there is the number of seconds left until that record expires (providing we're not querying the authoritative nameserver). Obviously with a CNAME there's a level of redirection, so the TTL for the A record it points to in this case may be important as well.

If you wait a couple of seconds and run dig again on your local nameserver, you should see that TTL number decrease by the number of seconds you waited (approximately). When it hits 0, it'll refresh or if your nameserver refreshes the zone for some reason.

As mentioned above, there is a difference between dig being run against a nameserver with a cached entry and the nameserver that is authoritative for that entry.

(in the examples I use below I use the +noauthority +noquestion & +nostats flags just to keep the output terse).

Note the difference between the following queries:

$ dig +noauthority +noquestion +nostats stackoverflow.com @ns2.p19.dynect.net.

; <<>> DiG 9.7.0-P1 <<>> +noauthority +noquestion +nostats stackoverflow.com @ns2.p19.dynect.net.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50066
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; WARNING: recursion requested but not available

stackoverflow.com.  432000  IN  A

So in the above query, we're querying a nameserver that is authoritative for stackoverflow.com. If you notice the flags section, pay special attention to the aa flag which denotes this is an authoritative answer (i.e. not cached).

$ dig +noauthority +noquestion +noadditional +nostats stackoverflow.com 

; <<>> DiG 9.7.0-P1 <<>> +noauthority +noquestion +noadditional +nostats stackoverflow.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43514
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

stackoverflow.com.  246696  IN  A

In the above query, we don't have an aa flag, and the TTL will keep decreasing as we query and query. This is essentially the counter I was talking about previously.

  • In the second example the TTL of 246696 means that the nameserver (which returned the address of fetched the answer from its cache and it'll do so for another 246696 seconds, right? After which it'll reach out to the authoritative nameserver or to another non-authoritive one and cache the results got from there, right? Thanks for the clarification. Having a hard time with this one. Oct 16, 2020 at 20:58

If you happen to be stuck on a windows box and only have access to nslookup:

nslookup -qa=A -debug host.example.com authoritiative-dns-host-here.com
  • And if you happen to try using WSL, you might get a TTL of 0. In which case, you'll need to use the above. Apr 11, 2023 at 13:23

Is the value '43200' the TTL for this DNS record?

Yes - as reported to you by the server that answered your query (if you're asking a caching server it will return the remaining time in its cache).

To see the TTL set on the actual record query the authoritative nameserver (dig @some.dns.server host.example.gov - The authoritative DNS servers will be listed in the Authority section of the dig output)

Quick check to see if you're asking the authoritative NS: If you run dig again and the TTL changes you're probably hitting a cache. If it stays the same you're probably asking the authoritative server (or one that has broken caching).

  • 1
    if ttl doesn't change it could just be one that believes itself to be authoritative: the domain owner may have changed DNS server without shuttiong the old one down.... had that problem last month.
    – Jasen
    Jul 12, 2015 at 23:29
  • 2
    @Jasen Yes, that's definitely possible (It indicates something important as well: The DNS admin will be buying drinks at the next company outing for screwing up the migration!)
    – voretaq7
    Jul 13, 2015 at 15:26

I couldn't see the authoritative servers in the default dig output, but the following

dig +nssearch host.example.com

returned them, which could then be used as described by voretaq7 to get the actual TTL value for the record.

Update: kept forgetting how to do this and having to come back, so wrote a little script to first fetch the authoritative nameserver then dig using it


        echo Usage $0 domain

if [ -z "$1" ]; then
        exit 1

APEX_DOMAIN=`echo $DOMAIN | sed 's/\(.*\.\)\([^.]*\.[^.]*\)/\2/'`
FIRST_AUTHORITATIVE_NS=$(dig +nssearch $APEX_DOMAIN | awk '$1=="SOA"{sub(".$","",$2);print $2;exit;}')

echo Using authoritative nameserver $FIRST_AUTHORITATIVE_NS


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .