Ubuntu
net-dns-fingerprint package

net-dns-fingerprint 20190131-1.1 source package in Ubuntu

Changelog

net-dns-fingerprint (20190131-1.1) sid; urgency=medium

  * Non maintainer upload by the Reproducible Builds team.
  * No source change upload to rebuild on buildd with .buildinfo files.

 -- Holger Levsen <email address hidden>  Mon, 04 Jan 2021 14:52:36 +0100

Upload details

Uploaded by:
Thorsten Alteholz
Uploaded to:
Sid
Original maintainer:
Thorsten Alteholz
Architectures:
all
Section:
net
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe net
Noble release universe net
Mantic release universe net
Lunar release universe net
Jammy release universe net

Builds

Hirsute: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
net-dns-fingerprint_20190131-1.1.dsc 2.0 KiB 650412008f4bcec597adb832a71bec120013fcbb74a7544778ec674a7c91efef
net-dns-fingerprint_20190131.orig.tar.gz 11.8 KiB be01317b1da366f8312cba800bb0f3ed25c6aff96d40265c7f535dc581271e94
net-dns-fingerprint_20190131-1.1.debian.tar.xz 8.3 KiB b5846a086ba26a514ba2a12a1efb1b2410579aa8e0c06f3b94f1d7a3bf3cd4c3

Available diffs

No changes file available.

Binary packages built by this source

fpdns: remotely determine DNS server version

 A nameserver basically responds to a query. Interoperability is an
 obvious requirement here. The standard protocol behaviour of different
 DNS implementations is expected to be the same.
 .
 The reality is quite different though. fpdns uses a series of borderline
 DNS queries to determine the vendor, product and version of a nameserver.

libnet-dns-fingerprint-perl: library to determine DNS server vendor, product and version

 Identifying individual nameserver implementations is based on "borderline"
 protocol behaviour. The DNS protocol offers a multitude of message bits,
 response types, opcodes, classes, query types and label types in a fashion
 that makes some mutually exclusive while some are not used in a query
 messages at all.
 .
 Not every implementation offers the full set of features the DNS protocol
 set currently has. Some implementations offer features outside the protocol
 set, and there are implementations that do not conform to standards.
 .
 Amongst the servers it is able to identify are:
 .
  - VGRS ATLAS
  - BIND (v4, v8, v9)
  - eNom DNS
  - Incognito DNS commander
  - MARADNS
  - MS Server NT4/2000/2003
  - MyDNS
  - Net::DNS::Namesever
  - Nominnum 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
 .
 This module is called: Net::Dns::Fingerprint