Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support provider defaults for google, cloudflare #27

Merged
merged 6 commits into from Jun 12, 2018
Merged

Conversation

fardog
Copy link
Owner

@fardog fardog commented Jun 10, 2018

  • allows passing of simple -google or -cloudflare flags to
    configure google or cloudflare DNS, respectively. Provides sane
    defaults for each, and avoids some unintuitive settings needed
    for cloudflare to work properly.
  • adds new CLI flags for specifying DNS headers or additional
    query parameters which should be sent along with the request to
    the DNS-over-HTTPS server
  • fixes CLI flag "help" indentation for newer golang
  • update CI and build versions
  • use ENTRYPOINT in dockerfile for more pleasant container use

* allows passing of simple `-google` or `-cloudflare` flags to
  configure google or cloudflare DNS, respectively. Provides sane
  defaults for each, and avoids some unintuitive settings needed
  for cloudflare to work properly.
* adds new CLI flags for specifying DNS headers or additional
  query parameters which should be sent along with the request to
  the DNS-over-HTTPS server
@zoonderkins
Copy link

I'd suggest use 1.0.0.1 first then 1.1.1.1 (some school, office Cisco don't support 1.1.1.1)

@fardog
Copy link
Owner Author

fardog commented Jun 10, 2018

@ookangzheng good suggestion. it won't have the desired effect until I implement another feature though: right now, DNS servers are picked at random, but they should be used in order. I'll change the order here, and have created a bug #28 to track fixing the DNS lookup order.

@fardog fardog merged commit 3ea4d87 into master Jun 12, 2018
@fardog fardog deleted the provider-defaults branch June 12, 2018 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants