Before connecting to a service by name, a client may ask DNS for an address. A resolver can record the question and its result. A resolver looks up names for clients.
Network Monitoring · Lesson 3
DNS Logs
Learn to distinguish a DNS question, its answer, and a later application connection.
Identifying the Question
A DNS record can contain the time, client address, name, and requested record type. An A query asks for an IPv4 address.
09:21:00Z client=192.0.2.10 query=site.example type=A result=NOERROR answer=192.0.2.20
09:21:03Z client=192.0.2.10 query=preview.example type=A result=NXDOMAIN
The first result contains an address for site.example. The second reports that DNS found no name matching preview.example in this lookup.
Which row returned an IPv4 address for the requested name?
Reading the Outcome
NOERROR means the DNS exchange did not report a protocol error. Check the answer field too. A response can use NOERROR and contain no address record of the type requested. A failed lookup may also appear as a different result, such as a timeout recorded by the client.
A DNS row says NOERROR but has no address answer. What should you report?
Following the Connection Separately
A client can look up a name and then choose to make a connection. To test whether that happened, find a matching flow or connection record. Compare the endpoint and time. DNS results may be cached, so some connections occur without a fresh lookup in the available logs.
What would best show that a client later connected to the returned address?
Lesson complete
You finished DNS Logs
You can now read a DNS log without confusing it with later network activity.
Find the client, question, and requested record type.
Interpret the result and answer together.
Look for a separate record of a later connection.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account