DNS Availability Zone Routing for Cloud Service Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for domain name resolution in cloud computing services with multiple availability zones (AZs) result in high delays and service interruptions due to the need for manual switching or repeated attempts to find a functional AZ when one becomes faulty.
Innovation Solution
A domain name system (DNS) that proactively determines and sends the IP address of a service-available AZ to the client, based on real-time monitoring of AZ statuses, heartbeats, and loads, reducing the need for manual intervention and client-driven attempts, and optimizing access performance by selecting the closest or least loaded AZ.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual switching or repeated attempts are used to find a functional AZ when one becomes faulty, then service availability is maintained, but service delay increases and continuity is reduced
Solution Approach 1:
The DNS server proactively monitors the service status of multiple availability zones in advance and pre-determines alternative AZs before faults occur. When a fault is detected, the DNS server has already identified available alternatives, eliminating the need for manual switching or repeated client attempts, thus reducing service delay while maintaining availability
Solution Approach 2:
The system implements real-time feedback mechanisms where the DNS server continuously monitors AZ service status and immediately responds to status changes. This feedback loop enables the DNS server to detect faults and redirect clients to alternative AZs automatically, preventing time loss associated with manual intervention or client-side retry logic
2Reliability
If manual switching of AZ address is performed by operation and maintenance personnel, then service continuity is maintained, but operational complexity and time consumption increase
Solution Approach 1:
The DNS server autonomously monitors AZ status, detects faults, and performs switching operations without human intervention. The system self-manages the entire fault detection and recovery process, eliminating the need for operation and maintenance personnel to manually switch AZ addresses, thus improving ease of operation while maintaining service continuity
Solution Approach 2:
The DNS server pre-configures multiple AZ addresses and proactively monitors their status. When faults are detected, the server has already prepared alternative routing information, enabling automatic switching without requiring manual configuration or intervention, thereby simplifying operations while ensuring continuity
3Reliability
If the client makes repeated attempts to find a usable AZ, then service availability is ensured, but access delay and client resource consumption increase
Solution Approach 1:
The DNS server acts as an intermediary between clients and AZs, managing the complexity of multiple AZ addresses and their status. Instead of clients directly attempting multiple AZs, the DNS server filters and provides only the currently available AZ addresses to clients, eliminating repeated failed attempts and reducing access delay while ensuring service accessibility
Solution Approach 2:
The DNS server proactively determines and caches the status of multiple AZs in advance. When clients request access, the server has already identified which AZs are available and provides the optimal choice directly, preventing clients from making repeated attempts and reducing access delay while maintaining service accessibility
Data Source
AI summary
The present disclosure provides a domain name resolution method and apparatus based on a plurality of availability zones (AZ). After receiving, from a client, a domain name resolution request including a domain name of a to-be-accessed resource, a domain name system (DNS) determines, from a plurality of AZs corresponding to the domain name, a first AZ in a service available state, where each of the plurality of AZs is capable of providing the to-be-accessed resource, and then sends an internet protocol (IP) address of the first AZ to the client. In this way, the DNS processes the domain name resolution request sent by the client. After receiving the domain name resolution request sent by the client, the DNS feeds back, to the client, an IP address that is of an AZ in the service available state and that corresponds to the domain name resolution request.