From 1681d4944bb2ab023716e41308d9a2ac63c14da8 Mon Sep 17 00:00:00 2001
From: Stefan Lasiewski <slasiewski@lbl.gov>
Date: Fri, 15 May 2020 16:42:44 -0700
Subject: [PATCH] Improve documentation about rfc2126 TTLs

Now that `--rfc2136-min-ttl` is an option, show how to set it and also how to override it using an annotation.
---
 docs/tutorials/rfc2136.md | 26 +++++++++++++++++++++++---
 1 file changed, 23 insertions(+), 3 deletions(-)

diff --git a/docs/tutorials/rfc2136.md b/docs/tutorials/rfc2136.md
index 4d1849fd37..f36dddf12f 100644
--- a/docs/tutorials/rfc2136.md
+++ b/docs/tutorials/rfc2136.md
@@ -108,9 +108,29 @@ spec:
                 serviceName: my-service
                 servicePort: 8000
 ```
-There are other annotation that can affect the generation of DNS records like
-external-dns.alpha.kubernetes.io/ttl. These are beyond the scope of this
-tutorial and are covered elsewhere in the docs.
+
+### Custom TTL
+
+The default DNS record TTL (Time-To-Live) is 0 seconds. You can customize this value by setting the annotation `external-dns.alpha.kubernetes.io/ttl`. e.g., modify the service manifest YAML file above:
+
+```
+apiVersion: v1
+kind: Service
+metadata:
+  name: nginx
+  annotations:
+    external-dns.alpha.kubernetes.io/hostname: nginx.external-dns-test.my-org.com
+    external-dns.alpha.kubernetes.io/ttl: 60
+spec:
+    ...
+```
+
+This will set the DNS record's TTL to 60 seconds.
+
+A default TTL for all records can be set using the the flag with a time in seconds, minutes or hours, such as `--rfc2136-min-ttl=60s`
+
+There are other annotation that can affect the generation of DNS records, but these are beyond the scope of this
+tutorial and are covered in the main documentation.
 
 ### Test with external-dns installed on local machine (optional)
 You may install external-dns and test on a local machine by running: