Skip to content

Commit 2d88a31

Browse files
authored
zone-level dashbutton (cloudflare#25241)
1 parent c6cc50b commit 2d88a31

File tree

3 files changed

+23
-9
lines changed

3 files changed

+23
-9
lines changed

src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns.mdx

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 51
66
---
77

8-
import { Render, TabItem, Tabs } from "~/components";
8+
import { Render, TabItem, Tabs, DashButton } from "~/components";
99

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

2020
To create a new DNS record for your tunnel:
2121

22-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
23-
2. Go to **DNS** > **Records**.
24-
3. Select **Add record**.
25-
4. Input the following information:
22+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to the **DNS Records** page for your domain.
23+
24+
<DashButton url="/?to=/:account/:zone/dns/records" />
25+
2. Select **Add record**.
26+
3. Input the following information:
2627
- **Type**: _CNAME_
2728
- **Name**: Subdomain of your application
2829
- **Target**: `<UUID>.cfargotunnel.com`
29-
5. Select **Save**.
30+
4. Select **Save**.
3031

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

src/content/docs/cloudflare-one/tutorials/gitlab.mdx

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ pcx_content_type: tutorial
66
title: Zero Trust GitLab SSH & HTTP
77
---
88

9+
import { DashButton } from "~/components";
10+
911
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.
1012

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

239241
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.
240242

241-
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:
243+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to the **DNS Records** page for your domain.
244+
245+
<DashButton url="/?to=/:account/:zone/dns/records" />
246+
247+
2. Select **Add record**. Choose `CNAME` as the record type.
248+
3. In the **Name** field, input `gitlab`.
249+
4. In the **Target** field, input the ID of the Tunnel created followed by `cfargotunnel.com`. In this example, that value is:
242250

243251
```txt
244252
6ff42ae2-765d-4adf-8112-31c55c1551ef.cfargotunnel.com
245253
```
246254

247-
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.
255+
5. Select **Save**.
256+
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.
248257

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

src/content/docs/cloudflare-one/tutorials/kubectl.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@ pcx_content_type: tutorial
55
title: Connect through Cloudflare Access using kubectl
66
---
77

8+
import { DashButton } from "~/components";
9+
810
You can connect to machines over `kubectl` using Cloudflare's Zero Trust platform.
911

1012
**This walkthrough covers how to:**
@@ -97,7 +99,9 @@ ingress:
9799

98100
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).
99101

100-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. Select your domain and go to **DNS** > **Records**.
102+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to the **DNS Records** page for your domain.
103+
104+
<DashButton url="/?to=/:account/:zone/dns/records" />
101105

102106
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.
103107

0 commit comments

Comments
 (0)