Module simple_dns::rdata

source ·
Expand description

Contains RData implementations

Structs§

  • Represents a Resource Address (IPv4)
  • Represents a Resource Address (IPv6) rfc3596
  • AFSDB records represents servers with ASD cells
  • RFC 8659: Allow domain name holders to indicate whether they are authorized to issue digital certificates for particular domain name Used as a security policy for certificate authorities This implementation does not validate the tag or value; it splits based on packet byte structure
  • Canonical name for an alias, RFC 1035
  • HINFO records are used to acquire general information about a host.
    The main use is for protocols such as FTP that can use special procedures when talking between machines or operating systems of the same type.
  • HTTPS RR type is a SVCB-compatible RR type, specific to the “https” and “http” schemes. RFC 9460.
  • An ISDN (Integrated Service Digital Network) number is simply a telephone number.
  • A Means for Expressing Location Information in the Domain Name System RFC 1876
  • Mailbox domain name (EXPERIMENTAL), RFC 1035
  • Mail destination (Obsolete - use MX), RFC 1035
  • Mail forwarder (Obsolete - use MX), RFC 1035
  • Mail group member (EXPERIMENTAL), RFC 1035
  • MINFO recors are used to acquire mailbox or mail list information
  • Mail rename domain name (EXPERIMENTAL), RFC 1035
  • MX is used to acquire mail exchange information
  • RFC 3403: Used to map a domain name to a set of services. The fields determine the order of processing, specify the protocol and service to be used, and transform the original domain name into a new domain name or URI.
  • Authoritative name server, RFC 1035
  • NSAP structure RFC 1706
    ATTENTION: this code doesn’t validade the content of the NSAP RR, it just split the bytes in the correct order
  • PTR for NSAP records, RFC 1348
  • NULL resources are used to represent any kind of information.
  • OPT is a pseudo-rr used to carry control information
    If an OPT record is present in a received request, responders MUST include an OPT record in their respective responses.
    OPT RRs MUST NOT be cached, forwarded, or stored in or loaded from master files.
  • Represents the variable part of an OPT rr
  • Domain name pointer, RFC 1035
  • RP Responsible Person, RFC 1183
  • The RT resource record provides a route-through binding for hosts that do not have their own direct wide area network addresses
  • SOA records are used to mark the start of a zone of authority
  • SRV records specifies the location of the server(s) for a specific protocol and domain.
  • The SVCB DNS RR type is used to locate alternative endpoints for a service. RFC 9460.
  • Represents a TXT Resource Record
  • The WKS record is used to describe the well known services supported by a particular protocol on a particular internet address.
  • X.25 address, RFC 1183

Enums§

  • Represents the RData of each TYPE
  • Possible TYPE values in DNS Resource Records Each value is described according to its own RFC