You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/1.1.1.1/encryption/dns-over-https/dns-over-https-client.mdx
+2-81Lines changed: 2 additions & 81 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,88 +7,9 @@ description: Learn how to connect to Cloudflare's 1.1.1.1 using DNS over HTTPS (
7
7
8
8
Several DoH clients are available for connecting to 1.1.1.1.
9
9
10
-
## cloudflared
10
+
## Cloudflare WARP client
11
11
12
-
1.[Download and install the `cloudflared` daemon](/cloudflare-one/connections/connect-networks/downloads/).
13
-
14
-
2. Verify that the `cloudflared` daemon is installed by entering the following command:
15
-
16
-
```sh
17
-
cloudflared --version
18
-
```
19
-
20
-
```sh output
21
-
cloudflared version 2020.11.11 (built 2020-11-25-1643 UTC)
22
-
```
23
-
24
-
3. Start the DNS proxy on an address and port in your network. If you do not specify an address and port, it will start listening on `localhost:53`. DNS (53) is a privileged port, so for the initial demo we will use a different port:
25
-
26
-
```sh
27
-
cloudflared proxy-dns --port 5553
28
-
```
29
-
30
-
```sh output
31
-
INFO[2020-12-04T19:58:57Z] Adding DNS upstream - url: https://1.1.1.1/dns-query
32
-
INFO[2020-12-04T19:58:57Z] Adding DNS upstream - url: https://1.0.0.1/dns-query
33
-
INFO[2020-12-04T19:58:57Z] Starting metrics server on 127.0.0.1:44841/metrics
34
-
INFO[2020-12-04T19:58:57Z] Starting DNS over HTTPS proxy server on: dns://localhost:5553
35
-
```
36
-
37
-
4. You can verify that `cloudflared` is running using a `dig`, `kdig`, `host`, or any other DNS client.
38
-
39
-
```sh
40
-
dig +short @127.0.0.1 -p5553 cloudflare.com AAAA
41
-
```
42
-
43
-
```sh output
44
-
2606:4700::6810:85e5
45
-
2606:4700::6810:84e5
46
-
```
47
-
48
-
5. Run `cloudflared` as a service so it starts on user login. On many Linux distributions, this can be done with:
49
-
50
-
```sh
51
-
sudo tee /etc/systemd/system/cloudflared-proxy-dns.service >/dev/null <<EOF
52
-
```
53
-
54
-
```sh output
55
-
[Unit]
56
-
Description=DNS over HTTPS (DoH) proxy client
57
-
Wants=network-online.target nss-lookup.target
58
-
Before=nss-lookup.target
59
-
60
-
[Service]
61
-
AmbientCapabilities=CAP_NET_BIND_SERVICE
62
-
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
63
-
DynamicUser=yes
64
-
ExecStart=/usr/local/bin/cloudflared proxy-dns
65
-
66
-
[Install]
67
-
WantedBy=multi-user.target
68
-
EOF
69
-
```
70
-
71
-
```sh
72
-
sudo systemctl enable --now cloudflared-proxy-dns
73
-
```
74
-
75
-
6. Change your system DNS servers to use `127.0.0.1`. On Linux, you can modify `/etc/resolv.conf`:
76
-
77
-
```sh
78
-
sudo rm -f /etc/resolv.conf
79
-
echo nameserver 127.0.0.1 | sudo tee /etc/resolv.conf >/dev/null
80
-
```
81
-
82
-
7. Finally, verify it locally with:
83
-
84
-
```sh
85
-
dig +short @127.0.0.1 cloudflare.com AAAA
86
-
```
87
-
88
-
```sh output
89
-
2606:4700::6810:85e5
90
-
2606:4700::6810:84e5
91
-
```
12
+
Refer to [WARP client](/warp-client/) for guidance on WARP modes and get-started information for different [operating systems](/warp-client/get-started/).
0 commit comments