What is DNS and what does it do?
DNS (Domain Name System) translates human-readable domain names into the IP addresses machines use. When someone types a domain into the address bar, that translation has to finish before any connection can be made.
That makes DNS an invisible dependency almost everything relies on. Servers can be up, the link healthy and the application running; if resolution fails, the service is down as far as the user is concerned.
- 1
Browser / application
- 2
Resolver
- 3
Root and TLD servers
- 4
Authoritative name server
- 5
IP address returned
If any step in the chain slows down, the user experiences it as 'the site won't load'.
How a domain name is resolved
Resolution is not a single question to a single server. The request first goes to a resolver; if the answer is not cached, a chain is followed from the root servers down to the domain's authoritative name server.
Every link in that chain is a separate failure point. The cache lifetime (TTL) decides how long a record is kept, which is why a DNS change never reaches everyone at the same moment.
- A / AAAA: the domain's IPv4 and IPv6 addresses
- CNAME: one name pointing at another
- MX: where email traffic should be delivered
- TXT: verification and policy records
- NS: the domain's authoritative name servers
How DNS problems show up in the field
DNS issues are rarely reported as DNS issues. What reaches the team is usually 'the site won't open', 'the app won't log in' or 'email isn't going out'.
The most misleading case is partial breakage: one location resolves and another does not, because each uses a different resolver. Inspecting the server there wastes time; the first place to look is resolution itself.
- A service that opens for some users and not others
- Pages that load slowly but eventually arrive: resolution delay
- Mixed behaviour after a record change: the TTL has not expired
- Email delivery problems: an MX or TXT record error
How DNS resolution is monitored
Meaningful DNS monitoring does not stop at pinging the name server. The real question is whether this domain returns the expected answer within an acceptable time.
In Sentry, domain and certificate tracking is configured for exactly this; resolution and reachability checks are read together. Managing or changing records is out of scope — the product reads state and reports it.
- Regularly checking whether resolution succeeds
- Watching response time and its trend
- Comparing the returned result with the expected address
- Tracking the domain expiry date separately