Study guide
DNS, DHCP, and NAT Services
CCST Networking Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation, Official Sources, and Exam Strategy
Official Exam Profile and Source Hierarchy Registration, Delivery, Attempts, and Results Using the Six Official Topic Areas Building a Practical Study Plan Exam Strategy Without Unsupported Shortcuts Ethical Preparation and Path Forward
2 Network Standards, Models, and Common Protocols
Network Building Blocks OSI and TCP/IP Models Frames, Packets, Segments, and Data Flow Network Types and Scope Cloud, On-Premises, Protocols, and Ports Bandwidth, Throughput, Latency, and Jitter
3 Chapter 3: IPv4, IPv6 Addressing, and Subnet Formats
3.1 Public, Private, and Local Addressing 3.2 IPv4 Dotted Decimal and Binary Basics 3.3 Subnet Masks, CIDR, and Prefix Lengths 3.4 Subnet Logic, Host Ranges, and Gateways 3.5 IPv6 Address and Prefix Formats 3.6 MAC vs IP in Addressing Troubleshooting
4 Endpoints, Media, Cabling, and Client Connectivity
Endpoint Devices and Network Roles Network Interface Cards and Link Status Copper, Fiber, Coax, and Connector Basics Wired, Wi-Fi, and Cellular Access Methods Interference, Signal Quality, and Physical Reliability Client Connectivity Checks by Operating System
5 Infrastructure Devices, Ports, and Physical Installation
Infrastructure Device Roles Ports, Connectors, and Device Identification Cisco Device LEDs and Status Checks Network Diagrams and Cabling Instructions Power over Ethernet and Powered Devices Racks, Patch Panels, and Installation Basics
6 Switching, Routing, and Network Services
Basic Switching and MAC Learning VLANs and Local Boundaries Routing, Default Gateway, and ARP DNS, DHCP, and NAT Services Transport-Layer Services Small Network Traffic Flow
7 Troubleshooting Methodology, Ticketing, and Documentation
Help Desk Intake and Information Gathering Scope, Impact, and Prioritization Reproduce, Isolate, and Escalate Ticket Quality and Operational Documentation User Communication and Change History Physical, Data Link, and Network Layer Triage
8 Diagnostic Commands, Packet Capture, and Device Data
Command-Line Triage and Ping Path and Client Configuration Commands DNS and Socket Diagnostics Wireshark Capture and Save Device Access and Data Collection Basic Cisco Show Commands
9 Security, Firewalls, Wireless, and Safe Defaults
Firewall Filtering and Traffic Policy Least Privilege, AAA, Passwords, and MFA Wireless Security, WPA2, WPA3, and WPAx Guest Networks, Segmentation, and Shared Devices Common Threats and Safe User Practices Secure Home Router Baseline
10 Integrated Small Network Build and Repair Labs
Lab 1: Build a Basic Office LAN Lab 2: Repair No Internet After an Office Move Lab 3: Wireless Clients Cannot Reach Local Resources Lab 4: DHCP, DNS, and Default Gateway Symptoms Lab 5: Switch, Router, and Service Boundaries Lab 6: Escalation, Documentation, and Handoff
11 CCST to CCNA Career Path and Operational Readiness
Entry-Level Networking Roles and Expectations CCST vs CCNA and the Cisco Roadmap NetAcad 70-Hour Path and Study Plan Lab Habits for Real Operational Readiness Ethical Preparation, Portfolio, and Logbook Exam Scheduling Calendar and Readiness Check
12 Final Review, Exam Day, and Remediation Plan
Final Review Map to Official Objectives 50-Minute Exam Day Timing Unsupported Facts and Ethical Preparation Retake Planning Before the First Attempt Post-Fail Remediation Workflow Post-Pass Next Steps and Validity
DNS, DHCP, and NAT Services
Key Takeaways Explain This Topic AI
DHCP automatically leases a client its IP address, mask, default gateway, DNS servers, and lease time using the DORA exchange.
DNS resolves names to IP addresses; if names fail but IPs work, suspect DNS, not the network path.
NAT translates private RFC 1918 addresses to public addresses; PAT shares one public IP across many hosts using port numbers.
Private ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 and are never routed on the public Internet.
A client can have perfect Layer 2 connectivity and still fail if DHCP, DNS, or NAT is down or misconfigured.
Last updated: June 2026
Three Services, Three Jobs
A network can be cabled perfectly and still be unusable if its support services fail. DHCP , DNS , and NAT are distinct, and mixing them up slows every ticket. The one-line summary: DHCP gives you addressing, DNS resolves names to addresses, and NAT translates addresses between private and public.
DHCP — Dynamic Host Configuration Protocol
DHCP removes manual endpoint setup. A client and server complete a four-message exchange remembered as DORA :
- Step Message Direction Purpose
- D Discover Client broadcast "Any DHCP server out there?"
- O Offer Server Proposes an address and options
- R Request Client broadcast Accepts a specific offer
- A Acknowledge Server Confirms the lease
The lease carries an IP address, subnet mask/prefix, default gateway, DNS server addresses, and a lease time . DHCP runs over UDP (server port 67 , client port 68 ). In a small office the router or firewall is the DHCP server; in larger sites a dedicated server is used and routers run a DHCP relay (ip helper-address) to forward the broadcasts across VLANs. If DHCP fails entirely, the client self-assigns an APIPA address in 169.254.0.0/16 and loses its gateway.
- DNS and NAT
- DNS — Domain Name System
DNS maps human names like www.example.com to IP addresses. The client asks a configured resolver , which may recurse up to root, top-level-domain, and authoritative servers. DNS uses UDP port 53 for ordinary queries and TCP port 53 for large responses and zone transfers. DNS failure looks exactly like an Internet outage because names stop working even when raw IP connectivity is fine. The classic test: ping or browse a known IP versus the name. If the IP works but the name does not, DNS settings or DNS reachability are the suspect — not the link or the gateway.
NAT — Network Address Translation
NAT rewrites IP address information as traffic crosses a router or firewall. Internal networks use RFC 1918 private ranges, which are never routed on the public Internet:
- Range CIDR Typical use
- 10.0.0.0 - 10.255.255.255 10.0.0.0/8 Large enterprise
- 172.16.0.0 - 172.31.255.255 172.16.0.0/12 Mid-size networks
- 192.168.0.0 - 192.168.255.255 192.168.0.0/16 Home/small office
PAT (Port Address Translation) , also called NAT overload , lets many inside hosts share one public IP by tracking each conversation with a unique transport port number . NAT is not a firewall — it hides addresses but does not decide policy; firewall rules still permit or deny traffic.
A normal web visit ties it together
DHCP leases the client 192.168.10.25 , gateway 192.168.10.1 , DNS 192.168.10.10 . DNS resolves the site to a public IP. The client sends to its gateway, which uses PAT to swap the private source for a public address. Replies return to the public address and the NAT table maps them back to the right inside host.
Isolating the failure
No valid IP -> DHCP, VLAN, cabling, Wi-Fi, or relay.
Valid IP, gateway pings, names fail -> DNS.
Local and DNS fine, Internet fails for many users -> NAT, firewall, upstream routing, or ISP.
Common traps
Calling everything 'the Internet is down' instead of separating what works from what fails.
Believing NAT secures the network — it does not.
Forgetting DHCP and DNS both ride UDP, so a UDP-blocking firewall can break both.
- Leases, Record Types, and Translation Tables
- Inside the DHCP lease
A lease is temporary. Roughly halfway through the lease time (the T1 timer, about 50%), the client tries to renew with the same server using a unicast Request; later (T2, about 87.5%) it broadcasts to any server. If renewal fails before the lease expires, the client gives up the address and falls back to APIPA. This is why a client that 'worked yesterday' can lose connectivity overnight when a DHCP server is down — the lease simply expired. A DHCP relay (the ip helper-address on a router) is essential in multi-VLAN networks because the client's Discover broadcast cannot cross a VLAN boundary on its own.
Common DNS record types
A CCST tech should recognize the everyday record types a resolver returns:
- Record Maps Example use
- A Name -> IPv4 address www.example.com -> 93.184.x.x
AAAA Name -> IPv6 address www.example.com -> 2606:...
- CNAME Name -> another name (alias) shop -> store.example.com
- MX Domain -> mail server example.com mail routing
- PTR IP -> name (reverse) reverse lookups, logging
When nslookup name returns an address but the site still fails, DNS is fine and the fault is elsewhere; when nslookup times out or returns 'server failed', DNS is the problem.
Inside the NAT/PAT table
PAT keeps a translation table so replies find the right inside host. Each row maps an inside socket to an outside socket:
- Inside IP:port Translated to Destination
- 192.168.10.25:51000 203.0.113.5:51000 8.8.8.8:443
- 192.168.10.40:52210 203.0.113.5:52210 1.1.1.1:443
Because the port number distinguishes each conversation, dozens of inside hosts share one public address. If the table fills or an entry ages out mid-session, a long-idle connection can drop — another symptom worth recognizing.
Putting it together
The failure-isolation logic is always the same: confirm the client has a valid DHCP lease, that DNS resolves names, and that NAT plus routing carry packets outward. Test them in that order and a vague 'Internet is down' ticket resolves into a specific, fixable service.