DNS is an amazing protocol. After starting life as a simple mechanism for name resolution, it is now used to enforce TLS rules, prevent email impersonation, authorize users, protect endpoints, enable service discovery, and much more. DNS services run across a range of devices and provide quite a bit of information about the environment, given the right queries. This post describes the techniques used by the Beta 2 version of Rumble Network Discovery to identify DNS services.
version.bind TXT response is supported by a handful of common DNS implementations, including ISC BIND,
and returns the name and version number of the service. This can be correlated against public fingerprints
to determine the operating system and version. Querying this by hand is easy with
$ dig version.bind txt chaos @target-dns version.bind. 0 CH TXT "9.11.3-1ubuntu1.5-Ubuntu"
hostname.bind TXT response is less common, but supported by newer versions of ISC BIND and a few other DNS
server implementations. This query returns the hostname of the DNS server itself. This is also simple to query by hand using
$ dig hostname.bind txt chaos @target-dns hostname.bind. 0 CH TXT "ns01"
Rumble will send an
A record lookup for a common internet domain name.This lookup returns the resolved address for the
name, indicating whether a DNS-based captive portal is in place, and whether DNS queries are being modified. This lookup
is equivalent the following command:
$ dig www.google.com A @target-dns www.google.com. 30 IN A 184.108.40.206
In addition to queries above, Rumble will ask the server for a PTR record for it’s own IPv4 address. This can return the
internally-configured hostname of the server, making identification more accurate, especially when normal reverse DNS and the
hostname.bind result is not available. An example of doing this query using the
$ dig 254.0.168.192.in-addr.arpa PTR @target-dns 254.0.168.192.in-addr.arpa. 20384 IN PTR firewall.lab.
Rumble will send a DNS query for a randomized subdomain of
rumble.network with the destination server address and timestamp
encoded into the request. A custom DNS server handles these requests, echoes the timestamp, and returns the IP addresses
of the requesting DNS resolvers back to the server, which forwards it on to the Rumble scan engine. This process acts as
a DNS traceroute and can identify problems with the destination server’s performance and configuration. The DNS service
details within the Rumble console will show the upstream resolvers:
Rumble will send a second DNS query for a randomized subdomain of
rumble.network, identical to the first, except using a different
prefix (e0 vs t0) and with the EDNS0 flag set. If the destination server supports the Client Subnet extension, this will be sent
rumble.network DNS server, which will encode the received subnet information back into the response. This can identify the
egress network used by the DNS server, which can be helpful when diagnosing configuration issues. An example
The five queries described above are designed to be safe and informative, but are just the beginning of Rumble’s support for DNS. We are continuing to look into service discovery and specific product fingerprinting that would help with asset identication and inventory. If you haven’t had a chance to try Rumble yet, please give it a shot and share your thoughts.
Our last post covered some of the ways that Rumble gathers information from DNS services. While working on the tracer implementation, we identified a trick that other folks might find it useful. It turns out that most DNS resolvers do not filter the address ranges they will contact when handling a request, allowing for remote subnet “ping scans” with a little work. This technique isn’t foolproof, and is probably not new, but it may have interesting security implications.