Overview
Private DNS is a DNS management service tailored for Virtual Private Clouds (VPCs), enabling the swift deployment of a DNS system across one or multiple customized VPCs. It simplifies the management of resources linked to the VPCs, such as CVMs, CLBs, CDNs, and COS, which are inaccessible externally, through the use of private DNS records.
Benefits
Flexible Configuration
Private DNS empowers users to establish customized private domains tailored to their specific requirements. These domains do not necessitate registration on the public network and can be promptly designated and labeled for enhanced flexibility and streamlined configuration.
Reverse DNS
Through the establishment of a private domain with a designated suffix and the configuration of a PTR record, it becomes possible to associate IP addresses with the domain, thus enabling reverse DNS functionality. This process significantly diminishes spam volume and enhances the transparency of IP utilization.
Load Balancing
Private DNS offers load balancing capabilities through various record types such as CNAME, A, AAAA, and TXT, supporting modes like “random response” and “weighted round robin.” By configuring the record value and weight, it effectively distributes client requests across multiple servers.
Request Volume Statistics
Private DNS enables users to filter and analyze request volume statistics based on region, VPC, or domain name, providing insights into instance consumption details and ensuring users remain informed.
Subdomain Recursive DNS
Upon enabling “Subdomain Recursive Query,” if a domain name query does not find a match within the VPC, it will undergo recursive querying on the public network.
High Security and Stability
Utilizing DNSPod’s extensive DNS infrastructure established over a decade and leveraging the VPC service, Private DNS delivers secure, reliable, and exceptionally available private DNS functionalities.
Custom Private Domain
Private DNS empowers you to establish personalized private domains tailored to your requirements. These domains do not necessitate registration on the public network and can be promptly identified and categorized for enhanced flexibility and ease of configuration.
Scenarios
Private Network Access Hijacking:
Private DNS enables the creation of private domain names associated with a VPC, allowing the addition of DNS records and resource mappings to implement private network access hijacking. Consequently, accessing the private domain within the VPC returns the predetermined mapped resource.
Service Resource Management:
Private DNS records facilitate the management of resources like CVM, CLB, CDN, and COS within VPCs. For instance, hosts of CVM instances can be planned according to region, business scenario, and server information. Subsequently, private domain names and DNS records can be added for these instances, ensuring accessibility exclusively within VPCs for streamlined resource management.
Mutual Access Between Service Resources:
VPCs and traditional IDCs can be interconnected through Direct Connect or VPN to enable mutual access to each other’s resources via private domain names, promoting intuitive utilization of service resources.
Service Resource Switching:
To ensure the stable operation of high-concurrency businesses distributed across multiple CVM instances, instances within the same VPC can mutually access each other via private IPs. However, instance switching typically necessitates modifying business code, which is cumbersome. By creating private domain names for each instance through Private DNS and adding DNS records pointing to corresponding private IPs, instances can access each other using domain names. Consequently, instance switching no longer requires code modification; instead, DNS record adjustments suffice.
How It Works:
In a VPC, a private domain “example.com” is created with a DNS record of “www host – CNAME record – domain.com record value”. Consequently, querying the CNAME record returns the configured result “domain.com”. If querying the A record of “test.domain.com”, as it is unconfigured, SOA will be returned.
In a VPC, enabling subdomain recursive DNS for a private domain “example.com”, a DNS record of “www host – A record – 8.8.8.8 record value” is added, and configured with a record value of “119.29.29.29” in the public authoritative DNS. Consequently, querying the A record returns the result “8.8.8.8”. If the private domain record is deleted, “119.29.29.29” will be returned.
Compute
Edge Computing
Container
Distributed Cloud
Microservice
Serverless
Essential Storage Service
Data Migration
Data Process and Analysis
Relational Database
NoSQL Database
Enterprise Distributed DBMS
Database SaaS Tool
Networking
CDN and Edge platform
Network Security
Data Security
Application Security
Endpoint Security
Business Security
Security Services
Security Management
Domains & Websites
Office Collaboration
Enterprise Applications
Data Analysis
Image Recognition
Face Recognition
Voice Technology
AI Platform Service
Natural Language Processing
Optical Character Recognition
Internet of Things
Message Queue
Middleware
Communication
Interactive Video Services
Stream Services
Media On-Demand
Media Process Services
Media SDK
Cloud Real-time Rendering
Game Services
Game Video Service
Education Services
Blockchain Service
Building Services
Cloud Resource Management
Management and Audit Tools
Developer Tools
Monitor and Operation
Education