||6 years ago|
|R||6 years ago|
|man||6 years ago|
|tests||6 years ago|
|.Rbuildignore||6 years ago|
|.gitignore||6 years ago|
|.travis.yml||6 years ago|
|CONDUCT.md||6 years ago|
|DESCRIPTION||6 years ago|
|LICENSE||6 years ago|
|NAMESPACE||6 years ago|
|README.Rmd||6 years ago|
|README.md||6 years ago|
|gdns.Rproj||6 years ago|
gdns : Tools to work with the Google DNS over HTTPS API
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.
The following functions are implemented:
query: perform Google DNS query for a single host (retreives metadata & answer)
bulk_query: perform bulk host queries, returning a of only answers (no metadata)
- Version 0.1.0.9000 released
library(gdns) # current verison packageVersion("gdns") #>  '0.1.0.9000'
library(gdns) library(testthat) date() #>  "Sat Apr 9 21:17:02 2016" test_dir("tests/") #> testthat results ======================================================================================================== #> OK: 2 SKIPPED: 0 FAILED: 0 hosts <- c("rud.is", "dds.ec", "r-project.org", "rstudio.com", "apple.com") gdns::bulk_query(hosts) #> Source: local data frame [7 x 4] #> #> name type TTL data #> (chr) (int) (int) (chr) #> 1 rud.is. 1 710 184.108.40.206 #> 2 dds.ec. 1 280 220.127.116.11 #> 3 r-project.org. 1 6410 18.104.22.168 #> 4 rstudio.com. 1 71 22.214.171.124 #> 5 apple.com. 1 3290 126.96.36.199 #> 6 apple.com. 1 3290 188.8.131.52 #> 7 apple.com. 1 3290 184.108.40.206
Code of Conduct
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.