Learn / Field guide

DNS: how names become addresses

The Domain Name System turns names like example.com into IP addresses. Almost every connection starts with a DNS question, so DNS problems often look like the whole internet is broken.

31 DNS fields, explained

Field names are the ones Wireshark and TShark use, so you can search for them or use them in display filters.

dns.id

Transaction ID, used to match an answer to its question.

dns.flags

Says whether this is a question or an answer, and whether it worked.

dns.flags.response

Whether this message is a question (query) or an answer (response).

dns.flags.rcode

The result of the lookup.

Why it matters: NOERROR means success, NXDOMAIN means the name doesn't exist, and SERVFAIL means the server couldn't answer.

dns.count.queries

How many questions are in this message. Almost always 1.

dns.count.answers

How many answers are included.

Why it matters: Zero answers with NOERROR means the name exists but has no record of that type.

dns.count.auth_rr

Records that point to the servers responsible for the name.

dns.count.add_rr

Extra records the server chose to include.

dns.qry.name

The name being looked up.

Why it matters: Misspelled or unexpected names here often explain connection problems.

dns.qry.type

What kind of record is wanted. A is an IPv4 address; AAAA is IPv6.

dns.qry.class

The record class. Almost always IN (internet).

dns.a

An IPv4 address returned for the name.

Why it matters: This is the address your device will connect to next.

dns.resp.ttl

How long this answer may be cached before asking again.

dns.qry.name.len

The length of the queried name.

dns.count.labels

How many parts the name has, separated by dots.

dns.response_to

Which query packet this answer belongs to.

Why it matters: Generated by Wireshark by matching transaction IDs.

dns.time

How long the answer took, from query to response.

Why it matters: Answers over a few hundred milliseconds make everything that needs the name start late.

dns.resp.name

The name this answer is for.

dns.resp.type

The kind of record in this answer, such as A for an IPv4 address.

dns.resp.class

The record class. Almost always IN (internet).

dns.resp.len

The length of the answer's data.

dns.cname

An alias: the name points to another name, which is looked up next.

Why it matters: Content delivery networks use aliases heavily.

dns.aaaa

An IPv6 address returned for the name.

dns.flags.opcode

The kind of request. Almost always a standard query.

dns.flags.authoritative

Whether the answer comes from a server responsible for the name, not a cache.

dns.flags.truncated

Whether the answer was cut short and should be retried over TCP.

dns.flags.recdesired

The client asks the server to do the full lookup on its behalf.

dns.flags.recavail

The server is willing to do full lookups for clients.

dns.flags.z

A reserved bit that must be zero.

dns.flags.authenticated

Whether the server checked the answer with DNSSEC.

dns.flags.checkdisable

Whether the client asked to skip DNSSEC checking.