A record, in the sense that matters to a demand for production, is an inscription: a writing that survived the moment of the event it concerns. An event and an inscription are not the same kind of thing. A packet answered and discarded is an event. Memory of that packet, once gone, is not a document. The distinction is older than computers. Courts compel the production of papers that exist. They cannot, by the grammar of production, compel the creation of a past that was never written down.
Being, here, is having been written. What was merely answered has already ceased to be available as evidence. A demand that treats the answering as if it had been a keeping mistakes the ontology of the service. The Operator answers questions about hosted names and refuses the rest. The answers are computed and forgotten. The Operator does not save DNS queries. The same emptiness covers DoH clients, DoT clients, resolver traces, client IP addresses for DNS, and connection history for DNS. There is no retention period behind which a log is hiding. There is no log.
What may exist, if a specific account or a domain actually hosted here is identified, is small: that a token-hash account owns a named domain, and the records currently published for that domain. Currently published. Who asked was never written. The account token is stored as a hash. A hash is not a recoverable secret, and it is not a diary of lookups.