Network

Read a saved DNS answer after changing an address

·

Inspect the status, record types, values and TTLs in a saved DNS-over-HTTPS JSON response. The records come from your pasted report.

DNS response reader

Identify the answer in a saved response

Paste the JSON response in the table. Status 0 indicates that the query completed without a DNS error.

Type 1 identifies an IPv4 A record. The answer associates example.org. with 192.0.2.1 for the reported TTL.

Identify the answer in a saved response
ExampleExpected result
{"Status":0,"Answer":[{"name":"example.org.","type":1,"TTL":60,"data":"192.0.2.1"}]}Status 0 · example.org. · A · TTL 60 · 192.0.2.1

What DNS TTL means after a record change

TTL expresses a cache lifetime in seconds. A recursive resolver may return the remaining lifetime of information it has cached, so two responses can show different TTLs for otherwise identical data. The returned number is not a countdown to the moment every resolver worldwide will use your new value.

RFC 2181, section 8: Time to liveRFC 2308: Negative caching of DNS queriesRFC 8767: Serving stale DNS data

Compare recordings from the same query

Save the query name, requested type, resolver and capture time with each response. If yesterday’s A record differs from today’s AAAA record, the two values describe different address families.

For a change investigation, compare the same name and type across captures and keep the resolver identities visible.

Frequently asked questions

Why can status 0 have an empty Answer list?

The query can complete without finding data of the requested type. Review the original question and authority section before concluding that the name does not exist.

Can a saved response prove every resolver has updated?

It describes one response at its capture time. Collect comparable observations if you need to investigate a change across resolvers.

Sources and further reading

Put it into practice.

Related guides