Effective Date: August 14, 2026
1. SCOPE AND DEFINITIONS
1.1. Service Definition.
These Terms govern the "Managed DNS" service provided by the Pinkdude Group ("Provider"). The Service consists of:
(a) Authoritative DNS: Provisioning of nameservers (e.g., ns1.pinkdude.com, ns2.pinkdude.com) to host the DNS Zone File for the Customer’s domain.
(b) Record Management: Tools for creating, editing, and deleting DNS records (A, CNAME, MX, TXT, SRV, etc.).
1.2. NOT a Domain Registrar.
The Provider is NOT an ICANN-accredited Registrar or a Domain Reseller.
(a) No Registration: We do not register, renew, or transfer domain names.
(b) Customer Duty: You are solely responsible for maintaining your domain registration with your third-party Registrar (e.g., Namecheap, GoDaddy). If your domain expires at your Registrar, our DNS Service will cease to function immediately. We have no control over the lifecycle of the domain name string itself.
1.3. Customer Redundancy Responsibility.
The Customer is solely responsible for maintaining appropriate redundancy where DNS availability is critical, including the use of secondary DNS providers if desired. The Provider does not guarantee that the Managed DNS Service alone is sufficient for mission-critical availability without independent Customer-managed redundancy.
2. DNS MANAGEMENT AND AUTOMATION
2.1. Customer Responsibility (The "Fat Finger" Clause).
You acknowledge that DNS is a critical infrastructure component.
(a) Accuracy: You are solely responsible for the accuracy of records entered into the Dashboard. A single typo in an A-Record or MX-Record can render your website or email unreachable.
(b) No Validation: The Provider does not validate the logical correctness of your records. We broadcast exactly what you type.
(c) TTL (Time To Live): You understand that changes to DNS records are subject to "Caching" by ISPs worldwide. We are not responsible for downtime caused by high TTL values set by you or previous providers.
2.2. Automated Record Injection.
To facilitate the instant provisioning of Provider Services (e.g., Analytics, Mail Servers, Web Hosting), you grant the Provider explicit permission to automatically modify your DNS Zone File.
(a) Auto-Configuration: We may automatically inject, update, or overwrite records (e.g., SPF, DKIM, CNAME) required to validate your ownership of a service or route traffic to our infrastructure.
(b) Conflict Waiver: While we use commercially reasonable logic to avoid conflicts, the Provider is not liable if an automated record update inadvertently interferes with a pre-existing manual configuration.
2.3. Propagation Delays.
You acknowledge that the Internet Domain Name System (DNS) relies on a distributed cache.
(a) Global Propagation: Changes made to your records may take up to 48 hours or longer in exceptional circumstances to propagate globally.
(b) No Liability: The Provider cannot expedite this process and is not liable for service unavailability, lost emails, or traffic drops during this propagation window.
2.4. Recursive Resolver Disclaimer.
The Provider is not responsible for delays, failures, or resolution errors caused by third-party recursive resolvers (e.g., Google DNS, Cloudflare 1.1.1.1, ISP caches) or corporate firewalls. We control only our Authoritative Nameservers; we cannot control how third-party resolvers cache or expire your records.
2.5. Configuration Backup Disclaimer.
The Customer is responsible for maintaining independent backups of DNS configurations. The Provider does not guarantee that zone files can be recovered or rolled back in the event of accidental deletion or corruption by the Customer.
3. AVAILABILITY AND ATTACKS
3.1. Infrastructure Protection.
The DNS Service is a shared resource. An attack on one Customer’s zone can affect others.
(a) DDoS Attacks: If your domain becomes the target of a DNS-based Distributed Denial of Service (DDoS) attack (e.g., NXDOMAIN flood, DNS Amplification) that threatens the stability of our Nameservers, we reserve the right to "Null-Route" your domain or suspend DNS resolution immediately and without notice.
(b) Migration Order: In the event of persistent attacks, we may require you to move your DNS hosting to a specialized mitigation provider (e.g., Cloudflare) to protect our infrastructure.
3.2. Query Limits.
(a) Fair Use: The Service is intended for normal business traffic. We reserve the right to throttle or charge overage fees for domains exceeding reasonable query-per-second limits as determined by the Provider, unless a dedicated high-traffic plan is purchased.
3.3. Emergency Changes Clause.
The Provider reserves the right to temporarily modify, disable, or redirect DNS records where reasonably necessary to mitigate security threats, infrastructure instability, or active attacks. This right may be exercised without prior notice to protect the integrity of the Provider’s network.
4. SECURITY AND ABUSE
4.1. Zone File Content.
You may not use the DNS Service to facilitate illegal activities.
(a) Fast-Flux: The use of "Fast-Flux" DNS techniques (rapidly changing IPs to hide malicious hosting) is strictly prohibited.
(b) Malicious Pointers: You may not point records to known malware distribution sites, Phishing pages, or C&C (Command & Control) servers.
(c) Take Down: We reserve the right to remove specific records or suspend the entire Zone if we receive a credible abuse report, as determined by the Provider in its reasonable discretion, indicating the domain is resolving to illegal content.
5. TERMINATION AND OFF-BOARDING
5.1. Effect of Termination.
Upon termination of your Account or the DNS Service:
(a) Zone Deletion: Your DNS Zone File may be deleted immediately.
(b) Resolution Failure: Your domain will stop resolving globally. It is your sole responsibility to change your Nameservers at your Registrar before terminating the Service to avoid downtime.
(c) No Export Duty: We are not obligated to export your zone file or migrate your records to a new provider.
6. LIMITATION OF LIABILITY (DNS SPECIFIC)
6.1. Resolution Failures.
THE PROVIDER DOES NOT GUARANTEE 100% UPTIME FOR DNS RESOLUTION.
(a) Traffic Loss: We are not liable for lost website traffic, lost sales, or undelivered emails resulting from DNS resolution failures, propagation delays, or ISP caching issues.
(b) Third-Party Failures: We are not liable for resolution failures caused by TLD Registry outages (e.g., Verisign) or upstream connectivity issues.
6.2. No Mission-Critical Use.
The DNS Service is not designed for use in environments where failure could lead to death, personal injury, or severe environmental damage. The Provider is not liable for any catastrophic damages arising from the unavailability of DNS resolution for mission-critical applications. This limitation is subject always to the maximum liability limitation set forth in the Master Terms of Service.