INSIDEDNSPacket Quest

Sparks0
Shields0
Score0
Sparks Dash recharge Glitches

Packet Quest

Run the maze, collect sparks and dash through glitches. Find the right servers to bring your client an answer.

↑ ↓ ← → Hold to runSpace Dash

You can stop and read at any point.

Start your journey. First stop: the resolver.

Packet Quest

  1. Run. Hold arrow keys, WASD, or a touch arrow. Hold your next direction just before a corner to turn smoothly.
  2. Collect. Lights give points. Collect five in a row for a multiplier; keep going to reach ×4. More than five empty steps break the streak.
  3. Dash. Press Space or Dash to cross up to four tiles and pass through glitches safely. Blue batteries and server deliveries restore a charge.
  4. Deliver. Reach the glowing server. Its reply returns automatically to the resolver. Choose the next recipient with the buttons or keys 1–4.

Glitches appear from level 3 and advance as you move. A hit costs a shield; reaching a server restores one. Losing all three shields ends the run. Stop moving whenever you need to read. P pauses.

Sparks give 10–40 points, batteries 50, deliveries 250, correct routing decisions 100, and dashing through a glitch 75. Completing the mission adds 1,000. Wrong routing choices cost 150, hints 100, hits 75, and moves beyond the shortest route 2 each. Stars reward accurate routing, fewer hits and an efficient route.

Daily mazes are shared and change at midnight UTC. Campaign stars stay in this browser. Scores from the original maze are kept separately from this edition.

Your callsign

Pick from these approved words. No free-text names or personal details appear on the leaderboard.

Changes apply to your next run. Callsigns are shared nicknames, not unique accounts.

Leaderboard

This challenge

Best replay-checked score per callsign. Replays check game rules, not player identity or unaided learning.

What this means

DNS model and sources

These bounded, offline scenarios teach the roles of clients, recursive resolvers and authoritative servers. Domain names are fictional props here; no requests are sent to them. IP examples use documentation ranges.

Real resolvers can start from cached delegations, retry multiple servers, prefetch, validate DNSSEC and apply policies not modeled here. A DNS response does not guarantee that a website or mail service is healthy.

Packet Quest’s walking courier, congestion and move score are game mechanics. Each delivery represents a separate DNS question, reply, or return of control after a timeout. The resolver chooses the next query. TTL waits in detective cases advance simulated time, never all global caches.

Progress and stars are self-reported practice records, not certification or proof of learning. For a class, ask learners to explain the evidence and predict a different scenario.