How can administrators verify DNS hostname resolution and reverse lookup resolution using Command Prompt or PowerShell?

How can administrators verify DNS hostname resolution and reverse lookup resolution using Command Prompt or PowerShell?

• A. By using the nslookup command
• B. By pinging the hostname only
• C. By using tracert
• D. By using ipconfig

Answer: (A)

DNS queries can be tested with a DNS query tool to verify both forward and reverse resolution. Using nslookup in Command Prompt or PowerShell lets you ask a DNS server for the IP address of a hostname (forward lookup) and, by supplying an IP address, obtain the associated hostname (reverse lookup). For example, nslookup example.com will show the IP address for that hostname, while nslookup 203.0.113.5 will attempt a reverse lookup to reveal the hostname tied to that IP. You can also use interactive mode to tailor queries, such as switching to PTR records with set type=PTR or selecting a specific DNS server with the server command. This direct ability to query DNS records makes nslookup the best tool for confirming both kinds of DNS resolution. Pinging a hostname, tracing a route, or checking IP configuration, while useful for other purposes, does not provide direct verification of DNS name-to-IP or IP-to-name mappings.

DNS queries can be tested with a DNS query tool to verify both forward and reverse resolution. Using nslookup in Command Prompt or PowerShell lets you ask a DNS server for the IP address of a hostname (forward lookup) and, by supplying an IP address, obtain the associated hostname (reverse lookup). For example, nslookup example.com will show the IP address for that hostname, while nslookup 203.0.113.5 will attempt a reverse lookup to reveal the hostname tied to that IP. You can also use interactive mode to tailor queries, such as switching to PTR records with set type=PTR or selecting a specific DNS server with the server command. This direct ability to query DNS records makes nslookup the best tool for confirming both kinds of DNS resolution. Pinging a hostname, tracing a route, or checking IP configuration, while useful for other purposes, does not provide direct verification of DNS name-to-IP or IP-to-name mappings.