System and method for improving network performance when using secure dns access schemes
US-2021092088-A1 · Mar 25, 2021 · US
US11770320B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11770320-B2 |
| Application number | US-202217743441-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 12, 2022 |
| Priority date | Jan 13, 2021 |
| Publication date | Sep 26, 2023 |
| Grant date | Sep 26, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for domain name resolution is provided, applied to a system for domain name resolution deployed in a scheduling cluster. The system includes a scheduling system, a probe system, and an analysis system. The scheduling system receives each query request from each DNS server, records each egress IP address of each local DNS server to generate a list of IP addresses to be probed, and reports the list of IP addresses to the probe system. The probe system distributes the list of IP addresses to each probe to probe each of IP addresses in the list through each probe. And the analysis system receives each probing result fed back by each probe, sets each authoritative DNS server for each local DNS server, and processes each domain name resolution request sent by each local DNS server through each authoritative DNS server.
Opening claim text (preview).
What is claimed is: 1. A method for domain name resolution, comprising: at a system for domain name resolution deployed in a scheduling cluster, the system for domain name resolution including a scheduling system, a probe system, and an analysis system, receiving, by the scheduling system, one or more query requests from each of a plurality of local domain name system (DNS) servers, recording an egress Internet protocol (IP) address of each of the plurality of local DNS servers to generate a list of IP addresses that are to be probed, and reporting the list of IP addresses to the probe system; distributing, by the probe system, the list of IP addresses to a plurality of probes, each of the plurality of probes to probe a respective plurality of IP addresses in the list of IP addresses; and receiving, by the analysis system, probing result fed back by each of the plurality of probes, setting an authoritative DNS server for each of the plurality of local DNS servers, and processing each domain name resolution request sent by each of the plurality of local DNS servers through a corresponding authoritative DNS server; wherein generating the list of IP addresses that are to be probed comprises: classifying the egress IP address of each of the plurality of local DNS servers based on a specified address segment to obtain classified egress IP addresses for the plurality of local DNS servers; and allocating a service region identifier to each class of the classified egress IP addresses, and aggregating each class of the classified egress IP addresses carrying service region identifiers into the list of IP addresses. 2. The method according to claim 1 , wherein probing the respective plurality of IP addresses in the list of IP addresses through each of the plurality of probes comprises: setting a reference tracking hop count for a time to live in response to that probing for a target IP address fails; probing the target IP address through a detection protocol group; in response to the probing succeeding, recording a round-trip time corresponding to the probing succeeding, and terminating the probing for the target IP address; and in response to the probing failing, determining whether to update the reference tracking hop count, and determining whether to terminate the probing for the target IP address. 3. The method according to claim 2 , wherein probing the target IP address through the probe protocol group comprises: sending a request packet to the target IP address based on a current probe protocol in the probe protocol group; and in response to the target IP address feeding back a response packet to the request packet, calculating a time difference between the request packet and the response packet, and taking the time difference as the round-trip time corresponding to the probing succeeding. 4. The method according to claim 3 , wherein a probe protocol in the probe protocol group includes a user datagram protocol (UDP), the request packet is a UDP probe packet, and the response packet is an Internet control message protocol (ICMP) destination unreachable packet; the probe protocol in the probe protocol group includes a transmission control protocol (TCP), the request packet is a TCP SYN probe packet, and the response packet is a TCP ACK packet; and the probe protocol in the probe protocol group includes an Internet control message protocol (ICMP), the request packet is an ICMP echo request probe packet, and the response packet is an ICMP echo reply packet. 5. The method according to claim 3 , further comprising: In response to the target IP address not feeding back the response packet for the request packet, acquiring a timeout packet with a maximum time to live sent back by an intermediate gateway by the probe system; and calculating, by the probe system, a time difference between the timeout packet and the request packet, and taking the time difference as the round-trip time corresponding to the probing succeeding. 6. The method according to claim 5 , wherein before calculating the time difference between the timeout packet and the response packet, the method further comprises: in response to a time to live corresponding to the timeout packet being greater than or equal to a specified time to live threshold, calculating the time difference between the timeout packet and the request packet by the probe system; and in response to the time to live corresponding to the timeout packet being less than the specified time to live threshold, discarding the timeout packet and using a next probe protocol to probe the target IP address by the probe system. 7. The method according to claim 2 , wherein determining whether to update the reference tracking hop count comprises: in response to the reference tracking hop count being greater than a minimum tracking hop count, decreasing the reference tracking hop count, and taking the decreased tracking hop count as the reference tracking hop count for a next round of probing. 8. The method according to claim 2 , wherein determining whether to terminate the probing for the target IP address comprises: in response to the reference tracking hop count being less than or equal to a minimum tracking hop count, determining that the target IP address probe fails, and terminating the probing for the target IP address. 9. The method according to claim 1 , wherein setting an authoritative DNS server for each of the plurality of local DNS servers comprises: querying a target probe corresponding to an optimal probe result for a current local DNS server; and setting an authoritative DNS server in a region where the target probe is located as an authoritative DNS server corresponding to the current local DNS server. 10. The method according to claim 1 , wherein setting an authoritative DNS server for each of the plurality of local DNS servers comprises: for any one local DNS server in the local DNS servers: identifying a region where the local DNS server is located and a network operator that the local DNS server supports; obtaining an IP address of an authoritative DNS server set for the local DNS server; and constructing a mapping relationship among the region where the local DNS server is located, the network operator, and the IP address of the authoritative DNS server. 11. The method according to claim 9 , wherein setting an authoritative DNS server for each of the plurality of local DNS servers comprises: for any one local DNS server in the local DNS servers: identifying a region where the local DNS server is located and a network operator that the local DNS server supports; obtaining an IP address of an authoritative DNS server set for the local DNS server; and constructing a mapping relationship among the region where the local DNS server is located, the network operator, and the IP address of the authoritative DNS server. 12. The method according to claim 1 , wherein processing each domain name resolution request sent by each of the plurality of local DNS servers through the corresponding authoritative DNS server comprises: sending a resolution IP address fed back for a current local DNS server to the scheduling system to compare the resolution IP address with an IP address of an authoritative DNS server set for the current local DNS server through the scheduling system; and in response to the resolution IP address being inconsistent with the IP address of the authoritative DNS server set for the current local DNS server, replacing the resolution IP address with the IP address of the authoritative DNS server set for the current local DNS server, and feeding back the replaced IP address to the current local DNS se
using time related information in packets, e.g. by adding timestamps · CPC title
Round trip delays · CPC title
Network monitoring probes · CPC title
using domain name system [DNS] · CPC title
Internet protocol [IP] addresses · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.