Tools to work with the Google DNS over HTTPS API in R
https://cinc.rud.is/web/packages/gdns/
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
61 lines
2.5 KiB
61 lines
2.5 KiB
% Generated by roxygen2: do not edit by hand
|
|
% Please edit documentation in R/gdns.r
|
|
\name{query}
|
|
\alias{query}
|
|
\title{Perform DNS over HTTPS queries using Google}
|
|
\usage{
|
|
query(name, type = "1", edns_client_subnet = "0.0.0.0/0")
|
|
}
|
|
\arguments{
|
|
\item{name}{item to lookup. Valid characters are numbers, letters, hyphen, and dot. Length
|
|
must be between 1 and 255. Names with escaped or non-ASCII characters
|
|
are not supported. Internationalized domain names must use the
|
|
punycode format (e.g. "\code{xn--qxam}").\cr
|
|
\cr If an IPv4 string is input, it will be transformed into
|
|
a proper format for reverse lookups.}
|
|
|
|
\item{type}{RR type can be represented as a number in [1, 65535] or canonical
|
|
string (A, aaaa, etc). More information on RR types can be
|
|
found \href{http://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4}{here}.}
|
|
|
|
\item{edns_client_subnet}{The edns0-client-subnet option. Format is an IP
|
|
address with a subnet mask. Examples: \code{1.2.3.4/24},
|
|
\code{2001:700:300::/48}.\cr
|
|
If you are using DNS-over-HTTPS because of privacy concerns, and do
|
|
not want any part of your IP address to be sent to authoritative
|
|
nameservers for geographic location accuracy, use
|
|
\code{edns_client_subnet=0.0.0.0/0}. Google Public DNS normally sends
|
|
approximate network information (usually replacing the last part of
|
|
your IPv4 address with zeroes). \code{0.0.0.0/0} is the default.}
|
|
}
|
|
\value{
|
|
a \code{list} with the query result or \code{NULL} if an error occurred
|
|
}
|
|
\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.\cr
|
|
\cr
|
|
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.
|
|
}
|
|
\details{
|
|
To perform vectorized queries with only answers (and no metadata) use
|
|
\code{bulk_query()}).
|
|
}
|
|
\examples{
|
|
query("rud.is")
|
|
query("microsoft.com", "MX")
|
|
query("google-public-dns-a.google.com", "TXT")
|
|
query("apple.com")
|
|
query("17.142.160.59", "PTR")
|
|
}
|
|
\references{
|
|
\url{https://developers.google.com/speed/public-dns/docs/dns-over-https}
|
|
}
|
|
|
|
|