Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
9 changed files
with
185 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
.. _message-edns: | ||
|
||
Message EDNS Options | ||
-------------------- | ||
|
||
EDNS allows for larger messages and also provides an extension | ||
mechanism for the protocol. EDNS *options* are typed data, and are | ||
treated much like Rdata. For example, if dnsython encouters the EDNS | ||
``ECS`` option code when parsing a DNS wire format message, it | ||
will create a ``dns.edns.ECSOption`` object to represent it. | ||
|
||
.. autodata:: dns.edns.NSID | ||
.. autodata:: dns.edns.DAU | ||
.. autodata:: dns.edns.DHU | ||
.. autodata:: dns.edns.N3U | ||
.. autodata:: dns.edns.ECS | ||
.. autodata:: dns.edns.EXPIRE | ||
.. autodata:: dns.edns.COOKIE | ||
.. autodata:: dns.edns.KEEPALIVE | ||
.. autodata:: dns.edns.PADDING | ||
.. autodata:: dns.edns.CHAIN | ||
|
||
.. autoclass:: dns.edns.Option | ||
:members: | ||
|
||
.. autoclass:: dns.edns.GenericOption | ||
:members: | ||
|
||
.. autoclass:: dns.edns.ECSOption | ||
:members: | ||
|
||
.. autofunction:: dns.edns.get_option_class | ||
.. autofunction:: dns.edns.option_from_wire |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
.. _message-flags: | ||
|
||
Message Flags | ||
============= | ||
|
||
DNS message flags are used for signalling of various kinds | ||
in the DNS protocol. For example, the ``QR`` flag indicates | ||
that a message is a response to a prior query. | ||
|
||
Messages flags are encoded in two locations: the DNS header | ||
and the EDNS flags field. | ||
|
||
Header Flags | ||
------------ | ||
|
||
.. autodata:: dns.flags.QR | ||
.. autodata:: dns.flags.AA | ||
.. autodata:: dns.flags.TC | ||
.. autodata:: dns.flags.RD | ||
.. autodata:: dns.flags.RA | ||
.. autodata:: dns.flags.AD | ||
.. autodata:: dns.flags.CD | ||
|
||
.. autofunction:: dns.flags.from_text | ||
.. autofunction:: dns.flags.to_text | ||
|
||
EDNS Flags | ||
---------- | ||
|
||
.. autodata:: dns.flags.DO | ||
|
||
.. autofunction:: dns.flags.edns_from_text | ||
.. autofunction:: dns.flags.edns_to_text |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
.. _message-opcode: | ||
|
||
Message Opcodes | ||
--------------- | ||
|
||
DNS Opcodes describe what kind of operation a DNS message is requesting | ||
or replying to. Opcodes are embedded in the flags field in the DNS | ||
header. | ||
|
||
.. autodata:: dns.opcode.QUERY | ||
.. autodata:: dns.opcode.IQUERY | ||
.. autodata:: dns.opcode.STATUS | ||
.. autodata:: dns.opcode.NOTIFY | ||
.. autodata:: dns.opcode.UPDATE | ||
|
||
.. autofunction:: dns.opcode.from_text | ||
.. autofunction:: dns.opcode.to_text | ||
.. autofunction:: dns.opcode.from_flags | ||
.. autofunction:: dns.opcode.to_flags | ||
.. autofunction:: dns.opcode.is_update |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
.. _message-rcode: | ||
|
||
Message Rcodes | ||
-------------- | ||
|
||
A DNS Rcode describes the result of a DNS request. If EDNS is not in | ||
use, then the rcode is encoded solely in the DNS header. If EDNS is | ||
in use, then the rcode is encoded using bits form both the header and | ||
the EDNS OPT RR. | ||
|
||
.. autodata:: dns.rcode.NOERROR | ||
.. autodata:: dns.rcode.FORMERR | ||
.. autodata:: dns.rcode.SERVFAIL | ||
.. autodata:: dns.rcode.NXDOMAIN | ||
.. autodata:: dns.rcode.NOTIMP | ||
.. autodata:: dns.rcode.REFUSED | ||
.. autodata:: dns.rcode.YXDOMAIN | ||
.. autodata:: dns.rcode.YXRRSET | ||
.. autodata:: dns.rcode.NXRRSET | ||
.. autodata:: dns.rcode.NOTAUTH | ||
.. autodata:: dns.rcode.NOTZONE | ||
.. autodata:: dns.rcode.BADVERS | ||
|
||
.. autofunction:: dns.rcode.from_text | ||
.. autofunction:: dns.rcode.to_text | ||
.. autofunction:: dns.rcode.from_flags | ||
.. autofunction:: dns.rcode.to_flags |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters