feat(dns): implement max 24 hour data loss

Author: Wouter0100

dns/docs/description.md

@@ -18,7 +18,7 @@ The DNS service is integrated seamlessly with the broader CBWS ecosystem, making
 
 * **Distributed & Redundant Cluster:** Your DNS zones are replicated across a distributed cluster, ensuring that if one node fails, others seamlessly pick up the query load without interruption.
 * **High Availability & Reliability:** Designed from the ground up to prevent single points of failure, ensuring your applications remain discoverable. 
-* **Zero Data Loss (RPO):** Thanks to our synchronously replicated and highly redundant setup, our Recovery Point Objective (RPO) guarantees no loss of your DNS records and configurations.
+* **Minimal Data Loss (RPO)**: Thanks to our replicated and highly redundant setup, we strive for almost no data loss. In the unlikely worst-case scenario, our Recovery Point Objective (RPO) is a maximum of 24 hours, and any potential loss is strictly limited to DNS records and zone configurations.
 * **Rapid Recovery (RTO):** Our Recovery Time Objective (RTO) is strictly aligned with our 99.9% uptime guarantee, ensuring any service restoration happens within the allowed downtime window.
 
 ## Service Level Agreement (SLA)

dns/docs/sla.md

@@ -12,7 +12,7 @@ This document outlines the Service Level Agreement (SLA) specific to the CBWS ma
 
 ## Recovery Objectives
 
-* **Recovery Point Objective (RPO):** Due to the heavily redundant, distributed nature of our DNS cluster setup, our RPO is zero data loss. Your DNS zone data and records are safely replicated across the cluster.
+* **Recovery Point Objective (RPO):** Due to the heavily redundant, distributed nature of our DNS cluster setup, our RPO is designed to ensure almost no data loss under normal operating conditions. In a worst-case disaster scenario, the maximum potential data loss is up to 24 hours, and this is exclusively restricted to DNS records.
 * **Recovery Time Objective (RTO):** Our RTO is strictly based on maintaining our 99.9% uptime commitment, meaning total permitted downtime for recovery operations will not exceed approximately 43.8 minutes in a standard 30-day billing month.
 
 ## Downtime Measurement