Computer Science · Grade 10

Active learning ideas

IP Addresses and DNS

Active learning turns abstract IP and DNS concepts into tangible experiences. When students trace real DNS lookups or scan classroom devices, they see how network addressing works in practice, which builds durable understanding beyond memorization.

• Ontario Curriculum Expectations
• CS.HS.N.3
• CS.HS.N.4

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

Activity 01

• Simulation Game
• 30 min · Pairs

Terminal Task: DNS Resolution Trace

Pairs open command line tools like nslookup or dig. They enter domain names such as google.com and bbc.co.uk, record the IP addresses returned and query steps shown. Groups then compare results and diagram the resolution path on chart paper.

Differentiate between an IP address and a domain name.

Facilitation Tip

For the DNS Resolution Trace, have students record each DNS server response they receive and annotate queries to visualize the delay between request and answer.

What to look for

Provide students with a scenario: 'You type www.google.com into your browser.' Ask them to list, in order, the three main types of DNS servers involved in resolving this request and briefly state the role of each. Also, ask them to identify if the IP address for google.com is likely public or private.

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

Activity 02

• Simulation Game
• 45 min · Small Groups

Network Scan: Classroom IP Hunt

Small groups install safe tools like Advanced IP Scanner. They scan the local Wi-Fi network to list device IPs and hostnames. Teams categorize public versus private addresses and discuss uniqueness needs.

Explain the process of DNS resolution when accessing a website.

Facilitation Tip

In the Network Scan, assign small groups to one device type (laptops, printers, phones) so they notice patterns in private IP ranges.

What to look for

Display two IP addresses on the board, one IPv4 (e.g., 172.16.254.1) and one IPv6 (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). Ask students to write down which is which and one key difference between the two formats.

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

Activity 03

• Simulation Game
• 40 min · Whole Class

Simulation Game: DNS Query Relay

Assign roles as client, resolver, root server, TLD server, and authoritative server. The client calls out a domain; servers relay queries step-by-step around the room. Switch roles twice and debrief on failure points.

Analyze the importance of unique identifiers for devices on a network.

Facilitation Tip

During the DNS Query Relay game, rotate the role of the root server every few minutes to show how queries distribute across the hierarchy.

What to look for

Pose the question: 'Imagine a large school network with hundreds of computers. Why is it essential for each computer to have a unique identifier, and what problems could arise if two computers accidentally had the same IP address?' Facilitate a class discussion on network collisions and data routing.

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

Activity 04

• Simulation Game
• 35 min · Individual

Debug Drill: IP Conflict Scenarios

Individuals read case studies of duplicate IPs causing network issues. They propose fixes like DHCP reservations, then test by pinging conflicting addresses on a simulated LAN using virtual machines if available.

Differentiate between an IP address and a domain name.

Facilitation Tip

In the Debug Drill, provide a real network tool like `ipconfig /all` so students see DHCP leases and compare static versus dynamic addresses.

What to look for

Provide students with a scenario: 'You type www.google.com into your browser.' Ask them to list, in order, the three main types of DNS servers involved in resolving this request and briefly state the role of each. Also, ask them to identify if the IP address for google.com is likely public or private.

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

A few notes on teaching this unit

Teach IP addresses by starting with students’ own devices—let them check their device’s IP, then force a network restart to observe changes. Avoid long lectures on binary math; instead, focus on how the address formats serve real devices. For DNS, use analogies like a phonebook but emphasize the distributed system, because research shows students grasp hierarchy better through role-play than diagrams.

Students will confidently explain the difference between IPv4 and IPv6, identify public and private IP roles, and describe the step-by-step DNS resolution process. They should also troubleshoot common network issues like IP conflicts with clear reasoning.

---

Watch Out for These Misconceptions

• During the Network Scan activity, watch for students assuming their device’s IP will always remain the same.

  After students record their IP addresses, have them disconnect and reconnect to the network, then update their scan sheets to observe and discuss dynamic versus static IPs in pairs.

• During the DNS Query Relay activity, watch for students thinking DNS is a single central service that stores all domain records.

  During the relay, pause after each server role to ask students to identify which part of the domain hierarchy they represent, reinforcing the distributed nature of DNS.

• During the DNS Resolution Trace activity, watch for students equating a domain name directly to its IP address as a permanent pairing.

  After tracing a live lookup, ask students to revisit the same domain minutes later and compare IPs, then discuss why the same name can point to different addresses over time.

---

Methods used in this brief

• Simulation Game