Week 9 · Lesson 3

DNS (2): Records and Resolution

Lesson 2 said DNS is a phone book — now you open the book. The pages are resource records, and reading them is the difference between a stock answer and a defended one. This lesson covers the record types the CCNA expects, an exact resolution walkthrough, troubleshooting with nslookup and dig, and DNSSEC in a nutshell.

CCNA 200-301 Domain 4.0 IP Services Verified 2026-10-11
Part 1

Resource records: the seven you must know

Every DNS answer is delivered as one or more resource records (RRs). A record says, for a given owner name: this name stands for this data, valid for this long. The exam expects these record types by heart — RFC 1035 defines the original set, and RFC 3596 later added the IPv6 record.

Record types · select one

      

TypeFull nameWhat it holdsExample
AAddressAn IPv4 address for a host name.www.example.com. 300 IN A 93.184.216.34
AAAAIPv6 AddressAn IPv6 address (pronounced “quad-A”).www.example.com. 300 IN AAAA 2606:2800:21f:cb07:6820:80da:af6b:8b2c
CNAMECanonical NameAn alias: this name is another name.www.example.com. 300 IN CNAME example.com.
MXMail ExchangerMail servers for the domain, each with a priority (lower = preferred).example.com. 300 IN MX 10 mail.example.com.
NSName ServerAuthoritative name servers for the zone (used for delegation).example.com. 300 IN NS ns1.example.com.
PTRPointerReverse mapping: IP to name (used in in-addr.arpa / ip6.arpa).34.216.184.93.in-addr.arpa. 300 IN PTR www.example.com.
TXTTextArbitrary text; used for SPF, DKIM, verification tokens.example.com. 300 IN TXT "v=spf1 mx -all"
Exam tip. The big four traps: (1) AAAA is the IPv6 record, not a bigger A; (2) CNAME is an alias and cannot coexist with other records at the same name; (3) MX priority — the LOWER number is preferred (10 beats 20); (4) PTR is the reverse of A/AAAA and lives under in-addr.arpa / ip6.arpa, so the IP is written backwards in nslookup reverse questions.
Part 2

A zone-style record block

Below is a typical master file for example.com (the RFC 1035 master-file format). Each line is: owner — TTL — class (IN) — type — data. Select a record type to find its line.

Zone file for example.com · highlight a type

      

Part 3

A full resolution walkthrough

Now replay Lesson 2’s flow, watching the records at each step (a browser asking for www.example.com).

What each step returns · select a step

      

Watch the record types. Steps 2 and 3 return NS records (a referral to lower the chain); step 4 returns the A/AAAA answer; reverse lookups (step 0 in the opposite direction) return PTR. If an exam lists the RDATA at each stage, expect exactly these types.
Part 4

UDP vs TCP on port 53

DNS uses port 53 on both transports, but the split is precise. Pick the scenario.

Which transport carries this? · select a scenario

Exam tip. Memorise this sentence verbatim: “DNS uses UDP 53 for queries; TCP 53 is used for zone transfers and for replies truncated beyond the 512-byte UDP limit (TC bit set).” If a question shows a firewall blocking TCP 53 between two name servers, suspect broken zone transfers even though normal resolution keeps working.
Part 5

Troubleshooting: nslookup and dig

Two command-line tools dominate exam examples. nslookup ships with Windows and shows a friendly two-line answer; dig is the Linux/UNIX tool and shows the raw record.

Basic forward lookup with nslookup:

C:\Users\student> nslookup www.example.com
Server:  dns.google
Address:  8.8.8.8

Name:    www.example.com
Address: 93.184.216.34

The first two lines identify the DNS server your PC used (here the recursive resolver 8.8.8.8); the last two are the returned A record.

Querying a specific record type:

C:\Users\student> nslookup -type=MX example.com
Server:  dns.google
Address:  8.8.8.8

example.com      mail exchanger = 10 mail.example.com.

Reverse lookup (PTR): the IP is appended in reversed order to in-addr.arpa:

C:\Users\student> nslookup -type=PTR 34.216.184.93.in-addr.arpa
Server:  dns.google
Address:  8.8.8.8

34.216.184.93.in-addr.arpa  name = www.example.com.

With dig, the answer section is explicit — note TTL, class, and type:

$ dig www.example.com A +short
93.184.216.34

$ dig www.example.com A
;; ANSWER SECTION:
www.example.com.  300  IN  A  93.184.216.34

$ dig +trace www.example.com
;; first: root referral, then .com referral, then final A answer

The +trace flag replays the full iterative journey — exactly the root → TLD → authoritative sequence from Lesson 2 — which is why it is the exam’s favourite “prove you understand resolution” example. The +short flag prints only the RDATA line, handy in scripts that just need the IP.

Part 6

DNSSEC and common failure scenarios

DNSSEC. DNSSEC (RFC 4033) adds cryptographic signatures to DNS records so a resolver can verify that an answer really came from the authoritative zone and was not spoofed or modified in transit. It signs records with the zone’s private key and publishes the public key in a DNSKEY record; a signature (RRSIG) failing verification makes the resolver reject the answer rather than trust it. DNSSEC does not encrypt queries or hide them from your ISP — it only authenticates. Encryption of the query channel itself is a separate feature (DNS over TLS, port 853).

Exam questions usually present a symptom and ask for the cause. Pick a symptom to see the classic answer.

DNS failure scenarios · choose a symptom

SymptomLikely causeFix / check
“The IP address of the DNS server was entered incorrectly”Client configured with a wrong DNS server address that is unreachable.Verify ipconfig /all; correct the configured server.
“Looks up the name but gets no IP / NXDOMAIN”Wrong or missing record (typographical error), or the name is truly undelegated.Query the authoritative server directly with dig @ns1.example.com to bypass caches.
“Changed records but old IP still returned”TTL staleness — intermediate resolvers still hold the old cached copy.Wait for TTL expiry, or lower TTL before making changes.
“Newly added subdomain does not resolve for some users”NS delegation not yet propagated, or glue records missing at the parent.Verify the parent TLD holds NS + glue for the zone.
Warning. The single most common exam error: blaming “the DNS server is down” when the real cause is a typo’d server address on the client or a stale cache. Always test in layers — the client’s configured server, then the record itself (“host”) — and check the TTL before concluding the record is wrong.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Mockapetris, P. RFC 1035: Domain Names — Implementation and Specification (1987), §3.2–3.5 (RR types, master files), §4.2 (512-octet UDP and TCP usage, TC bit). rfc-editor.org/rfc/rfc1035.
  2. Thomson, S., Narten, T. & Jinmei, T. RFC 3596: DNS Extensions to Support IP Version 6 (2003), defines the AAAA record. rfc-editor.org/rfc/rfc3596.
  3. Kitterman, S. RFC 7208: Sender Policy Framework (SPF) (2014), specifies SPF in TXT records. rfc-editor.org/rfc/rfc7208.
  4. Arends, R., Austein, R., Larson, M., Massey, D. & Rose, S. RFC 4033: DNS Security Introduction and Requirements (2005), DNSSEC overview. rfc-editor.org/rfc/rfc4033.
  5. Bellis, R. RFC 5625: DNS Proxy Implementation Guidelines (2009), confirms the 512-octet limit and TC-based TCP retry. rfc-editor.org/rfc/rfc5625.
  6. IANA. Service Name and Transport Protocol Port Number Registry, DNS domain 53 (tcp/udp). iana.org/assignments/service-names-port-numbers.
  7. Cisco. CCNA (200-301) Exam Topics, IP Services — DNS. cisco.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.