CyberKit

DNS Tunneling

Smuggling data or C2 inside DNS queries and responses.

What it is

DNS tunneling encodes data within DNS queries and responses, abusing a protocol that is almost always allowed out of networks to carry C2 traffic or exfiltrate data.

Why it matters

Because DNS is rarely blocked and often under-inspected, tunneling slips past controls that only watch HTTP. Unusually long, high-volume, or high-entropy subdomains are the tell.

In practice

Long, random-looking subdomains under a single domain carrying encoded command output.

What to look for

  • Long, high-entropy subdomains under one parent domain.
  • Unusual volumes of TXT or NULL queries.
  • One host making far more queries to one domain than anyone else.

Common mistake

Looking only at the domains. The pattern of query length, type and volume gives it away even when the domain looks fine.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Wireshark Open source

    Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.

  • Zeek Open source

    Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.

  • Suricata Open source

    An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.

  • Arkime Open source

    Indexes full packet capture at scale so you can search and pull sessions later. Our notes.

ATT&CK techniques

Read next

Sources