Central DNS Traffic Scheduling for Low-Latency SD-WAN Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing domain name-based traffic scheduling scheme in SD-WAN networks results in long access delays due to domain name resolution on the client, requiring traffic to jump to the nearest DNS server, and frequent changes in flow table configurations when IP addresses change, leading to inefficient and complex traffic routing.
Innovation Solution
Forward domain name resolution requests to a central domain name system, which directs them to target egress gateways for resolution, and perform network address translation to obtain virtual network addresses, allowing data transmission based on these addresses, thus reducing access delays and minimizing flow table changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If domain name resolution is performed on the client, then traffic scheduling can be implemented, but access delays increase due to jumping to the nearest DNS server
Solution Approach 1:
The patent introduces a central DNS server as an intermediary between the client and the target DNS server. The client sends domain name resolution requests to the central DNS server, which then forwards them to the appropriate target DNS server. This mediator approach eliminates the need for the client to directly jump to distant DNS servers, thereby reducing access delays while maintaining domain name-based traffic scheduling capability.
2Adaptability or versatility
If IP addresses change frequently, then network flexibility is improved, but flow table configuration changes increase, leading to complex traffic routing
Solution Approach 1:
The patent implements a feedback mechanism where the central DNS server continuously monitors IP address changes and automatically updates the flow table configurations in the SD-WAN network. When the target DNS server returns a new IP address for a domain name, the central DNS server receives this information and triggers automatic flow table updates, eliminating the need for manual configuration changes and reducing complexity despite frequent IP address changes.
Solution Approach 2:
The system performs preliminary configuration by establishing the correspondence between domain names and egress gateways in advance through the central DNS server. This pre-configuration allows the network to automatically adapt to IP address changes without requiring real-time manual intervention, thereby maintaining network flexibility while minimizing the complexity of flow table management.
3Loss of time
If domain name resolution requests are forwarded through the central DNS system, then access delays are reduced, but the system complexity increases
Solution Approach 1:
The central DNS server is designed to perform multiple functions: it acts as a standard DNS resolver for clients, a traffic scheduler that determines optimal egress gateways, and an automatic flow table updater. By consolidating these functions into a single multi-functional component, the patent reduces overall system complexity compared to having separate specialized components for each function.
Data Source
AI summary
The present disclosure relates to the field of network communication technologies and discloses a traffic scheduling method, an apparatus, a device, a storage medium, and a program product. The method includes: forwarding a domain name resolution request of a business application to a central domain name system, wherein the domain name resolution request carries a target domain name, and the central domain name system is configured to forward the domain name resolution request to a target egress gateway corresponding to the target domain name; receiving a first target network address and a gateway address of the target egress gateway that are fed back by the central domain name system; performing network address translation on the first target network address to obtain a virtual network address; and performing data transmission based on the virtual network address, the gateway address, and the first target network address.