Which command verifies DNS resolution from MikroTik to a hostname using the CLI?

Which command verifies DNS resolution from MikroTik to a hostname using the CLI?

• A. /dns resolve example.com
• B. /system dns resolve example.com
• C. /resolve example.com
• D. /resolve dns-example.com

Answer: (C)

Testing DNS resolution from MikroTik’s CLI is done with the built‑in resolve command. It asks the router to look up a hostname using the DNS servers configured on the device and prints the resulting IP address(es) right in the terminal. This is the clearest, quickest way to verify that DNS is working from the router because it uses the actual DNS settings you have in /ip dns and shows exactly what the DNS returns for the hostname. The reason this command is the best choice is its simplicity and direct purpose: you feed it a hostname and it immediately tells you the IPs, confirming both DNS configuration and reachability. If DNS isn’t configured or the DNS server can’t be reached, you’ll see an error, which helps pinpoint where the problem lies. The other forms aren’t the standard quick test for hostname resolution in RouterOS. They either refer to other parts of the DNS configuration or aren’t the typical single-step lookup command, so they aren’t as straightforward for verifying a simple hostname-to-IP resolution from the CLI.

Testing DNS resolution from MikroTik’s CLI is done with the built‑in resolve command. It asks the router to look up a hostname using the DNS servers configured on the device and prints the resulting IP address(es) right in the terminal. This is the clearest, quickest way to verify that DNS is working from the router because it uses the actual DNS settings you have in /ip dns and shows exactly what the DNS returns for the hostname.

The reason this command is the best choice is its simplicity and direct purpose: you feed it a hostname and it immediately tells you the IPs, confirming both DNS configuration and reachability. If DNS isn’t configured or the DNS server can’t be reached, you’ll see an error, which helps pinpoint where the problem lies.

The other forms aren’t the standard quick test for hostname resolution in RouterOS. They either refer to other parts of the DNS configuration or aren’t the typical single-step lookup command, so they aren’t as straightforward for verifying a simple hostname-to-IP resolution from the CLI.