diff options
author | Edwin Groothuis <edwin@FreeBSD.org> | 2004-07-03 14:23:35 +0000 |
---|---|---|
committer | Edwin Groothuis <edwin@FreeBSD.org> | 2004-07-03 14:23:35 +0000 |
commit | a2f9c950793bb7f8cec162fdf61ab27257c9676b (patch) | |
tree | 541dbfb4aba5c155e44ef41777e0fc4ef888fade /dns/fpdns/pkg-descr | |
parent | 9448cc82dee36a3fd9a27727a88f2dc56467d348 (diff) | |
download | ports-a2f9c950793bb7f8cec162fdf61ab27257c9676b.tar.gz ports-a2f9c950793bb7f8cec162fdf61ab27257c9676b.zip |
Notes
Diffstat (limited to 'dns/fpdns/pkg-descr')
-rw-r--r-- | dns/fpdns/pkg-descr | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/dns/fpdns/pkg-descr b/dns/fpdns/pkg-descr new file mode 100644 index 000000000000..6fc344742c70 --- /dev/null +++ b/dns/fpdns/pkg-descr @@ -0,0 +1,23 @@ +fpdns - Fingerprinting DNS servers + +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. + +WWW: http://www.rfc.se/fpdns/ |