Hunting for DNS Tunneling with Zeek
When to Use
- When hunting for data exfiltration over DNS covert channels
- After threat intelligence indicates DNS-based C2 frameworks targeting your industry
- When dns.log shows unusually high query volumes to specific domains
- During investigation of suspected data theft where no HTTP/S exfiltration is found
- When monitoring for tools like iodine, dnscat2, DNSExfiltrator, or DNS-over-HTTPS tunneling
Prerequisites
- Zeek deployed on network tap or SPAN port capturing DNS traffic
- Zeek dns.log with full query and response fields
- SIEM platform for dns.log analysis (Splunk, Elastic)
- RITA (Real Intelligence Threat Analytics) for automated DNS analysis
- Passive DNS data for historical domain resolution context
Workflow
- Analyze Query Length Distribution: DNS tunneling encodes data in subdomain labels, producing queries significantly longer than normal. Normal DNS queries average 20-30 characters; tunneling queries often exceed 50+ characters. Calculate mean and standard deviation of query lengths per domain.
- Calculate Subdomain Entropy: Tunneling encodes data using Base32/Base64, producing high-entropy subdomain strings. Calculate Shannon entropy of subdomain labels -- values above 3.5 bits/character strongly suggest encoded data.
- Count Unique Subdomains Per Domain: Legitimate domains have relatively few unique subdomains. DNS tunneling generates hundreds or thousands of unique subdomains under a single parent domain.
- Monitor DNS Record Type Distribution: TXT, NULL, CNAME, and MX records can carry more data than A records. Excessive TXT queries to a single domain indicate data transfer via DNS.
- Detect High Query Volume: Flag domains receiving more than 100 queries per hour from a single source, especially when combined with high subdomain uniqueness.
- Analyze Query Timing: DNS tunneling tools produce regular query patterns (beaconing) or burst patterns (data transfer). Apply frequency analysis to DNS query timestamps.
- Cross-Reference with conn.log: Correlate DNS queries with connection metadata to identify the process or endpoint generating suspicious queries.
- Validate with Domain Intelligence: Check suspicious domains against WHOIS data, certificate transparency, and threat intelligence feeds.
Key Concepts
| Concept |
Description |
| T1071.004 |
Application Layer Protocol: DNS |
| T1048.003 |
Exfiltration Over Alternative Protocol: DNS |
| T1572 |
Protocol Tunneling |
| Shannon Entropy |
Measure of randomness in subdomain strings |
| Zeek dns.log |
DNS query/response metadata |
| RITA |
Automated DNS tunneling detection from Zeek logs |
| iodine |
IPv4-over-DNS tunneling tool |
| dnscat2 |
DNS-based command-and-control tool |
| DNSExfiltrator |
Data exfiltration tool using DNS requests |
Detection Queries
Zeek Script -- DNS Tunnel Detection
@load base/protocols/dns
module DNSTunnel;
export {
redef enum Notice::Type += { DNSTunnel::Long_DNS_Query };
const query_length_threshold = 50 &redef;
const query_count_threshold = 100 &redef;
}
event dns_request(c: connection, msg: dns_msg, query: string, qtype: count, qclass: count) {
if ( |query| > query_length_threshold ) {
NOTICE([$note=DNSTunnel::Long_DNS_Query,
$msg=fmt("Long DNS query detected: %s (%d chars)", query, |query|),
$conn=c]);
}
}
Splunk -- DNS Tunneling Indicators from Zeek
index=zeek sourcetype=bro_dns
| rex field=query "(?<subdomain>[^.]+)\.(?<basedomain>[^.]+\.[^.]+)$"
| stats count dc(subdomain) as unique_subs avg(len(query)) as avg_len max(len(query)) as max_len by src basedomain
| where count > 100 AND (unique_subs > 50 OR avg_len > 40)
| sort -unique_subs
Splunk -- High Entropy Subdomain Detection
index=zeek sourcetype=bro_dns
| rex field=query "^(?<subdomain>[^.]+)"
| where len(subdomain) > 20
| eval char_count=len(subdomain)
| stats count dc(query) as unique_queries avg(char_count) as avg_sub_len by src query_type_name basedomain
| where unique_queries > 30 AND avg_sub_len > 25
| sort -unique_queries
RITA Analysis
rita import /path/to/zeek/logs dataset_name
rita show-dns-fqdn-ips-long dataset_name
rita show-exploded-dns dataset_name
rita show-dns-tunneling dataset_name --csv > dns_tunnel_results.csv
Common Scenarios
- dnscat2 C2: Encodes command-and-control traffic in DNS CNAME/TXT queries with Base64-encoded subdomain labels. Produces high query volumes with long, high-entropy subdomains.
- iodine IPv4 Tunnel: Creates a virtual network interface tunneling all IP traffic through DNS. Generates massive DNS query volumes with NULL record types.
- Data Exfiltration via DNS: Sensitive data encoded in subdomain labels (e.g.,
aGVsbG8gd29ybGQ.exfil.attacker.com), sent as A or TXT queries. Each query carries ~63 bytes of data.
- DNS-over-HTTPS Tunneling: Bypasses traditional DNS monitoring by sending DNS queries over HTTPS to public resolvers (8.8.8.8, 1.1.1.1), requiring TLS inspection for detection.
- Cobalt Strike DNS Beacon: Uses DNS A/TXT records for C2 communication with configurable subdomain encoding schemes.
Output Format
Hunt ID: TH-DNSTUNNEL-[DATE]-[SEQ]
Source IP: [Internal IP]
Source Host: [Hostname]
Target Domain: [Base domain]
Query Count: [Total queries in window]
Unique Subdomains: [Count]
Avg Query Length: [Characters]
Max Query Length: [Characters]
Subdomain Entropy: [Bits per character]
Primary Record Type: [A/TXT/CNAME/NULL]
Data Volume Estimate: [Bytes exfiltrated]
Risk Level: [Critical/High/Medium/Low]
1---2name: hunting-for-dns-tunneling-with-zeek-23description: Detects DNS tunneling and covert-channel data exfiltration by analyzing4 Zeek dns.log for high-entropy subdomain queries, excessive query volume, abnormally5 long query lengths, and unusual DNS record types (TXT/NULL/CNAME). Use when hunting6 for DNS-based data exfiltration or C2 covert channels in network traffic, or when7 triaging suspicious DNS query volume/patterns surfaced by Zeek logs.8domain: cybersecurity9subdomain: threat-hunting10tags:11- threat-hunting12- dns-tunneling13- zeek14- data-exfiltration15- covert-channel16- mitre-t1071-00417- network-monitoring18version: '1.0'19author: mahipal20license: Apache-2.021d3fend_techniques:22- Application Protocol Command Analysis23- Network Isolation24- Network Traffic Analysis25- Client-server Payload Profiling26- DNS Traffic Analysis27nist_csf:28- DE.CM-0129- DE.AE-0230- DE.AE-0731- ID.RA-0532mitre_attack:33- T104634- T105735- T108236- T108337- T104838metadata:39 source: https://skillmd.com/skills/26zl/hunting-for-dns-tunneling-with-zeek-240---4142# Hunting for DNS Tunneling with Zeek4344## When to Use4546- When hunting for data exfiltration over DNS covert channels47- After threat intelligence indicates DNS-based C2 frameworks targeting your industry48- When dns.log shows unusually high query volumes to specific domains49- During investigation of suspected data theft where no HTTP/S exfiltration is found50- When monitoring for tools like iodine, dnscat2, DNSExfiltrator, or DNS-over-HTTPS tunneling5152## Prerequisites5354- Zeek deployed on network tap or SPAN port capturing DNS traffic55- Zeek dns.log with full query and response fields56- SIEM platform for dns.log analysis (Splunk, Elastic)57- RITA (Real Intelligence Threat Analytics) for automated DNS analysis58- Passive DNS data for historical domain resolution context5960## Workflow61621. **Analyze Query Length Distribution**: DNS tunneling encodes data in subdomain labels, producing queries significantly longer than normal. Normal DNS queries average 20-30 characters; tunneling queries often exceed 50+ characters. Calculate mean and standard deviation of query lengths per domain.632. **Calculate Subdomain Entropy**: Tunneling encodes data using Base32/Base64, producing high-entropy subdomain strings. Calculate Shannon entropy of subdomain labels -- values above 3.5 bits/character strongly suggest encoded data.643. **Count Unique Subdomains Per Domain**: Legitimate domains have relatively few unique subdomains. DNS tunneling generates hundreds or thousands of unique subdomains under a single parent domain.654. **Monitor DNS Record Type Distribution**: TXT, NULL, CNAME, and MX records can carry more data than A records. Excessive TXT queries to a single domain indicate data transfer via DNS.665. **Detect High Query Volume**: Flag domains receiving more than 100 queries per hour from a single source, especially when combined with high subdomain uniqueness.676. **Analyze Query Timing**: DNS tunneling tools produce regular query patterns (beaconing) or burst patterns (data transfer). Apply frequency analysis to DNS query timestamps.687. **Cross-Reference with conn.log**: Correlate DNS queries with connection metadata to identify the process or endpoint generating suspicious queries.698. **Validate with Domain Intelligence**: Check suspicious domains against WHOIS data, certificate transparency, and threat intelligence feeds.7071## Key Concepts7273| Concept | Description |74|---------|-------------|75| T1071.004 | Application Layer Protocol: DNS |76| T1048.003 | Exfiltration Over Alternative Protocol: DNS |77| T1572 | Protocol Tunneling |78| Shannon Entropy | Measure of randomness in subdomain strings |79| Zeek dns.log | DNS query/response metadata |80| RITA | Automated DNS tunneling detection from Zeek logs |81| iodine | IPv4-over-DNS tunneling tool |82| dnscat2 | DNS-based command-and-control tool |83| DNSExfiltrator | Data exfiltration tool using DNS requests |8485## Detection Queries8687### Zeek Script -- DNS Tunnel Detection88```zeek89@load base/protocols/dns90module DNSTunnel;9192export {93 redef enum Notice::Type += { DNSTunnel::Long_DNS_Query };94 const query_length_threshold = 50 &redef;95 const query_count_threshold = 100 &redef;96}9798event dns_request(c: connection, msg: dns_msg, query: string, qtype: count, qclass: count) {99 if ( |query| > query_length_threshold ) {100 NOTICE([$note=DNSTunnel::Long_DNS_Query,101 $msg=fmt("Long DNS query detected: %s (%d chars)", query, |query|),102 $conn=c]);103 }104}105```106107### Splunk -- DNS Tunneling Indicators from Zeek108```spl109index=zeek sourcetype=bro_dns110| rex field=query "(?<subdomain>[^.]+)\.(?<basedomain>[^.]+\.[^.]+)$"111| stats count dc(subdomain) as unique_subs avg(len(query)) as avg_len max(len(query)) as max_len by src basedomain112| where count > 100 AND (unique_subs > 50 OR avg_len > 40)113| sort -unique_subs114```115116### Splunk -- High Entropy Subdomain Detection117```spl118index=zeek sourcetype=bro_dns119| rex field=query "^(?<subdomain>[^.]+)"120| where len(subdomain) > 20121| eval char_count=len(subdomain)122| stats count dc(query) as unique_queries avg(char_count) as avg_sub_len by src query_type_name basedomain123| where unique_queries > 30 AND avg_sub_len > 25124| sort -unique_queries125```126127### RITA Analysis128```bash129rita import /path/to/zeek/logs dataset_name130rita show-dns-fqdn-ips-long dataset_name131rita show-exploded-dns dataset_name132rita show-dns-tunneling dataset_name --csv > dns_tunnel_results.csv133```134135## Common Scenarios1361371. **dnscat2 C2**: Encodes command-and-control traffic in DNS CNAME/TXT queries with Base64-encoded subdomain labels. Produces high query volumes with long, high-entropy subdomains.1382. **iodine IPv4 Tunnel**: Creates a virtual network interface tunneling all IP traffic through DNS. Generates massive DNS query volumes with NULL record types.1393. **Data Exfiltration via DNS**: Sensitive data encoded in subdomain labels (e.g., `aGVsbG8gd29ybGQ.exfil.attacker.com`), sent as A or TXT queries. Each query carries ~63 bytes of data.1404. **DNS-over-HTTPS Tunneling**: Bypasses traditional DNS monitoring by sending DNS queries over HTTPS to public resolvers (8.8.8.8, 1.1.1.1), requiring TLS inspection for detection.1415. **Cobalt Strike DNS Beacon**: Uses DNS A/TXT records for C2 communication with configurable subdomain encoding schemes.142143## Output Format144145```146Hunt ID: TH-DNSTUNNEL-[DATE]-[SEQ]147Source IP: [Internal IP]148Source Host: [Hostname]149Target Domain: [Base domain]150Query Count: [Total queries in window]151Unique Subdomains: [Count]152Avg Query Length: [Characters]153Max Query Length: [Characters]154Subdomain Entropy: [Bits per character]155Primary Record Type: [A/TXT/CNAME/NULL]156Data Volume Estimate: [Bytes exfiltrated]157Risk Level: [Critical/High/Medium/Low]158```