Query Analytics Reporting
Most client queries are going to be for A or AAAA and not for other records because the client device just knows it wants to connect to an IP address so it can find that via an A query, or a AAAA query.
You should always expect to see more A and/or AAAA queries for most other records because a client usually has no way of knowing that something is a specific DNS record until it asks for something else (like an "A" or an "MX") first.
The authoritative DNS will push out the other records in response to an "A" or "AAAA" (or any other RRtype, as other records conflict with every other rrtype) and then recursive will continue querying the hostnames in the DNS record chain until it arrives it's final answer of an "A" record (or "AAAA" if it was a AAAA query).
The AAAA queries often are part of refreshing the cache for A or alias records. Modern operating systems and devices will first check for the existence of AAAA records. If none are found, they will re-query for A records. This behavior started with Vista and spread to everything in 2024.
If hostnames are randomized then the query is probably from Chromium (browser or Android devices) performing security checks against your DNS.
Why would the client would only be chasing the A or AAAA record vs. the other records?
Think of DNS records as just redirections. It directs to a different DNS record. An A record is an actual destination, though. as It points to an IP address. Most DNS records will eventually lead you back to an IP address as that is how computers identify each other. While all CNAMES should always be a subdomain, A records can also be subdomains. So while there is nothing on the surface that can tell you subdomain.exampledomain.com is a CNAME, a forward, or an A record it is very easy to assume there is going to be an A record somewhere along the chain of records as - at some point - you will eventually end up at an IP address somewhere along the way.
If you are attempting to determine how records are being routed, chasing down the A record just provides more useful data. If you look at your use case, you can see how the query was eventually routed to an IP address.
The only way to decrease the number of these queries is extending TTLs. Non-existent hostnames (NXDOMAIN) are cached for the duration of a domains SOA min cache or TTL value (whichever is shorter).