Which command is a replacement for nslookup and is used for name server lookups?

Which command is a replacement for nslookup and is used for name server lookups?

• A. Dig
• B. Whois
• C. Arp
• D. Route

Answer: (A)

DNS name lookups involve asking a DNS server to translate a domain name into IP address records and other information. The tool dig is a modern, widely used replacement for nslookup because it gives more control and clearer output. With dig, you can query a specific DNS server by adding @server, request any record type (A, AAAA, MX, TXT, etc.), and tailor the output with options like +short for concise results or +trace to see the resolution path. It is part of the standard DNS toolkit and is considered more robust and script-friendly than nslookup. The other options don’t perform general DNS lookups: whois fetches registration data; Arp resolves local MAC addresses; route relates to routing tables rather than DNS queries. Therefore, dig is the best replacement for nslookup.

DNS name lookups involve asking a DNS server to translate a domain name into IP address records and other information. The tool dig is a modern, widely used replacement for nslookup because it gives more control and clearer output. With dig, you can query a specific DNS server by adding @server, request any record type (A, AAAA, MX, TXT, etc.), and tailor the output with options like +short for concise results or +trace to see the resolution path. It is part of the standard DNS toolkit and is considered more robust and script-friendly than nslookup. The other options don’t perform general DNS lookups: whois fetches registration data; Arp resolves local MAC addresses; route relates to routing tables rather than DNS queries. Therefore, dig is the best replacement for nslookup.