Lesson 1 — DHCP, DNS, and NTP Basics
Week 6 outline
- Week 6 overview
- Lesson 1DHCP, DNS, and NTP Basics (current step)
- Lesson 2NAT and PAT Fundamentals
- QuizAddressing Services & NAT
- Lesson 3IPv6 Addressing and Dual-Stack
- Lesson 4IPv6 Static Routing
- QuizIPv6 Addressing & Routing
- Lesson 5Network Management Services: SNMP, Syslog, TFTP/FTP, QoS
- CheckpointWeek 6 Checkpoint
DHCP, DNS, and NTP Basics
Explain what each of DHCP, DNS, and NTP does and what breaks without it, walk the four DORA messages and know which are broadcast, and configure a router as a DHCP server and an NTP client.
Lesson orientation
What you'll learn (5 objectives)~27 min: video → lesson → check → apply → lab prep
Learning objectives
- Describe the role each of DHCP, DNS, and NTP plays and what breaks when each is missing
- Put the four DORA messages in order and state which are broadcast and why
- Configure a Cisco router DHCP pool with excluded addresses and verify leases with show ip dhcp binding
- Explain when a DHCP relay (ip helper-address) is required and point a client-facing interface at a remote server
- Configure basic NTP client mode and confirm the clock is synchronized
Terms you will see
Time breakdown
- Read the notes15 min
- Walk the DHCP and NTP configuration8 min
- Predict the relay scenario4 min
Assigned video

Free CCNA | NTP | Day 37 | CCNA 200-301 Complete Course
By Jeremy's IT Lab · Opens externally on YouTube
- Assigned watch
- ~8 min
Where to stop
The video covers the NTP objective only. DHCP and DNS are taught in the written sections above it.
The source marks this segment timestampStatus="unresolved" with no start or end, so no bounds are shown here.
The link opens in a new browser tab. Return here when you finish watching.
Watch for these concepts
- Why synchronized time matters for logs and certificates
- How stratum ranks a time source
- How ntp server makes a device a client of a trusted clock
Go beyond the video
The assigned video introduces the idea. CCNA Practice Labs completes the learning path: clarify core concepts, explore how each device behaves, visualize the communication path, check your understanding, and prepare for hands-on lab work.
Watch the concept → understand it → visualize it → practice it → apply it.
Three services, three kinds of manual work removed
Picture standing up a new office of 200 laptops. Each of these services removes a different chunk of work that would otherwise be done by hand, and each fails in a distinctive way — which is what makes them easy to tell apart when something breaks.
| Service | Provides | Symptom when it fails |
|---|---|---|
| DHCP | IP address, subnet mask, default gateway, and DNS server from a pool | Host has no address at all (or an APIPA 169.254 address) and reaches nothing |
| DNS | Name-to-address resolution — www.example.com becomes an IP | Numeric addresses still work; every name lookup fails |
| NTP | Clocks synchronized to a common reference, ranked by stratum | Connectivity is fine, but logs cannot be correlated and time-window certificates fail |
One design point the exam likes: servers, routers, switches, and printers are normally given static addresses, not DHCP leases. Their whole job is to be reachable at a known, unchanging address — a DNS server that moved every week would defeat its own purpose. DHCP is for the large, changing population of user devices.
DORA — four messages to bootstrap an address
A host with no address cannot have a normal conversation, so the lease exchange starts with a shout. Four messages, in a fixed order.
| Step | Message | Sent by | Cast | Why |
|---|---|---|---|---|
| Discover | DHCP Discover | Client | Broadcast | The client has no IP yet, so it asks 255.255.255.255 whether any server is out there |
| Offer | DHCP Offer | Server | Toward the client | A server proposes an address and options |
| Request | DHCP Request | Client | Broadcast | The client formally accepts one offer — broadcast so the other servers see the choice and reclaim theirs |
| Acknowledge | DHCP Ack | Server | Toward the client | The server confirms the lease and the client may use the address |
That reliance on broadcast has a direct consequence: DHCP broadcasts do not cross a router. If the server lives on a different subnet from the client, the Discover dies at the first router and the client never gets an offer.
Configure the pool, the resolver, and the clock
! --- DHCP: reserve the gateway/servers first, then define the pool ---
R1(config)# ip dhcp excluded-address 10.10.10.1 10.10.10.10
R1(config)# ip dhcp pool LAN
R1(dhcp-config)# network 10.10.10.0 255.255.255.0
R1(dhcp-config)# default-router 10.10.10.1
R1(dhcp-config)# dns-server 10.10.20.10
R1(dhcp-config)# lease 7
! --- DNS: let the router resolve names for its own lookups ---
R1(config)# ip name-server 10.10.20.10
R1(config)# ip domain-lookup
! --- NTP: become a client of a trusted time source ---
R1(config)# ntp server 10.10.20.10R1# show ip dhcp binding
Bindings from all pools not associated with VRF:
IP address Client-ID/Hardware address Lease expiration Type
10.10.10.11 0100.1122.3344.55 Jul 27 2026 09:14 AM Automatic
10.10.10.12 0100.aabb.ccdd.ee Jul 27 2026 09:15 AM Automatic
R1# show ntp status
Clock is synchronized, stratum 4, reference is 10.10.20.10- ip dhcp excluded-address 10.10.10.1 10.10.10.10 reserves the gateway and the low addresses so the pool never leases the router's own IP or a statically assigned server.
- network scopes the pool; default-router and dns-server are DHCP options 3 and 6, pushed to every client.
- show ip dhcp binding proves leasing works — one row per address handed out, tied to a client MAC.
- show ntp status reporting "Clock is synchronized, stratum 4" confirms the router locked to a stratum-3 source and now sits one level below it.
What you should retain
- DHCP supplies address, mask, gateway, and DNS; DNS maps names to addresses; NTP agrees clocks, ranked by stratum.
- DORA = Discover, Offer, Request, Acknowledge. Discover and Request are broadcast because the client has no usable address yet.
- Router pool = ip dhcp pool + network + default-router (+ dns-server); always exclude the gateway and static servers.
- ip helper-address goes on the client-facing interface, and is needed whenever server and client are on different subnets.
- Verify with show ip dhcp binding for leases and show ntp status for "Clock is synchronized".
- Ping by address working while ping by name fails is DNS — and proves DHCP is fine.
Before you read on
A branch has PCs on VLAN 20, and the only DHCP server is a router pool built for VLAN 10 on a different interface. The VLAN 20 PCs get no address. Which single feature turns this from broken to working, and on which interface does it go?
See it happen
Flashcards
Drill DORA order and cast, DHCP options 3 and 6, when a relay is required, and how stratum numbering works, until recall is automatic rather than reconstructed.
Section quiz follows Lesson 2, once NAT has joined DHCP on the same edge router.
Study deeper
Topic guides extend this lesson — they do not replace the first-party walkthrough above.
DHCP
For the full DHCP option list, the lease lifecycle including renewal, and who should and should not be a DHCP client
