Effective Date: 26/01/2026.
This DNS Server Policy (“Policy”) governs the use, configuration, and operation of Domain Name System (“DNS”) services provided by Govaio Network (“Govaio”, “we”, “us”, “our”) via https://www.govaio.com.
By using Govaio DNS services, you agree to comply with this Policy in addition to our Terms & Conditions, Acceptable Use Policy, Service Level Agreement (SLA), and Domain Policy.
1. PURPOSE OF DNS SERVICES
The purpose of Govaio DNS services is to:
Provide reliable domain name resolution
Ensure high availability and low latency
Protect against DNS abuse and attacks
Maintain global DNS stability and integrity
2. SCOPE OF DNS SERVICES
This Policy applies to:
Authoritative DNS hosting
Managed DNS
Shared DNS infrastructure
Dedicated DNS services (where applicable)
DNS records associated with domains using Govaio services
3. DNS SERVICE AVAILABILITY
3.1 Govaio provides DNS services on a best-effort basis, subject to SLA where applicable.
3.2 DNS uptime targets:
99.9% monthly availability for managed DNS services
3.3 Downtime exclusions:
Scheduled maintenance
DDoS attacks beyond mitigation capacity
Registry or upstream provider issues
Customer misconfiguration
3. DNS SERVICE AVAILABILITY
3.1 Govaio provides DNS services on a best-effort basis, subject to SLA where applicable.
3.2 DNS uptime targets:
99.9% monthly availability for managed DNS services
3.3 Downtime exclusions:
Scheduled maintenance
DDoS attacks beyond mitigation capacity
Registry or upstream provider issues
Customer misconfiguration
5. DNS RECORD MANAGEMENT
5.1 Supported record types include:
A, AAAA
CNAME
MX
TXT
SRV
NS
PTR (where supported)
5.2 Unsupported or malformed records may be rejected.
5.3 Customers must not configure records that:
Facilitate spam or phishing
Enable malware or botnets
Bypass security mechanisms
6. DNS PROPAGATION & TTL
6.1 DNS changes are not instantaneous.
6.2 Propagation time depends on:
TTL values
ISP caching behavior
Global resolver caching
6.3 Govaio is not responsible for delays caused by third-party resolvers.
6. DNS PROPAGATION & TTL
6.1 DNS changes are not instantaneous.
6.2 Propagation time depends on:
TTL values
ISP caching behavior
Global resolver caching
6.3 Govaio is not responsible for delays caused by third-party resolvers.
7. DNS SECURITY & ABUSE PREVENTION
7.1 Prohibited DNS Use
DNS services must NOT be used for:
Fast-flux hosting
Command-and-control infrastructure
Phishing redirection
Malware distribution
DNS tunneling without permission
8. RATE LIMITING & QUERY ABUSE
8.1 Govaio enforces query rate limits to:
Prevent abuse
Protect infrastructure
8.2 Excessive DNS queries may result in:
Temporary rate limiting
Suspension of DNS service
9. DNS CHANGES & AUDITING
9.1 DNS changes are logged for:
Security auditing
Troubleshooting
Abuse investigation
9.2 Customers are responsible for:
Maintaining internal change records
Limiting access to DNS management panels
9. DNS CHANGES & AUDITING
9.1 DNS changes are logged for:
Security auditing
Troubleshooting
Abuse investigation
9.2 Customers are responsible for:
Maintaining internal change records
Limiting access to DNS management panels
10. DNS & EMAIL DELIVERABILITY
10.1 Proper DNS configuration is essential for email delivery.
10.2 Customers are responsible for:
Correct MX records
SPF, DKIM, and DMARC TXT records
10.3 Govaio is not responsible for email delivery issues caused by DNS misconfiguration.
11. SUSPENSION & TERMINATION
11.1 Govaio may suspend DNS services for:
Abuse complaints
Policy violations
Legal requirements
Non-payment
11.2 Suspension may result in domain resolution failure.
12. DATA & LOG RETENTION
12.1 DNS logs may be retained for:
Security monitoring
Abuse handling
Compliance purposes
12.2 Logs are handled in accordance with the Data Protection Policy.
13. LIMITATION OF LIABILITY
Govaio is not liable for:
Downtime caused by DNS misconfiguration
Third-party resolver failures
Customer errors
Registry-level outages
13. LIMITATION OF LIABILITY
Govaio is not liable for:
Downtime caused by DNS misconfiguration
Third-party resolver failures
Customer errors
Registry-level outages
14. POLICY MODIFICATIONS
Govaio may modify this Policy at any time.
Changes take effect upon publication.
15. GOVERNING LAW
This Policy is governed by the laws of India, with exclusive jurisdiction of Indian courts.
ADDITIONAL SCOPES FOR DEDICATED DNS SERVICES
These scopes apply to customers who subscribe to Dedicated DNS or Enterprise DNS services provided by Govaio Network.
1. ISOLATED DNS INFRASTRUCTURE
Scope
Dedicated nameservers (NS) assigned per customer or organization
No shared DNS zones with other customers
Independent DNS configuration and zone management
Benefits
No reputation impact from other users
Enhanced security and privacy
Ideal for banks, SaaS, enterprises, and resellers
2. DEDICATED ANYCAST DNS NETWORK (OPTIONAL)
Scope
Anycast-enabled DNS nodes
Multiple geographic locations
Traffic routed to nearest DNS node
Benefits
Faster resolution globally
Improved redundancy
Higher DDoS resilience
3. CUSTOM NAMESERVER BRANDING
Scope
White-labeled nameservers (e.g.
ns1.customer.com)Branded DNS for resellers and enterprises
Custom reverse DNS (rDNS) where applicable
Benefits
Brand trust
Professional presentation
Better client retention for resellers
4. ENHANCED DNS SECURITY CONTROLS
Scope
DNSSEC signing
DDoS protection (L3/L4/L7 DNS attacks)
Query rate limiting per zone
Zone transfer restrictions (AXFR/IP allowlist)
Benefits
Protection from DNS hijacking
Compliance with enterprise security standards
Reduced attack surface
4. ENHANCED DNS SECURITY CONTROLS
Scope
DNSSEC signing
DDoS protection (L3/L4/L7 DNS attacks)
Query rate limiting per zone
Zone transfer restrictions (AXFR/IP allowlist)
Benefits
Protection from DNS hijacking
Compliance with enterprise security standards
Reduced attack surface
5. HIGH QUERY RATE & PERFORMANCE GUARANTEES
Scope
Higher DNS query-per-second (QPS) limits
No aggressive throttling
Priority processing during peak loads
Benefits
Stable performance for high-traffic websites
Suitable for APIs, apps, and large portals
7. CHANGE MANAGEMENT & AUDITING
Scope
DNS change history
Role-based access control (RBAC)
Multi-user access with permissions
Change approval workflows (optional)
Benefits
Reduced human error
Enterprise governance
Audit readiness
8. SLA-BACKED DEDICATED DNS UPTIME
Scope
Higher uptime SLA (e.g. 99.99%)
Faster incident response
Priority escalation path
Benefits
Mission-critical reliability
Contractual assurance
8. SLA-BACKED DEDICATED DNS UPTIME
Scope
Higher uptime SLA (e.g. 99.99%)
Faster incident response
Priority escalation path
Benefits
Mission-critical reliability
Contractual assurance
9. DNS FAILOVER & HEALTH CHECKS
Scope
Automated health checks
Failover between IPs or regions
Weighted or priority-based routing
Benefits
High availability
Disaster recovery support
10. API ACCESS & AUTOMATION
Scope
DNS management API
Infrastructure-as-code compatibility
Automated zone updates
Benefits
DevOps-friendly
Faster deployments
Reduced manual errors
11. CUSTOM TTL & CACHE CONTROL
Scope
Ultra-low TTL support
Granular cache control
Rapid change propagation options
Benefits
Fast failover
Dynamic applications
Blue-green deployments
12. COMPLIANCE & REGULATORY SUPPORT
Scope
Data residency options (where available)
Audit documentation
Compliance reporting support
Benefits
Enterprise & government readiness
Easier vendor onboarding
14. DEDICATED SUPPORT & ESCALATION
Scope
Priority support queue
Direct NOC escalation
Named technical contact (optional)
Benefits
Faster resolution
Higher accountability
15. USE CASES FOR DEDICATED DNS
Dedicated DNS is recommended for:
Financial institutions
SaaS platforms
High-traffic eCommerce
Enterprises & government entities
Large resellers
API-driven applications
DNS FAILOVER POLICY
This DNS Failover Policy (“Policy”) defines the scope, operation, limitations, and responsibilities related to DNS-based failover services provided by Govaio Network (“Govaio”, “we”, “us”, “our”).
This Policy applies to customers using Managed DNS, Dedicated DNS, or Enterprise DNS services with failover functionality enabled.
1. PURPOSE OF DNS FAILOVER
The purpose of DNS failover is to:
Improve service availability
Redirect traffic during outages
Reduce downtime impact
Provide disaster recovery support
DNS failover operates at the DNS level and is not a substitute for application-level redundancy.
1. PURPOSE OF DNS FAILOVER
The purpose of DNS failover is to:
Improve service availability
Redirect traffic during outages
Reduce downtime impact
Provide disaster recovery support
DNS failover operates at the DNS level and is not a substitute for application-level redundancy.
3. FAILOVER MECHANISM
3.1 Health Checks
Failover is triggered based on automated health checks, which may include:
ICMP (Ping)
TCP port checks
HTTP / HTTPS response codes
Custom endpoint checks (enterprise plans)
Health check intervals and thresholds are configurable per plan.
3.2 Failover Logic
Failover actions may include:
Switching from primary IP to secondary IP
Routing traffic to backup region
Weighted or priority-based routing
Failover is dependent on DNS TTL values and global resolver caching.
4. TTL & PROPAGATION LIMITATIONS
4.1 DNS failover is not instantaneous.
4.2 Actual failover time depends on:
Configured TTL
ISP and resolver cache behavior
End-user DNS settings
4.3 Ultra-low TTLs may be supported on Dedicated DNS but may increase query load.
5. CUSTOMER RESPONSIBILITIES
Customers are responsible for:
Configuring valid primary and secondary endpoints
Maintaining functional backup infrastructure
Testing failover regularly
Selecting appropriate TTL values
Govaio does not create or manage customer backend infrastructure unless explicitly agreed.
6. SUPPORTED FAILOVER SCENARIOS
Supported:
Active-Passive setups
Regional failover
Disaster recovery redirection
Not supported:
Application-level session persistence
Database replication
Load balancing beyond DNS level
6. SUPPORTED FAILOVER SCENARIOS
Supported:
Active-Passive setups
Regional failover
Disaster recovery redirection
Not supported:
Application-level session persistence
Database replication
Load balancing beyond DNS level
7. EMAIL FAILOVER LIMITATIONS
7.1 DNS failover for email (MX records):
Does not guarantee message delivery
Depends on sender retry behavior
7.2 Email failover is best-effort only.
8. FAILOVER TESTING
8.1 Customers are encouraged to:
Perform scheduled failover tests
Validate DNS responses
Verify application behavior
8.2 Govaio is not responsible for service disruption caused by testing.
9. MONITORING & ALERTING
9.1 Govaio may provide:
Health check status
Failover event logs
Alerts (email or dashboard)
9.2 Alert delivery depends on customer contact details.
11. LIMITATIONS & EXCLUSIONS
Govaio is not responsible for failover failure caused by:
Misconfigured DNS records
High TTL values
Third-party DNS resolvers
Backend application failures
Force majeure events
12. ABUSE & MISUSE
DNS failover must not be used to:
Evade abuse detection
Hide malicious infrastructure
Rotate endpoints for illegal activity
Violation may result in suspension.
13. SUSPENSION & TERMINATION
Govaio may suspend DNS failover services for:
Policy violations
Non-payment
Abuse investigations
Legal requirements
14. DATA & LOGGING
Failover-related logs may include:
Health check results
Failover timestamps
Endpoint status
Logs are handled per the Data Protection Policy.
15. NO WARRANTY
DNS failover is provided on a best-effort basis.
Govaio does not guarantee:
Zero downtime
Immediate traffic redirection
Specific recovery times
16. POLICY MODIFICATIONS
Govaio may modify this Policy at any time.
Changes take effect upon publication.
17. GOVERNING LAW
16. POLICY MODIFICATIONS
Govaio may modify this Policy at any time.
Changes take effect upon publication.
18. CONTACT INFORMATION
For DNS failover queries: