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.
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.
| Type | Full name | What it holds | Example |
|---|---|---|---|
| A | Address | An IPv4 address for a host name. | www.example.com. 300 IN A 93.184.216.34 |
| AAAA | IPv6 Address | An IPv6 address (pronounced “quad-A”). | www.example.com. 300 IN AAAA 2606:2800:21f:cb07:6820:80da:af6b:8b2c |
| CNAME | Canonical Name | An alias: this name is another name. | www.example.com. 300 IN CNAME example.com. |
| MX | Mail Exchanger | Mail servers for the domain, each with a priority (lower = preferred). | example.com. 300 IN MX 10 mail.example.com. |
| NS | Name Server | Authoritative name servers for the zone (used for delegation). | example.com. 300 IN NS ns1.example.com. |
| PTR | Pointer | Reverse mapping: IP to name (used in in-addr.arpa / ip6.arpa). | 34.216.184.93.in-addr.arpa. 300 IN PTR www.example.com. |
| TXT | Text | Arbitrary text; used for SPF, DKIM, verification tokens. | example.com. 300 IN TXT "v=spf1 mx -all" |
in-addr.arpa / ip6.arpa, so the IP is written backwards in nslookup reverse questions.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.
@is shorthand for the zone’s origin (example.com.).- The SOA (Start of Authority) opens every zone with the primary NS, the admin contact, a serial, and timers that secondaries use for zone transfer.
blogis a CNAME alias pointing atexample.com.— note the alias must ultimately resolve to an A/AAAA record, and it holds no other records itself.- The two MX records for one host show priority in action: mail (10) is tried before mail2 (20).
- The TXT record carries SPF syntax (
v=spf1), declaring which IPs are allowed to send mail for this domain.
A full resolution walkthrough
Now replay Lesson 2’s flow, watching the records at each step (a browser asking for www.example.com).
UDP vs TCP on port 53
DNS uses port 53 on both transports, but the split is precise. Pick the scenario.
- UDP is the default for queries and responses. RFC 1035 sets the original UDP message limit at 512 octets — one request, one small response, no connection setup, and no retransmission, which is exactly the right trade for a quick lookup.
- If a response would exceed the 512-byte limit, the server sets the TC (truncation) bit and the resolver retries over TCP. Modern resolvers use EDNS0 to negotiate larger UDP payloads, but the TC fallback remains the mechanism.
- TCP is always used for zone transfers (AXFR/IXFR — copying the entire zone to a secondary name server) because the whole zone is far bigger than a tiny datagram and must arrive in order and intact.
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.
DNSSEC and common failure scenarios
Exam questions usually present a symptom and ask for the cause. Pick a symptom to see the classic answer.
| Symptom | Likely cause | Fix / 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. |
Review
Check what you have learned with these review questions.
Sources & references
- 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.
- 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.
- Kitterman, S. RFC 7208: Sender Policy Framework (SPF) (2014), specifies SPF in TXT records. rfc-editor.org/rfc/rfc7208.
- 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.
- Bellis, R. RFC 5625: DNS Proxy Implementation Guidelines (2009), confirms the 512-octet limit and TC-based TCP retry. rfc-editor.org/rfc/rfc5625.
- IANA. Service Name and Transport Protocol Port Number Registry, DNS domain 53 (tcp/udp). iana.org/assignments/service-names-port-numbers.
- 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.