Computer Science · Grade 12

Active learning ideas

Domain Name System (DNS)

Active learning helps students grasp DNS because it is a process that happens invisibly behind every web request. By mapping the steps themselves, students transform abstract concepts into concrete understanding, making retention stronger and misconceptions easier to correct through direct observation.

• Ontario Curriculum Expectations
• CS.N.5

• 25–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Collaborative Problem-Solving
• 35 min · Small Groups

Collaborative Problem-Solving: Tracing DNS Lookups

Students launch command-line tools like nslookup or dig on school-filtered domains. They record query paths, repeat for caching effects, and compare recursive versus iterative modes. Groups share findings on shared docs.

How does DNS facilitate user-friendly access to web resources?

Facilitation Tip

During the Lab: Tracing DNS Lookups, have students work in pairs to reduce setup time and encourage discussion about each step's purpose.

What to look for

Provide students with a scenario: 'A user types www.example.com into their browser.' Ask them to list the first three steps in the DNS lookup process and identify which type of server is queried at each step.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 02

• Document Mystery
• 25 min · Small Groups

Role-Play: DNS Hierarchy Chain

Assign roles in small groups: user, resolver, root server, TLD server, authoritative server. Practice passing query slips until IP resolution. Debrief on bottlenecks and redundancies.

Explain the process of a DNS lookup from a user's perspective.

Facilitation Tip

For the Role-Play: DNS Hierarchy Chain, assign specific roles to avoid confusion and ensure every student participates in the query handoff.

What to look for

Present students with a simplified DNS zone file. Ask them to identify the IP address for a given subdomain or determine which record type (e.g., A, CNAME) is used for a specific entry.

• Analyze
• Evaluate
• Self-Management
• Decision-Making

Activity 03

• Document Mystery
• 40 min · Pairs

Scenario: DNS Outage Simulation

Provide mock network diagrams; groups predict and map outage propagation from root failure. Use polling tools for class vote on impacts, then verify with case studies like 2016 Dyn attack.

Predict the impact of a large-scale DNS outage on internet services.

Facilitation Tip

When running Scenario: DNS Outage Simulation, provide a checklist of observable effects so students can systematically document changes.

What to look for

Pose the question: 'Imagine the root DNS servers went offline for 24 hours. What would be the immediate and cascading effects on global internet usage?' Facilitate a class discussion on the implications.

• Analyze
• Evaluate
• Self-Management
• Decision-Making

Activity 04

• Document Mystery
• 45 min · Pairs

Capture: Wireshark DNS Traffic

Pairs install Wireshark, browse sites, filter DNS packets. Annotate query/response pairs, note UDP port 53 usage. Discuss encryption gaps in class.

How does DNS facilitate user-friendly access to web resources?

Facilitation Tip

In Capture: Wireshark DNS Traffic, remind students to filter for DNS traffic only to focus their analysis and reduce noise.

What to look for

Provide students with a scenario: 'A user types www.example.com into their browser.' Ask them to list the first three steps in the DNS lookup process and identify which type of server is queried at each step.

• Analyze
• Evaluate
• Self-Management
• Decision-Making

A few notes on teaching this unit

Teach DNS by starting with the big picture: students need to see the entire system before diving into details. Use analogies like a postal system to explain hierarchy, but always return to real tools and data. Avoid overwhelming students with too many record types at once. Instead, introduce A and CNAME records through guided discovery, and use live demos to show their real-world effects. Research shows that students learn DNS best when they experience latency firsthand and compare cached versus uncached lookups.

By the end of these activities, students should confidently trace a complete DNS lookup, explain the roles of each server tier, and predict the impact of caching or outages. They should also be able to interpret DNS records and troubleshoot simple resolution failures using tools like nslookup and Wireshark.

---

Watch Out for These Misconceptions

• During Role-Play: DNS Hierarchy Chain, watch for students treating DNS as a flat list where domains map directly to IPs.

  Use the role-play to explicitly assign each student a server tier (root, TLD, authoritative) and have them simulate forwarding queries step by step. Emphasize that no single server holds all mappings, reinforcing the hierarchical handoffs.

• During Lab: Tracing DNS Lookups, watch for students assuming every lookup starts fresh at the root servers.

  Have students run repeated nslookup queries for the same domain and compare the timing and server responses. Point out cached responses in the output to demonstrate how resolvers avoid full recursion.

• During Scenario: DNS Outage Simulation, watch for students predicting a complete internet shutdown when DNS fails.

  Guide students to test specific services (e.g., pinging an IP directly) during the simulation. Discuss which services remain accessible and why, then connect these observations to real-world scenarios like bookmarked sites or cached content.

---

Methods used in this brief

• Collaborative Problem-Solving
• Document Mystery