Skip to content

[Maintenance] Zone-level dashbutton for Tunnel docs #25241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 17, 2025
Merged

[Maintenance] Zone-level dashbutton for Tunnel docs #25241

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 7 additions & 6 deletions ...tent/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar:
order: 51
---

import { Render, TabItem, Tabs } from "~/components";
import { Render, TabItem, Tabs, DashButton } from "~/components";

<Render
file="tunnel/dns-record"
Expand All @@ -19,14 +19,15 @@ import { Render, TabItem, Tabs } from "~/components";

To create a new DNS record for your tunnel:

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
2. Go to **DNS** > **Records**.
3. Select **Add record**.
4. Input the following information:
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to the **DNS Records** page for your domain.

<DashButton url="/?to=/:account/:zone/dns/records" />
2. Select **Add record**.
3. Input the following information:
- **Type**: _CNAME_
- **Name**: Subdomain of your application
- **Target**: `<UUID>.cfargotunnel.com`
5. Select **Save**.
4. Select **Save**.

![Example of fields completed to create a new CNAME record.](~/assets/images/cloudflare-one/connections/connect-apps/dns/dns-record.png)

Expand Down
13 changes: 11 additions & 2 deletions src/content/docs/cloudflare-one/tutorials/gitlab.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ pcx_content_type: tutorial
title: Zero Trust GitLab SSH & HTTP
---

import { DashButton } from "~/components";

You can use Cloudflare Access to add Zero Trust rules to a self-hosted instance of GitLab. Combined with Cloudflare Tunnel, users can connect through HTTP and SSH and authenticate with your team's identity provider.

**This walkthrough covers how to:**
Expand Down Expand Up @@ -238,13 +240,20 @@ This command should be run as a `systemd` service for long-term use; if it termi

You can now create DNS records for GitLab in the Cloudflare dashboard. Remember, you will still need two records - one for the web application and one for SSH traffic.

In the **DNS** tab, choose the website where you built your [Access policies](/cloudflare-one/policies/access/). Select **Add record** and select `CNAME` from type. In the **Name** field, input `gitlab`. In the **Target** field, input the ID of the Tunnel created followed by `cfargotunnel.com`. In this example, that value is:
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to the **DNS Records** page for your domain.

<DashButton url="/?to=/:account/:zone/dns/records" />

2. Select **Add record**. Choose `CNAME` as the record type.
3. In the **Name** field, input `gitlab`.
4. In the **Target** field, input the ID of the Tunnel created followed by `cfargotunnel.com`. In this example, that value is:

```txt
6ff42ae2-765d-4adf-8112-31c55c1551ef.cfargotunnel.com
```

Select **Save**. Repeat the process again by creating a second `CNAME` record, with the same **Target**, but input `gitlab-ssh` for the **Name**. Both records should then appear, pointing to the same Tunnel. The ingress rules defined in the configuration file above will direct traffic to the appropriate port.
5. Select **Save**.
6. Repeat the process again by creating a second `CNAME` record, with the same **Target**, but input `gitlab-ssh` for the **Name**. Both records should then appear, pointing to the same Tunnel. The ingress rules defined in the configuration file above will direct traffic to the appropriate port.

![View DNS](~/assets/images/cloudflare-one/zero-trust-security/gitlab/view-dns.png)

Expand Down
6 changes: 5 additions & 1 deletion src/content/docs/cloudflare-one/tutorials/kubectl.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ pcx_content_type: tutorial
title: Connect through Cloudflare Access using kubectl
---

import { DashButton } from "~/components";

You can connect to machines over `kubectl` using Cloudflare's Zero Trust platform.

**This walkthrough covers how to:**
Expand Down Expand Up @@ -97,7 +99,9 @@ ingress:

You can now create a DNS record that will route traffic to this Tunnel. Multiple DNS records can point to a single Tunnel and will send traffic to the configured service as long as the hostname is defined with an [ingress rule](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-public-hostnames).

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. Select your domain and go to **DNS** > **Records**.
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to the **DNS Records** page for your domain.

<DashButton url="/?to=/:account/:zone/dns/records" />

2. Select **Add record**. Choose `CNAME` as the record type. For **Name**, choose the hostname where you want to create a Tunnel. This should match the hostname of the Access policy.

Expand Down