From 05a152d154a015986c6e95635324300e68c1049e Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Tue, 10 Dec 2013 07:15:26 +0100 Subject: [PATCH] Some notes removed --- i-d/pdns-qof.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i-d/pdns-qof.xml b/i-d/pdns-qof.xml index d2b9bea..58e70f3 100644 --- a/i-d/pdns-qof.xml +++ b/i-d/pdns-qof.xml @@ -190,7 +190,7 @@ The document does not describe the protocol (e.g. whois, HTTP REST or XMPP) nor
- This field returns the data of the queried resource. In general, this is to be interpreted as string. Depending on the rtype, this can be an IPv4 or IPv6 address, a domain name (as in the case of CNAMEs), an SPF record, etc. A client MUST be able to interpret any value which is legal as the right hand side in a DNS zone file RFC 1035 and RFC 1034. If the rdata came from an unknown DNS resource records, the server must follow the transparency principle as described in RFC 3597. (binary stream if any? base64?) + This field returns the data of the queried resource. In general, this is to be interpreted as string. Depending on the rtype, this can be an IPv4 or IPv6 address, a domain name (as in the case of CNAMEs), an SPF record, etc. A client MUST be able to interpret any value which is legal as the right hand side in a DNS zone file RFC 1035 and RFC 1034. If the rdata came from an unknown DNS resource records, the server must follow the transparency principle as described in RFC 3597.
This field returns the first time that the record / unique tuple (rrname, rrtype, rdata) has been seen by the passive DNS. The date is expressed in seconds (decimal ascii) since 1st of January 1970 (unix timestamp). The time zone MUST be UTC.