diff --git a/docs/reference/auditbeat/processor-dns.md b/docs/reference/auditbeat/processor-dns.md
index 55f7b807501b..fd2523ab4d56 100644
--- a/docs/reference/auditbeat/processor-dns.md
+++ b/docs/reference/auditbeat/processor-dns.md
@@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
 `success_cache.min_ttl`
 :   The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`success_cache.enabled`
-:  Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
@@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
 `failure_cache.ttl`
 :   The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`failure_cache.enabled`
-:  Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
diff --git a/docs/reference/filebeat/processor-dns.md b/docs/reference/filebeat/processor-dns.md
index d8a721079aad..a8a6228e65cd 100644
--- a/docs/reference/filebeat/processor-dns.md
+++ b/docs/reference/filebeat/processor-dns.md
@@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
 `success_cache.min_ttl`
 :   The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`success_cache.enabled`
-:  Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
@@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
 `failure_cache.ttl`
 :   The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`failure_cache.enabled`
-:  Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
diff --git a/docs/reference/heartbeat/processor-dns.md b/docs/reference/heartbeat/processor-dns.md
index 34f6d8f941fc..222b2c4a4b8d 100644
--- a/docs/reference/heartbeat/processor-dns.md
+++ b/docs/reference/heartbeat/processor-dns.md
@@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
 `success_cache.min_ttl`
 :   The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`success_cache.enabled`
-:  Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
@@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
 `failure_cache.ttl`
 :   The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`failure_cache.enabled`
-:  Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
diff --git a/docs/reference/metricbeat/processor-dns.md b/docs/reference/metricbeat/processor-dns.md
index 08e5ba90b60c..ce92a22e96e2 100644
--- a/docs/reference/metricbeat/processor-dns.md
+++ b/docs/reference/metricbeat/processor-dns.md
@@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
 `success_cache.min_ttl`
 :   The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`success_cache.enabled`
-:  Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
@@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
 `failure_cache.ttl`
 :   The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`failure_cache.enabled`
-:  Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
diff --git a/docs/reference/packetbeat/processor-dns.md b/docs/reference/packetbeat/processor-dns.md
index 4289a253cd0b..7005d6a2fb36 100644
--- a/docs/reference/packetbeat/processor-dns.md
+++ b/docs/reference/packetbeat/processor-dns.md
@@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
 `success_cache.min_ttl`
 :   The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`success_cache.enabled`
-:  Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
@@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
 `failure_cache.ttl`
 :   The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`failure_cache.enabled`
-:  Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
diff --git a/docs/reference/winlogbeat/processor-dns.md b/docs/reference/winlogbeat/processor-dns.md
index d096aa200c08..cd01939a2206 100644
--- a/docs/reference/winlogbeat/processor-dns.md
+++ b/docs/reference/winlogbeat/processor-dns.md
@@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
 `success_cache.min_ttl`
 :   The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`success_cache.enabled`
-:  Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
@@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
 `failure_cache.ttl`
 :   The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.
 
-`failure_cache.enabled`
-:  Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
+`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
+:   Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
 
 ::::{note}
 Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.