A systems administrator receives reports of issues in one of the Linux systems.

The dig command is used to perform DNS lookups. The output shows a timeout with the message:

"no servers could be reached" — indicating the system lacks a configured DNS server.

Reviewing /etc/resolv.conf, we see that no nameserver entry exists, which is required for DNS resolution.

Option D adds a public DNS server (8.8.8.8) to /etc/resolv.conf, solving the missing nameserver issue.

Option F restarts NetworkManager, which manages network and DNS settings on many Linux systems. This ensures the new DNS configuration is properly applied.

Incorrect Options:

A attempts to map a hostname manually but does so incorrectly (wrong syntax for /etc/hosts).

B modifies a volatile systemd symlink that resets on reboot.

C restarts networkd, which may not even be used on systems running NetworkManager.

E updates a static script but doesn’t apply immediately.

G assumes a local DNS server (named/BIND) is running, which isn't indicated in the scenario.