Skip to content

Instantly share code, notes, and snippets.

@chr-lei
chr-lei / controld-dnsproxy.md
Last active March 18, 2023 21:39
Deploying dnsproxy for ControlD using a config.yaml file

Deploying dnsproxy for ControlD using a config.yaml file

Prerequisites

  • You've got a config.yaml file built. Check out the sample file provided by AdGuard here, or a ControlD-specific sample here.
    • You can also run dnsproxy without a config.yaml file and use command-line switches. I prefer a config.yaml file since it means you don't need to change any startup scripts or re-create the Docker/Podman container if you need to update a value, but any arguments in the config.yaml file can be passed to the command line as well. Check out the dnsproxy readme for more information on additional functions.
  • If you want to use Docker/Podman, this assumes you have either installed and have a basic level of knowledge on either platform. Unfortunately, I am not an expert in either myself and there are many better
@chr-lei
chr-lei / dnsproxy_controld_config_sample.yaml
Created October 3, 2022 15:39
Sample dnsproxy configuration for ControlD upstream
# config.yaml - source:
# https://github.com/AdguardTeam/dnsproxy/blob/master/config.yaml.dist
# also reference: https://github.com/AdguardTeam/dnsproxy/blob/master/README.md
#
# ---
# Bootstrap DNS servers - these are used to resolve any hostnames in the upstream or
# fallback resolvers specified later. These can be ISP DNS servers or public DNS
# servers like Google or Cloudflare.
bootstrap:
- "8.8.8.8:53"