BlackSponge
/
dns-lg
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Browse Source

RFC 8427. See #45

master
Stephane Bortzmeyer 3 years ago
parent
38cd2d39d3
commit
8dd39e5270
1 changed files with 4 additions and 3 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 7
      JSON.txt

7
JSON.txt
View File

@ -1,8 +1,9 @@
[This is the description of the JSON output format produced by the
*current* code. A work is going on at the IETF to specify a
*current* code. A work was going on at the IETF to specify this
DNS-in-JSON format
<https://tools.ietf.org/html/draft-bortzmeyer-dns-json>. The tool and
the IETF document may not agree at every moment.]
<https://datatracker.ietf.org/doc/draft-bortzmeyer-dns-json/> but it
is now dead. Another format, slightly different, has been
standardized, in RFC 8427.]
A DNS response is represented as a JSON object. The main members of
this object (the names are self-explanatory) are:

Write Preview
Loading…
Cancel
Save