Skip to main content

Module op

Module op 

Expand description

Operations to send with a Client or server, e.g. Query, Message, or UpdateMessage can be used together to either query or update resource records sets.

Modules§

update_message
Update related operations for Messages

Structs§

DnsRequest
A DNS request object
DnsRequestOptions
A set of options for expressing options to how requests should be treated
DnsResponse
A DNS response object
Edns
Edns implements the higher level concepts for working with extended dns as it is used to create or be created from OPT record data.
EdnsFlags
EDNS flags
Flags
All the flags of the request/response header
Header
Metadata for the Message struct.
LowerQuery
Identical to Query, except that the Name is guaranteed to be in lower case form.
Message
The basic request and response data structure, used for all DNS protocols.
MessageParts
Consumes Message giving public access to fields in Message so they can be destructured and taken by value
Query
Query struct for looking up resource records, basically a resource record without RDATA.
SerialMessage
A DNS message in serialized form, with either the target address or source address

Enums§

MessageType
Message types are either Query (also Update) or Response
OpCode
Operation code for queries, updates, and responses
ResponseCode
The status code of the response to a query.

Constants§

DEFAULT_RETRY_FLOOR
Default retry interval floor. This value is somewhat arbitrary, but is based on observed, real-world latencies and offers the chance to send three queries in a second to maximize the chance of a successful response in periods of high packet loss without overwhelming upstream servers.

Traits§

EmitAndCount
A trait that defines types which can be emitted as a set, with the associated count returned.
UpdateMessage
To reduce errors in using the Message struct as an Update, this will do the call throughs to properly do that.

Functions§

emit_message_parts
Emits the different sections of a message properly