{"id":4000,"date":"2016-01-12T02:05:28","date_gmt":"2016-01-11T18:05:28","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=4000"},"modified":"2016-01-12T02:05:41","modified_gmt":"2016-01-11T18:05:41","slug":"dnscat2-dns-tunnel-tool","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2016\/01\/dnscat2-dns-tunnel-tool\/","title":{"rendered":"dnscat2 – DNS Tunnel Tool"},"content":{"rendered":"

This DNS tunnel tool named dnscat2 creates an encrypted tunnel over the DNS protocol primarily as a command-and-control (C&C) channel for penetration testers as outbound DNS is rarely blocked in networks.<\/p>\n

\"dnscat2<\/p>\n

This makes it a very effective tunnel out of almost every network.<\/p>\n

Overview<\/h3>\n

dnscat2 comes in two parts: the client and the server.<\/p>\n

The client is designed to be run on a compromised machine. It’s written in C and has the minimum possible dependencies. It should run just about anywhere (if you find a system where it doesn’t compile or run, please file a ticket, particularly if you can help me get access to said system).<\/p>\n

When you run the client, you typically specify a domain name. All requests will be sent to the local DNS server, which are then redirected to the authoritative DNS server for that domain (which you, presumably, have control of).<\/p>\n

If you don’t have an authoritative DNS server, you can also use direct connections on UDP\/53 (or whatever you choose). They’ll be faster, and still look like DNS traffic to the casual viewer, but it’s much more obvious in a packet log (all domains are prefixed with “dnscat.”, unless you hack the source). This mode will frequently be blocked by firewalls.<\/p>\n