DNS: practice questions

Name resolution, DNS record types and reverse lookups, and diagnosing a DNS failure.

CCNA 200-301 v2.0, exam topic 4.4 · part of 4. Network Services and Security, 20% of the exam

The same material in the CCNA 200-301 v1.1 exam: Network Services

What this topic covers

Name hierarchy
Domains are organized in a tree with delegated zones.
Name resolution
Resolvers query name servers, often iteratively.
Resource records
A, NS, CNAME and MX records map names to data.
Which record answers which lookup
A and AAAA records give host addresses, CNAME aliases, MX mail servers, NS delegation and PTR reverse lookups.
Reverse lookups
PTR records under in-addr.arpa and ip6.arpa map addresses back to names.
DNS failure symptoms
Reach by IP but not by name.

Sample question

Try it, then open the answer. Our questions are written by AI and checked independently before they are published.

Medium Multiple choice

Refer to the exhibit. An engineer tests connectivity to app.corp.example.com and reports that name resolution fails, even though direct IP access to 192.0.2.10 works. Which two conclusions are supported by the DNS zone export? (Choose two.)

{
  "zones": [
    {
      "name": "corp.example.com",
      "records": [
        {"name": "@", "type": "SOA", "value": "ns1.corp.example.com. admin.corp.example.com. 2023101501 3600 1800 604800 86400"},
        {"name": "@", "type": "NS", "value": "ns1.corp.example.com."},
        {"name": "ns1", "type": "A", "value": "192.0.2.2"},
        {"name": "app", "type": "CNAME", "value": "srv1.internal.example.com."}
      ]
    },
    {
      "name": "internal.example.com",
      "records": [
        {"name": "@", "type": "SOA", "value": "ns1.internal.example.com. admin.internal.example.com. 2023101501 3600 1800 604800 86400"},
        {"name": "@", "type": "NS", "value": "ns1.internal.example.com."},
        {"name": "ns1", "type": "A", "value": "192.0.2.3"},
        {"name": "srv2", "type": "A", "value": "192.0.2.20"},
        {"name": "db1", "type": "A", "value": "192.0.2.30"}
      ]
    },
    {
      "name": "2.0.192.in-addr.arpa",
      "records": [
        {"name": "@", "type": "SOA", "value": "ns1.corp.example.com. admin.corp.example.com. 2023101501 3600 1800 604800 86400"},
        {"name": "10", "type": "PTR", "value": "legacy-app.corp.example.com."},
        {"name": "20", "type": "PTR", "value": "srv2.internal.example.com."}
      ]
    }
  ]
}
  1. A. The authoritative name server ns1.corp.example.com has an unreachable loopback address.
  2. B. The CNAME record for app violates standards by coexisting with an address record.
  3. C. The reverse lookup pointer for 192.0.2.10 does not match app.corp.example.com.
  4. D. The in-addr.arpa zone specifies an invalid subnet boundary for the /24 prefix.
  5. E. The canonical target srv1.internal.example.com lacks an address record.
Show the answer

Answers: C. The reverse lookup pointer for 192.0.2.10 does not match app.corp.example.com.; E. The canonical target srv1.internal.example.com lacks an address record.

Resolving app.corp.example.com leads to an alias (CNAME) pointing to srv1.internal.example.com. In the internal.example.com zone, records exist for srv2 and db1, but no A or AAAA record exists for srv1.internal.example.com, creating a broken CNAME chain that results in a resolution failure. Furthermore, inspecting the reverse mapping zone 2.0.192.in-addr.arpa reveals that host 10 (192.0.2.10) points to legacy-app.corp.example.com rather than app.corp.example.com, confirming forward and reverse mapping inconsistencies.

Further reading