All DNS Records — Everything a Domain Publishes
This is the wide-angle view: rather than asking for one record type, it enumerates everything a domain publishes — addresses, mail routing, nameservers, aliases, certificate authority authorisations and the growing pile of text records that now carry security and mail policy. Modern domains publish far more than their owners remember, and seeing the whole set at once is usually a mildly surprising experience.
Why run it
Two situations make this essential. The first is inheriting a domain, where the only reliable documentation is the zone itself. The second is a security review, because text records are where verification tokens accumulate: every service that ever asked you to prove domain ownership left one behind, and most were never cleaned up. Those tokens are a map of which third-party services have or once had a relationship with your domain, which is useful to you and equally useful to anyone enumerating your attack surface.
Why automate it
Records get added far more often than they get removed, and additions come from people outside whatever process you think governs DNS — a marketing team verifying a new tool, a contractor setting up a service. A scheduled enumeration diffed against the previous run tells you what appeared, which is the only practical way to keep a zone from silently accumulating a decade of debris. It also catches the case that matters most: a record you did not add and cannot explain.
What it gives you
A complete, current inventory of what your domain tells the world. Run once it is a clean-up list; run continuously it is change detection on the part of your infrastructure most likely to be edited by someone you have never met.