From 27ae01bb3ff6aa38bbbb137226b766a24bb12b7f Mon Sep 17 00:00:00 2001 From: Bob Rudis Date: Sat, 9 Apr 2016 17:16:24 -0400 Subject: [PATCH] README --- README.Rmd | 4 ++++ README.md | 14 +++++++++----- 2 files changed, 13 insertions(+), 5 deletions(-) diff --git a/README.Rmd b/README.Rmd index 3edb7c4..e98ca38 100644 --- a/README.Rmd +++ b/README.Rmd @@ -16,6 +16,10 @@ knitr::opts_chunk$set( `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 the DNS query diff --git a/README.md b/README.md index 1693dd8..d044042 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,10 @@ `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 the DNS query @@ -32,7 +36,7 @@ library(gdns) library(testthat) date() -#> [1] "Sat Apr 9 17:14:38 2016" +#> [1] "Sat Apr 9 17:16:13 2016" test_dir("tests/") #> testthat results ======================================================================================================== @@ -52,10 +56,10 @@ map_df(results, "Answer") #> #> name type TTL data #> (chr) (int) (int) (chr) -#> 1 rud.is. 1 3147 104.236.112.222 -#> 2 dds.ec. 1 299 162.243.111.4 -#> 3 r-project.org. 1 1801 137.208.57.37 -#> 4 rstudio.com. 1 3482 45.79.156.36 +#> 1 rud.is. 1 823 104.236.112.222 +#> 2 dds.ec. 1 204 162.243.111.4 +#> 3 r-project.org. 1 927 137.208.57.37 +#> 4 rstudio.com. 1 3386 45.79.156.36 ``` ### Code of Conduct