Dual-stack network adaptive scheduling method and system based on DNS analysis strategy

Abstract

The invention relates to the technical field of network communication, provides a dual-stack network adaptive scheduling method and system based on a DNS analysis strategy, and is used for establishing an effective protocol stack feature association mechanism so as to realize cross-protocol-layer intelligent scheduling. The method comprises the steps that a DNS analysis request sent by a client side is received, and the DNS analysis request carries a target domain name and a request protocol type; analyzing the request protocol type to determine a network protocol stack type supported by the client; generating an adaptive scheduling strategy corresponding to the target domain name according to the network protocol stack type and a preset address type priority list; selecting a target IP address type from a pre-configured IP address pool based on the self-adaptive scheduling strategy; and returning an analysis result corresponding to the target IP address type to the client so as to guide the client to establish network connection through the target IP address type.

Description

Technical Field

[0001] The present application belongs to the field of network communication technology, and specifically relates to a dual-stack network adaptive scheduling method and system based on DNS resolution strategy. Background Art

[0002] In the current Internet environment, the network protocol stacks supported by client devices are showing a diversified development trend. Dual-stack deployment of IPv4 and IPv6, and coexistence of QUIC and TCP protocols are becoming increasingly common. Traditional DNS resolution systems are usually based on statically configured address return policies, such as returning IPv6 addresses first to promote network upgrades, or allocating IP addresses of different protocol types through a simple polling mechanism.

[0003] However, existing technologies fail to effectively identify the network protocol capabilities actually supported by the client, resulting in the returned address type possibly exceeding the compatibility range of the client protocol stack, causing network connection failure. Secondly, traditional address selection strategies lack a dynamic adaptation mechanism and are unable to dynamically adjust priorities based on client protocol stack characteristics, resulting in inefficient utilization of network resources. In addition, existing solutions rely heavily on clients to actively report protocol support information, which adds additional communication overhead and implementation complexity, and is prone to delay sensitivity issues, especially in mobile scenarios. It can be seen that the existing DNS system has not yet established an effective protocol stack feature association mechanism, making it difficult to achieve intelligent scheduling across protocol layers. Summary of the invention

[0004] The present application provides a dual-stack network adaptive scheduling method and system based on DNS resolution strategy, which is used to establish an effective protocol stack feature association mechanism, thereby realizing intelligent scheduling across protocol layers.

[0005] In the first aspect, an embodiment of the present application provides a dual-stack network adaptive scheduling method based on DNS resolution strategy, which is applied to a dual-stack network adaptive scheduling system, the method comprising: receiving a DNS resolution request sent by a client, the DNS resolution request carrying a target domain name and a request protocol type; parsing the request protocol type to determine the network protocol stack type supported by the client; generating an adaptive scheduling policy corresponding to the target domain name according to the network protocol stack type and a preset address type priority list; based on the adaptive scheduling policy, selecting a target IP address type from a preconfigured IP address pool; and returning the resolution result corresponding to the target IP address type to the client to guide the client to establish a network connection through the target IP address type.

[0006] In a second aspect, an embodiment of the present application provides a dual-stack network adaptive scheduling system, which includes a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the above method.

[0007] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, which includes a computer program. When the computer program is run on a dual-stack network adaptive scheduling system, the computer program is used to enable the dual-stack network adaptive scheduling system to perform the steps of the above method.

[0008] The embodiment of the present application realizes multi-dimensional optimization of network connection through protocol perception and intelligent scheduling mechanism, and significantly improves the resource adaptation capability in heterogeneous network environment. Different from the passive response mode of traditional DNS resolution, this solution innovatively constructs the closed-loop logic of client protocol stack resolution and address type decision, which can deeply identify the network protocol support characteristics of the client and dynamically generate adaptation strategies. By introducing the elastic mapping mechanism of the address type priority list, the optimal IP address type can be intelligently screened according to the real-time protocol stack characteristics, and the client can be actively guided to establish the most efficient network channel on the basis of ensuring protocol compatibility. This technology breaks through the limitations of traditional single-dimensional scheduling, realizes seamless collaboration between IPv4 / IPv6 dual stack environment and emerging network protocols (such as HTTP / 3), and effectively avoids delay losses caused by protocol fallback. At the same time, the pre-decision mechanism based on protocol stack characteristics can significantly shorten the connection establishment time window and improve end-to-end communication efficiency by eliminating redundant protocol negotiation processes. This protocol-sensitive intelligent scheduling system not only strengthens the forward-looking adaptation capability of network services, but also provides a smooth transition path for the evolution of multi-protocol ecology, and has significant value in network resource optimization.

[0009] In summary, the embodiments of the present application can establish an effective protocol stack feature association mechanism, thereby realizing intelligent scheduling across protocol layers. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A schematic diagram of a flow chart of a dual-stack network adaptive scheduling method based on a DNS resolution strategy provided in an embodiment of the present application.

[0011] Figure 2 A schematic diagram of the structure of a dual-stack network adaptive scheduling system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0012] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the technical solution of the present application, rather than all of the embodiments. Based on the embodiments recorded in the application documents, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the technical solution of the present application.

[0013] See also Figure 1 , which is a dual-stack network adaptive scheduling method based on DNS resolution strategy provided in an embodiment of the present application. The method can be applied to a dual-stack network adaptive scheduling system. The specific process is as follows: Step 101-Step 105.

[0014] Step 101: Receive a DNS resolution request sent by a client, wherein the DNS resolution request carries a target domain name and a request protocol type.

[0015] In this embodiment, the dual-stack network adaptive scheduling system receives the DNS resolution request sent by the client through the core switch of the enterprise office network. The client is an office terminal device used by internal employees of the enterprise, which is connected to the enterprise LAN via wired or wireless means and triggers the domain name resolution process when accessing the target business system.

[0016] For example, when an employee enters the target domain name "oa.example.com" in the browser, the client generates a DNS query message containing the target domain name and the requested protocol type. The requested protocol type is implicitly carried through the extended field EDNS Client Subnet (ECS) in the DNS message header, which is specifically manifested as the protocol stack type activated in the client network interface card (NIC) configuration. In the enterprise network environment, the request is filtered by the security policy of the edge firewall and forwarded by the enterprise intranet DNS server to the resolution processing module of the dual-stack network adaptive scheduling system.

[0017] Step 102: Parse the request protocol type to determine the network protocol stack type supported by the client.

[0018] In this embodiment, the protocol analysis module of the dual-stack network adaptive scheduling system performs in-depth analysis on the received DNS resolution request, focusing on extracting the relevant features of the request protocol type. The analysis process is achieved by deconstructing the application layer load of the DNS message, specifically including identifying the transport layer protocol identifier, parsing the DNS extended option field, and associating the network session context information.

[0019] For example, when the client network protocol stack is configured with only an IPv4 address, the DNS query message it generates will only contain the IPv4 source address field, and the EDNS extension will not carry IPv6-related parameters; if the client has enabled dual protocol stacks, the DNS request will contain both the IPv6 flow label field and the IPv4 service type (ToS) field. By comparing the terminal protocol configuration list preset in the enterprise network device management system, the system can accurately determine the type of network protocol stack actually supported by the current client, including IPv4 single stack, IPv6 single stack, or dual protocol stack.

[0020] Step 103: Generate an adaptive scheduling policy corresponding to the target domain name according to the network protocol stack type and a preset address type priority list.

[0021] In this embodiment, the policy generation module of the dual-stack network adaptive scheduling system generates an adaptive scheduling policy for the target domain name based on the identified network protocol stack type and the address type priority list preset by the enterprise network administrator. The address type priority list is stored in the policy database of the system, and its content reflects the protocol evolution strategy of the enterprise network, such as setting rules such as dual-stack clients to use IPv6 addresses first and single-stack clients to match existing protocol types.

[0022] For another example, when the target domain name "oa.example.com" corresponds to a business system that has completed IPv6 transformation, the priority list will be configured as follows: dual-stack clients return AAAA records, IPv4 single-stack clients return A records, and IPv6 single-stack clients trigger protocol conversion services. During the policy generation process, the dual-stack network adaptive scheduling system also refers to the real-time collected network status indicators, including the link load rate of each protocol stack, end-to-end delay measurement value, and address resource pool capacity, and dynamically adjusts the weight parameters of the final output policy.

[0023] Step 104: Based on the adaptive scheduling policy, select a target IP address type from a preconfigured IP address pool.

[0024] In this embodiment, the address selection module of the dual stack network adaptive scheduling system selects a set of candidate addresses that meet the target address type from a pre-configured IP address pool according to the generated adaptive scheduling strategy. The IP address pool is dynamically synchronized by connecting to the enterprise network infrastructure management platform, and includes IPv4 A records and IPv6 AAAA records published by each business system.

[0025] For example, for the enterprise file server corresponding to the target domain name "file.example.com", the address pool maintains two records: IPv4 address 192.0.2.45 and IPv6 address 2001:db8::1:10. When the policy requires the priority selection of IPv6 addresses, the selection module will perform the following operations: first verify the accessibility of the IPv6 address in the current network topology, then check the service status of the target server IPv6 port, and finally select the optimal access point based on the client's geographic location (obtained through EDNS Client Subnet). For scenarios where there are multiple qualified addresses, the system uses a weighted polling algorithm for load balancing, and the weight value is dynamically calculated based on the historical connection success rate and response time.

[0026] Step 105: Return the parsing result corresponding to the target IP address type to the client to guide the client to establish a network connection through the target IP address type.

[0027] In this embodiment, the response processing module of the dual-stack network adaptive scheduling system encapsulates the resolution result corresponding to the selected target IP address type into a standard DNS response message, and returns it to the client through the enterprise intranet DNS server. The response message strictly follows the RFC standard format and adapts different transport layer encapsulation methods according to the protocol stack type supported by the client.

[0028] For example, for clients that support IPv6, the system carries a resource record (RR) of the AAAA record type in the Answer Section of the response message, and its RDATA field is filled with the verified IPv6 address 2001:db8::1:10; for clients that only support IPv4, a resource record of the A record type is returned. The resolution result guides the client to establish a network connection that conforms to the target address type. When the client application layer initiates a TCP three-way handshake, its protocol stack automatically selects the IP version that matches the resolution result for data packet encapsulation. The system synchronously updates the resolution log and triggers the connection tracking mechanism to record the address type actually used by the client and the connection establishment success rate, providing data support for subsequent strategy optimization.

[0029] In the above application scenarios, the dual-stack network adaptive scheduling system realizes intelligent perception of protocol stack types and dynamic scheduling of address resources by deeply integrating the infrastructure of the enterprise network. This effectively solves the problems of rigid protocol selection and low address resource utilization in traditional dual-stack networks, and gradually promotes the IPv6 deployment process of enterprise networks while maintaining backward compatibility. In addition, through the adaptive policy generation mechanism, the dual-stack network adaptive scheduling system can automatically optimize the traffic distribution of different protocol stacks according to changes in network status and business needs, significantly improving the reliability of enterprise network services and resource utilization efficiency.

[0030] In one implementation, the step 103 of generating an adaptive scheduling strategy corresponding to the target domain name according to the network protocol stack type and a preset address type priority list includes: Step 1031: Acquire in real time a first real-time parameter set of the IPv4 network link associated with the target domain name, wherein the first real-time parameter set includes IPv4 link delay, IPv4 node available bandwidth, and IPv4 request response success rate.

[0031] In an embodiment of the present application, the link monitoring module of the dual-stack network adaptive scheduling system obtains the first real-time parameter set of the IPv4 network link associated with the target domain name in real time through the traffic mirror port of the core switch of the enterprise office network. Among them, the IPv4 link delay is obtained by sending an ICMP detection packet to the authoritative DNS server of the target domain name and calculating the round-trip time. In specific implementation, the dual-stack network adaptive scheduling system takes the preset monitoring node 192.0.2.45 in the IPv4 address pool corresponding to "oa.example.com" as the target, and sends a detection message containing a specific timestamp every 5 seconds. The measurement of the available bandwidth of the IPv4 node is based on the traffic statistics of the enterprise wide area network egress router, and is calculated by analyzing the relationship between the change of the TCP session window size and the data packet transmission rate per unit time. The IPv4 request response success rate is obtained by counting the TCP three-way handshake success ratio of the client to initiate an HTTP connection to the domain name IPv4 address in the last 10 minutes. For example, if 98 sessions are successfully established out of 100 connection requests, the recorded success rate is 98%.

[0032] Step 1032: Synchronously collect a second real-time parameter set of the IPv6 network link associated with the target domain name, wherein the second real-time parameter set includes IPv6 link throughput, IPv6 node load balancing index, and IPv6 path hop count.

[0033] In step 1032, the IPv6 performance collection unit of the dual-stack network adaptive scheduling system interacts with the enterprise software-defined network controller to synchronously collect the second real-time parameter set of the IPv6 network link associated with the target domain name. The measurement of the IPv6 link throughput adopts the segment routing monitoring technology. For the service cluster where the IPv6 address 2001:db8::1:10 corresponding to "oa.example.com" is located, the total amount of effective load transmitted per unit time is counted by analyzing the flow label field in the IPv6 extension header across the enterprise data center boundary router. The IPv6 node load balancing index is obtained by parsing the real-time resource utilization data of the target server, specifically including the weighted average of the three parameters of CPU usage, memory occupancy and number of active TCP connections of each IPv6 node. The determination of the IPv6 path hop count is performed by executing the Traceroute6 tool to trace the path of the target address and counting the number of forwarding times of the three-layer network devices from the client subnet to the target server. For example, if the measured path is client gateway→core switch→border router→IDC access switch→target server, the hop count is recorded as 4.

[0034] Step 1033: Compare the first real-time parameter set with the preset IPv4 benchmark parameters to generate an IPv4 link quality score; compare the second real-time parameter set with the preset IPv6 benchmark parameters to generate an IPv6 link quality score.

[0035] In an embodiment of the present application, the quality assessment module of the dual-stack network adaptive scheduling system compares the first real-time parameter set with the preset IPv4 benchmark parameters to generate an IPv4 link quality score. The above comparison process adopts a multi-dimensional parameter normalization algorithm. For example, when the current IPv4 link delay is 28ms (the benchmark value is 30ms), the available bandwidth is 95Mbps (the benchmark value is 100Mbps), and the request response success rate is 99% (the benchmark value is 98%), the dual-stack network adaptive scheduling system obtains a comprehensive score through a weighted calculation formula. Exemplarily, the delay parameter weight is set to 40%, the bandwidth weight is 35%, and the success rate weight is 25%, and a score result 3% higher than the benchmark value is finally generated. In the simultaneous calculation of the IPv6 link quality score, the system compares the throughput, load balancing index and path hop count in the second real-time parameter set with the IPv6 performance baseline set by the enterprise network operation and maintenance department. For example, if the measured IPv6 throughput reaches 110% of the benchmark value, the load index is 15% better than the baseline, and the path hop count is 1 more than expected, the final score is obtained by dynamically adjusting the weight coefficients of each parameter.

[0036] Step 1034: Dynamically adjust the sorting weights of IPv4 and IPv6 in the address type priority list according to the difference between the IPv4 link quality score and the IPv6 link quality score.

[0037] In the embodiment of the present application, the weight adjustment module of the dual stack network adaptive scheduling system dynamically adjusts the sorting weight of the address type priority list according to the difference between the IPv4 and IPv6 link quality scores. When the IPv4 link quality score of the "file.example.com" domain name is monitored to be 85 points, the IPv6 score is 78 points, and the difference exceeds the preset first threshold of 10 points, the dual stack network adaptive scheduling system will increase the sorting level of IPv4 in the priority list by two levels.

[0038] On the contrary, if the IPv6 score of the same domain name reaches 92 points during peak business hours and the IPv4 score drops to 80 points and the difference exceeds the second threshold of 8 points, the IPv6 priority policy upgrade is triggered. When the difference between the two scores is in the dynamic adjustment range of 5-7 points, the system maintains the existing weight configuration unchanged to ensure the stability of the scheduling strategy.

[0039] At the same time, the dual-stack network adaptive scheduling system retrieved the historical connection records of the domain name in the past 24 hours and found that the successful connection rate of the IPv6 address continued to remain above 99.5%, while the IPv4 address had a 2% failure rate. Based on this, the weight generated by the real-time score was corrected with a +5% success rate compensation.

[0040] Step 1035: Based on the adjusted sorting weights, an adaptive scheduling policy including a dynamic split ratio of IPv4 addresses to IPv6 addresses is generated, where the dynamic split ratio is used to control the address allocation priority of different protocol stacks.

[0041] In an embodiment of the present application, the policy generation module of the dual-stack network adaptive scheduling system generates an adaptive scheduling policy including a dynamic diversion ratio of IPv4 and IPv6 addresses based on the adjusted sorting weights. For the "mail.example.com" mail system domain name, when the real-time weight shows that the IPv6 priority is 65% and the IPv4 priority is 35%, the dual-stack network adaptive scheduling system will be configured to return a mixed resolution result of 3 IPv6 addresses and 2 IPv4 addresses to the dual-protocol stack client, forming an address allocation ratio of 6:4. This address allocation ratio is achieved by sorting multiple resource records in the DNS response message. The AAAA record of the IPv6 address is arranged before the A record, guiding most clients to establish IPv6 connections first. At the same time, the dual-stack network adaptive scheduling system deploys a protocol type counter at the enterprise wide area network exit to monitor the actual usage of different address types in real time. When it is detected that the proportion of IPv6 connections is lower than the preset target value, the weight readjustment process is automatically triggered.

[0042] In the next step, the step 1034 dynamically adjusts the sorting weights of IPv4 and IPv6 in the address type priority list according to the difference between the IPv4 link quality score and the IPv6 link quality score, including: (1) If the IPv4 link quality score is higher than the IPv6 link quality score and the difference exceeds a first threshold, the ranking of IPv4 in the address type priority list is increased.

[0043] In this step, when the dual-stack network adaptive scheduling system determines that the IPv4 link quality score is higher than that of IPv6 and the difference exceeds the first threshold, the protocol stack priority adjustment operation is performed. For example, for the video conferencing system domain name "meet.example.com", when the IPv4 link delay is stable at 25ms and the IPv6 link delay reaches 45ms due to incomplete path optimization, the dual-stack network adaptive scheduling system compares the difference in quality scores between the two and is 15 points (exceeding the set threshold of 10 points), and immediately raises the ranking of IPv4 in the address type priority list from the second level to the first level. This adjustment is achieved by modifying the protocol stack priority field in the policy database, so that IPv4 addresses are given priority in subsequent resolution request processing. Furthermore, the promotion operation follows the principle of gradual adjustment, and each level change does not exceed two gradients to prevent policy shocks caused by instantaneous fluctuations in network status.

[0044] (2) If the IPv6 link quality score is higher than the IPv4 link quality score and the difference exceeds a second threshold, the ranking level of IPv6 is increased.

[0045] In this step, when the IPv6 link quality score is significantly better than that of IPv4, the dual-stack network adaptive scheduling system starts the IPv6 priority strengthening mechanism. Taking the file transfer service domain name "ftp.example.com" as an example, when its IPv6 path passes through the newly deployed dedicated backbone network direct link, the throughput reaches 1.2Gbps and the number of hops is reduced to 3 hops, and the IPv4 link has a throughput of only 800Mbps due to the limited cross-operator interconnection bandwidth, the dual-stack network adaptive scheduling system calculates that the difference in the quality scores of the two reaches 12 points (exceeding the second threshold of 8 points), and then directly upgrades the ranking of IPv6 from the default third level to the highest level. After the adjustment takes effect, all clients that support IPv6 will first obtain the AAAA record when resolving the domain name, and only try the IPv4 address when the IPv6 connection fails to be established. Then, the dual-stack network adaptive scheduling system synchronously updates the preferred path mark in the network topology map to provide a reference for subsequent service quality evaluation.

[0046] (3) When the difference between the IPv4 and IPv6 link quality scores is between the first threshold and the second threshold, the current sorting weight remains unchanged.

[0047] In this step, the dual-stack network adaptive scheduling system maintains the current ranking weight when the network status fluctuates slightly. For example, the difference between the IPv4 and IPv6 link quality scores of the office OA system domain name "oa.example.com" on weekdays continues to fluctuate between 5 and 7 points, and does not reach the adjustment threshold of 8 points. The dual-stack network adaptive scheduling system maintains the existing IPv6 priority level unchanged. This stability assurance mechanism is achieved by setting a state maintenance timer. When the difference does not exceed the threshold in the last three evaluation cycles, the weight parameter is locked for at least 30 minutes. During this period, the dual-stack network adaptive scheduling system continues to collect new network performance data but does not trigger weight adjustment for the time being, avoiding frequent policy changes caused by short-term network congestion and ensuring the continuity of client connections.

[0048] (4) Compensate and correct the sorting weights based on the successful connection rates of IPv4 and IPv6 in historical scheduling records.

[0049] In this step, the historical data analysis module of the dual-stack network adaptive scheduling system compensates and corrects the sorting weights. For the CRM system domain name "crm.example.com", although real-time monitoring shows that the IPv6 link quality score is slightly higher than that of IPv4, the connection records of the past 7 days are retrieved and it is found that the success rate of the IPv6 address is only 92%, while the success rate of IPv4 remains at 98%. The system calculates that the difference in the historical success rates of the two is 6 percentage points, which exceeds the preset 5% compensation threshold, and then applies a -10% compensation coefficient to the weight generated by the current real-time score. This compensation mechanism is achieved by introducing a time decay factor, with the weight of recent historical data accounting for 70% and the weight of long-term data accounting for 30%, ensuring that the correction result reflects both long-term trends and the latest network status.

[0050] (5) The compensated and corrected sorting weight is weighted and integrated with the real-time link quality score to generate a final sorting weight to update the address type priority list.

[0051] In this step, the dual-stack network adaptive scheduling system generates the final ranking weight through a weighted fusion algorithm. Taking the domain name "www.example.com" of the enterprise portal website as an example, its real-time link quality score shows that the difference between IPv6 and IPv4 is 9 points, and the weight of IPv6 should be increased. At the same time, the historical success rate analysis shows that the IPv6 connection success rate is 3 percentage points higher than that of IPv4, resulting in a +5% compensation coefficient. For example, the two can be combined in a linear superposition manner, with the real-time score accounting for 70% of the weight and the historical compensation accounting for 30%, and finally generating a comprehensive decision value with a 12% increase in IPv6 priority. The fusion result is written into the dynamic policy library and synchronized to all DNS resolution nodes through distributed cache to ensure the consistency of the scheduling strategy of the entire network.

[0052] In the next step, the sorting weight is compensated and corrected according to the successful connection rate of IPv4 and IPv6 in the historical scheduling record, including: Step 10341: extract the ratio of the cumulative number of successful connections to the number of failed connections of the IPv4 address under the target domain name within a preset historical time period as the IPv4 historical success rate.

[0053] In step 10341, the log analysis unit of the dual-stack network adaptive scheduling system extracts IPv4 connection data within a preset historical time period from the connection tracking database. For the VPN access domain name "vpn.example.com", statistics show that among the 12,000 connections established by the client using the IPv4 address in the last 24 hours, 11,760 TCP handshakes were successfully completed, and the failure records included 240 timeouts and 20 connection rejections. By calculating the ratio of the number of successes to the number of failures, the IPv4 historical success rate is 11760 / (11760+260)=97.8%. This process uses a sliding time window mechanism to continuously update the statistical results at a granularity of 1 hour to ensure the timeliness and accuracy of historical data.

[0054] Step 10342: Extract the ratio of the cumulative number of successful connections to the number of failed connections of the IPv6 address in the same time period as the IPv6 historical success rate.

[0055] In step 10342, continuing with "vpn.example.com" as an example, 8500 IPv6 connection attempts were monitored in the same 24 hours, of which 8320 were successful, and the reasons for failure included 150 network unreachable and 30 certificate errors. By excluding application layer errors (such as certificate problems) and only counting the number of network layer failures, the historical IPv6 success rate is 8320 / (8320+150)=98.2%. The system uses independent data processing threads to process IPv4 and IPv6 logs respectively, and uses atomic counters to ensure data consistency during concurrent access.

[0056] Step 10343: Calculate the ratio difference between the historical success rate of IPv4 and the historical success rate of IPv6; if the ratio difference exceeds a preset compensation threshold, increase the difference compensation coefficient for the current sorting weight.

[0057] In step 10343, the difference calculation module of the dual-stack network adaptive scheduling system can compare the historical success rates of IPv4 and IPv6. Taking the aforementioned "vpn.example.com" as an example, the absolute difference between the success rate of IPv6 of 98.2% and the success rate of IPv4 of 97.8% is 0.4 percentage points, and the relative difference ratio is 1.004. When the ratio exceeds the preset compensation threshold of 1.005, the compensation mechanism is triggered. The calculation process uses double-precision floating-point operations to retain four decimal places of precision, and uses an outlier filtering algorithm to eliminate the impact of occasional network jitter, such as ignoring local failure events that last less than 5 minutes.

[0058] Step 10344: linearly superimpose the difference compensation coefficient and the real-time link quality score to generate a compensated ranking weight.

[0059] In step 10344, the difference compensation coefficient is linearly superimposed with the real-time link quality score. Taking the enterprise cloud disk domain name "cloud.example.com" as an example, its real-time score shows that the difference between IPv6 quality and IPv4 is 7 points, which should generate a +5% basic weight adjustment. At the same time, the historical success rate analysis shows that IPv6 is 1.2 percentage points higher than IPv4, triggering a +3% compensation coefficient. The final adjustment value is calculated by the weighted formula (real-time score × 0.7 + historical compensation × 0.3) to be +4.4%, which is converted into a specific ranking change in the priority list. The superposition process follows the saturation operation rule, limiting the maximum amplitude of a single adjustment to no more than 15% to prevent policy mutations caused by extreme network conditions.

[0060] It can be understood that the above-mentioned adaptive scheduling strategy generation process realizes dynamic optimization through a multi-layer feedback mechanism, taking into account historical experience while ensuring real-time performance. The above-mentioned embodiment adopts a microservice architecture to deploy various functional modules, and conducts asynchronous communication through message queues to ensure that the millisecond-level response speed can be maintained under high-concurrency resolution requests. Furthermore, after the policy takes effect, key indicators such as the client connection establishment time and data transmission rate are continuously monitored to form a closed-loop optimization system, which promotes the dual-stack evolution of the enterprise network to steadily develop towards the established service quality goals.

[0061] In one implementation, the step of selecting a target IP address type from a preconfigured IP address pool based on the adaptive scheduling policy in step 104 includes: Step 1041: When the adaptive scheduling strategy indicates to adopt the protocol stack parallel mode, an IPv4 address list and an IPv6 address list are simultaneously extracted from the IP address pool.

[0062] In this embodiment, the address selection module of the dual-stack network adaptive scheduling system performs protocol stack parallel mode operation in an enterprise office network environment. When the system determines that the business system corresponding to the target domain name "oa.example.com" has both IPv4 and IPv6 service capabilities, and the client supports dual protocol stacks, an IPv4 address list and an IPv6 address list are extracted in parallel from a preconfigured IP address pool. The IP address pool is synchronized with the data interface of the enterprise network infrastructure management platform, wherein the IPv4 address list includes two preset A records of 192.0.2.45 and 192.0.2.46, and the IPv6 address list includes two AAAA records of 2001:db8::1:10 and 2001:db8::1:11. The two lists are pre-processed by the address validity verification mechanism, so that IP addresses that are in maintenance status or fail health checks can be excluded, ensuring that each entry in the candidate address set has routability and service availability.

[0063] Step 1042: Determine the primary allocation order and the backup allocation order of the IPv4 and IPv6 addresses according to the request protocol type of the client.

[0064] In this embodiment, the protocol decision module of the dual-stack network adaptive scheduling system determines the address allocation order according to the client request protocol type. For clients accessing through the enterprise wireless network, the EDNSClient Subnet extension field in its DNS request message shows that the client has the ability to support both IPv4 and IPv6 protocol stacks. The dual-stack network adaptive scheduling system refers to the preset address type priority policy and sets the IPv6 address as the primary allocation order and the IPv4 address as the backup allocation order. The decision-making process is dynamically adjusted in combination with real-time network status data. For example, when regional congestion is detected in the IPv6 backbone link, the dual-stack network adaptive scheduling system temporarily sets IPv4 as the primary allocation order. For clients that only support the IPv4 protocol, the dual-stack network adaptive scheduling system automatically sets the IPv4 address list as the primary allocation order, and triggers a protocol conversion service alarm when there are no available IPv4 addresses.

[0065] Step 1043: Encapsulate the IPv4 or IPv6 address corresponding to the primary allocation order into the preferred record field of the DNS response message.

[0066] In this embodiment, the response generation module of the dual-stack network adaptive scheduling system encapsulates the address corresponding to the primary allocation order into the preferred record field of the DNS response message. Taking the enterprise file service domain name "file.example.com" as an example, when the primary allocation order is set to IPv6 priority, the dual-stack network adaptive scheduling system arranges the AAAA records of the IPv6 addresses 2001:db8::1:10 and 2001:db8::1:11 in the first two positions of the DNS message Answer Section. The encapsulation process follows the resource record sorting rules specified in the RFC 1035 standard to ensure that the client gives priority to trying the addresses that are arranged first when resolving the response. The dual-stack network adaptive scheduling system also performs address geographic location matching calculations. When it is detected that the request source belongs to the enterprise branch subnet, the IPv6 address entry that is closest to the regional network topology is returned first.

[0067] Step 1044: Add the standby protocol stack address corresponding to the standby allocation sequence to the additional record field of the DNS response message.

[0068] In this embodiment, the backup address processing unit of the dual-stack network adaptive scheduling system adds the backup protocol stack address to the additional record field of the DNS response message. For the resolution request of the video conferencing system domain name "meet.example.com", the dual-stack network adaptive scheduling system fills the IPv6 address 2001:db8::1:20 in the main record field of the Answer Section, and then adds an A record of the IPv4 address 192.0.2.55 in the Additional Section. The additional record adopts the standard resource record format and contains the same domain name, record type and lifetime value as the main record. The dual-stack network adaptive scheduling system distinguishes the primary and backup address types by setting the protocol stack identification bit. When the client supports the protocol stack fallback mechanism, the additional record can be used to achieve fast failover.

[0069] Step 1045: In response to the client failing to connect to the primary address, triggering a protocol stack switching process based on the backup address in the additional record field to guide the client to re-initiate a connection request.

[0070] In this embodiment, the connection monitoring module of the dual-stack network adaptive scheduling system responds to the client's failure to connect to the primary address and initiates the protocol stack switching process. When the enterprise mobile office client attempts to access the "oa.example.com" service through the IPv6 address 2001:db8::1:10, if the TCP three-way handshake is not completed within the preset 3000 millisecond timeout period, the dual-stack network adaptive scheduling system captures the abnormal connection event through the deep packet inspection device in the enterprise network. The protocol stack switching instruction generation unit immediately triggers the address fallback mechanism, resolves the IPv4 backup address 192.0.2.45 in the additional record field of the DNS response message, and sends an ICMP redirect message to the client through the policy execution node of the enterprise intranet. The message contains the protocol stack switching identifier and the backup address information.

[0071] The protocol stack switching process includes: (1) Monitoring the connection establishment status between the client and the primary address, and generating a protocol stack switching instruction if no connection confirmation signal is received within a preset timeout period.

[0072] Based on this step, the connection status monitoring unit of the dual-stack network adaptive scheduling system tracks the connection establishment process between the client and the primary address in real time. For the scenario where the client of the enterprise R&D department accesses the code repository domain name "git.example.com", the TCP SYN message sending event is captured through the kernel-level network probe, and the connection establishment countdown timer is started. When no SYN-ACK response is received for three consecutive SYN retransmissions, and the cumulative time exceeds the 2000 millisecond threshold, a protocol stack switching instruction containing a failure reason code is generated. This monitoring mechanism is synchronized with the session tracking table of the enterprise firewall, and can accurately distinguish between network layer connection failures and application layer service unavailability.

[0073] (2) Parse the additional record field of the DNS response message to extract the protocol stack type and IP address corresponding to the backup address.

[0074] Based on this step, the message parsing module of the dual-stack network adaptive scheduling system deeply decodes the additional record field of the DNS response message. Taking the resolution response of the enterprise mail system domain name "mail.example.com" as an example, the A record of the backup IPv4 address 192.0.2.60 is extracted from the Additional Section, and the protocol stack type identifier corresponding to the address is obtained. The parsing process strictly follows the DNS message format specification, and processes operations including resource record name compression, TTL value parsing, and RDATA field decoding. By establishing an address type mapping table, the compatibility verification of the backup address and the client protocol stack capabilities is ensured.

[0075] (3) Sending an address redirection message to the client, wherein the address redirection message includes the backup address and a protocol stack switching identifier.

[0076] Based on this step, the redirection control module of the dual-stack network adaptive scheduling system sends an address redirection message to the client. When the marketing department client fails to access the primary IPv6 address "crm.example.com", an ICMPv6 Destination Unreachable message containing the protocol stack switching identifier 0xA6 is generated, and its payload is embedded in the backup IPv4 address 192.0.2.70. The redirection message is directed to the request source client through the policy routing function of the enterprise core switch, while retaining the port number and session identification information of the original request. By setting the DSCP field priority of the IP message, it is ensured that the redirection instruction can still be delivered in time under network congestion.

[0077] (4) Record the protocol stack type, switching timestamp, and switching reason of this switching operation, and update it to the historical switching log.

[0078] Based on this step, the logging unit of the dual-stack network adaptive scheduling system writes the switching operation details into the historical switching log. For the protocol stack switching event of the financial system domain name "erp.example.com", the record includes the switching timestamp (accurate to milliseconds), the original primary IPv6 address 2001:db8::1:30, the target backup IPv4 address 192.0.2.75, the failure reason code (network unreachable), and other metadata. These log entries are transmitted to the central analysis platform through an encrypted channel, and are correlated with the alarm events of the enterprise network performance monitoring system to form a complete fault diagnosis evidence chain.

[0079] (5) According to the cumulative number of switches of the same target domain name in the historical switch log, dynamically adjust the allocation ratio of the primary and backup addresses in the subsequent scheduling strategy.

[0080] Based on this step, the policy optimization module of the dual-stack network adaptive scheduling system dynamically adjusts the primary and backup address allocation ratios according to the historical switching logs. When analysis finds that the number of times the IPv6 primary address of the "file.example.com" domain name switches to the IPv4 backup address more than 50 times in the past 24 hours, the IPv6 allocation weight of the primary address is automatically reduced by 20%, and the priority of the IPv4 address in the backup allocation order is increased. This adjustment process uses a sliding time window algorithm, focusing on the trend of switching frequency changes in the last 2 hours to ensure that the scheduling strategy responds to network status fluctuations in a timely manner. The optimized allocation ratio is synchronized to all DNS resolution nodes in real time through the configuration management interface to form a closed-loop control mechanism.

[0081] By applying the above embodiment, the entire address selection and protocol stack switching process can be intelligently scheduled through a multi-layer collaborative mechanism, optimizing network resource utilization while ensuring service continuity. By deploying monitoring agents at key nodes of the enterprise network, an end-to-end connection quality perception system is constructed, so that the protocol stack switching decision is in line with the global scheduling strategy and can adapt to the dynamic changes of the local network environment. It can be seen that the above embodiment effectively solves the problem of rigid protocol switching in traditional dual-stack networks, and significantly improves the reliability and user experience of enterprise employees accessing key business systems.

[0082] In another implementation, the method further includes: deploying a protocol stack compatibility detection service at the DNS resolution layer. The following execution operations of the protocol stack compatibility detection service are performed:

[0083] Step 201: Send an IPv4 protocol detection message and an IPv6 protocol detection message to the client, wherein the IPv4 protocol detection message and the IPv6 protocol detection message both contain a preset protocol identifier.

[0084] In step 201, the protocol detection module of the dual-stack network adaptive scheduling system sends IPv4 protocol detection messages and IPv6 protocol detection messages to the client through the core switch of the enterprise office network. The IPv4 protocol detection message is encapsulated in the UDP protocol, the target port is set to the standard DNS service port 53, and the preset protocol identifier "IPv4_Probe_OA_v1.2" is embedded in the application layer load. The IPv6 protocol detection message adopts the ICMPv6 protocol format, its type field is set to information request message, and carries the unique identifier "IPv6_Probe_OA_v1.2" in the option field.

[0085] Take the enterprise human resources system client accessing the "hr.example.com" domain name as an example. When the client first accesses the enterprise wireless network, its ARP request message is captured through the traffic mirror port of the core switch, triggering the protocol stack detection process. After the detection message is filtered by the enterprise firewall security policy, it is forwarded to the target client after adding a priority tag by the edge router.

[0086] Step 202: monitor the feedback behavior of the client to the IPv4 protocol detection message and the IPv6 protocol detection message within a preset response time.

[0087] In step 202, the response monitoring unit of the dual-stack network adaptive scheduling system monitors the client feedback behavior within the preset response time window. For the detection request of the intelligent terminal device in the enterprise conference room, the global response timeout threshold is set to 3000 milliseconds, and the response message from the client is captured in real time through the flow analysis probe deployed in the core switch. When the client network interface card supports the IPv6 protocol stack, it will return an ICMPv6 reply message; if it only supports the IPv4 protocol stack, it will respond to the TCP RST message or remain silent.

[0088] Taking the R&D department workstation access to the code management platform "git.example.com" as an example, after sending the dual-protocol detection message, the dual-stack network adaptive scheduling system uses deep packet inspection technology to analyze the protocol type field of the return message and record the precise response timestamp and protocol interaction characteristics. The session state table configured by the enterprise firewall is updated synchronously to ensure that the detection response message will not be mistakenly intercepted by the security policy.

[0089] Step 203: If only an IPv4 probe response is received, the protocol stack support status of the client is marked as IPv4-only compatible; if only an IPv6 probe response is received, the protocol stack support status of the client is marked as IPv6-only compatible; if both the IPv4 probe response and the IPv6 probe response are received at the same time, the protocol stack support status of the client is marked as dual-stack compatible.

[0090] In step 203, the state marking module of the dual stack network adaptive scheduling system updates the client protocol stack support status according to the response message characteristics. When the marketing department mobile office device only returns an IPv4 protocol detection response, the dual stack network adaptive scheduling system sets the client's MAC address corresponding status to IPv4 only compatible in the protocol stack support status table.

[0091] For newly deployed IPv6 single-stack IoT devices, the dual-stack network adaptive scheduling system detects that they only respond to IPv6 protocol detection messages and marks them as IPv6-only compatible. Taking the 4K smart terminal in the enterprise video conference room as an example, the device returns both IPv4 and IPv6 detection response messages. The dual-stack network adaptive scheduling system confirms its dual-stack compatibility by parsing the protocol identifier matching field in the response message and sets the dual-stack support flag in the status table. This marking process is cross-validated with the OUI (Organizationally Unique Identifier) ​​information of the client network interface card to improve the accuracy of status determination.

[0092] Step 204: Store the marking result in a protocol stack support state table, where the protocol stack support state table is a direct call object for subsequent DNS resolution requests.

[0093] In step 204, the data storage module of the dual-stack network adaptive scheduling system stores the protocol stack support status marking result persistently in the distributed database. The protocol stack support status table adopts a three-copy storage mechanism, which includes three core fields: client MAC address, latest detection timestamp, and protocol stack compatibility status. Taking the encrypted terminal equipment of the finance department as an example, its dual-stack compatibility status marking record includes MAC address 00:1A:3F:2B:55:CC, last updated time 2023-08-20T14:30:00Z, and status value Dual-Stack. The table synchronizes data with the employee terminal equipment management system through the enterprise intranet LDAP service to ensure that the protocol stack information of the newly added equipment can be collected in time. The dual-stack network adaptive scheduling system establishes an hourly incremental backup mechanism to prevent status misjudgment caused by data loss.

[0094] Furthermore, the protocol stack supports a calling process of the state table including: Step 301: when receiving a new DNS resolution request, extract the source IP address and request protocol type of the new client corresponding to the new DNS resolution request.

[0095] In step 301, the request resolution unit of the dual-stack network adaptive scheduling system performs a source information extraction operation when processing a new DNS resolution request. When an enterprise mobile office employee accesses "oa.example.com" through VPN access, the dual-stack network adaptive scheduling system extracts the source IPv4 address 203.0.113.25 from the IP header of the DNS request message, and simultaneously resolves the request protocol type identifier in the EDNS extension field. The extraction process uses zero-copy technology to directly access the network interface card receiving buffer to ensure processing efficiency in high-concurrency scenarios. For clients accessed through the IPv6 protocol, the dual-stack network adaptive scheduling system simultaneously records its IPv6 source address 2001:db8:cafe::1a3f:2b55:cc and establishes a dual-protocol address association mapping table.

[0096] Step 302: Query the protocol stack support status table for a historical marking result associated with the source IP address.

[0097] In step 302, the status query module of the dual-stack network adaptive scheduling system retrieves the protocol stack support status table through the source IP address. Taking the branch client accessing the enterprise file server "file.example.com" as an example, the dual-stack network adaptive scheduling system queries the distributed database based on the source IPv4 address 192.168.12.34, and returns the historical mark result of the client as dual-stack compatible. The query process uses Bloom filters for pre-screening to quickly exclude client devices with no historical records. For enterprise guest network clients using NAT conversion, the dual-stack network adaptive scheduling system associates the internal device list through the mapped public IP address to ensure accurate tracing of protocol stack status information.

[0098] Step 303: If the historical marking result indicates that the new client is dual-stack compatible, an IPv4 address or an IPv6 address is allocated according to the current adaptive scheduling policy.

[0099] In step 303, the policy execution module of the dual-stack network adaptive scheduling system implements a dynamic address allocation strategy for dual-stack compatible clients. When it is detected that the design department workstation accesses "cad.example.com", the dual-stack network adaptive scheduling system refers to the current network status evaluation result and preferentially allocates the IPv6 address 2001:db8::cad:1. This allocation strategy is implemented by sorting the AAAA records in the DNS response message, placing the preferred address at the top of the resource record list. The dual-stack network adaptive scheduling system also monitors the real-time quality indicators of the IPv6 link. If abnormal traffic is found on the target server IPv6 port, it automatically switches to the IPv4 address allocation mode. The policy execution process is linked with the enterprise software-defined network controller to dynamically adjust the bandwidth allocation ratio of each protocol stack.

[0100] Step 304: If the historical marking result is that the single protocol stack is compatible, the adaptive scheduling strategy generation step is skipped and the corresponding protocol stack address is directly allocated.

[0101] In step 304, the direct allocation module of the dual-stack network adaptive scheduling system implements a fast response mechanism for the single protocol stack client. For the scenario where the old attendance terminal that only supports the IPv4 protocol accesses "attendance.example.com", the dual-stack network adaptive scheduling system skips the complex policy calculation process and directly returns the A record of the IPv4 address 192.0.2.101. This process is implemented through a pre-generated protocol stack address mapping table to establish a direct cache channel for known single-protocol clients. The dual-stack network adaptive scheduling system also records the log information of the direct allocation operation for equipment compatibility analysis of subsequent network transformation projects.

[0102] Step 305: When the protocol stack support status of the new client changes, the protocol stack support status table is updated through periodic re-detection.

[0103] In step 305, the status maintenance service of the dual-stack network adaptive scheduling system updates the protocol stack support status table through a periodic re-detection mechanism. For smart whiteboard devices that upgrade network interface cards in corporate conference rooms, the dual-stack network adaptive scheduling system sends dual-protocol detection messages every 24 hours. When the newly added IPv6 protocol response capability is detected, the status mark is updated to dual-stack compatibility. The re-detection process uses a progressive time interval algorithm to shorten the detection cycle to 6 hours for clients that frequently change protocols and extend it to 72 hours for devices with stable status. The update operation uses a two-stage commit protocol to ensure data consistency and avoid erroneous updates caused by network jitter. In addition, the dual-stack network adaptive scheduling system synchronously cleans up client records that have been inactive for more than 90 days to maintain efficient query performance of the status table.

[0104] Applying the above-mentioned embodiments, the protocol stack compatibility detection and status management mechanism builds an accurate client capability portrait through multi-layer collaborative work. While ensuring the efficiency of DNS resolution, it provides a reliable decision-making basis for adaptive scheduling strategies, effectively improving the service quality and operation and maintenance transparency of enterprise networks during the dual-stack evolution process. It can be understood that by deploying a detection agent cluster on the core network node, it is possible to achieve real-time perception of the protocol stack status of the entire network client, combine historical data analysis to predict equipment upgrade trends, and provide data support for enterprises to formulate network transformation plans.

[0105] In a preferred implementation, when the protocol stack support status of the new client changes in step 305, updating the protocol stack support status table by periodic re-detection includes: Step 30501: deploy a timer trigger mechanism at the DNS resolution layer and start a periodic detection timer associated with the protocol stack support status table.

[0106] In this embodiment, the timer management module of the dual-stack network adaptive scheduling system deploys the timer trigger mechanism through the core DNS server of the enterprise office network. When the system detects that there are more than 1,000 client records in the protocol stack support status table, the periodic detection timer service is automatically started. The timer service maintains clock synchronization with the enterprise network time protocol server and adopts a hierarchical triggering strategy: the core network device triggers the main timer every 5 minutes, and the edge access layer device starts the sub-timer synchronously by region. Taking the enterprise headquarters data center as an example, when the dual-stack network adaptive scheduling system performs a full client status scan at 3 a.m. every day, it synchronously initializes the periodic detection timer cluster to ensure load balancing of detection tasks in different business areas.

[0107] Step 30502: When the periodic detection timer reaches a preset re-detection period, scan the protocol stack support status entries of all clients in the protocol stack support status table.

[0108] In this embodiment, the status scanning module of the dual-stack network adaptive scheduling system starts the full scanning process of the protocol stack support status table after the periodic detection timer is triggered. When the re-detection cycle of the enterprise branch network reaches the preset 24-hour threshold, the dual-stack network adaptive scheduling system reads the client status entries in batches from the distributed database. The scanning process uses cursor paging technology, processing 500 records each time to avoid memory overflow. Taking the client device of the enterprise R&D department as an example, the dual-stack network adaptive scheduling system traverses the state table copies stored in the three available zones, compares the data consistency between the copies, and generates a queue to be processed.

[0109] Step 30503: Extract the last detection timestamp and protocol stack support status mark value corresponding to the source IP address of each client.

[0110] In this embodiment, the metadata extraction component of the dual-stack network adaptive scheduling system extracts key time parameters from the protocol stack support status table. For the records of the encrypted terminal of the finance department, the dual-stack network adaptive scheduling system extracts its last detection timestamp field value "2023-08-20T14:30:00Z" and the protocol stack support status tag value "Dual-Stack". The extraction process uses column storage optimization technology to read only necessary fields to improve processing efficiency. The dual-stack network adaptive scheduling system also verifies the legitimacy of the timestamp and filters out abnormal records of future timestamps caused by network delays.

[0111] Step 30504: Calculate the time interval between the current system time and the last detection timestamp, and compare the difference with the preset re-detection period.

[0112] In this embodiment, the timeliness calculation module of the dual-stack network adaptive scheduling system performs a time interval comparison operation. Taking the last detection time of the marketing department's mobile office equipment "2023-08-20T10:15:00" as an example, after the dual-stack network adaptive scheduling system obtains the current coordinated universal time "2023-08-21T09:00:00", it calculates that the time interval is 22 hours and 45 minutes. The interval value is compared with the preset 24-hour re-detection cycle to generate an evaluation result of a remaining effective time of 1 hour and 15 minutes. The above calculation process uses a sliding time window algorithm to dynamically adapt to client devices in different time zones.

[0113] Step 30505: If the time interval exceeds the validity threshold of the preset re-detection period, the source IP address of the client is added to the queue to be re-detected.

[0114] In this embodiment, the queue generation module of the dual-stack network adaptive scheduling system screens the devices to be detected based on the timeliness evaluation results. When it is detected that the last detection time of the terminal device of the human resources department has exceeded the 72-hour validity period threshold, the dual-stack network adaptive scheduling system adds its IPv4 address 192.168.5.20 to the queue to be re-detected. Among them, the queue generation process adopts a priority sorting strategy to arrange the client devices of the enterprise's key business systems (such as ERP system access terminals) at the front of the queue to ensure priority re-detection. In addition, the queue management module also implements de-duplication verification to prevent the same device from being repeatedly queued due to multiple IP bindings.

[0115] Step 30506: Send an IPv4 protocol detection message and an IPv6 protocol detection message to each client according to the order of source IP addresses in the queue to be re-detected.

[0116] In this embodiment, the detection message distribution unit of the dual-stack network adaptive scheduling system initiates protocol detection in queue order. For example, for the 50th device in the re-detection queue: the conference room smart display screen (IP address 203.0.113.88), the dual-stack network adaptive scheduling system sends a UDP detection message carrying the identifier "IPv4_Probe_V2.1" to port 53 through the policy routing port of the enterprise core switch, and simultaneously sends an ICMPv6 information request message containing the identifier "IPv6_Probe_V2.1". In detail, the message sending interval is set to 500 milliseconds to avoid network congestion, and each client sends three detection messages in succession to ensure reliability.

[0117] Step 30507: Monitor the type of the probe response message returned by the client within a preset response time window.

[0118] In this embodiment, the response monitoring service of the dual-stack network adaptive scheduling system captures the return message within a preset 3000 millisecond time window. For the detection request of the enterprise warehouse management terminal, the dual-stack network adaptive scheduling system collects response data through the traffic mirror port deployed on the access switch. When the terminal only returns the IPv4 protocol detection response, the monitoring service records its MAC address 00:1A:3F:2B:55:CD and the response timestamp. Among them, the response message type identification module also analyzes the transport layer protocol characteristics to distinguish the TCP RST message of IPv4 from the ICMPv6 reply message of IPv6.

[0119] Step 30508: Extract the protocol identifier and client source IP address carried in the probe response message.

[0120] In this embodiment, the message parsing component of the dual stack network adaptive scheduling system extracts the protocol features in the probe response. Taking the response message of the design department workstation as an example, the system decodes the protocol identifier "IPv6_Probe_V2.1" from the extended header of the IPv6 probe response message and extracts the source IPv6 address 2001:db8:cafe::1a3f:2b55:cc. The parsing process implements strict security verification, including verifying the hash signature of the identifier and checking the message integrity check value to prevent probe response attacks.

[0121] Step 30509: If the protocol identifier indicates that the client returns an IPv4 probe response, the IPv4 compatibility mark of the corresponding source IP address in the protocol stack support status table is updated to a valid state; if the protocol identifier indicates that the client returns an IPv6 probe response, the IPv6 compatibility mark of the corresponding source IP address in the protocol stack support status table is updated to a valid state; if no IPv4 probe response or IPv6 probe response is received within the response time window, the corresponding protocol stack compatibility mark is set to an invalid state.

[0122] In this embodiment, the state update module of the dual-stack network adaptive scheduling system refreshes the protocol stack support state table according to the response result. When the enterprise video conferencing terminal returns the IPv4 and IPv6 dual-protocol detection response, the dual-stack network adaptive scheduling system sets its IPv4 compatibility flag and IPv6 compatibility flag to a valid state at the same time. For the old version of the attendance machine that did not respond to three detections, the dual-stack network adaptive scheduling system sets its IPv4 compatibility flag to an invalid state and triggers the device offline alarm. The update operation of this step uses atomic transaction processing to ensure the eventual consistency of each copy in the distributed database cluster.

[0123] Step 30510: recalculate the protocol stack support status mark value of the client according to the updated protocol stack compatibility mark; and overwrite the historical mark value in the protocol stack support status table with the recalculated protocol stack support status mark value.

[0124] In this embodiment, the tag calculation module of the dual-stack network adaptive scheduling system re-evaluates the protocol support capability of the client. A mobile office device only returns an IPv6 detection response after re-detection. The dual-stack network adaptive scheduling system changes the protocol stack support status tag value from "Dual-Stack" to "IPv6-Only" based on the latest result. The calculation process of this step adopts a state machine model to define the mapping relationship between the valid tag combination and the final state. For example, when the IPv4 tag is invalid and the IPv6 tag is valid, a new state code "0x6A" is generated.

[0125] Step 30511: Record the timestamp of this re-detection operation into the last detection timestamp field of the protocol stack support status table.

[0126] In this embodiment, the timestamp recording service of the dual-stack network adaptive scheduling system updates the timeliness information of the protocol stack support status table. After completing the re-detection of the R&D department test terminal (IP address 192.168.10.55), the dual-stack network adaptive scheduling system updates the last detection timestamp field to the current system time "2023-08-21T10:30:45.123Z". This process uses a high-precision clock source (error less than 1 millisecond), the timestamp format follows the ISO 8601 standard, and the time zone offset information is attached to adapt to the multinational enterprise network environment.

[0127] Step 30512: dynamically adjust the preset re-detection period of the periodic detection timer according to the change ratio of the protocol stack support status flag value in the queue to be re-detected.

[0128] In this embodiment, the cycle adjustment algorithm of the dual-stack network adaptive scheduling system optimizes the detection parameters according to the frequency of state changes. When it is detected that more than 30% of the client protocol stack support states in the queue to be re-detected have changed, the dual-stack network adaptive scheduling system shortens the preset re-detection cycle from 24 hours to 12 hours. The adjustment process of this step adopts an exponential backoff strategy. When a high change rate is detected for three consecutive cycles, the cycle is gradually reduced to the minimum threshold of 6 hours. The dual-stack network adaptive scheduling system also records the adjustment log for network administrators to audit the effectiveness of the cycle optimization strategy.

[0129] Step 30513: If the change ratio exceeds the dynamic adjustment threshold, shorten the preset re-detection period of the periodic detection timer; if the change ratio is lower than the stable threshold, extend the preset re-detection period of the periodic detection timer.

[0130] In this embodiment, the dynamic adjustment module of the dual-stack network adaptive scheduling system implements periodic parameter tuning. When the enterprise network upgrade causes 70% of the clients to enable the IPv6 protocol stack, the dual-stack network adaptive scheduling system detects that the state change ratio exceeds the dynamic adjustment threshold and immediately adjusts the preset re-detection period from 24 hours to 8 hours. Conversely, when the state change ratio is lower than the stable threshold of 5% for five consecutive cycles, the dual-stack network adaptive scheduling system gradually extends the period to 48 hours. The adjustment process uses a PID control algorithm to smoothly transition the period value to avoid sudden changes in network detection traffic.

[0131] Step 30514: Reset the periodic detection timer and start a new round of periodic re-detection process.

[0132] In this embodiment, the timer control unit of the dual-stack network adaptive scheduling system completes the periodic reset operation. After updating the protocol stack support status of all clients, the dual-stack network adaptive scheduling system sends a timer reset instruction to the core DNS server and each regional proxy node. The new detection cycle starts counting down based on the current system time, and clears the processed records in the queue to be re-detected. Among them, the reset process adopts a two-phase commit protocol to ensure that the timer status of all network nodes is strictly synchronized, and establish an accurate time reference for the next round of periodic re-detection.

[0133] The periodic re-detection mechanism in the above technical solution can build a dynamic and adaptive protocol stack status maintenance system through multi-layer collaborative control. In the enterprise network environment, it effectively solves the compatibility status drift problem caused by device protocol stack upgrades and network configuration changes. By intelligently adjusting the detection frequency and accurately updating status data, the dual-stack network adaptive scheduling system can ensure that the DNS resolution strategy is always based on the latest network topology and terminal capability information, significantly improving the reliability and resource scheduling efficiency of dual-stack network services, and providing continuous monitoring guarantees for the smooth evolution of enterprise networks.

[0134] In an optional implementation, the method further includes: Step 401: configure a global traffic scheduling policy template in a DNS server, wherein the global traffic scheduling policy template includes protocol stack scheduling rules corresponding to domain names of different service levels.

[0135] In step 401, the policy configuration module of the dual stack network adaptive scheduling system deploys a global traffic scheduling policy template in the enterprise core DNS server. The template defines the mapping relationship between service level and protocol stack scheduling through an XML format file, and contains classification information of all registered domain names in the enterprise office network.

[0136] Taking the enterprise resource planning system domain name "erp.example.com" as an example, it is classified as the first priority business category, and the corresponding protocol stack scheduling rules require the use of IPv6 addresses first. The template is stored in a high-availability distributed database cluster and is visually configured through the graphical interface of the enterprise network management platform, supporting batch import of business domain name lists and hierarchical policy parameters.

[0137] Step 402: In response to the target domain name belonging to the first priority service category, the IPv6 address is forcibly set as the primary address and allocated preferentially.

[0138] In step 402, the priority execution module of the dual-stack network adaptive scheduling system implements a mandatory scheduling strategy for the first priority service domain name. When it is detected that the video conferencing system domain name "meet.example.com" belongs to the first priority category, the system ignores the real-time link quality assessment result and directly sets the IPv6 address 2001:db8::1:20 as the primary address. This strategy is implemented by modifying the resource record sorting in the DNS response message, placing the AAAA record before the A record. During the mandatory execution process, the dual-stack network adaptive scheduling system synchronously sends a policy effectiveness notification to the enterprise software-defined network controller, triggering the update of the IPv6 traffic priority routing rules for the corresponding service domain name.

[0139] Step 403: monitor the network congestion index of the IPv6 link in real time, and if the network congestion index exceeds a preset alarm threshold, start the protocol stack fallback mechanism.

[0140] In step 403, the network status monitoring service of the dual-stack network adaptive scheduling system collects congestion indicators of IPv6 links in real time. For the IPv6 backbone link of the file transfer service domain name "ftp.example.com", the dual-stack network adaptive scheduling system uses the sFlow sampling technology deployed in the core switch to count the packet retransmission rate and buffer queue depth every 5 seconds. When it is detected that the packet retransmission rate exceeds the preset alarm threshold of 15%, the dual-stack network adaptive scheduling system generates a protocol stack rollback instruction. The monitoring data is transmitted to the analysis module in real time through the enterprise network operation and maintenance bus, and compared with the historical baseline data for analysis to accurately identify sudden network congestion events.

[0141] Step 404: Filter available IPv4 addresses from the IP address pool through the protocol stack fallback mechanism, and update the DNS resolution result to replace it with the available IPv4 address.

[0142] In step 404, the address fallback module of the dual-stack network adaptive scheduling system performs a protocol stack switching operation. Taking the enterprise mail system domain name "mail.example.com" as an example, when the IPv6 link is severely congested, the dual-stack network adaptive scheduling system selects the IPv4 address 192.0.2.60 with the closest geographical location from the pre-configured IP address pool. The address selection process combines the subnet information provided by the client EDNS Client Subnet extension field and matches the optimal access node through the enterprise geographic information database. The updated DNS resolution results are quickly distributed to the DNS cache nodes in each region through anycast addresses to ensure the consistency of the resolution strategy of the entire network.

[0143] Step 405: Write the association relationship between the mandatory policy and the fallback mechanism into the exception handling rule base of the adaptive scheduling policy.

[0144] In step 405, the rule management unit of the dual-stack network adaptive scheduling system establishes a policy association mechanism. After each protocol stack rollback event occurs, the dual-stack network adaptive scheduling system writes the service level, rollback time, duration and other parameters of the target domain name "oa.example.com" into the exception handling rule library. The rule library automatically adjusts the congestion alarm threshold of the first priority domain name by analyzing historical records through machine learning algorithms. For example, when a domain name is detected to frequently trigger rollback during peak business hours, the system dynamically lowers its packet retransmission rate threshold from 15% to 12%, improving the policy response sensitivity.

[0145] In a preferred implementation, the configuring of the global traffic scheduling policy template in the DNS server in step 401 includes: Step 4011: Create a global traffic scheduling policy template in the policy management module of the DNS server, wherein the global traffic scheduling policy template includes a service level domain name classification table.

[0146] In step 4011, the template creation service of the dual stack network adaptive scheduling system initializes the global traffic scheduling policy template in the policy management module. Exemplarily, the enterprise network administrator creates three levels of service classification through the management interface:

[0147] The first priority includes the video conferencing system "meet.example.com" and the core database "db.example.com"; The second priority covers the file service "ftp.example.com"; The third priority contains the internal information portal "wiki.example.com".

[0148] Each category is associated with an independent protocol stack scheduling rule configuration file, which is stored in an encrypted distributed key-value storage system to ensure the security and high availability of policy data.

[0149] Step 4012: Different domain names are classified into first priority, second priority and third priority according to the service level domain name classification table, and a preset protocol stack scheduling rule is bound to each service level.

[0150] In step 4012, the service classification module of the dual-stack network adaptive scheduling system implements domain name classification mapping. The enterprise office automation system domain name "oa.example.com" is classified into the first priority category, and its corresponding protocol stack scheduling rule is configured to force IPv6 priority and enable real-time monitoring. The second priority customer relationship management system domain name "crm.example.com" sets a dynamic quality optimization strategy, and the third priority employee forum domain name "bbs.example.com" adopts a load balancing mode. The classification process matches domain name features through regular expressions and supports wildcard rules to achieve batch classification.

[0151] Step 4013: For the service category domain name of the first priority, set the mandatory use of IPv6 address as the primary address in the protocol stack scheduling rule, and activate the enabling switch of the protocol stack fallback mechanism.

[0152] In step 4013, the rule binding module of the dual-stack network adaptive scheduling system configures a mandatory policy for the high-priority domain name. For the enterprise unified communications system domain name "uc.example.com", the dual-stack network adaptive scheduling system sets the primary address type to IPv6 in the protocol stack scheduling rule and activates the monitoring switch of the protocol stack fallback mechanism. This configuration is achieved by modifying the binary flag of the policy template. During the period when the mandatory policy is in effect, even if the IPv6 link quality score is lower than that of IPv4, the dual-stack network adaptive scheduling system still returns the AAAA record first. The fallback mechanism activation switch is linked with the network probe service to monitor the IPv6 service availability of the target domain name in real time.

[0153] Step 4014: Collect real-time congestion parameters of the IPv6 link corresponding to the target domain name, wherein the real-time congestion parameters include a packet retransmission rate and a buffer queue depth.

[0154] In step 4014, the performance collection unit of the dual-stack network adaptive scheduling system obtains the IPv6 link status parameters in real time. Taking the enterprise cloud storage service domain name "cloud.example.com" as an example, the dual-stack network adaptive scheduling system counts the number of IPv6 data packet retransmissions and buffer queue occupancy every 30 seconds through the NetFlow collector deployed on the border router. The collected data is aggregated and stored in the time series database to provide a real-time data source for congestion detection. The buffer queue depth measurement in this step adopts a combination of active detection and passive monitoring, and calculates the end-to-end delay fluctuation by sending a probe message with a timestamp.

[0155] Step 4015: When the real-time congestion parameter exceeds the preset alarm threshold in the protocol stack scheduling rule, the start condition of the protocol stack fallback mechanism is triggered.

[0156] In step 4015, the threshold detection module of the dual-stack network adaptive scheduling system triggers the protocol stack fallback mechanism. When the IPv6 link packet retransmission rate of the video conference domain name "meet.example.com" is detected to reach 18% (exceeding the preset 15% threshold), the dual-stack network adaptive scheduling system generates a level 3 alarm event. The event processing module immediately interrupts the current scheduling strategy and sends a protocol stack switching request to the address selection service. The switching decision process introduces a progressive response mechanism, which only implements fallback for some clients at the beginning of the threshold breakthrough, and gradually expands the fallback range as the congestion level increases.

[0157] Step 4016: According to the protocol stack fallback mechanism, a set of IPv4 addresses bound to the target domain name is filtered from the IP address pool.

[0158] In step 4016, the address screening service of the dual stack network adaptive scheduling system obtains a backup IPv4 address from the IP address pool. For the enterprise VPN access domain name "vpn.example.com", the dual stack network adaptive scheduling system queries the pre-configured address pool to obtain three available IPv4 addresses: 192.0.2.101, 192.0.2.102, and 192.0.2.103. The screening process in this step performs strict health checks, including ICMP reachability tests, TCP port response verification, and application layer service detection. Addresses that pass multi-dimensional verification are marked as candidate fallback targets and stored in the temporary address cache queue.

[0159] Step 4017: Based on the geographic location proximity index of each IPv4 address in the IPv4 address set, select the IPv4 address closest to the client's geographic location as the fallback target address.

[0160] In step 4017, the geographic matching algorithm of the dual-stack network adaptive scheduling system selects the optimal fallback address. When a client of a city branch accesses "file.example.com", the dual-stack network adaptive scheduling system selects 192.0.2.105 located in the eastern regional data center from the candidate IPv4 address pool based on the client IP address location information. The geographic proximity index is calculated by measuring the number of autonomous system (AS) path hops between the client and each data center, and access nodes in the same city and the same operator are preferred. The matching process of this step refers to the optimal path mark in the enterprise network topology map to ensure the optimal network performance after fallback.

[0161] Step 4018: Encapsulate the fallback target address into the preferred record field of the DNS response message, and generate a protocol stack fallback operation log including a switching timestamp and congestion parameters.

[0162] In step 4018, the response reconstruction module of the dual-stack network adaptive scheduling system generates a new DNS resolution result. For the fallback target address 192.0.2.108, the dual-stack network adaptive scheduling system encapsulates it into the first position of the DNS response message AnswerSection, and adds the protocol stack fallback identifier 0xA5 in the extension field. The response message is digitally signed by the enterprise intranet DNS cluster and sent to the client. The dual-stack network adaptive scheduling system simultaneously generates a detailed operation log, recording parameters such as the fallback time, duration, and number of clients affected. The log entries are transmitted to the centralized audit platform through a secure channel.

[0163] Step 4019: Associate the protocol stack rollback operation log with the service level of the target domain name, and update it to the exception handling rule base of the global traffic scheduling policy template; dynamically adjust the preset alarm threshold in the protocol stack scheduling rule according to the historical rollback record of the domain name with the same service level in the exception handling rule base.

[0164] In step 4019, the policy optimization module of the dual-stack network adaptive scheduling system implements closed-loop control. After each protocol stack rollback event, the dual-stack network adaptive scheduling system analyzes the historical records of "erp.example.com" and finds that there have been 8 rollbacks due to excessive packet retransmission rates in the past 30 days. Based on this, the dual-stack network adaptive scheduling system automatically adjusts the retransmission rate threshold of the domain name from 15% to 12%. The above optimization process uses a sliding window algorithm, focusing on the operating data of the last 7 days, and introducing holiday traffic pattern recognition to dynamically adapt to the cyclical changes in corporate business.

[0165] In an optional implementation, the protocol stack fallback mechanism in step 403 includes step 4030: collecting real-time congestion parameters of the IPv6 link, the real-time congestion parameters including packet retransmission rate, buffer overflow times and average queuing delay; if the packet retransmission rate exceeds a first congestion threshold, or the buffer overflow times exceeds a second congestion threshold, determining that the IPv6 link is in an unavailable state; selecting a set of IPv4 addresses bound to the target domain name from an IP address pool, and filtering the target IPv4 address based on geographic proximity; generating a protocol stack fallback instruction, and encapsulating the target IPv4 address into a preferred record field of a DNS response message; sending a protocol stack fallback alarm message to a network management terminal, and recording log data of the fallback operation.

[0166] In step 4030, the protocol stack fallback mechanism of the dual-stack network adaptive scheduling system performs the full process operation. When the number of IPv6 link buffer overflows of the enterprise unified communication system domain name "uc.example.com" reaches 50 times in 5 minutes (exceeding the second congestion threshold of 40 times), the dual-stack network adaptive scheduling system determines that the link is unavailable. The address selection service immediately selects two IPv4 addresses 192.0.2.110 and 192.0.2.115 in the eastern and northern regions from the IP address pool, and selects the optimal address based on the client's geographical location. After the fallback instruction is encapsulated into the DNS response message, the dual-stack network adaptive scheduling system sends an SNMP trap alarm message to the network operation and maintenance center, recording the event time, impact range and solution in detail. The entire fallback process mentioned above can be completed within a few hundred milliseconds, minimizing the service interruption time.

[0167] As an optional but non-limiting embodiment, the generating of an adaptive scheduling strategy including a dynamic split ratio of IPv4 addresses to IPv6 addresses based on the adjusted sorting weights includes: Step 10351: Obtain the final ranking weights of the IPv4 link quality score and the IPv6 link quality score, calculate the weight ratio of the IPv4 address and the weight ratio of the IPv6 address; determine the dynamic diversion ratio base of the IPv4 address and the IPv6 address based on the ratio of the weight ratio of the IPv4 address to the weight ratio of the IPv6 address.

[0168] In step 10351, the weight calculation module of the dual-stack network adaptive scheduling system generates a dynamic diversion ratio base according to the final ranking weight. Taking the domain name "meet.example.com" of the enterprise video conferencing system as an example, the dual-stack network adaptive scheduling system obtains the final ranking weights of the IPv4 link quality score of 85 points and the IPv6 link quality score of 92 points, of which the IPv4 weight accounts for 48% and the IPv6 weight accounts for 52%. By calculating the ratio of the two, 0.923 (48 / 52), the initial dynamic diversion ratio base is determined to be IPv4:IPv6=48:52. This calculation process uses a normalization algorithm to map the scores of each protocol stack to a weight range of 0-100% to ensure the comparability of the ratio base. The dual-stack network adaptive scheduling system synchronously verifies the rationality of the weight ratio, and triggers the manual review process when an abnormal fluctuation in the weight of a protocol stack is detected.

[0169] Step 10352: Extract the difference in success connection rate between the IPv4 address and the IPv6 address in the historical address allocation record corresponding to the target domain name, and calculate the offset between the success connection rate difference and the preset benchmark difference; generate a correction coefficient for the dynamic diversion ratio base according to the positive and negative sign and absolute value of the offset; multiply the correction coefficient by the dynamic diversion ratio base to obtain the corrected dynamic diversion ratio of the IPv4 address and the IPv6 address; based on the corrected dynamic diversion ratio, determine the primary allocation interval and the backup allocation interval of the IPv4 address and the IPv6 address in accordance with the ratio threshold interval division rule.

[0170] In step 10352, the historical data analysis module of the dual-stack network adaptive scheduling system extracts the difference in connection success rate of the target domain name for proportional correction. For the enterprise file service domain name "file.example.com", the dual-stack network adaptive scheduling system retrieves the difference of 1.3% between the connection success rate of the IPv4 address of 98.2% and the IPv6 address of 99.5% in the past 24 hours, and compares it with the preset benchmark difference of 0.5% to generate a positive offset of 0.8%. A correction coefficient of +1.5% is generated based on the absolute value of the offset, and the initial ratio base IPv4:IPv6=45:55 is adjusted to the corrected 43.5:56.5. The correction process uses a piecewise linear interpolation algorithm, and the exponential compensation mechanism is enabled when the offset exceeds 2%. The dual-stack network adaptive scheduling system divides the primary allocation interval (≥55%) and the backup allocation interval (<45%) according to the correction ratio, and the middle interval retains elastic adjustment space.

[0171] Step 10353: When the proportion of IPv4 addresses in the dynamic diversion ratio is in the main allocation interval, the IPv4 address is set as the first priority allocation address; when the proportion of IPv6 addresses in the dynamic diversion ratio is in the main allocation interval, the IPv6 address is set as the first priority allocation address.

[0172] In step 10353, the priority decision module of the dual-stack network adaptive scheduling system determines the primary address type. When the dynamic diversion ratio correction result of the enterprise unified communication system domain name "uc.example.com" is 58% IPv6, the dual-stack network adaptive scheduling system sets the IPv6 address 2001:db8::1:30 as the primary allocation address type. This setting is achieved by modifying the protocol stack priority field in the DNS policy library, and AAAA records are returned preferentially in the subsequent address allocation process. For the diversion ratio in the middle range (such as IPv4:IPv6=50:50), the dual-stack network adaptive scheduling system maintains the current primary protocol stack type by default until the next evaluation cycle triggers recalculation.

[0173] Step 10354: According to the address type of the primary allocation interval, select an address set of the corresponding protocol stack type from the IP address pool; according to the ratio difference between the primary allocation interval and the backup allocation interval, adjust the address sorting of nodes in different geographical locations in the address set.

[0174] In step 10354, the address screening module of the dual-stack network adaptive scheduling system performs geographical location optimization sorting. Taking the enterprise branch office accessing "oa.example.com" as an example, when the primary allocation interval is determined to be IPv6, the dual-stack network adaptive scheduling system selects three IPv6 addresses from the IP address pool: 2001:db8::1:10 (eastern node), 2001:db8::1:11 (northern node), and 2001:db8::1:12 (southern node). After identifying that the client's location is in the eastern region based on the client's EDNS subnet information, the dual-stack network adaptive scheduling system promotes the ranking of 2001:db8::1:10 to the first place. The sorting adjustment process refers to the autonomous system path cost data in the enterprise network topology diagram, and gives priority to selecting service nodes that have direct backbone links with the client.

[0175] Step 10355: Encapsulate the sorted address set into different record fields of the DNS response message in order of priority; select the address closest to the client's geographic location from the sorted address set as the preferred resolution result based on the client's geographic location information; add the preferred resolution result and the secondary resolution result to the address allocation queue of the DNS response message; set the quantity distribution of different protocol stack addresses in the address allocation queue based on the ratio of primary addresses to backup addresses in the dynamic diversion ratio.

[0176] In step 10355, the response encapsulation module of the dual-stack network adaptive scheduling system builds an address allocation queue. For the dynamic traffic distribution ratio of IPv4:IPv6=40:60 for the enterprise cloud storage domain name "cloud.example.com", the dual-stack network adaptive scheduling system fills in the first two digits of the DNS response message Answer Section with the IPv6 addresses 2001:db8::1:20 and 2001:db8::1:21, and the next three digits with the IPv4 addresses 192.0.2.30, 192.0.2.31, and 192.0.2.32. Based on the geographic location information of the eastern client, the dual-stack network adaptive scheduling system sets the IPv6 address 2001:db8::1:20 located in a certain city data center as the preferred resolution result. The number distribution of the address queue strictly follows the 6:4 ratio requirement, and the IPv6 address occupies the first 6 sorting positions in the 10 resource records.

[0177] Step 10356: In response to the client initiating a connection request, the resolution results of different protocol stack addresses are returned in sequence according to the priority order of the address allocation queue.

[0178] In step 10356, the request processing unit of the dual-stack network adaptive scheduling system returns the resolution result in priority order. When the enterprise mobile office client accesses "crm.example.com", the dual-stack network adaptive scheduling system returns the IPv6 addresses 2001:db8::1:40, 2001:db8::1:41 and IPv4 address 192.0.2.50 in sequence according to the address allocation queue. The client application layer protocol stack attempts to establish a connection according to the DNS response order, and first initiates a TCP three-way handshake for the first IPv6 address. The dual-stack network adaptive scheduling system records the actual address type in use through the connection tracking module deployed in the core switch. When it detects that a certain address fails to connect three times in a row, it automatically downgrades its order in the queue and triggers the address health check process.

[0179] Based on the same inventive concept, the present application embodiment also provides a dual-stack network adaptive scheduling system. Figure 2 As shown, it is a structural diagram of a possible dual-stack network adaptive scheduling system provided in an embodiment of the present application, Figure 2 In the embodiment, the dual stack network adaptive scheduling system 200 includes: a processor 210 and a memory 220. The memory 220 stores a computer program executable by the processor 210, and the processor 210 can execute the steps of the dual stack network adaptive scheduling method based on the DNS resolution strategy by executing the instructions stored in the memory 220.

[0180] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, which includes a computer program. When the computer program runs on a dual-stack network adaptive scheduling system, the computer program is used to enable the dual-stack network adaptive scheduling system to execute the steps of the dual-stack network adaptive scheduling method based on the DNS resolution policy. In some possible implementations, various aspects of the dual-stack network adaptive scheduling method based on the DNS resolution policy provided by the present application can also be implemented in the form of a program product, which includes a computer program. When the program product runs on a dual-stack network adaptive scheduling system, the computer program is used to enable the dual-stack network adaptive scheduling system to execute the steps of the dual-stack network adaptive scheduling method based on the DNS resolution policy. For example, the dual-stack network adaptive scheduling system can execute the following steps: Figure 1 Follow the steps shown in .

Claims

1. A dual-stack network adaptive scheduling method based on DNS resolution strategy, characterized in that: include: Receive a DNS resolution request sent by a client, wherein the DNS resolution request carries a target domain name and a request protocol type; Parsing the request protocol type to determine the network protocol stack type supported by the client; Generate an adaptive scheduling strategy corresponding to the target domain name according to the network protocol stack type and a preset address type priority list; Based on the adaptive scheduling strategy, selecting a target IP address type from a preconfigured IP address pool; The parsing result corresponding to the target IP address type is returned to the client to guide the client to establish a network connection through the target IP address type.

2. The method according to claim 1, characterized in that The step of generating an adaptive scheduling strategy corresponding to the target domain name according to the network protocol stack type and a preset address type priority list includes: Acquire in real time a first real-time parameter set of the IPv4 network link associated with the target domain name, the first real-time parameter set comprising IPv4 link delay, IPv4 node available bandwidth, and IPv4 request response success rate; Synchronously collecting a second real-time parameter set of the IPv6 network link associated with the target domain name, the second real-time parameter set including IPv6 link throughput, IPv6 node load balancing index, and IPv6 path hop count; Comparing the first real-time parameter set with a preset IPv4 benchmark parameter to generate an IPv4 link quality score; Comparing the second real-time parameter set with a preset IPv6 benchmark parameter to generate an IPv6 link quality score; Dynamically adjust the sorting weights of IPv4 and IPv6 in the address type priority list according to the difference between the IPv4 link quality score and the IPv6 link quality score; Based on the adjusted sorting weights, an adaptive scheduling policy including a dynamic split ratio of IPv4 addresses to IPv6 addresses is generated, wherein the dynamic split ratio is used to control the address allocation priority of different protocol stacks.

3. The method according to claim 2, characterized in that The dynamically adjusting the sorting weights of IPv4 and IPv6 in the address type priority list according to the difference between the IPv4 link quality score and the IPv6 link quality score comprises: If the IPv4 link quality score is higher than the IPv6 link quality score and the difference exceeds a first threshold, the ranking of IPv4 in the address type priority list is increased; If the IPv6 link quality score is higher than the IPv4 link quality score and the difference exceeds a second threshold, the ranking level of IPv6 is increased; When the difference between the IPv4 and IPv6 link quality scores is between the first threshold and the second threshold, the current sorting weight is kept unchanged; According to the successful connection rates of IPv4 and IPv6 in historical scheduling records, the sorting weights are compensated and corrected; The compensated and corrected sorting weight is weightedly integrated with the real-time link quality score to generate a final sorting weight to update the address type priority list; The compensation and correction of the sorting weight according to the successful connection rates of IPv4 and IPv6 in the historical scheduling records includes: Extract the ratio of the cumulative number of successful connections to the number of failed connections of the IPv4 address under the target domain name within a preset historical time period as the IPv4 historical success rate; The ratio of the cumulative number of successful connections to the number of failed connections of the IPv6 address in the same time period is extracted as the IPv6 historical success rate; Calculate the difference between the historical success rate of IPv4 and the historical success rate of IPv6; If the ratio difference exceeds a preset compensation threshold, a difference compensation coefficient is added to the current sorting weight; The difference compensation coefficient is linearly superimposed on the real-time link quality score to generate a compensated ranking weight.

4. The method according to claim 1, characterized in that: The selecting a target IP address type from a preconfigured IP address pool based on the adaptive scheduling strategy includes: When the adaptive scheduling strategy indicates that the protocol stack parallel mode is adopted, the IPv4 address list and the IPv6 address list are simultaneously extracted from the IP address pool; Determine the primary allocation order and the backup allocation order of the IPv4 and IPv6 addresses according to the request protocol type of the client; Encapsulate the IPv4 or IPv6 address corresponding to the primary allocation order into the preferred record field of the DNS response message; Adding the standby protocol stack address corresponding to the standby allocation order to the additional record field of the DNS response message; In response to the client failing to connect to the primary address, triggering a protocol stack switching process based on the backup address in the additional record field to guide the client to re-initiate a connection request; The protocol stack switching process includes: Monitoring the connection establishment status between the client and the primary address, and generating a protocol stack switching instruction if no connection confirmation signal is received within a preset timeout period; Parsing the additional record field of the DNS response message to extract the protocol stack type and IP address corresponding to the backup address; Sending an address redirection message to the client, wherein the address redirection message includes the standby address and a protocol stack switching identifier; Record the protocol stack type, switching timestamp and switching reason of this switching operation, and update it to the historical switching log; According to the accumulated number of switching times of the same target domain name in the historical switching log, the allocation ratio of the primary and backup addresses in the subsequent scheduling strategy is dynamically adjusted.

5. The method according to claim 1, characterized in that: The method further comprises: A protocol stack compatibility detection service is deployed at the DNS resolution layer, and the following execution operations of the protocol stack compatibility detection service are performed: Sending an IPv4 protocol detection message and an IPv6 protocol detection message to the client, wherein the IPv4 protocol detection message and the IPv6 protocol detection message both contain a preset protocol identifier; Monitoring the feedback behavior of the client to the IPv4 protocol detection message and the IPv6 protocol detection message within a preset response time; If only an IPv4 probe response is received, marking the protocol stack support status of the client as only IPv4 compatible; If only an IPv6 probe response is received, marking the protocol stack support status of the client as only IPv6 compatible; If the IPv4 probe response and the IPv6 probe response are received at the same time, marking the protocol stack support status of the client as dual stack compatible; The marking result is stored in the protocol stack support state table, which is a direct call object for subsequent DNS resolution requests; The protocol stack supports the calling process of the state table including: When receiving a new DNS resolution request, extracting the source IP address and request protocol type of the new client corresponding to the new DNS resolution request; Query the protocol stack support status table for a historical marking result associated with the source IP address; If the historical marking result indicates that the new client is dual-stack compatible, allocating an IPv4 address or an IPv6 address according to the current adaptive scheduling policy; If the historical marking result is that a single protocol stack is compatible, the adaptive scheduling strategy generation step is skipped and the corresponding protocol stack address is directly allocated; When the protocol stack support status of the new client changes, the protocol stack support status table is updated through periodic re-detection.

6. The method according to claim 5, characterized in that When the protocol stack support status of the new client changes, updating the protocol stack support status table by periodic re-detection includes: Deploy a timer trigger mechanism at the DNS resolution layer to start a periodic detection timer associated with the protocol stack support state table; When the periodic detection timer reaches a preset re-detection period, scanning the protocol stack support status entries of all clients in the protocol stack support status table; Extract the last detection timestamp and protocol stack support status mark value corresponding to the source IP address of each client; Calculate the time interval between the current system time and the last detection timestamp, and compare the difference with the preset re-detection period; If the time interval exceeds the validity period threshold of the preset re-detection period, the source IP address of the client is added to the queue to be re-detected; Sending an IPv4 protocol detection message and an IPv6 protocol detection message to each client according to the order of source IP addresses in the queue to be re-detected; Monitoring the type of the probe response message returned by the client within a preset response time window; Extracting the protocol identifier and the client source IP address carried in the probe response message; If the protocol identifier indicates that the client returns an IPv4 probe response, the IPv4 compatibility mark of the corresponding source IP address in the protocol stack support status table is updated to a valid state; if the protocol identifier indicates that the client returns an IPv6 probe response, the IPv6 compatibility mark of the corresponding source IP address in the protocol stack support status table is updated to a valid state; if no IPv4 probe response or IPv6 probe response is received within the response time window, the corresponding protocol stack compatibility mark is set to an invalid state; Recalculate the protocol stack support status mark value of the client according to the updated protocol stack compatibility mark; overwrite the historical mark value in the protocol stack support status table with the recalculated protocol stack support status mark value; Record the timestamp of this re-detection operation to the last detection timestamp field of the protocol stack support status table; Dynamically adjusting a preset re-detection period of the periodic detection timer according to a change ratio of a protocol stack support status flag value in the queue to be re-detected; If the change ratio exceeds the dynamic adjustment threshold, the preset re-detection period of the periodic detection timer is shortened; if the change ratio is lower than the stable threshold, the preset re-detection period of the periodic detection timer is extended; The periodic detection timer is reset and a new round of periodic re-detection process is started.

7. The method according to claim 1, characterized in that The method further comprises: Configuring a global traffic scheduling policy template in the DNS server, wherein the global traffic scheduling policy template includes protocol stack scheduling rules corresponding to domain names of different service levels; In response to the target domain name belonging to the first priority service category, forcibly setting the IPv6 address as the primary address and allocating it preferentially; Monitor the network congestion index of the IPv6 link in real time, and if the network congestion index exceeds a preset alarm threshold, initiate a protocol stack fallback mechanism; Filtering available IPv4 addresses from an IP address pool through the protocol stack fallback mechanism, and updating a DNS resolution result to replace the available IPv4 address; The association relationship between the mandatory strategy and the fallback mechanism is written into the exception handling rule base of the adaptive scheduling strategy.

8. The method according to claim 7, characterized in that The configuring of the global traffic scheduling policy template in the DNS server includes: Creating a global traffic scheduling policy template in a policy management module of the DNS server, wherein the global traffic scheduling policy template includes a service level domain name classification table; According to the service level domain name classification table, different domain names are divided into a first priority, a second priority and a third priority according to the service level, and a preset protocol stack scheduling rule is bound to each service level; For the service category domain name of the first priority, setting in the protocol stack scheduling rule to force the use of the IPv6 address as the primary address and activating the enabling switch of the protocol stack fallback mechanism; Collecting real-time congestion parameters of the IPv6 link corresponding to the target domain name in real time, wherein the real-time congestion parameters include a packet retransmission rate and a buffer queue depth; When the real-time congestion parameter exceeds the preset alarm threshold in the protocol stack scheduling rule, triggering the start condition of the protocol stack fallback mechanism; According to the protocol stack fallback mechanism, screening the IPv4 address set bound to the target domain name from the IP address pool; Based on the geographical location proximity index of each IPv4 address in the IPv4 address set, select the IPv4 address closest to the client's geographical location as the fallback target address; Encapsulating the fallback target address into the preferred record field of the DNS response message, and generating a protocol stack fallback operation log including a switching timestamp and congestion parameters; Associating the protocol stack rollback operation log with the service level of the target domain name, and updating the exception handling rule base of the global traffic scheduling policy template; According to the historical rollback records of the same service level domain name in the exception handling rule base, the preset alarm threshold in the protocol stack scheduling rule is dynamically adjusted.

9. The method according to claim 7, characterized in that: The protocol stack fallback mechanism includes: Collecting real-time congestion parameters of the IPv6 link, wherein the real-time congestion parameters include a packet retransmission rate, a buffer overflow number, and an average queuing delay; If the data packet retransmission rate exceeds a first congestion threshold, or the number of buffer overflows exceeds a second congestion threshold, the IPv6 link is determined to be in an unavailable state; Selecting a set of IPv4 addresses bound to the target domain name from an IP address pool, and filtering the target IPv4 addresses based on geographic proximity; Generate a protocol stack fallback instruction, and encapsulate the target IPv4 address into a preferred record field of a DNS response message; Send a protocol stack rollback alarm message to the network management terminal and record the log data of the rollback operation.

10. A dual-stack network adaptive scheduling system, characterized in that: It comprises a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of any one of the methods of claims 1 to 9.

Images