Which command would you use to collect DNS frame traces on a network?

Using tcpdump to collect DNS frame traces on a network is appropriate because tcpdump is a powerful command-line packet sniffer that allows you to capture and analyze network traffic. When it comes to monitoring DNS requests and responses, tcpdump can filter traffic based on port numbers (typically UDP port 53 for DNS), which enables you to capture only the DNS-related packets. This makes it an effective tool for diagnosing DNS issues or analyzing DNS traffic patterns.

In contrast, while tools like dig and nslookup are primarily used for querying DNS records and testing DNS resolutions, they do not have the capability to capture network frames or traffic. Netstat, on the other hand, provides information about network connections, routing tables, interface statistics, and more, but it does not capture or analyze actual packet data as tcpdump does. Thus, tcpdump stands out as the correct choice for the task of collecting DNS frame traces.