DNS forwarding grading method and system
By introducing a forwarding hierarchical module in LocalDNS, dynamically generate priority packets and selecting the fastest-responsive authoritative DNS, the problem of authoritative DNS attacks and delays is solved, security protection and low-cost DNS response are achieved, and user experience and System performance.
Patent Information
- Application Number
- CN202411199219.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-29
- Publication Date
- 2024-11-29
AI Technical Summary
Authoritative DNS is paralyzed when attacked, causing client websites to be unable to resolve domain names. The existing technology affects user experience when processing DNS requests are delayed, and the existing DNS packet forwarding methods are complex and costly.
Add a forwarding hierarchical module to LocalDNS, generate priority packets through static or dynamic methods, select the fastest-responsive authoritative DNS for domain name resolution, dynamically detect the RTT delay of authoritative DNS and automatically generate hierarchies to ensure that the DNS of high-priority packets are available Use priority, low priority packets are only used when high priority fails.
It realizes the security protection of authoritative DNS and low latency response, reduces costs, avoids dependence on expensive DDoS devices, ensures overall DNS response speed and user experience, and is simple to configure.
Smart Images

Figure CN119052211A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of Internet technology, and in particular to a DNS forwarding classification method and system thereof. Background Art
[0002] Local DNS refers to the DNS server configured on computers, mobile phones and other terminal devices, which provides domain name resolution to the terminal. LocalDNS is built by network operators to provide domain name query and resolution services to Internet users. When LocalDNS receives a user's domain name resolution request, if the result is not found in the local cache server, it will initiate a recursive query: first, it will query the root server, which records the location of the server where each top-level domain is located; secondly, it will query the top-level domain name server for the location of the domain name server of the next level domain; then, it will query level by level until it finds the authoritative DNS address of the domain where the requested domain name is located; finally, it will initiate a query request to the authoritative DNS, obtain the resolution IP, and respond to the user.
[0003] The forwarding function is one of the important functions of DNS query. When a domain is configured with forwarding, LocalDNS does not need recursion and directly initiates a resolution query for the domain name under the domain to the forwarding DNS server. The forwarding DNS server can be a recursive DNS or an authoritative DNS.
[0004] In the CDN enterprise-specific DNS protection service, for example, 114DNS will hide the CDN enterprise's authoritative DNS and pass the recursive request of LocalDNS to the customer's authoritative DNS. In this way, the CDN enterprise's NS server is protected. When there is an attack, 114DNS will wash away the attack traffic and then pass the clean DNS data to the CDN enterprise's NS server. This solution is relatively expensive because DNS cleaning is required during an attack. The larger the attack volume, the higher the cleaning cost; special normal requests may also be cleaned. Generally, CDN enterprises will only protect one NS when renting. During an attack, only one NS is in service, and the service performance will be reduced at this time; because the protection DNS is added during the recursive process, the delay is also increased.
[0005] In addition, the existing patent discloses a DNS packet forwarding method and device - CN202211703423.0. The purpose of this patent is to achieve local scheduling, that is, to return the IP closest to the user. The authoritative DNS determines the user's location based on the IP of the requested LocalDNS, so when making a recursive request to the user, it is necessary to select the LocalDNS closest to the user to initiate a recursive request. This patent must split LocalDNS into two parts: cache and recursion. The cache is user-oriented, and recursion is deployed in multiple computer rooms across the country. The cache forwards user requests to the recursive server closest to the user. This patent requires the configuration of the entire network IP address library, and the grouping is associated with the user address library, so the configuration is relatively complex. Summary of the invention
[0006] The purpose of the present invention is to provide a DNS forwarding hierarchical method and system to solve the problem that the authoritative DNS is paralyzed due to attacks, resulting in the customer's website or business being inaccessible due to the domain name resolution failure, and to solve the problem that the delay of a small number of DNS requests is large and affects the user experience of ultra-low delay services.
[0007] The technical solution adopted by the present invention is: A DNS forwarding hierarchical method comprises the following steps: Step 1: The local domain name server (LocalDNS) receives the user's DNS resolution request and determines whether the local cache has the resolution of the requested domain name; if so, the local cache resolution address is used as a response feedback and the process ends; otherwise, execute step 2; Step 2: Check whether the domain where the requested domain name is located is configured with a forwarding function; if so, proceed to step 3; otherwise, proceed to the normal recursive process; Step 3, determine whether the domain is configured with forwarding classification grouping; if so, enter the forwarding classification process and execute step 4; otherwise, execute the normal forwarding process; Step 4, obtaining the highest priority forwarding packet; Step 5, obtain a list of all authoritative DNS in the selected group; Step 6: Select one of the authoritative DNSs according to the set algorithm to determine whether there is an available DNS; if so, initiate a domain name resolution request to the corresponding DNS and execute step 7; otherwise, select the next high priority group and execute step 5; Step 7: The authoritative DNS responds with the resolution result, and localdns returns the response result to the user.
[0008] Furthermore, the DNS forwarding hierarchical grouping generation in step 3 supports two modes: static configuration and dynamic generation.
[0009] Furthermore, in step 3, the static configuration method is: statically setting the priority weight for each authoritative DNS.
[0010] Furthermore, the dynamic generation method in step 3 is: LocalDNS periodically detects the delay of each authoritative DNS and generates automatic groups according to the delay level. The specific steps are as follows: Step 3-2-1, set the initial parameters: detection time (half an hour), number of consecutive detections (10 times), and RTT step value (100ms).
[0011] Step 3-2-2, start the detection regularly to obtain the delay of each authoritative DNS Step 3-2-3, calculate the average RTT value of each authoritative DNS under the hierarchical domain, Step 3-2-4, sort by 100ms intervals, the interval with the smallest RTT is set to the highest priority, the interval with the second smallest RTT is set to the second highest priority, and the rest of the DNS are set to the third highest priority regardless of their RTT; Furthermore, the authoritative DNS detection timeout in step 3-2-2 is counted as 3000ms (3s).
[0012] Furthermore, in step 6, one of the authoritative DNS is selected according to the RTT algorithm.
[0013] Specifically, when receiving a DNS resolution request from a user, the local cache does not have the resolution of the requested domain name, and the domain where the requested domain name is located is configured with forwarding (forward), the forwarding process is entered (otherwise, the normal recursive process is followed); if the domain is statically configured or automatically generated with forwarding classification, the forwarding classification process is entered (otherwise, the normal forwarding process is followed); the highest priority forwarding group is obtained; Get a list of all authoritative DNS in the selected group; select one of the authoritative DNS according to the RTT algorithm (this algorithm uses the original algorithm of LocalDNS). If there is no available DNS, select the next high priority group, repeat the above steps until an available authoritative DNS is selected, and then initiate a domain name resolution request to the DNS; the authoritative DNS responds with the resolution result, and localdns returns the response result to the user.
[0014] A DNS forwarding hierarchical system includes a client, a local DNS server (localdns) and an authoritative DNS server; the local DNS server is provided with a cache module, a recursive module, a common forwarding module and a DNS forwarding hierarchical module; the cache module provides a DNS cache service; the recursive module provides a DNS recursive service; the local DNS server (LocalDNS server) is used to return an accurate query result to the user when receiving a user resolution request; when the local DNS server has a forwarding configuration for the domain where the requested domain name is located, it does not need to recursively directly query the authoritative DNS server until the final query result is responded to the user; wherein, the common forwarding module is used to forward the user resolution request to the authoritative DNS server to obtain the query result when there is no forwarding hierarchical grouping; the DNS forwarding hierarchical module is used to generate authoritative DNS groups of different priorities, select the highest priority group and select the next level authoritative DNS group only when all DNSs of the highest priority authoritative DNS group are inaccessible, and the DNS forwarding hierarchical module selects an authoritative DNS in the selected authoritative DNS group and sends the customer's domain name resolution request to the selected authoritative DNS.
[0015] The present invention adopts the above technical solution and adds forwarding hierarchical modules with different priorities to LocalDNS. When DNS recursion occurs, if the request domain has enabled domain name forwarding hierarchical, the authoritative DNS of the highest priority group will be used first. When the high priority group can provide DNS resolution service, LocalDNS will not forward the domain name resolution request to the low priority group. The forwarding hierarchical module supports automatic grouping and dynamically detects the response RTT delay of each authoritative DNS.
[0016] The solution designed by the present invention can not only realize the security protection of authoritative DNS, but also does not require investment or rental of expensive DDoS equipment, and the cost of use is very low. In order to eliminate the authoritative DNS with slow response, ensure that the overall response is very fast, and hide part of the authoritative DNS for the security protection of authoritative DNS. The present invention does not distinguish between the deployment forms of LocalDNS, which can be cache-recursive integrated or separate. The present invention only needs to configure the authoritative DNS with similar response RTT in the same level group. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The present invention is further described in detail below with reference to the accompanying drawings and specific embodiments; Figure 1 A schematic diagram of a flow chart of a DNS forwarding classification method of the present invention; Figure 2 A schematic diagram of the structure of a DNS forwarding hierarchical system of the present invention; Figure 3 This is a schematic diagram of the principle structure of the forwarding classification module of the present invention; Figure 4Schematic diagram of the principle of secure hosting of domain names; Figure 5 This is a schematic diagram for comparing the low latency of the present invention with other technologies. Implementation
[0018] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.
[0019] The present invention adds forwarding hierarchical modules with different priorities to LocalDNS. When DNS recursion occurs, if the request domain has enabled domain name forwarding hierarchical, the authoritative DNS of the highest priority group will be used first. When the high priority group can provide DNS resolution service, LocalDNS will not forward the domain name resolution request to the low priority group. The forwarding hierarchical module supports automatic grouping and dynamically detects the response RTT delay of each authoritative DNS.
[0020] like Figures 1 to 5 As shown in one, the present invention discloses a DNS forwarding hierarchical method, which specifically includes the following steps: Step 1: Receive the user's DNS resolution request and determine whether the local cache has the resolution of the requested domain name; if so, use the local cached resolution address as a response feedback and end the process; otherwise, execute step 2; Step 2: Check whether the domain where the requested domain name is located is configured with a forwarding function; if so, proceed to step 3; otherwise, proceed to the normal recursive process; Step 3, determine whether the domain is configured with forwarding classification grouping; if so, enter the forwarding classification process and execute step 4; otherwise, execute the normal forwarding process; Step 4, obtaining the highest priority forwarding packet; Step 5, obtain a list of all authoritative DNS in the selected group; Step 6: Select one of the authoritative DNSs according to the set algorithm to determine whether there is an available DNS; if so, initiate a domain name resolution request to the corresponding DNS and execute step 7; otherwise, select the next high priority group and execute step 5; Step 7: The authoritative DNS responds with the resolution result, and localdns returns the response result to the user.
[0021] Furthermore, the DNS forwarding hierarchical grouping generation in step 3 supports two modes: static configuration and dynamic generation.
[0022] Furthermore, in step 3, the static configuration method is: statically setting the priority weight for each authoritative DNS.
[0023] Furthermore, the dynamic generation method in step 3 is: LocalDNS periodically detects the delay of each authoritative DNS and generates automatic groups according to the delay level. The specific steps are as follows: Step 3-2-1, set the initial parameters: detection time (half an hour), number of consecutive detections (10 times), and RTT step value (100ms).
[0024] Step 3-2-2, start the detection regularly to obtain the delay of each authoritative DNS Step 3-2-3, calculate the average RTT value of each authoritative DNS under the hierarchical domain, Step 3-2-4, sort by 100ms intervals, the interval with the smallest RTT is set to the highest priority, the interval with the second smallest RTT is set to the second highest priority, and the rest of the DNS are set to the third highest priority regardless of their RTT; Furthermore, the authoritative DNS detection timeout in step 3-2-2 is counted as 3000ms (3s).
[0025] Furthermore, in step 6, one of the authoritative DNS is selected according to the RTT algorithm.
[0026] Specifically, when receiving a DNS resolution request from a user, the local cache does not have the resolution of the requested domain name, and the domain where the requested domain name is located is configured with forwarding (forward), the forwarding process is entered (otherwise, the normal recursive process is followed); if the domain is statically configured or automatically generated with forwarding classification, the forwarding classification process is entered (otherwise, the normal forwarding process is followed); the highest priority forwarding group is obtained; Get a list of all authoritative DNS in the selected group; select one of the authoritative DNS according to the RTT algorithm (this algorithm uses the original algorithm of LocalDNS). If there is no available DNS, select the next high priority group, repeat the above steps until an available authoritative DNS is selected, and then initiate a domain name resolution request to the DNS; the authoritative DNS responds with the resolution result, and localdns returns the response result to the user.
[0027] A DNS forwarding hierarchical system includes a client, a local DNS server (localdns) and an authoritative DNS server; the local DNS server is provided with a cache module, a recursive module, a common forwarding module and a DNS forwarding hierarchical module; the cache module provides a DNS cache service; the recursive module provides a DNS recursive service; the local DNS server (LocalDNS server) is used to return an accurate query result to the user when receiving a user resolution request; when the local DNS server has a forwarding configuration for the domain where the requested domain name is located, it does not need to recursively directly query the authoritative DNS server until the final query result is responded to the user; wherein, the common forwarding module is used to forward the user resolution request to the authoritative DNS server to obtain the query result when there is no forwarding hierarchical grouping; the DNS forwarding hierarchical module is used to generate authoritative DNS groups of different priorities, select the highest priority group and select the next level authoritative DNS group only when all DNSs of the highest priority authoritative DNS group are inaccessible, and the DNS forwarding hierarchical module selects an authoritative DNS in the selected authoritative DNS group and sends the customer's domain name resolution request to the selected authoritative DNS.
[0028] Specifically, the DNS forwarding grading module includes the following functions: authoritative DNS group selection: select the group with the highest priority, and only when all DNS in the highest priority group are inaccessible will the next level group be selected; authoritative DNS selection: select a DNS in the same level group to resolve, following the original recursive selection algorithm (RTT algorithm) of recursive DNS; DNS forwarding: send the customer's domain name resolution request to the selected authoritative DNS; group generation: including static configuration and automatic dynamic grading modes to generate authoritative DNS groups of different priorities.
[0029] The present invention adopts the technical solution process as follows Figure 4 The process is described as follows: (1) When receiving a DNS resolution request from a user, the cache does not have the resolution of the requested domain name, and the domain where the requested domain name is located is configured with forwarding, the forwarding process is entered (otherwise, the normal recursive process is followed); (2) If the domain is statically configured or automatically generated for forwarding classification, the forwarding classification process is entered (otherwise the normal forwarding process is followed); (3) Obtain the highest priority forwarding packet, (4) Obtain a list of all authoritative DNS in the selected group; (5) Select one of the authoritative DNSs according to the RTT algorithm (this algorithm uses the original LocalDNS algorithm). If there is no available DNS, select the next high priority group and repeat step (4); if an available authoritative DNS is selected, initiate a domain name resolution request to the DNS; (6) The authoritative DNS responds with the resolution result, and localdns returns the response result to the user.
[0030] Furthermore, the present invention relates to DNS forwarding packet generation supporting two modes: static configuration and dynamic generation.
[0031] Static configuration, taking the two most widely used DNS in the industry as an example, other DNS software can refer to it.
[0032] BIND configuration method: Syntax: forwarders{ ip priority}; here, priority is 1 to 9, 1 is the highest.
[0033] Example: zone "test.cn" { type forward; forwarders{ 1.1.1.1 1; 2.2.2.2 1; 5.5.5.5 2; 6.6.6.6 2 8.8.8.8 3; 9.9.9.9 3; }; }; Unbound configuration method: Syntax: forward-addr: ip priority; here, priority is 1 to 9, 1 is the highest.
[0034] Example: forward-zone: name: test.cn forward-addr: 1.1.1.1 1 forward-addr: 2.2.2.2 1 forward-addr: 5.5.5.5 2 forward-addr: 6.6.6.6 2 forward-addr: 8.8.8.8 3 forward-addr: 9.9.9.9 3 Furthermore, the present invention supports automatic dynamic classification. LocalDNS periodically detects the delay of each authoritative DNS and generates automatic groups according to the delay level. The method is as follows: (1) Set the initial parameters: detection time (half an hour), number of consecutive detections (10 times), and RTT step value (100ms).
[0035] (2) Start detection at a scheduled time.
[0036] (3) Calculate the average RTT value of each authoritative DNS in the hierarchical domain, and count each timeout as 3000ms (3s).
[0037] (4) Sort by 100ms intervals. The interval with the smallest RTT is set to the highest priority, the interval with the second smallest RTT is set to the second highest priority, and the remaining DNSs are given the third highest priority regardless of their RTT.
[0038] Example of automatically generated priority groups: The detection results of test1.cn are as follows: 1.1.1.1 40ms 2.2.2.2 80ms 3.3.3.3 160ms 4.4.4.4 150ms 5.5.5.5 390ms 6.6.6.6 250ms test1.cn is classified as follows: #ip priority 1.1.1.1 1 2.2.2.2 1 3.3.3.3 2 4.4.4.4 2 5.5.5.5 3 6.6.6.6 3 test2.cn is classified as follows: 10.1.1.1 140ms 20.2.2.2 110ms 30.3.3.3 260ms 40.4.4.4 250ms 50.5.5.5 590ms 60.6.6.6 450ms test2.cn is classified as follows: #ip priority 10.1.1.1 1 20.2.2.2 1 30.3.3.3 2 40.4.4.4 2 50.5.5.5 3 60.6.6.6 3 In order to better understand the technical solution and application scenarios of the present invention, two embodiments are described below.
[0039] Embodiment 1: Domain security hosting - when the public authoritative DNS is attacked and paralyzed, the customer's DNS resolution can still be provided normally.
[0040] The IP of the enterprise's authoritative DNS will only take effect after it is registered with the domain name registration agency. The IP of the authoritative DNS is public and can be obtained by Internet users by querying the NS record. When hackers launch attacks on all the authoritative IPs of the enterprise, if the enterprise's authoritative DNS does not rent anti-DDoS services, LocalDNS will fail to access these authoritative DNS and time out, Internet users' DNS requests will fail, and the enterprise's website and other services will be interrupted.
[0041] After the attack occurs, enterprise operation and maintenance personnel can register a new authoritative DNS IP and deploy new DNS software, but the authoritative DNS IP takes a long time to take effect, and the attack may stop before it takes effect. Optional anti-attack methods include purchasing anti-DDoS equipment or renting anti-DDoS products (such as 114dns' CDN enterprise-specific DNS protection service), but the cost is relatively high.
[0042] like Figure 4 As shown, the domain security hosting method scheme of the present invention is as follows: LocalDNS configures the unregistered hidden authoritative DNS (not public) in the low priority forwarding group and the registered authoritative DNS (public) in the high priority forwarding group. Internet users cannot know the hidden authoritative DNS (there is only a public IP in the NS record), so hackers cannot attack the hidden authoritative DNS. When the public authoritative DNS is attacked and cannot be accessed, LocalDNS accesses the authoritative DNS of the low priority group (i.e., the hidden DNS), ensuring that the enterprise DNS is not affected.
[0043] The DNS security hosting of the present invention is not only simple to deploy, but also very low in cost. The LocalDNS operator has no other cost except upgrading LocalDNS. In addition to the high cost, the anti-DDoS service method may cause accidental damage during cleaning, causing DNS failure for a small number of users.
[0044] Embodiment 2: Low latency response—ensuring that all recursive resolution response times are very low.
[0045] LocalDNS has RTT delay detection for authoritative DNS. Authoritative DNS with large delay will allocate less access, but as long as authoritative DNS can provide service, no matter how large the delay is, a small number of recursive requests will always be allocated. For services such as VR that have extremely high delay requirements, these small number of users have a poor service experience.
[0046] like Figure 5 As shown, the enterprise signs a contract with LocalDNS and configures the authoritative DNS IP of the enterprise domain according to the RTT size. The high priority group is assigned to the group with small RTT, and the low priority group is assigned to the group with large RTT. Then LocalDNS usually only assigns DNS requests to the authoritative DNS with low latency, ensuring that all users have fast DNS responses, thereby ensuring that all users have a good low-latency service experience. The method of the present invention is also well applied in CDN indicator rankings. The DNS latency and the first packet response latency will not be affected by the large latency of the authoritative DNS of the customer.
[0047] The LocalDNS of the present invention adds a forwarding classification module for forwarding according to priority; LocalDNS forwarding (forward) adds a priority grouping generation module (IP+priority vs. only configuring IP according to DNS standard), including two modes of static configuration and automatic dynamic classification; high priority forwarding groups are given priority: LocalDNS receives a resolution request for a domain configured with a forward priority and only sends it to the NS server in the highest priority group, and the NS in the low priority group does not receive the domain name resolution request; only when all NS in the high priority group cannot be accessed, LocalDNS forwards to the NS in the second priority group.
[0048] The solution designed by the present invention can not only realize the security protection of authoritative DNS, but also does not require investment or rental of expensive DDoS equipment, and the cost of use is very low. In order to eliminate the authoritative DNS with slow response, ensure that the overall response is very fast, and hide part of the authoritative DNS for the security protection of authoritative DNS. The present invention does not distinguish between the deployment forms of LocalDNS, which can be cache-recursive integrated or separate. The present invention only needs to configure the authoritative DNS with similar response RTT in the same level group.
[0049] Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the detailed description of the embodiments of the present application is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians of the art without making creative work are within the scope of protection of the present application.
Claims
1. A DNS forwarding hierarchical method, characterized in that: It includes the following steps: Step 1: The local domain name server receives the user's DNS resolution request and determines whether the local cache has the resolution of the requested domain name; if so, the local cached resolution address is used as a response feedback and the process ends; Otherwise, go to step 2; Step 2: Check whether the domain where the requested domain name is located is configured with a forwarding function; if yes, proceed to step 3; Otherwise, execute the normal recursive process; Step 3, determine whether the domain is configured with forwarding classification grouping; if so, enter the forwarding classification process and execute step 4; Otherwise, the normal forwarding process is executed; Step 4, obtaining the highest priority forwarding packet; Step 5, obtain a list of all authoritative DNS in the selected group; Step 6: Select one of the authoritative DNSs according to the set algorithm to determine whether there is an available DNS; if so, initiate a domain name resolution request to the corresponding DNS and execute step 7; otherwise, select the next high priority group and execute step 5; Step 7: The authoritative DNS responds with the resolution result, and localdns returns the response result to the user.
2. A DNS forwarding hierarchical method according to claim 1, characterized in that: In step 3, the DNS forwarding hierarchical grouping generation supports two modes: static configuration and dynamic generation.
3. A DNS forwarding hierarchical method according to claim 2, characterized in that: Static configuration method in step 3: statically set the priority value for each authoritative DNS.
4. A DNS forwarding hierarchical method according to claim 3, characterized in that: The dynamic generation method in step 3 is: LocalDNS periodically detects the delay of each authoritative DNS and generates automatic groups according to the delay level.
5. A DNS forwarding hierarchical method according to claim 4, characterized in that: Step 3 The specific steps are as follows: Step 3-2-1, set the initial delay parameters for detecting each authoritative DNS, including detection timing, number of consecutive detections, and RTT step value; Step 3-2-2, start detection regularly to obtain the delay of each authoritative DNS; Step 3-2-3, calculate the average RTT value of each authoritative DNS under the hierarchical domain, Step 3-2-4, sort by RTT step value, set the interval with the smallest RTT as the highest priority, set the interval with the second smallest RTT as the second highest priority, and the remaining DNSs are set as the third highest priority regardless of their RTT.
6. A DNS forwarding hierarchical method according to claim 5, characterized in that: Step 3-2-1 The detection timing is half an hour, the number of consecutive detections is 10 times, and the step value of the round-trip communication delay RTT is 100ms; sort by 100ms intervals, the interval with the smallest round-trip communication delay RTT is set to the highest priority, the interval with the second smallest round-trip communication delay RTT is set to the second highest priority, and the remaining DNSs are assigned the third highest priority regardless of their round-trip communication delay RTT.
7. A DNS forwarding hierarchical method according to claim 5, characterized in that: In step 3-2-2, the authoritative DNS detection timeout is counted as 3000ms.
8. A DNS forwarding hierarchical method according to claim 1, characterized in that: In step 6, select one of the authoritative DNS servers according to the RTT algorithm.
9. A DNS forwarding classification system, applying a DNS forwarding classification method according to any one of claims 1 to 8, characterized in that: The system includes a client, a local DNS server, and an authoritative DNS server; the local DNS server is used to return an accurate query result to the user upon receiving a user resolution request; When the local DNS server has the forwarding configuration for the domain where the requested domain name is located, it does not need to recurse and directly query the authoritative DNS server until the final query result is responded to the user; the local DNS server is equipped with a cache module, a recursive module, a normal forwarding module and a DNS forwarding hierarchical module; the cache module provides DNS cache service; the recursive module provides DNS recursive service; the normal forwarding module is used to forward the user's resolution request to the authoritative DNS server to obtain the query result when there is no forwarding hierarchical grouping; among them, the DNS forwarding hierarchical module is used to generate authoritative DNS groups of different priorities, select the highest priority group and only select the next level authoritative DNS group when all DNS in the highest priority authoritative DNS group are inaccessible, and the DNS forwarding hierarchical module selects an authoritative DNS in the selected authoritative DNS group and sends the customer's domain name resolution request to the selected authoritative DNS.
