diff options
| author | V3n3RiX <venerix@koprulu.sector> | 2022-10-20 07:59:50 +0100 |
|---|---|---|
| committer | V3n3RiX <venerix@koprulu.sector> | 2022-10-20 07:59:50 +0100 |
| commit | 2eda3a3b8ebdb3fc8552feb6f49e466d3bc8e88c (patch) | |
| tree | 69a469da2fa8c3f4920325ac5595300929f5d884 /net-dns/fpdns/metadata.xml | |
| parent | 9ed0c42eb618229fa6f45e10155ee535e1f605a2 (diff) | |
gentoo auto-resync : 20:10:2022 - 07:59:49
Diffstat (limited to 'net-dns/fpdns/metadata.xml')
| -rw-r--r-- | net-dns/fpdns/metadata.xml | 34 |
1 files changed, 17 insertions, 17 deletions
diff --git a/net-dns/fpdns/metadata.xml b/net-dns/fpdns/metadata.xml index 7b8047263afb..d6cd618589b3 100644 --- a/net-dns/fpdns/metadata.xml +++ b/net-dns/fpdns/metadata.xml @@ -3,26 +3,26 @@ <pkgmetadata> <!-- maintainer-needed --> <longdescription> -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. + 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. + 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. + 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. -</longdescription> + Also, new features added to - or bugs removed allow for differentiations between + versions of an implementation. + </longdescription> <upstream> <remote-id type="github">kirei/fpdns</remote-id> </upstream> |