| 1 |
Source: net-dns-fingerprint |
| 2 |
Section: net |
| 3 |
Priority: optional |
| 4 |
Maintainer: Thorsten Alteholz <[email protected]> |
| 5 |
Build-Depends: debhelper (>= 11) |
| 6 |
, perl (>= 5.6.0-16) |
| 7 |
Standards-Version: 4.3.0 |
| 8 |
Homepage: https://github.com/kirei/fpdns |
| 9 |
Vcs-Browser: https://salsa.debian.org/alteholz/net-dns-fingerprint |
| 10 |
Vcs-Git: https://salsa.debian.org/alteholz/net-dns-fingerprint.git |
| 11 |
|
| 12 |
Package: libnet-dns-fingerprint-perl |
| 13 |
Section: perl |
| 14 |
Architecture: all |
| 15 |
Depends: ${shlibs:Depends}, ${misc:Depends}, ${perl:Depends}, libnet-dns-perl (>=0.77) |
| 16 |
Description: library to determine DNS server vendor, product and version |
| 17 |
Identifying individual nameserver implementations is based on "borderline" |
| 18 |
protocol behaviour. The DNS protocol offers a multitude of message bits, |
| 19 |
response types, opcodes, classes, query types and label types in a fashion |
| 20 |
that makes some mutually exclusive while some are not used in a query |
| 21 |
messages at all. |
| 22 |
. |
| 23 |
Not every implementation offers the full set of features the DNS protocol |
| 24 |
set currently has. Some implementations offer features outside the protocol |
| 25 |
set, and there are implementations that do not conform to standards. |
| 26 |
. |
| 27 |
Amongst the servers it is able to identify are: |
| 28 |
. |
| 29 |
- VGRS ATLAS |
| 30 |
- BIND (v4, v8, v9) |
| 31 |
- eNom DNS |
| 32 |
- Incognito DNS commander |
| 33 |
- MARADNS |
| 34 |
- MS Server NT4/2000/2003 |
| 35 |
- MyDNS |
| 36 |
- Net::DNS::Namesever |
| 37 |
- Nominnum ANS/CNS |
| 38 |
- NonSequitur DNS |
| 39 |
- NSD |
| 40 |
- Oak DNS |
| 41 |
- Pliant DNS Server |
| 42 |
- Posadis |
| 43 |
- PowerDNS |
| 44 |
- QuickDNS |
| 45 |
- Rbldnsd |
| 46 |
- Simple DNS plus |
| 47 |
- TinyDNS |
| 48 |
- TotD |
| 49 |
- UltraDNS |
| 50 |
- pdnsd |
| 51 |
- Yaku-NS |
| 52 |
- DeleGate DNS proxy |
| 53 |
- sheerdns |
| 54 |
- dproxy |
| 55 |
- dnrd |
| 56 |
- JDNSS |
| 57 |
- javadns jnamed |
| 58 |
- Nomde DNS tunnel |
| 59 |
- Viking DNS server |
| 60 |
- small HTTP server |
| 61 |
- Cisco Network Registrar |
| 62 |
- Netnumber ENUM server |
| 63 |
- RaidenDNSD |
| 64 |
- Runtop Implementation |
| 65 |
- Mikrotik Implementation |
| 66 |
- Axis Video Network Implementation |
| 67 |
- Fasthosts Envisage DNS server |
| 68 |
- WinGate DNS |
| 69 |
- Ascenvision SwiftDNS |
| 70 |
- Nortel Networks Instant Internet |
| 71 |
- Nortel Networks Alteon ACEswitch |
| 72 |
- Aethra ATOS Stargate ADSL |
| 73 |
- 3Com Office Connect Remote |
| 74 |
- 4d WebSTAR |
| 75 |
- Netopia Implementation |
| 76 |
- DNS4me |
| 77 |
- Tzolkin DNS service |
| 78 |
- jdns javadns service |
| 79 |
- dents |
| 80 |
. |
| 81 |
This module is called: Net::Dns::Fingerprint |
| 82 |
|
| 83 |
Package: fpdns |
| 84 |
Architecture: all |
| 85 |
Depends: libnet-dns-fingerprint-perl, libio-socket-inet6-perl, ${misc:Depends} |
| 86 |
Description: remotely determine DNS server version |
| 87 |
A nameserver basically responds to a query. Interoperability is an |
| 88 |
obvious requirement here. The standard protocol behaviour of different |
| 89 |
DNS implementations is expected to be the same. |
| 90 |
. |
| 91 |
The reality is quite different though. fpdns uses a series of borderline |
| 92 |
DNS queries to determine the vendor, product and version of a nameserver. |