#' @note As noted in , Multicast DNS can only carry DNS records with classes in the range 0-32767. Classes in the range 32768 to 65535 are incompatible with Multicast DNS.
#' @note Last updated 2019-06-27 11:16:48
#' @usage data('dns_classes')
NULL
#' @md
#' @title Resource Record (RR) TYPEs (dataset)
#' @description Resource Record (RR) TYPEs
#' @format data frame with columns: `type`, `value`, `meaning`, `reference`, `template`, `registration_date`
#' @note Registrations made by standards-track documents are listed as "Standard," and by non-standards-track documents as "Optional." Registrations for which there are no final specifications are listed as "On-Hold."
#' @note Last updated 2019-06-27 11:16:48
#' @usage data('edns0_option_codes')
NULL
#' @md
#' @title Underscored and Globally Scoped DNS Node Names (dataset)
#' @description Underscored and Globally Scoped DNS Node Names
#' @format data frame with columns: `rr_type`, `node_name`, `reference`
`gdns` : Tools to work with the Google DNS over HTTPS API
# gdns
Tools to work with the Google DNS over HTTPS (DoH) API
## Description
Traditional DNS queries and responses are sent over UDP or TCP without encryption. This is vulnerable to eavesdropping and spoofing (including DNS-based Internet filtering). Responses from recursive resolvers to clients are the most vulnerable to undesired or malicious changes, while communications between recursive resolvers and authoritative nameservers often incorporate additional protection.
Traditional DNS queries and responses are sent over UDP or TCP without encryption. This is vulnerable to eavesdropping and spoofing (including DNS-based Internet filtering). Responses from recursive resolvers to clients are the most vulnerable to undesired or malicious changes, while communications between recursive resolvers and authoritative nameservers often incorporate additional protection.
To address this problem, Google Public DNS offers DNS resolution over an encrypted HTTPS connection. DNS-over-HTTPS greatly enhances privacy and security between a client and a recursive resolver, and complements DNSSEC to provide end-to-end authenticated DNS lookups.
To address this problem, Google Public DNS offers DNS resolution over an encrypted HTTPS connection. DNS-over-HTTPS greatly enhances privacy and security between a client and a recursive resolver, and complements DNSSEC to provide end-to-end authenticated DNS lookups.
More info at <https://developers.google.com/speed/public-dns/docs/dns-over-https>.
More info at <https://developers.google.com/speed/public-dns/docs/doh/>.
The following functions are implemented:
The following functions are implemented:
Core:
- `query` / `dig`: Perform DNS over HTTPS queries using Google
- `bulk_query`: Vectorized query, returning only answers in a data frame
- `bulk_query`: Vectorized query, returning only answers in a data frame
- `as.data.frame`: Coerce a gdns query response answer to a data frame
Helpers:
- `has_spf`: Test for whether a DNS TXT record is an SPF record
- `has_spf`: Test for whether a DNS TXT record is an SPF record
- `is_hard_fail`: SPF "all" type test
- `is_hard_fail`: SPF "all" type test
- `is_soft_fail`: SPF "all" type test
- `is_soft_fail`: SPF "all" type test
- `passes_all`: SPF "all" type test
- `passes_all`: SPF "all" type test
- `query`: Perform DNS over HTTPS queries using Google
- `spf_exists`: SPF field extraction functions
- `spf_exists`: SPF field extraction functions
- `spf_includes`: SPF field extraction functions
- `spf_includes`: SPF field extraction functions
- `spf_ipv4s`: SPF field extraction functions
- `spf_ipv4s`: SPF field extraction functions
@ -36,9 +50,24 @@ The following functions are implemented:
- `spf_ptrs`: SPF field extraction functions
- `spf_ptrs`: SPF field extraction functions
- `split_spf`: Split out all SPF records in a domain's TXT record
- `split_spf`: Split out all SPF records in a domain's TXT record
IANA Datasets:
- `dns_classes`: DNS CLASSes (dataset)
- `dns_glob_names`: Underscored and Globally Scoped DNS Node Names (dataset)
- `dns_opcodes`: DNS OpCodes (dataset)
- `dns_rcodes`: DNS RCODEs (dataset)
- `edns0_option_codes`: DNS EDNS0 Option Codes (OPT) (dataset)
\format{data frame with columns: \code{decimal}, \code{hexadecimal}, \code{name}, \code{reference}}
\usage{
data('dns_classes')
}
\description{
DNS CLASSes
}
\note{
As noted in , Multicast DNS can only carry DNS records with classes in the range 0-32767. Classes in the range 32768 to 65535 are incompatible with Multicast DNS.
\format{data frame with columns: \code{value}, \code{name}, \code{status}, \code{reference}}
\usage{
data('edns0_option_codes')
}
\description{
DNS EDNS0 Option Codes (OPT)
}
\note{
Registrations made by standards-track documents are listed as "Standard," and by non-standards-track documents as "Optional." Registrations for which there are no final specifications are listed as "On-Hold."