Skip to content

Commit 45ce0cb

Browse files
Merge pull request #256983 from greg-lindsay/dns-faq
edit to DNS change Q/A
2 parents 0fee531 + d2b9627 commit 45ce0cb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/dns/dns-faq.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66
author: greg-lindsay
77
ms.service: dns
88
ms.topic: faq
9-
ms.date: 05/22/2023
9+
ms.date: 11/01/2023
1010
ms.author: greglin
1111
title: Azure DNS FAQ
1212
summary: |
@@ -192,9 +192,9 @@ sections:
192192
- question: |
193193
How long does it take for DNS changes to take effect?
194194
answer: |
195-
New DNS zones and DNS records typically appear in the Azure DNS name servers quickly. The timing is a few seconds.
195+
New or updated DNS zones and DNS records appear in the Azure DNS name servers within 60 seconds.
196196
197-
Changes to existing DNS records can take a little longer. They typically appear in the Azure DNS name servers within 60 seconds. DNS caching by DNS clients and DNS recursive resolvers outside of Azure DNS also can affect timing. To control this cache duration, use the Time-To-Live (TTL) property of each record set.
197+
For changes to existing records, DNS caching by DNS clients and DNS recursive resolvers outside of Azure DNS can affect timing. The cache duration is dependent on the [Time-To-Live (TTL)](dns-zones-records.md#time-to-live) property of each record set.
198198
199199
- question: |
200200
How can I protect my DNS zones against accidental deletion?

0 commit comments

Comments
 (0)