adulau/pdns-qof
1
0
Fork 0
mirror of https://github.com/adulau/pdns-qof.git synced 2024-11-22 18:17:04 +00:00
Code Issues Projects Releases Packages Wiki Activity

rrtype: Resource Record (RR) TYPEs and not "DNS Label types" (dnsop feedback)

Browse source
This commit is contained in:
Alexandre Dulaunoy 2014-02-02 07:10:45 +01:00
parent c07abd7429
commit 3c5f0ffd48
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
i-d/pdns-qof.xml
View file

@ -201,7 +201,7 @@ CR = %x0D
<t>This field returns the resource record type as seen by the passive DNS. The key is rrtype and the value is in the interpreted record type. If the value cannot be interpreted the <t>This field returns the resource record type as seen by the passive DNS. The key is rrtype and the value is in the interpreted record type. If the value cannot be interpreted the
decimal value is returned following the principle of transparency as described in <xref target="RFC3597">RFC 3597</xref>. decimal value is returned following the principle of transparency as described in <xref target="RFC3597">RFC 3597</xref>.
The resource record type can be any values as described by IANA in the DNS parameters document in the section 'DNS Label types' (http://www.iana.org/assignments/dns-parameters). The resource record type can be any values as described by IANA in the DNS parameters document in the section 'Resource Record (RR) TYPEs' (http://www.iana.org/assignments/dns-parameters).
Currently known and supported textual descriptions of rrtypes are: A, AAAA, CNAME, PTR, SOA, TXT, DNAME, NS, SRV, RP, NAPTR, HINFO, A6. Currently known and supported textual descriptions of rrtypes are: A, AAAA, CNAME, PTR, SOA, TXT, DNAME, NS, SRV, RP, NAPTR, HINFO, A6.
A client MUST be able to understand these textual rrtype values represented as a JSON string. In addition, a client MUST be able to handle a decimal value (as mentioned above) as answer represented as a JSON number. A client MUST be able to understand these textual rrtype values represented as a JSON string. In addition, a client MUST be able to handle a decimal value (as mentioned above) as answer represented as a JSON number.
</t> </t>