Logs DNS requests and responses through a HSL log publisher.
This iRules parses the dns protocol natively, there is no requirement for a DNS license.
This dns parser is based on the dns parser from the tcllib: https://github.com/tcltk/tcllib/blob/master/modules/dns/dns.tcl.
Supports:
- DNS over UDP
- DNS over TCP
- Multiple queries/answers in one TCP connection
- DNS pipelining
Supported DNS records:
- A
- AAAA
- NS
- CNAME
- PTR
- MX
- SRV
- NAPTR
- TXT
- SOA
Response data from other record types are logged without parsing.
Parses:
- Query (Request and response)
- Answer (response only)
- Authority (response only)
- Additional (response only)
Multiple entries are supported for each section.
dns_parser.irule- save as
dns_parseriRule - do not assign to a VS
- save as
dns-logging-config.irule- save as
dns-logging-configiRule - do not assign to a VS
- customize logging destination (Log Publisher)
- save as
dns-logging-tcp.irule- save as
dns-logging-tcpiRule - assign to a VS with an attached tcp profile
- save as
dns-logging-udp.irule- save as
dns-logging-udpiRule - assign to a VS with an attached udp profile
- save as
- Request:
client_ip="<Client IP>" target_ip="0.0.0.0" v_server="<VS>" msg_type="query" request_id="<Id>" payload="<Parsed payload>" - Response:
client_ip="<Client IP>" target_ip="<Backend IP>" v_server="<VS>" msg_type="<Section>" request_id="<Id>" payload="<Parsed payload>"
# Request
client_ip="1.1.1.1" target_ip="0.0.0.0" v_server="/Common/vs_dns-udp" msg_type="query" request_id="2172" payload="{name google.com type CNAME class IN}"
# Response
client_ip="1.1.1.1" target_ip="2.2.2.2" v_server="/Common/vs_dns-udp" msg_type="query" request_id="2172" payload="{name google.com type CNAME class IN}, flags: QR QUERY RD RA, query: 1, answer: 0, authority: 1, additional: 1, status ok"
client_ip="1.1.1.1" target_ip="2.2.2.2" v_server="/Common/vs_dns-udp" msg_type="authority" request_id="2172" payload="{name google.com type SOA class IN ttl 23 rdata {MNAME ns1.google.com RNAME dns-admin.google.com SERIAL 547140803 REFRESH 900 RETRY 900 EXPIRE 1800 MINIMUM 60}}"
client_ip="1.1.1.1" target_ip="2.2.2.2" v_server="/Common/vs_dns-udp" msg_type="additional" request_id="2172" payload="{name {} type OPT class 4000 ttl 0 rdata {}}"
# Request
client_ip="1.1.1.1" target_ip="0.0.0.0" v_server="/Common/vs_dns-udp" msg_type="query" request_id="64482" payload="{name google.com type A class IN}"
# Response
client_ip="1.1.1.1" target_ip="2.2.2.2" v_server="/Common/vs_dns-udp" msg_type="query" request_id="64482" payload="{name google.com type A class IN}, flags: QR QUERY RD RA, query: 1, answer: 1, authority: 0, additional: 1, status ok"
client_ip="1.1.1.1" target_ip="2.2.2.2" v_server="/Common/vs_dns-udp" msg_type="answer" request_id="64482" payload="{name google.com type A class IN ttl 292 rdata 216.58.212.174}"
client_ip="1.1.1.1" target_ip="2.2.2.2" v_server="/Common/vs_dns-udp" msg_type="additional" request_id="64482" payload="{name {} type OPT class 4000 ttl 0 rdata {}}"
Request and responses have the same structure.
TCP DNS packets starts with a 16 bit size field.
+------------+
| Size | Size of request or response (TCP only)
+------------+
| Header | DNS Header
+------------+
| Question | Question for the name server (in requests and responses)
+------------+
| Answer | Answers to the question (only in responses)
+------------+
| Authority | Authority section (only in responses)
+------------+
| Additional | Additional section (only in responses)
+------------+
The header has a fixed length of 12 bytes.
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 0| 1| 2| 3| 4| 5| 6| 7| 8| 9| 0| 1| 2| 3| 4| 5|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| ID, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|QR| OPCODE |AA|TC|RD|RA| ZZ | RCODE |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Query count, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Answer count, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Authority count, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Additional count, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
- QR: Query (0) or response (1)
- OPCODE: kind of query
- AA: Authoritative answer
- TC: Truncation
- RD: Recursion desired
- RA: Recursion available
- ZZ: Reserved for future use
- RCODE: Response code
Starts at offset 12 and has a variable length.
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 0| 1| 2| 3| 4| 5| 6| 7| 8| 9| 0| 1| 2| 3| 4| 5|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| |
| QNAME (variable length) |
| |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| QTYPE, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| QCLASS, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
This sections are only present in a DNS response and follow directly after the question.
The DNS header specifies how many answer, authority and additional sections are included in the response (in this order).
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 0| 1| 2| 3| 4| 5| 6| 7| 8| 9| 0| 1| 2| 3| 4| 5|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| |
| NAME (variable length) |
| |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TYPE, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| CLASS, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TTL, 32 bit integer |
| |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| RDLENGTH, 16 bit integer |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| |
| RDATA (variable length) |
| |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Domain names are represented as a sequence of labels. Each label consists of a length byte followed by that number of bytes. The name is terminated with a zero length. Dots between the domain name labels are omitted.
Example: [3]www[6]axians[2]de[0]
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent