Dig output looks dense at first because it shows both the DNS answer and the metadata around the query. Once you know the sections, it becomes one of the clearest ways to diagnose DNS.
The answer section
The answer section is the main result. For most support work, this is the first section to read.
example.com. 300 IN A 93.184.216.34| Field | Example | Meaning |
|---|---|---|
| Name | example.com. | The queried DNS name. |
| TTL | 300 | How long the answer may be cached. |
| Class | IN | Internet DNS class. |
| Type | A | Record type. |
| Data | 93.184.216.34 | The returned value. |
The status code
NOERROR: the query completed. The answer may still be empty if the name exists but that record type does not.NXDOMAIN: the queried name does not exist according to DNS.SERVFAIL: the resolver could not complete the query. DNSSEC, delegation, or name server problems are common causes.REFUSED: the server refused to answer that query.
Authority and additional sections
The authority section can show which name servers are responsible for a zone. The additional section can include helper records, such as IP addresses for name servers. These sections are most useful when debugging delegation.
Query time
Query time is not a website speed test. It only measures how long the DNS answer took for that query. A slow query can point to an unresponsive resolver or name server, but it does not measure the web application.