PTR records are opt-in, not universal

Forward DNS (a hostname pointing to an IP) is set up by whoever controls the domain, but reverse DNS (an IP pointing back to a hostname via a PTR record) has to be configured by whoever controls that IP's allocation — typically the hosting provider or ISP, not the domain owner. That means a huge number of IPs, especially residential and many cloud provider ranges, simply have no PTR record configured at all, and a blank result here is the normal, expected outcome for those rather than a sign anything is broken. Mail servers care about this a lot — many spam filters treat a missing or mismatched PTR record on a sending IP as a strong signal — which is part of why reverse DNS matters more for mail infrastructure than for most other services.

The everyday use case: labeling a log full of bare IPs

Access logs, firewall logs, and connection records are typically full of raw IP addresses with no indication of what they are — turning `203.0.113.7` into a recognizable hostname (a known scanner, a cloud provider's reverse DNS block, an ISP's customer range) is often the fastest way to triage a list of IPs without cross-referencing each one individually against an external lookup service. For the common case of checking a handful of IPs pulled from a log while investigating something, this is meant to be faster than opening a terminal and running `dig -x` in a loop.