From 240caa549878dbb8dbd4a64e1691ac3250886fd6 Mon Sep 17 00:00:00 2001 From: Prachi Damle Date: Mon, 25 Mar 2019 14:28:24 -0700 Subject: [PATCH] Correct the annotation for GlobalDNS --- content/rancher/v2.x/en/catalog/globaldns/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/catalog/globaldns/_index.md b/content/rancher/v2.x/en/catalog/globaldns/_index.md index b70643d86c1..9da0f7e2827 100644 --- a/content/rancher/v2.x/en/catalog/globaldns/_index.md +++ b/content/rancher/v2.x/en/catalog/globaldns/_index.md @@ -84,7 +84,7 @@ In order for Global DNS entries to be programmed, you will need to add a specifi 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. + * The ingress must have an annotation label (`rancher.io/globalDNS.hostname`) and the value of the label should match 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. ## Editing a Global DNS Provider