Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -165,6 +165,31 @@

Specifies the path to a <a href={props.configurationFileURL}>configuration file</a> in YAML format.

### `dns-resolver-addrs`

:::note

Requires `2025.7.0` or later.

Check warning on line 172 in src/content/partials/cloudflare-one/tunnel/run-parameters.mdx

View workflow job for this annotation

GitHub Actions / Semgrep

semgrep.style-guide-potential-date-year

Potential year found. Documentation should strive to represent universal truth, not something time-bound. (add [skip style guide checks] to commit message to skip)
:::

| Syntax | Environment Variable |
| ------------------------------------------------------------------------- | --------------------------- |
| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>` | `TUNNEL_DNS_RESOLVER_ADDRS` |

Specifies custom DNS resolver addresses for `cloudflared` to use. Each address must be in `ip:port` format — providing an IP address without a port will cause `cloudflared` to fail to start. You can specify multiple resolvers by repeating the flag.

A maximum of 10 resolver addresses are allowed.

```sh
cloudflared tunnel run --dns-resolver-addrs 1.1.1.1:53 <UUID or NAME>
```

To use multiple resolvers:

```sh
cloudflared tunnel run --dns-resolver-addrs 1.1.1.1:53 --dns-resolver-addrs 1.0.0.1:53 <UUID or NAME>
```

### `edge-bind-address`

| Syntax | Environment Variable |
Expand Down Expand Up @@ -321,7 +346,7 @@

:::note

For remotely-managed tunnels only. Requires `2025.4.0` or later.

Check warning on line 349 in src/content/partials/cloudflare-one/tunnel/run-parameters.mdx

View workflow job for this annotation

GitHub Actions / Semgrep

semgrep.style-guide-potential-date-year

Potential year found. Documentation should strive to represent universal truth, not something time-bound. (add [skip style guide checks] to commit message to skip)
:::

| Syntax | Environment Variable |
Expand Down
Loading