ProtoStackv0.1

Interactive Protocol Visualizer

Back to all protocols
IPv4
Network & CoreCore trackIntermediateOSI: Application LayerDefault Port: 53Standard: RFC 1034, RFC 1035

DNS

— Domain Name System

The Domain Name System (DNS) translates human-friendly hostnames like "google.com" into numerical IP addresses like "142.250.190.46", which computers use to identify each other on the network. Without DNS, users would need to memorize IP addresses for every website.

Read first: UDP, TCPContent reviewed 2026-11-18

Interactive Session: How DNS Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of DNS.

Threat Model & Attack Simulation

How this protocol is attacked in practice, what defenders can see, and which control stops it.

Threat model & attack simulation

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

DNS cache poisoning

Spoofing

A forged answer that matches the transaction ID and source port is cached and served to later clients.

Attackersimulated
DNStarget
Attack step 1 of 3
Trigger a lookup

The attacker causes the resolver to query a name it wants to poison.

What a defender can see

Unusual query bursts for one name.

Impact if unmitigated

Traffic redirection for every client behind the resolver.

Defences that matter
  • DNSSEC validation
  • Source port and transaction ID randomisation
  • Encrypted DNS to a trusted resolver

This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.

Protocol Specification & Architecture

Key characteristics, real-world deployment patterns, and trade-offs.

Core Technical Features

  • Hierarchical, distributed database structure
  • Uses UDP port 53 for standard queries and TCP for zone transfers/large responses
  • Recursive vs. Iterative query resolution
  • TTL (Time-To-Live) caching to reduce global network traffic

Real-World Use Cases

  • Web browser address resolution
  • Mail server routing via MX records
  • Service discovery via SRV records
  • Domain ownership verification via TXT records

Advantages & Strengths

  • Transparent to end-users
  • Extensible with DNSSEC for cryptographically validated lookups
  • Distributed resilience across 13 root server clusters globally

Limitations & Vulnerabilities

  • Traditional DNS traffic is unencrypted (mitigated by DoH/DoT)
  • Cache poisoning and DNS spoofing vulnerabilities if DNSSEC is absent
  • Propagation delays when TTLs are set high