Home / For Teachers / Game 2

TEACHER INFO · GAME 2

DNS Quest 2: Hex Strikes Back

A harder follow-up. Students investigate a poisoned resolver, see the attack from the attacker’s side in a sandboxed simulator, then fix it.

At a glance

CourseAP Cybersecurity, Unit 3: Securing Networks
TopicDNS poisoning (topic 3.1.A)
When to useA few days after Game 1, as review
Play timeAbout 30 to 35 minutes
StyleLess guided than Game 1. There is no arrow telling students where to go; the goal names a place, not the action.
Points30 for closing the case, plus Bonus Challenge extra credit (each student gets 6 questions from a bank of 10)
Turn inThe case file, which includes a verification code

The three acts

  1. Investigate (defender). Use a help-desk terminal to compare what the school resolver says with what the site’s own name server says. Read an unlabeled cache board and flag the poisoned rows (one scary-looking row is a decoy). Then a three-scene lesson on why HTTPS did not save the victim: plain HTTP, a wrong certificate, and HSTS.
  2. Be Hex (attacker). Inside a sandboxed Red Team Simulator, after a Rules of Engagement screen on ethics and the CFAA. Forge a reply against a predictable resolver, then see why random transaction IDs and random source ports make the attack nearly impossible.
  3. Fix and clean up (defender). Flush the cache (and see why that alone is not a fix), turn on the four real defenses, then run the attack waves and watch each get blocked. Clean only the infected devices on the network map. Finish with an Incident Report.

Study mode (not scored)

Support built in

After the case

Closing the case locks the graded run. Students can then roam Orange Vista for fun: ghost packets with networking facts, badges, gear and a small arcade game. None of it changes the score, XP or case file. It ends with a teaser for Game 3.