diff --git a/content/rancher/v2.x/en/tools/globaldns/_index.md b/content/rancher/v2.x/en/tools/globaldns/_index.md index 7be9e5d9791..c69ff23962b 100644 --- a/content/rancher/v2.x/en/tools/globaldns/_index.md +++ b/content/rancher/v2.x/en/tools/globaldns/_index.md @@ -23,11 +23,11 @@ The following table lists the first version of Rancher each provider debuted. ## Global DNS Entries -For each application that you want to route traffic to, you will need to create a Global DNS Entry. This entry will use a fully qualified domain name (a.k.a FQDN) from a global DNS provider to target applications. The applications can either resolve to a single multi-cluster application or to specific projects. You must [add specific annotation labels](#adding-annotations-to-ingresses-to-program-the-external-dns) to the ingresses in order for traffic to be routed correctly to the applications. Without this annotation, the programming for the DNS entry will not work. +For each application that you want to route traffic to, you will need to create a Global DNS Entry. This entry will use a fully qualified domain name (a.k.a FQDN) from a global DNS provider to target applications. The applications can either resolve to a single [multi-cluster application]({{< baseurl >}}/rancher/v2.x/en/catalog/multi-cluster-apps/) or to specific projects. You must [add specific annotation labels](#adding-annotations-to-ingresses-to-program-the-external-dns) to the ingresses in order for traffic to be routed correctly to the applications. Without this annotation, the programming for the DNS entry will not work. ## Permissions for Global DNS Providers/Entries -By default, only [global administrators]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/global-permissions/) and the creator of the Global DNS provider or Global DNS entry have access to use, edit and delete them. When creating the provider or entry, the creator can add additional users in order for those users to access and manage them. By default, these members will get `Owner` role to manage them. +By default, only [global administrators]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/global-permissions/) and the creator of the Global DNS provider or Global DNS entry have access to use, edit and delete them. When creating the provider or entry, the creator can add additional users in order for those users to access and manage them. By default, these members will get `Owner` role to manage them. ## Setting up Global DNS for Applications @@ -66,20 +66,19 @@ By default, only [global administrators]({{< baseurl >}}/rancher/v2.x/en/admin-s ### Add a Global DNS Entry 1. From the **Global View**, select **Tools > Global DNS Entries**. -1. Click on **Add DNS Entry**. +1. Click on **Add DNS Entry**. 1. Enter the **FQDN** you wish to program on the external DNS. 1. Select a Global DNS **Provider** from the list. -1. Select if this DNS entry will be for a multi-cluster application or for workloads in different [projects]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/). You will need to ensure that [annotations are added to any ingresses](#adding-annotations-to-ingresses-to-program-the-external-dns) for the applications that you want to target. +1. Select if this DNS entry will be for a [multi-cluster application]({{< baseurl >}}/rancher/v2.x/en/catalog/multi-cluster-apps/) or for workloads in different [projects]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/). You will need to ensure that [annotations are added to any ingresses](#adding-annotations-to-ingresses-to-program-the-external-dns) for the applications that you want to target. 1. Configure the **DNS TTL** value in seconds. By default, it will be 300 seconds. -1. Under **Member Access**, search for any users that you want to have the ability to manage this Global DNS entry. +1. Under **Member Access**, search for any users that you want to have the ability to manage this Global DNS entry. ## Adding Annotations to Ingresses to program the External DNS -In order for Global DNS entries to be programmed, you will need to add a specific annotation label on each ingress and this ingress needs to use a specific `hostname` that should match the FQDN of the Global DNS entry. +In order for Global DNS entries to be programmed, you will need to add a specific annotation label on each ingress and this ingress needs to use a specific `hostname` that should match the FQDN of the Global DNS entry. -1. For any application that you want targetted for your Global DNS entry, find the ingresses associated with these applications. +1. For any application that you want targetted for your Global DNS entry, find the ingresses associated with these applications. 1. In order for the DNS to pe programmed, the following requirements must be met: - * The ingress must be set to use a `hostname` that matches the FQDN of the Global DNS entry. - * The ingress must have an annotation label (`rancher.io/globalDNS.`) where `` matches is also the FQDN of the Global DNS entry. -1. Once the ingress in your multi-cluster application or in your target projects are in `active` state, the FQDN will be programmed on the external DNS against the Ingress IP addresses. - + * The ingress must be set to use a `hostname` that matches the FQDN of the Global DNS entry. + * The ingress must have an annotation label (`rancher.io/globalDNS.`) where `` matches is also the FQDN of the Global DNS entry. +1. Once the ingress in your [multi-cluster application]({{< baseurl >}}/rancher/v2.x/en/catalog/multi-cluster-apps/) or in your target projects are in `active` state, the FQDN will be programmed on the external DNS against the Ingress IP addresses.