ChangeLog

# ChangeLog for net-dns/fpdns
# Copyright 1999-2008 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/net-dns/fpdns/ChangeLog,v 1.1 2008/04/16 21:20:20 wschlich Exp $

*fpdns-0.9.1 (16 Apr 2008)

16 Apr 2008; Wolfram Schlich +metadata.xml,
+fpdns-0.9.1.ebuild:
initial import

Manifest

DIST fpdns-0.9.1.tar.gz 8583 RMD160 610645f0302c18a26741d2e9b45296340272f0b3 SHA1 c880bbc47be0e9dda5b79cfa8860d1f4bc39a214 SHA256 07f89105ba5c7a7da5cf773cba3473fcd62c3fe40a8db194f994d4a3d67c4cdf
EBUILD fpdns-0.9.1.ebuild 519 RMD160 f868b53cbe7d4dbfbf138e8236bd92b32c392bf5 SHA1 cc93d13b8dbf0506b8ae4059e439f2688f7ab253 SHA256 912d2b7937f42270b5cfde8b0a2ab01c2e5cbbeed11851ba958cc58191ddc3d1
MISC ChangeLog 338 RMD160 f18bf8c98905a4eb8228faa2215cfe41312dc014 SHA1 821d73bcd826d9866aff39716e9a5cc293b822b6 SHA256 edce13d65420b5007ea98924b99ffad2b0bb88bf97284ee991a2a69b1e9ee860
MISC metadata.xml 1476 RMD160 97a9bb3dcf9080407171df3e65daeb7175fdbf86 SHA1 e9a8192bf5039ebb7951269aaca4b506ae92cb97 SHA256 1386d7a2bd301b2ab7587d80f2a1021733d51d65ffcc9054ca7c1cc63536fae9

fpdns-0.9.1.ebuild

# Copyright 1999-2008 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/net-dns/fpdns/fpdns-0.9.1.ebuild,v 1.1 2008/04/16 21:20:20 wschlich Exp $

IUSE=""
DESCRIPTION="Fingerprinting DNS servers"
HOMEPAGE="http://www.rfc.se/fpdns/"
SRC_URI="http://www.rfc.se/fpdns/distfiles/${P}.tar.gz"
LICENSE="fpdns"
SLOT="0"
KEYWORDS="~amd64 ~x86"
RDEPEND=">=dev-perl/Net-DNS-0.42"

src_compile() { :; }

src_install() {
newbin fpdns.pl fpdns
doman fpdns.1
}

metadata.xml




no-herd

wschlich@gentoo.org
Wolfram Schlich
Primary maintainer


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.

Requirements for protocol behaviour of DNS implementations is widely documented
in the case of 'common' dns messages. The DNS protocol is over 20 years old and
since its inception, there have been over 40 independent DNS implementations,
while some implementations have over 20 versions.

The methodology used to identify 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.

Also, new features added to - or bugs removed allow for differentiations between
versions of an implementation.