Skip to content
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.

Implementation

jschlyter edited this page Feb 23, 2011 · 1 revision

The current software version is written as a proof-of-concept. In field tests, false positives were encountered when trying to identify a set of servers residing behind a load-balancing apparatus where the servers itself are of different implementations, when a specific implementation behaves like a forwarder, behind a firewall without statefull inspection or with ''Application Intelligence''.

The current set of strains identify the following implementations and some of their versions:

  • VGRS ATLAS
  • BIND 4/8/9
  • eNom DNS
  • Incognito DNS Commander
  • MARADNS
  • MS Server NT4/2000/2003
  • MyDNS
  • Net::DNS::Nameserver
  • Nominum ANS/CNS
  • NonSequitur DNS
  • NSD
  • Oak DNS
  • Pliant DNS Server
  • Posadis
  • PowerDNS
  • QuickDNS
  • Rbldnsd
  • Simple DNS plus
  • TinyDNS
  • TotD
  • UltraDNS
  • pdnsd
  • Yaku-NS
  • DeleGate DNS proxy
  • sheerdns
  • dproxy
  • dnrd
  • JDNSS
  • javadns jnamed
  • Nomde DNS tunnel
  • Viking DNS server
  • small HTTP server
  • Cisco Network Registrar
  • Netnumber ENUM server
  • RaidenDNSD
  • Runtop Implementation
  • Mikrotik Implementation
  • Axis Video Network Implementation
  • Fasthosts Envisage DNS server
  • WinGate DNS
  • Ascenvision SwiftDNS
  • Nortel Networks Instant Internet
  • Nortel Networks Alteon ACEswitch
  • Aethra ATOS Stargate ADSL
  • 3Com Office Connect Remote
  • 4d WebSTAR
  • Netopia Implementation
  • DNS4me
  • Tzolkin DNS service
  • jdns javadns service
  • dents
Clone this wiki locally