Skip to content

[Tunnel] Add dns-resolver-addrs run parameter#29120

Open
nikitacano wants to merge 2 commits intoproductionfrom
ncano/tunnel-dns-resolver-addrs
Open

[Tunnel] Add dns-resolver-addrs run parameter#29120
nikitacano wants to merge 2 commits intoproductionfrom
ncano/tunnel-dns-resolver-addrs

Conversation

@nikitacano
Copy link
Contributor

Summary

  • Documents the --dns-resolver-addrs flag for cloudflared tunnel run
  • Addresses must be in ip:port format (bare IP causes cloudflared to fail)
  • Maximum of 10 resolver addresses allowed
  • Requires cloudflared 2025.7.0 or later
  • Added to the shared partial so it appears on both /tunnel/advanced/run-parameters/ and /cloudflare-one/.../run-parameters/

@nikitacano nikitacano requested a review from a team as a code owner March 19, 2026 10:14
@github-actions
Copy link
Contributor

This PR requires additional review attention because it affects the following areas:

Partials

This PR updates partial files, which are pieces of content used across multiple files in our Render component.

@github-actions
Copy link
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
* @cloudflare/pcx-technical-writing

@github-actions
Copy link
Contributor

github-actions bot commented Mar 19, 2026

| ------------------------------------------------------------------------- | --------------------------- |
| `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. For example,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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. For example,
Specifies custom DNS resolver addresses for `cloudflared` to use for [private hostname routing](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#scenario-b-use-a-specific-private-dns-server-advanced). 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. For example,

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we explain what the custom DNS resolvers are used for?

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

A maximum of 10 resolver addresses are allowed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does cloudflared determine which resolver to use?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants