Question

Difficulty: MediumUtilizing Command-Line Network Troubleshooting Utilities

A network technician is troubleshooting an issue on a Linux host that cannot resolve the hostname of an internal server `app.corp.local`. The technician runs `dig app.corp.local` and receives a response indicating `STATUS: SERVFAIL` from the local recursive DNS server at `192.168.1.2`. To determine whether the issue is isolated to the local recursive server or affects the authoritative server directly, the technician wants to query the domain's designated authoritative DNS server at `10.0.5.50`. Which of the following command-line entries should the technician execute?

  1. A
    dig app.corp.local -x 10.0.5.50
  2. B
    dig app.corp.local AAAA
  3. dig @10.0.5.50 app.corp.localAnswer
  4. D
    netstat -an | grep 10.0.5.50:53

Answer

Executing `dig @10.0.5.50 app.corp.local` sends the query directly to the authoritative DNS server at `10.0.5.50`.
In the `dig` (Domain Information Groper) command-line utility, the `@` symbol followed by an IP address or hostname tells `dig` to send the query directly to that specific DNS server. Running `dig @10.0.5.50 app.corp.local` allows the technician to bypass the local recursive resolver (`192.168.1.2`) and evaluate the authoritative server's response.

Step-by-Step Solution

1
Identify the goal of the CLI command.
The goal is to direct a DNS resolution query for `app.corp.local` specifically to the server at `10.0.5.50` instead of the local default resolver.
Bypassing intermediate recursive resolvers helps isolate whether DNS failures originate from local cache/forwarding or the authoritative name server.
2
Analyze the syntax requirements for the `dig` utility.
In BIND `dig`, directing a query to a specific DNS server requires specifying `@server` before or after the domain name.
The `@` sign tells `dig` to bypass `/etc/resolv.conf` defaults and direct UDP/TCP port 53 packets to the specified IP address.
3
Evaluate the correct command syntax.
`dig @10.0.5.50 app.corp.local` correctly targets `10.0.5.50` for the lookup.
This isolates the DNS troubleshooting path effectively.

Key Concept

Directing DNS lookup queries to specific name servers using the `dig` utility
Rate this question