Struct trust_dns_server::server::Request

source · [−]

pub struct Request { /* private fields */ }

Expand description

An incoming request to the DNS catalog

Implementations

source

impl Request

source

pub fn new(message: MessageRequest, src: SocketAddr, protocol: Protocol) -> Self

Build a new requests with the inbound message, source address, and protocol.

This will return an error on bad verification.

source

pub fn request_info(&self) -> RequestInfo<'_>

Return just the header and request information from the Request Message

source

pub fn src(&self) -> SocketAddr

The IP address from which the request originated.

source

pub fn protocol(&self) -> Protocol

The protocol that was used for the request

Methods from Deref<Target = MessageRequest>

Return the request header

source

pub fn id(&self) -> u16

see Header::id()

source

pub fn message_type(&self) -> MessageType

see Header::message_type()

source

pub fn op_code(&self) -> OpCode

see Header::op_code()

source

pub fn authoritative(&self) -> bool

see Header::authoritative()

source

pub fn truncated(&self) -> bool

see Header::truncated()

source

pub fn recursion_desired(&self) -> bool

see Header::recursion_desired()

source

pub fn recursion_available(&self) -> bool

see Header::recursion_available()

source

pub fn authentic_data(&self) -> bool

see Header::authentic_data()

source

pub fn checking_disabled(&self) -> bool

see Header::checking_disabled()

source

pub fn response_code(&self) -> ResponseCode

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

source

pub fn query(&self) -> &LowerQuery

Question        Carries the query name and other query parameters.

source

pub fn answers(&self) -> &[Record]

Answer          Carries RRs which directly answer the query.

source

pub fn name_servers(&self) -> &[Record]

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

source

pub fn additionals(&self) -> &[Record]

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

source

pub fn edns(&self) -> Option<&Edns>

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.