host — Compact DNS Lookups
host is the most concise of the DNS lookup tools. It prints one readable line per answer instead of a structured protocol dump, which makes it the right choice when you are looking at many names rather than examining one closely. Given a hostname it returns addresses and mail servers; given an address it performs the reverse lookup; and its brevity means the output of a hundred invocations is still something a human can scan.
Why run it
Reach for host when the question is breadth rather than depth. Auditing which of your subdomains still resolve, confirming a reverse record matches the forward one, checking whether a batch of names all point at the load balancer you just migrated to — these are cases where dig's detail becomes an obstacle. It is also the friendliest tool for the reverse direction, where the question is not "what does this name point at" but "what claims to own this address".
Why automate it
Breadth is exactly what does not survive being done manually. Nobody audits two hundred subdomains by hand twice, and the ones that quietly stop resolving are the ones nobody was looking at — a decommissioned host whose record survives it, a forgotten name that now resolves into someone else's infrastructure. Automating a sweep across every name you own turns a task nobody repeats into a background check, and the interesting result is always the entry that changed since last time.
What it gives you
Wide, cheap coverage of the names you own. host is the tool that makes "check all of them" practical rather than aspirational, and that distinction matters because the record that breaks is never the one you would have thought to verify. Applied across a whole zone on a schedule, it is how the forgotten name gets found while it is still a tidy-up rather than an incident.