Following a DNS lookup
Every connection to a named server starts with DNS. This capture shows a successful lookup, a misspelled name, and a lookup answered from the resolver's cache.
-
The question
The laptop asks for the A record of api.shop.example. A records hold IPv4 addresses.
Think about it: Which transport protocol does this DNS query use?
UDP, to port 53. DNS queries are small, so UDP's speed wins.
-
The answer
The resolver answers in 21 ms with the address and a time to live, which says how long the answer can be cached.
-
A small typo
Two seconds later the laptop asks for api.shpo.example. Notice the swapped letters.
-
That name doesn't exist
The resolver answers NXDOMAIN: no such name. The app that asked will show an error, often a vague one.
Think about it: Where would you look to fix this?
In whatever setting or link contains the misspelled name. The network itself is fine.
-
Faster the second time
The correct name is asked again and answered in 2 ms, because the resolver kept the earlier answer in its cache.