From a121fb4e7d44f83ad483da5374e106e430471e74 Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Sun, 2 Feb 2014 07:43:24 +0100 Subject: [PATCH] rdata clarification (dnsop feedback) If resource records are multiple, an array is returned. Each record from the array is represented as a JSON string. If resource record returned is signle, it's a string. --- 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 79d79b0..5b0ed73 100644 --- a/i-d/pdns-qof.xml +++ b/i-d/pdns-qof.xml @@ -207,7 +207,7 @@ CR = %x0D
- This field returns the data of the queried resource. In general, this is to be interpreted as string. Depending on the rrtype, 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 resource records of the queried resource. When multiple resource records are returned, rdata MUST be a JSON array. In the case of a single resource record is returned, rdata MUST be a JSON string. Each resource record is represented as a JSON string. Depending on the rrtype, 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) since 1st of January 1970 (Unix timestamp). The time zone MUST be UTC.