mirrors/doh-server
1
0
Fork 0
mirror of https://github.com/DNSCrypt/doh-server.git synced 2025-04-03 04:57:37 +03:00
Code Issues Projects Releases Packages Wiki Activity

Clarify what -H and -g do

Browse source 
Fixes #68
This commit is contained in:
Frank Denis 2022-12-25 10:21:19 +01:00
parent 8b9f9377b3
commit 06a3fa0499
1 changed files with 10 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -60,6 +60,14 @@ OPTIONS:
Path to the PEM/PKCS#8-encoded certificates (only required for built-in TLS)
```
Example command-line:
```sh
doh-proxy -H 'doh.example.com' -u 127.0.0.1:53 -g 233.252.0.5
```
Here, `doh.example.com` is the host name (which should match a name included in the TLS certificate), `127.0.0.1:53` is the address of the DNS resolver, and `233.252.0.5` is the public IP address of the DoH server.
## HTTP/2 termination
The recommended way to use `doh-proxy` is to use a TLS termination proxy (such as [hitch](https://github.com/varnish/hitch) or [relayd](https://bsd.plumbing/about.html)), a CDN or a web server with proxying abilities as a front-end.
@ -142,10 +150,10 @@ upstream_addr = "127.0.0.1:3000"
## Example usage with `nginx`
In an existing `server`, a `/doh` endpoint can be exposed that way:
In an existing `server`, a `/dns-query` endpoint can be exposed that way:
```text
location /doh {
location /dns-query {
proxy_pass http://127.0.0.1:3000;
}
```