Computer Science · 10th Grade

Active learning ideas

Domain Name System (DNS)

DNS is abstract for students because it operates invisibly, yet it is foundational to every internet interaction. Active learning works here because students must physically trace and simulate the system’s steps, turning invisible steps like caching and hierarchy into visible, memorable actions.

• Common Core State Standards
• CSTA: 3A-NI-04
• CSTA: 3A-NI-05

• 20–30 min
• Pairs → Whole Class
• 3 activities

Activity 01

• Simulation Game
• 30 min · Whole Class

Role-Play: The DNS Lookup Chain

Assign students to play a browser, a local resolver, a root server, a TLD server (.com), and an authoritative server. The browser student holds a query card for 'www.school.edu' and passes it through the chain, with each server handing off the query to the next. The authoritative server returns the IP. Repeat with a cached response to show how the resolver skips the chain on a second lookup.

Explain the function of the Domain Name System.

Facilitation Tip

Before the role-play, assign each student a role card with only the information their ‘server’ would have in real life to force interdependence.

What to look for

Provide students with a scenario: 'A user types www.example.com into their browser, but the website does not load.' Ask them to list three specific DNS-related reasons why this might happen, referencing at least two types of DNS servers.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 02

• Inquiry Circle
• 30 min · Small Groups

Inquiry Circle: DNS Propagation Analysis

Groups use the command line (nslookup or dig) to query the DNS records for five different domains, recording the TTL values returned. They hypothesize: if a site's IP changes today, how long before all users see the new address? Groups compare TTL policies for different domain types (CDN vs. small business site) and discuss the trade-offs.

Analyze the process of a DNS lookup.

Facilitation Tip

During the propagation analysis, have students record TTL values from multiple DNS tools and compare them side-by-side to see live caching differences.

What to look for

Pose the question: 'Imagine the root DNS servers went offline for one hour. What would be the immediate and widespread impact on internet usage globally? Discuss the critical role these servers play in the DNS hierarchy.'

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Activity 03

• Think-Pair-Share
• 20 min · Pairs

Think-Pair-Share: What Breaks Without DNS?

Students are told DNS is completely unavailable for one hour. Individually, they list five tasks they could still perform (if they had IP addresses memorized) and five they could not. Pairs compare and identify which failure mode is most impactful, then present their reasoning to the class.

Predict the impact of a DNS server outage on internet accessibility.

Facilitation Tip

In the think-pair-share, require pairs to write their ‘broken’ scenario on one side of a paper and a corrected scenario on the other before sharing.

What to look for

Display a simplified diagram of a DNS lookup path (User -> Resolver -> Root -> TLD -> Authoritative). Ask students to label each component and briefly describe the function of the Resolver and the Authoritative Name Server in this specific path.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

A few notes on teaching this unit

Experienced teachers approach DNS by making the invisible hierarchy concrete through movement and props, avoiding over-reliance on diagrams alone. They emphasize TTL’s real-world impact by showing students actual DNS queries with tools like dig or nslookup, linking theory to observable data. Avoid starting with definitions—instead, let students discover the need for DNS through a broken scenario first.

By the end of these activities, students will explain the DNS lookup chain from resolver to authoritative server, identify how caching affects propagation, and justify why DNS structure prevents a single point of failure. They will use precise terminology and connect concepts to real-world reliability.

---

Watch Out for These Misconceptions

• During Role-Play: The DNS Lookup Chain, watch for students who treat DNS as a single, centralized system because they hand off information directly between roles without simulating delays or missing data.

  After the role-play, have students map the actual hierarchy on the board using arrows that show each server type (root, TLD, authoritative) and note where data is cached or missing to reinforce the distributed nature of DNS.

• During Collaborative Investigation: DNS Propagation Analysis, watch for students who assume all updates are visible immediately after changing a DNS record.

  During the analysis, direct students to compare TTL values and timestamps from different resolvers in their tools, then have them calculate when cached records will expire to visualize the propagation delay.

• During Think-Pair-Share: What Breaks Without DNS?, watch for students who only cite websites as affected services.

  After the pair work, ask each pair to add at least two non-web examples (like email or VPNs) to a class chart, prompting them to scan their notes from the overview for record types beyond A and AAAA.

---

Methods used in this brief

• Simulation Game
• Inquiry Circle
• Think-Pair-Share