From 8adca4601c28d6ee2420305b6ed852afd6896627 Mon Sep 17 00:00:00 2001
From: Michael Kozono <mkozono@gitlab.com>
Date: Fri, 18 Aug 2023 14:43:20 +0000
Subject: [PATCH] Geo failover: Adjust DNS TTL guidance

---
 doc/administration/geo/disaster_recovery/index.md            | 2 +-
 doc/administration/geo/disaster_recovery/planned_failover.md | 5 +++++
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/doc/administration/geo/disaster_recovery/index.md b/doc/administration/geo/disaster_recovery/index.md
index 151c0f7d9fb87..78e6bbd6c067b 100644
--- a/doc/administration/geo/disaster_recovery/index.md
+++ b/doc/administration/geo/disaster_recovery/index.md
@@ -67,7 +67,7 @@ must disable the **primary** site.
   - Physically disconnect a machine.
 
   If you plan to [update the primary domain DNS record](#step-4-optional-updating-the-primary-domain-dns-record),
-  you may wish to lower the TTL now to speed up propagation.
+  you may wish to maintain a low TTL to ensure fast propagation of DNS changes.
 
 ### Step 3. Promoting a **secondary** site
 
diff --git a/doc/administration/geo/disaster_recovery/planned_failover.md b/doc/administration/geo/disaster_recovery/planned_failover.md
index 6ac67c3d21e00..ff6b2400267aa 100644
--- a/doc/administration/geo/disaster_recovery/planned_failover.md
+++ b/doc/administration/geo/disaster_recovery/planned_failover.md
@@ -90,6 +90,11 @@ gitlab-ctl promotion-preflight-checks
 
 Each step is described in more detail below.
 
+### DNS TTL
+
+If you plan to [update the primary domain DNS record](index.md#step-4-optional-updating-the-primary-domain-dns-record),
+you may wish to maintain a low TTL to ensure fast propagation of DNS changes.
+
 ### Object storage
 
 If you have a large GitLab installation or cannot tolerate downtime, consider
-- 
GitLab