Struct trust_dns_proto::xfer::dns_request::DnsRequest[][src]

pub struct DnsRequest { /* fields omitted */ }
Expand description

A DNS request object

This wraps a DNS Message for requests. It also has request options associated for controlling certain features of the DNS protocol handlers.

Implementations

Returns a new DnsRequest object

Get the set of request options associated with this request

Unwraps the raw message

Methods from Deref<Target = Message>

Truncates a Message, this blindly removes all response fields and sets truncated to true

see Header::set_id

see Header::set_message_type

see Header::set_op_code

see Header::set_authoritative

see Header::set_truncated

see Header::set_recursion_desired

see Header::set_recursion_available

see Header::set_authentic_data

see Header::set_checking_disabled

see Header::set_response_code

Add a query to the Message, either the query response from the server, or the request Query.

Adds an iterator over a set of Queries to be added to the message

Add an answer to the Message

Add all the records from the iterator to the answers section of the Message

Sets the answers to the specified set of Records.

Panics

Will panic if answer records are already associated to the message.

Add a name server record to the Message

Add all the records in the Iterator to the name server section of the message

Sets the name_servers to the specified set of Records.

Panics

Will panic if name_servers records are already associated to the message.

Add an additional Record to the message

Sets the additional to the specified set of Records.

Panics

Will panic if additional records are already associated to the message.

Add the EDNS section to the Message

This is supported on crate feature dnssec only.

Add a SIG0 record, i.e. sign this message

This must be used only after all records have been associated. Generally this will be handled by the client and not need to be used directly

This is supported on crate feature dnssec only.

Add a TSIG record, i.e. authenticate this message

This must be used only after all records have been associated. Generally this will be handled by the client and not need to be used directly

Gets the header of the Message

see Header::id()

see Header::message_type()

see Header::op_code()

see Header::authoritative()

see Header::truncated()

see Header::recursion_desired()

see Header::recursion_available()

see Header::authentic_data()

see Header::checking_disabled()

Return value

The ResponseCode, if this is an EDNS message then this will join the section from the OPT record to create the EDNS ResponseCode

Question        Carries the query name and other query parameters.

Provides mutable access to queries

Removes all the answers from the Message

Answer          Carries RRs which directly answer the query.

Provides mutable access to answers

Removes all the answers from the Message

Authority       Carries RRs which describe other authoritative servers.
                May optionally carry the SOA RR for the authoritative
                data in the answer section.

Provides mutable access to name_servers

Remove the name servers from the Message

Additional      Carries RRs which may be helpful in using the RRs in the
                other sections.

Provides mutable access to additionals

Remove the additional Records from the Message

All sections chained

RFC 6891, EDNS(0) Extensions, April 2013

6.1.1.  Basic Elements

 An OPT pseudo-RR (sometimes called a meta-RR) MAY be added to the
 additional data section of a request.

 The OPT RR has RR type 41.

 If an OPT record is present in a received request, compliant
 responders MUST include an OPT record in their respective responses.

 An OPT record does not carry any DNS data.  It is used only to
 contain control information pertaining to the question-and-answer
 sequence of a specific transaction.  OPT RRs MUST NOT be cached,
 forwarded, or stored in or loaded from Zone Files.

 The OPT RR MAY be placed anywhere within the additional data section.
 When an OPT RR is included within any DNS message, it MUST be the
 only OPT RR in that message.  If a query message with more than one
 OPT RR is received, a FORMERR (RCODE=1) MUST be returned.  The
 placement flexibility for the OPT RR does not override the need for
 the TSIG or SIG(0) RRs to be the last in the additional section
 whenever they are present.

Return value

Returns the EDNS record if it was found in the additional section.

If edns is_none, this will create a new default Edns.

Return value

the max payload value as it’s defined in the EDNS section.

Return value

the version as defined in the EDNS record

RFC 2535, Domain Name System Security Extensions, March 1999

A DNS request may be optionally signed by including one or more SIGs
 at the end of the query. Such SIGs are identified by having a "type
 covered" field of zero. They sign the preceding DNS request message
 including DNS header but not including the IP header or any request
 SIGs at the end and before the request RR counts have been adjusted
 for the inclusions of any request SIG(s).

Return value

The sig0 and tsig, i.e. signed record, for verifying the sending and package integrity

RFC 2535, Domain Name System Security Extensions, March 1999

A DNS request may be optionally signed by including one or more SIGs
 at the end of the query. Such SIGs are identified by having a "type
 covered" field of zero. They sign the preceding DNS request message
 including DNS header but not including the IP header or any request
 SIGs at the end and before the request RR counts have been adjusted
 for the inclusions of any request SIG(s).

Return value

The sig0 and tsig, i.e. signed record, for verifying the sending and package integrity

Remove signatures from the Message

Encodes the Message into a buffer

Finalize the message prior to sending.

Subsequent to calling this, the Message should not change.

Trait Implementations

Returns a copy of the value. Read more

Performs copy-assignment from source. Read more

The resulting type after dereferencing.

Dereferences the value.

Mutably dereferences the value.

Performs the conversion.

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Performs the conversion.

Instruments this type with the provided Span, returning an Instrumented wrapper. Read more

Instruments this type with the current Span, returning an Instrumented wrapper. Read more

Performs the conversion.

The resulting type after obtaining ownership.

Creates owned data from borrowed data, usually by cloning. Read more

🔬 This is a nightly-only experimental API. (toowned_clone_into)

recently added

Uses borrowed data to replace owned data, usually by cloning. Read more

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.

Attaches the provided Subscriber to this type, returning a WithDispatch wrapper. Read more

Attaches the current default Subscriber to this type, returning a WithDispatch wrapper. Read more