CN113452808A - Domain name resolution method, device, equipment and storage medium - Google Patents

Domain name resolution method, device, equipment and storage medium Download PDF

Info

Publication number
CN113452808A
CN113452808A CN202110724967.4A CN202110724967A CN113452808A CN 113452808 A CN113452808 A CN 113452808A CN 202110724967 A CN202110724967 A CN 202110724967A CN 113452808 A CN113452808 A CN 113452808A
Authority
CN
China
Prior art keywords
address
target
domain name
cache
cache information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110724967.4A
Other languages
Chinese (zh)
Other versions
CN113452808B (en
Inventor
郑坤维
区润强
祝美祺
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bigo Technology Pte Ltd
Original Assignee
Bigo Technology Pte Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bigo Technology Pte Ltd filed Critical Bigo Technology Pte Ltd
Priority to CN202110724967.4A priority Critical patent/CN113452808B/en
Publication of CN113452808A publication Critical patent/CN113452808A/en
Application granted granted Critical
Publication of CN113452808B publication Critical patent/CN113452808B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/58—Caching of addresses or names

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the application discloses a domain name resolution method, a domain name resolution device, domain name resolution equipment and a storage medium, and belongs to the technical field of the Internet. The method comprises the following steps: responding to an application starting instruction, storing IP cache information in a disk cache to a memory cache, wherein the IP cache information comprises a corresponding relation between a domain name and an IP address; responding to a network resource acquisition request, and inquiring a target IP address in the IP cache information cached in the memory based on a target domain name; responding to the target IP address, and acquiring network resources based on the target IP address; and responding to the condition that the target IP address is not inquired, acquiring the target IP address from a DNS (domain name server) based on the target domain name, and acquiring network resources based on the target IP address. According to the method provided by the embodiment of the application, the disk cache can persistently store the IP cache information, the fast resolution of the domain name is facilitated, and the obtaining efficiency of the IP address is improved.

Description

Domain name resolution method, device, equipment and storage medium
Technical Field
The embodiment of the application relates to the technical field of internet, in particular to a domain name resolution method, a domain name resolution device, domain name resolution equipment and a storage medium.
Background
In the network resource request process, the domain name is firstly analyzed to obtain the corresponding IP address, and then the network resource is obtained through the IP address.
In the related art, an IP address corresponding to a domain name is obtained in a memory cache, that is, a correspondence between the domain name and the IP address accessed in the history is stored in the memory cache, so that the IP address corresponding to the domain name in the current network resource request is determined based on information stored in the memory cache.
However, when the IP address is obtained in this way, if the memory cache is released, the corresponding IP address cannot be obtained, and the corresponding IP address needs to be resolved again by the DNS server, which affects the obtaining of the network resource.
Disclosure of Invention
The embodiment of the application provides a domain name resolution method, a domain name resolution device, domain name resolution equipment and a storage medium, and the technical scheme is as follows:
in one aspect, an embodiment of the present application provides a domain name resolution method, where the method includes:
responding to an application starting instruction, storing IP cache information in a disk cache to a memory cache, wherein the IP cache information comprises a corresponding relation between a domain name and an IP address;
responding to a network resource acquisition request, and inquiring a target IP address in the IP cache information cached in the memory based on a target domain name;
responding to the target IP address, and acquiring network resources based on the target IP address;
and responding to the condition that the target IP address is not inquired, acquiring the target IP address from a DNS (domain name server) based on the target domain name, and acquiring network resources based on the target IP address.
On the other hand, an embodiment of the present application provides a domain name resolution apparatus, where the apparatus includes:
the storage module is used for responding to an application starting instruction, and storing IP cache information in the disk cache to a memory cache, wherein the IP cache information comprises a corresponding relation between a domain name and an IP address;
the query module is used for responding to a network resource acquisition request and querying a target IP address in the IP cache information cached in the memory based on a target domain name;
the first acquisition module is used for responding to the inquiry of the target IP address and acquiring network resources based on the target IP address;
and the second acquisition module is used for responding to the condition that the target IP address is not inquired, acquiring the target IP address from the DNS based on the target domain name and acquiring network resources based on the target IP address.
In another aspect, embodiments of the present application provide a computer device, which includes a processor and a memory, where at least one instruction, at least one program, a set of codes, or a set of instructions is stored in the memory, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the domain name resolution method according to the above aspect.
In another aspect, an embodiment of the present application provides a computer-readable storage medium, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by a processor to implement the domain name resolution method according to the above aspect.
In another aspect, embodiments of the present application provide a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the domain name resolution method provided in the various alternative implementations of the above aspects.
The technical scheme provided by the embodiment of the application at least comprises the following beneficial effects:
in the embodiment of the application, the storage IP cache information is stored in the disk cache. When the application is started, storing the IP cache information in the disk cache into a memory cache, and acquiring the IP address corresponding to the domain name from the IP cache information in the memory cache after receiving a network resource acquisition request. Because the disk cache can persistently store the IP cache information, when the IP cache information cached by the application memory is lost, the IP cache information can be obtained in the disk cache again, so that the domain name can be quickly resolved without being resolved by the DNS server again, and the efficiency of obtaining the IP address is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 illustrates a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application;
fig. 2 is a flowchart illustrating a domain name resolution method according to an exemplary embodiment of the present application;
FIG. 3 illustrates a schematic diagram of interaction among applications, caches, and DNS servers provided by an exemplary embodiment of the present application;
fig. 4 shows a flowchart of a domain name resolution method provided by another exemplary embodiment of the present application;
FIG. 5 illustrates a schematic diagram of determining a priority of a target IP address provided by an exemplary embodiment of the present application;
fig. 6 shows a flowchart of a domain name resolution method provided by another exemplary embodiment of the present application;
fig. 7 shows a block diagram of a domain name resolution apparatus according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
In the related technology, a memory cache is used for storing IP cache information, when a network resource acquisition request is received, a target IP address is inquired in the IP cache information according to a target domain name, then when an application process of the memory cache is closed, the cache information is released, namely the IP cache information in the memory cache is lost, when the network resource acquisition request is received again, the target IP address cannot be acquired in the memory cache, an analysis request needs to be sent to a DNS server, and then the target IP address is acquired, and the method increases the IP address acquisition delay and further influences the acquisition of network resources.
In the embodiment of the application, the IP cache information is stored in the disk cache, so that the IP cache information is persistently stored, and when the IP cache information cached in the memory is lost, the corresponding IP cache information can be still obtained in the disk cache, and the obtaining efficiency of the target IP address is ensured.
Referring to fig. 1, a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application is shown. The implementation environment can comprise: a computer device 101, a first server 102 and a second server 103.
A client having domain name resolution requirements is running in the computer device 101. The computer device 101 may be a smart phone, a tablet computer, a smart television, a digital player, a laptop or desktop computer, etc., and the client may be an in-device application, such as a game-like application, an instant messaging-like application, a social-like application, etc. The embodiment of the present application does not limit the specific type of the computer device 101 and the specific type of the client.
The first server 102 is an independent physical server, or a server cluster or distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, distribution networks, big data and artificial intelligence platforms, and the like. In this embodiment, the first server 102 is a server with a Domain Name resolution function, a client in the computer device 101 may obtain a target IP address corresponding to a target Domain Name at the first server 102, and the first server may be a Domain Name System (DNS) server or other servers, which is not limited in this embodiment.
The second server 103 is an independent physical server, or a server cluster or distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, distribution networks, and big data and artificial intelligence platforms. In this embodiment, the second server 103 is a server corresponding to the target IP address, the client in the computer device 101 may be connected to the second server 103 through the target IP address, and the second server 103 may provide the network resource to the client.
The computer device 101, the first server 102 and the second server 103 can be directly or indirectly connected through wired or wireless communication, and the present application is not limited thereto.
In a possible application scenario, a client in the computer device 101 requests a network resource, first, a target IP address is queried in cached IP cache information, if the target IP address is queried, the client is directly connected to the second server 103 through the target IP address, if the target IP address is not queried, a domain name resolution request is sent to the first server 102 to obtain the target IP address, the first server 102 provides the target IP address to the computer device 101, and the computer device 101 establishes network connection with the second server 103 through the target IP address.
Referring to fig. 2, a flowchart of a domain name resolution method according to an exemplary embodiment of the present application is shown. The embodiment is described by taking a computer device of the method used in the implementation environment shown in fig. 1 as an example, and the method includes the following steps:
step 201, in response to the application start instruction, storing the IP cache information in the disk cache to a memory cache, where the IP cache information includes a correspondence between the domain name and the IP address.
The disk cache means that information is stored in a disk, and the IP cache information in the disk cache can be stored persistently. The memory caching means that information is stored in a virtual memory of an application, and when the process corresponding to the application is closed, the information in the memory caching is released. Therefore, when the application start instruction is received, because the application is restarted, the corresponding memory cache does not store the IP cache information, and the stored IP cache information can be obtained from the disk cache and stored in the memory cache.
Illustratively, as shown in fig. 3, the memory cache 302 obtains the corresponding IP cache information at the disk cache 303.
Optionally, the domain name included in the IP cache information is a domain name that has been resolved by the history request, and correspondingly, the corresponding relationship between the included domain name and the IP address is a corresponding relationship that is established based on the domain name that has been resolved by the history request and the IP address obtained by the resolution.
Step 202, in response to the network resource obtaining request, querying a target IP address in the IP cache information of the memory cache based on the target domain name.
Optionally, the network resource obtaining request carries a target domain name, and when the network resource obtaining request is received, the target domain name in the network resource obtaining request can be obtained correspondingly. The target domain name may be a domain name input by a user, or a corresponding domain name determined by the application according to a link clicked by the user and based on the clicked link.
Since the corresponding relationship between the domain name and the IP address is stored in the memory cache, when a network resource acquisition request is received, the network resource acquisition request can be searched in the IP cache information of the memory cache to determine whether a target IP address corresponding to the target domain name exists.
As shown in fig. 3, the application 301 queries the memory cache for a target IP address corresponding to a target domain name.
And step 203, responding to the inquiry of the target IP address, and acquiring the network resource based on the target IP address.
When the target IP address is obtained by inquiring in the memory cache, the application can directly establish network connection based on the target IP address so as to obtain network resources, and a request for obtaining the target IP address does not need to be sent to the DNS server, so that the obtaining efficiency of the target IP address can be improved.
And step 204, responding to the target IP address which is not inquired, acquiring the target IP address from the DNS server based on the target domain name, and acquiring the network resource based on the target IP address.
In a possible implementation manner, the memory cache does not store the target IP address corresponding to the target domain name, and therefore, when the target IP address is not queried in the memory cache, a domain name resolution request is required to be sent to the DNS server, where the domain name resolution request includes the target domain name. Different domain names and corresponding IP addresses are stored in the DNS, and when a domain name resolution request containing a target domain name is received, the DNS searches the target IP address corresponding to the target domain name in a cache of the server and returns the target IP address to the application. And if the target IP address is not inquired, further analyzing according to the target domain name.
Optionally, the DNS server may include a Local DNS server, an Http DNS server, and the like, that is, an analysis request may be sent to different DNS servers to obtain a plurality of target IP addresses, and one of the plurality of target IP addresses is selected as the target IP address. Alternatively, a target DNS server is selected among different DNS servers, and a target IP address is acquired at the target DNS server.
It can be seen that, in this embodiment, even if the IP cache information in the memory cache is released, the IP cache information may be obtained again at the disk cache, and only when the target IP address corresponding to the target domain name is not stored in the IP cache information, the DNS server is requested to obtain the target IP address, which is different from that in the related art, after the IP cache information in the memory cache is released, only the DNS server is requested to obtain the target IP address.
To sum up, in the embodiment of the present application, the IP cache information is stored in the disk cache, when the application is started, the IP cache information in the disk cache is stored in the memory cache, and the IP address corresponding to the domain name can be obtained from the IP cache information in the memory cache when the network resource obtaining request is received. Because the disk cache can persistently store the IP cache information, when the IP cache information does not exist in the applied memory cache, the IP cache information can be acquired in the disk cache, so that the domain name can be quickly resolved without being resolved by the DNS server again, and the acquisition efficiency of the IP address is improved.
In a possible application scenario, when the network connection state is switched, the IP address corresponding to the domain name may change, and in order to quickly resolve the target domain name to obtain the corresponding IP address after the network connection state changes, in this embodiment, the network connection information is stored in the IP cache information. In addition, since the same domain name may correspond to different IP addresses, that is, the same domain name in the IP cache information may correspond to different IP addresses, in this embodiment, a priority is set for the IP address, and then the target IP address is determined according to the priority. The following description will be made with reference to exemplary embodiments.
Step 401, in response to the application start instruction, storing the IP cache information in the disk cache to a memory cache, where the IP cache information includes a correspondence between the network connection information, the domain name, and the IP address.
Optionally, the network connection information includes a network identifier of a network to which the current device is connected. For example, when the computer device connects to a Wireless network (WIFI), the network connection information includes a Service Set Identifier (SSID), which is a unique Identifier of the WIFI.
The same domain name may correspond to different IP addresses under different network connection states. For example, the same domain name corresponds to different IP addresses under the 4G network and the WIFI network. When the network connection information changes, if the current IP address is continuously used, the corresponding network resource cannot be acquired, the domain name needs to be resolved again to acquire the corresponding IP address in the current network connection state, and in the process, if the domain name is acquired again at the DNS server, the domain name resolution efficiency is slow, and the acquisition of the network resource is affected. Therefore, in one possible implementation, in storing the IP cache information, in addition to storing the correspondence between the domain name and the IP address, the network connection information is stored together with the correspondence between the domain name and the IP address, so as to facilitate obtaining the IP address corresponding to the domain name in different network states.
Illustratively, the correspondence between the network connection information, the domain name and the IP address may be as shown in table 1:
TABLE 1
Network connection information Domain name IP address
Network a www.aaa.com 192.168.1.101
Network b www.bbb.com 192.168.1.102
Network c www.ccc.com 192.168.1.103
Step 402, in response to the network resource obtaining request, obtaining current network connection information.
After receiving the network resource acquisition request, the device acquires current network connection information, that is, acquires a network identifier of a currently connected network.
Step 403, based on the current network connection information and the target domain name, querying a target IP address in the IP cache information cached in the memory, where the target IP address corresponds to the target domain name and the current network connection information.
In a possible implementation manner, after the computer device obtains the current network connection information and the target domain name in the network resource obtaining request, the computer device queries a corresponding target IP address in the IP cache information cached in the memory according to the network connection information and the target domain name, and ensures that the target IP address is the IP address of the target domain name corresponding to the current network connection information.
In connection with the example in table 1, when the current network connection information is determined to be network a and the target domain name is www.aaa.com, the corresponding target IP address may be determined to be 192.168.1.101.
In response to querying the at least two target IP addresses, a priority of each target IP address is determined, step 404.
For example, the Local DNS server and the Http DNS server may resolve the same domain name to obtain different IP addresses. Therefore, in a possible implementation manner, the IP cache information may cache a corresponding relationship between the same domain name and different IP addresses, and when a target IP address is queried in the IP cache information, at least two target IP addresses corresponding to the target domain name may be queried, and at this time, one target IP address needs to be selected from the at least two target IP addresses for network connection.
Alternatively, the priority may be determined based on at least one of historical connection parameters, update time, and address source of each destination IP address.
Optionally, when the correspondence between the network connection information, the domain name, and the IP address is stored in the IP cache information, the address source of the IP address may be further stored, that is, the IP cache information includes the correspondence between the network connection information, the address source, the domain name, and the IP address, and then the priority of each target IP address may be determined according to the address source information in the IP cache information.
Illustratively, the correspondence between the network connection information, the address source, the domain name and the IP address can be shown in table 2:
TABLE 2
Address source Network connection information Domain name IP address
Http DNS server Network a www.aaa.com 192.168.1.101
Local DNS server Network a www.aaa.com 192.168.1.102
Local DNS server Network c www.ccc.com 192.168.1.103
When the network connection information is network a and the domain name is www.aaa.com, the IP address from the Http DNS server is different from the IP address from the Local DNS server.
Alternatively, different IP address sources may be prioritized empirically in advance, e.g., Http DNS server has a higher priority than Local DNS server.
Optionally, the priority of the address source and the priority of the target IP address are in a positive correlation. As shown in fig. 5, IP _ a and IP _ B corresponding to the target domain name are stored in the IP cache information, where IP _ a is obtained by analyzing by the Http DNS server and corresponds to the source a; IP _ B is resolved by the Local DNS server and corresponds to source B, wherein, the priority of source A is higher than that of source B, and the priority of IP _ A is higher than that of IP _ B.
For the target IP addresses of the same source, the priority of each target IP address can be further determined according to the updating time of the IP addresses. Wherein, the time interval between the update time and the current time is in negative correlation with the priority of the target IP address.
Illustratively, as shown in FIG. 5, IP _ A _1 is the IP address of the target IP address from the A source after the first update, IP _ B _1 is the IP address of the target IP address from the B source after the first update, IP _ A _2 is the IP address of the target IP address from the A source after the second update, the priority of IP _ A _2 is higher than that of IP _ A _1, and the priority of IP _ A _1 is higher than that of IP _ B _ 1.
The IP addresses corresponding to the target domain names in the IP cache information can be subjected to priority ranking according to the address sources and the updating time of the target IP addresses, the priority of the target IP addresses is determined to ensure that the selected target IP addresses are effective and low-delay IP addresses, and then network connection can be established quickly based on the target IP addresses. Thus, in one possible implementation, the priority of each target IP address may also be determined according to the historical connection parameters of each target IP address.
Wherein determining the priority of each target IP address based on the historical connection parameters may comprise the steps of:
step one, determining an address score of each target IP address based on historical connection parameters of each target IP address, wherein the historical connection parameters comprise at least one of historical connection success rate, historical connection delay and historical connection duration.
Optionally, the address score of each target IP address may be determined according to at least one of historical connection power, historical connection latency, and historical connection duration. The historical connection power and the address score are in positive correlation, the historical connection power can be determined according to the proportion of the historical connection success times to the historical connection total times, and when the historical connection power is higher, the address score is correspondingly higher.
When the address score is determined according to the historical connection delay, the historical connection delay and the address score have a negative correlation relationship, wherein the historical connection delay may be an average delay of the historical connection of the target IP address or a delay of the latest connection, which is not limited in the present application. When the historical connection time delay is longer, the speed of acquiring the network resource based on the target IP address is slower, and correspondingly, the address score of the target IP address is lower.
When the address score of the target IP address is determined according to the historical connection time, the historical connection time and the address score of the target IP address are in a positive correlation relationship, wherein the historical connection time can be the average historical connection time or the highest time in the single connection time, and when the historical connection time is longer, the network connection established based on the target IP address is stable, and correspondingly, the address score corresponding to the target IP address is higher.
In one possible implementation, the address score of each target IP address may be determined based on any one of the historical connection power, the historical connection delay, and the historical connection duration, or may be determined based on multiple address scores that collectively determine the target IP address. When determining the address score of the target IP address based on various parameters, different weights may be set for different historical connection parameters, and the address score obtained by weighted averaging is performed. For example, the address score is determined according to the historical connection power, the historical connection delay and the historical connection duration, and weights can be set for the historical connection power, the historical connection delay and the historical connection duration. The computer equipment can store a first corresponding relation of historical connection power and address scores, a second corresponding relation of historical connection delay and address scores and a third corresponding relation of historical connection duration and address scores, after the historical connection success rate, the historical connection delay and the historical connection duration of the target IP address are obtained, corresponding first address scores, second address scores and third address scores can be determined according to the first corresponding relation, the second corresponding relation and the third corresponding relation respectively, and then the first address scores, the second address scores and the third address scores are weighted and averaged to obtain final address scores.
And secondly, determining the priority of each target IP address based on the address score, wherein the priority and the address score are in positive correlation.
Optionally, the address score is in positive correlation with the priority of each target IP address. When the address score is higher, it indicates that the success rate and stability of network connection based on the target IP address are higher, and the priority of the corresponding target IP address is higher.
Step 405, network resources are obtained based on the target IP address of the highest priority.
In a possible implementation manner, after the priority of each target IP address is determined, the target IP address with the highest priority is selected, network connection is established, and network resources are acquired. Optionally, for target IP addresses of different sources, priority ordering may be performed according to the address sources, and then priority ordering may be performed on target IP addresses of the same address source according to the update time. Since the address score may represent historical connection quality based on the target IP address, if there is a target IP address whose address score is higher than a score threshold value, indicating that the historical connection is stable based on the target IP address, the target IP address may be identified as the highest-priority target IP address, and if there are a plurality of target IP addresses whose address score is higher than the score threshold value, the highest-score IP address among the respective target IP addresses may be determined as the highest-priority target IP address.
Illustratively, as shown in fig. 5, IP _ a _3 is the IP address of the target IP address from the a source after the third update, the priority of IP _ a _3 is higher than that of IP _ a _2, and the priority of IP _ a _2 is higher than that of IP _ a _1, but when the address score of IP _ a _1 is the highest and is higher than the score threshold, IP _ a _1 is set as the highest priority, i.e., the priorities are IP _ a _1 > IP _ a _3 > IP _ a _2 > IP _ B _ 1.
And step 406, in response to that the target IP address is not queried, acquiring the target IP address from the DNS server based on the target domain name, and acquiring the network resource based on the target IP address.
In the present step, reference may be made to step 204, which is not described in detail in this embodiment.
Step 407, the IP cache information in the memory cache is updated based on the target domain name and the target IP address.
Because the target IP address corresponding to the target domain name is not queried in the IP cache information cached in the memory, after the target IP address corresponding to the target domain name is obtained at the DNS server, the correspondence between the target domain name and the target IP address is stored in the IP cache information cached in the memory.
Optionally, when the IP cache information is updated, the current network connection information is correspondingly obtained, and the corresponding relationship between the current network connection information, the target domain name and the target IP address is stored in the IP cache information of the memory cache, so that the target IP address corresponding to the target domain name can be quickly obtained in the memory cache in the same network connection state in the subsequent process.
And the address source of the target IP address can be stored into the IP cache information of the memory cache together, so that the priority of the target IP address can be determined based on the address source in the following.
And step 408, updating the disk cache based on the updated IP cache information.
Because the IP cache information in the memory cache is released after the application process is closed, that is, the IP cache information cannot be stored for a long time, in updating the IP cache information in the memory cache, the IP cache information in the disk cache needs to be updated synchronously, that is, the disk cache is updated based on the updated IP cache information, so that the problem of IP cache information loss caused by the release of the memory cache is avoided, and the persistent storage of the IP cache information can be realized.
In this embodiment, the IP cache information stores a corresponding relationship between the network connection information, the domain name, and the IP address, and when a network resource acquisition request is received, the IP address corresponding to the current network connection information can be quickly acquired based on the stored IP cache information, so that the acquisition of the network resource is prevented from being influenced by invalid acquired IP addresses.
In addition, in this embodiment, when at least two target IP addresses are obtained by querying in the IP cache information, the priority of each target IP address can be determined according to the address source, the update time, and the historical connection parameter of each target IP address, so as to obtain the network resource based on the target IP address with the highest priority, ensure that the target IP address with higher quality is obtained, and contribute to improving the obtaining efficiency of the network resource.
Since each IP address has a Time To Live (TTL) limit, when the stored IP address exceeds the TTL Time of the IP address, the IP address will be invalid, i.e., a network connection cannot be established through the IP address. Therefore, in a possible implementation manner, in order to ensure that the IP address in the IP cache information is a valid IP address, a domain name resolution request needs to be periodically initiated to the DNS server, so as to update the IP address in the IP cache information, thereby avoiding the problem of network connection failure caused by IP address failure. Wherein, updating the IP cache information at regular time can comprise the following steps:
step one, sending domain name resolution requests to at least two DNS servers based on domain names in the IP cache information, wherein different DNS servers correspond to different address sources.
In a possible implementation manner, the application sends the domain name resolution request to at least two DNS servers at regular time, for example, sends the domain name resolution request to an Http DNS server and a Local DNS server, and further updates the IP cache information in the memory cache.
Optionally, when sending the domain name resolution request, the domain name resolution requests corresponding to all domain names in the current IP cache information are sent, so as to obtain the IP addresses corresponding to all domain names.
Optionally, in order to avoid an influence on network connection or transmission of network resources, when the application sends the domain name resolution request, the application asynchronously sends the domain name resolution request to the DNS server.
And step two, updating the updating time and the address source of the IP address corresponding to each domain name in the IP cache information based on the domain name resolution results fed back by at least two DNS servers.
And when domain name resolution results fed back by at least two DNS servers are received, updating the IP cache information in the memory cache according to the corresponding relation between each domain name and the IP address obtained by re-resolution. Because the IP addresses may come from different DNS servers, when updating the IP cache information, the corresponding relation between the IP addresses and the address sources is stored in the IP cache information, and the updating time corresponding to each IP address is stored in the IP cache information, so that when selecting the target IP address subsequently, the priority of the target IP address is determined according to the updating time corresponding to each IP address in the stored IP cache information and the address source.
Optionally, after the IP cache information in the memory cache is updated, the updated IP cache information needs to be cached in the disk cache, so as to implement persistent storage.
That is, in this embodiment, by updating the IP cache information in the memory cache and the disk cache at regular time, it is avoided that the IP cache information contains an invalid IP address, which affects the acquisition of network resources.
In a possible scenario, according to the IP cache information or the target IP address acquired at the DNS server, the IP address is not an effective or lower-latency IP address, and therefore, after the network connection is established between the target IP address and the target server, the target server detects the target IP address, determines whether there is a better IP address, and ensures that the application acquires the network resource based on the effective and lower-latency IP address. Therefore, in a possible implementation, after acquiring the network resource based on the target IP address, the method further includes the following steps:
step one, receiving an optimized IP address sent by a target server, wherein the target server is a server corresponding to the target IP address, and the optimized IP address is superior to the target IP address.
In one possible implementation, when the application establishes a network connection with the target server through the target IP address, the target server detects the target IP address, and detects whether a preferred IP address better than the target IP address exists, where the preferred IP address and the target IP address correspond to the same domain name.
Optionally, a priority list of the IP address corresponding to the target domain name is stored in the target server, and the IP address priority and the quality of the network connection established based on the IP address are in a positive correlation. When the target server receives the target IP address, whether a preferred IP address with the priority higher than that of the target IP address exists or not is judged according to the stored priority list, and if yes, the preferred IP address is sent to the application.
Optionally, when the target server sends the preferred IP address to the application, the target server sends the preferred IP address based on the established network connection, without increasing additional communication cost.
And step two, acquiring network resources based on the preferred IP address.
After receiving the preferred IP address sent by the target server, the application establishes network connection again based on the preferred IP address to acquire network resources, wherein the network connection quality established based on the preferred IP address is superior to the network connection quality established based on the target IP address, and the time delay is relatively low.
And step three, updating the IP cache information in the memory cache based on the preferred IP address.
Because the preferred IP address is better than the target IP address, in a possible implementation, after receiving the preferred IP address, the application updates the IP cache information in the memory cache based on the correspondence between the preferred IP address and the target domain name, and correspondingly, synchronously updates the current network connection information corresponding to the IP address and the source of the IP address in the IP cache information corresponding to the memory cache.
Optionally, after the IP cache information in the memory cache is updated, the IP cache information in the disk cache is updated based on the updated IP cache information, so as to ensure persistent storage of the IP cache information.
In this embodiment, whether an optimal IP address better than the target IP address exists is determined by detecting the target IP address by the target server, and if so, the application establishes the network connection based on the optimal IP address, so that the quality of establishing the network connection is ensured, and the acquisition efficiency of the network resource is improved.
In connection with the above embodiments, in an illustrative example, the domain name resolution process is as shown in fig. 6:
step 601, the application is started.
Step 602, reading the IP cache information in the disk cache.
Step 603, the disk cache returns the IP cache information to the memory cache.
Step 604, a target IP address is obtained in the memory cache based on the target domain name in the network resource obtaining request.
Step 605, determining whether the target IP address is stored in the memory cache, if yes, performing step 606, and if no, performing step 607.
Step 606, return the destination IP address to the application.
At step 607, the destination IP address is obtained at the DNS server.
At step 608, the DNS server returns the destination IP address.
After the DNS server returns the target IP address, the application updates the IP cache information in the memory cache based on the target IP address.
And step 609, updating the IP cache information in the disk cache.
At step 610, the network connection information is changed.
Step 611, obtain the target IP address at the memory cache based on the current network connection information and the target domain name.
Step 612, determining whether the target IP address corresponding to the network connection information is stored in the memory cache, if yes, performing step 613, and if no, performing step 614.
Step 613 returns the destination IP address to the application.
At step 614, the destination IP address is obtained at the DNS server.
At step 615, the DNS server returns the destination IP address.
Optionally, after receiving the target IP address, the application updates the IP cache information in the memory cache.
Step 616, updating the IP cache information in the disk cache.
The application obtains network resources at the target server based on the target IP address, step 617.
In step 618, the target server detects whether there is a preferred IP address, if so, step 619 is executed, and if not, the process ends.
The target server returns the preferred IP address to the application, step 619.
At step 620, the application obtains network resources at the target server based on the preferred IP address.
Step 621, update the IP cache information in the memory cache.
Step 622, the IP cache information in the disk cache is updated.
Optionally, the IP cache information in the memory cache and the disk cache is updated based on the preferred IP address.
Fig. 7 is a block diagram of a domain name resolution apparatus according to an exemplary embodiment of the present application, where the apparatus includes:
a storage module 701, configured to respond to an application start instruction, store IP cache information in a disk cache to a memory cache, where the IP cache information includes a correspondence between a domain name and an IP address;
a query module 702, configured to respond to a network resource acquisition request, query a target IP address in the IP cache information cached in the memory based on a target domain name;
a first obtaining module 703, configured to, in response to querying the target IP address, obtain a network resource based on the target IP address;
a second obtaining module 704, configured to, in response to that the target IP address is not queried, obtain the target IP address from a DNS server based on the target domain name, and obtain a network resource based on the target IP address.
Optionally, the IP cache information includes a correspondence between network connection information, a domain name, and an IP address.
Optionally, the query module 702 includes:
a first obtaining unit, configured to obtain current network connection information in response to the network resource obtaining request;
and the query unit is used for querying the target IP address in the IP cache information cached in the memory based on the current network connection information and the target domain name, wherein the target IP address corresponds to the target domain name and the current network connection information.
Optionally, the first obtaining module 703 includes:
the determining unit is used for responding to at least two inquired target IP addresses and determining the priority of each target IP address;
and the second acquisition unit is used for acquiring the network resources based on the target IP address with the highest priority.
Optionally, the determining unit is further configured to:
determining the priority based on at least one of historical connection parameters, update time, and address source for each of the target IP addresses.
Optionally, the determining unit is further configured to:
determining an address score of each target IP address based on the historical connection parameters of each target IP address, wherein the historical connection parameters comprise at least one of historical connection success rate, historical connection delay and historical connection duration;
determining the priority of each target IP address based on the address score, wherein the priority is in positive correlation with the address score.
Optionally, the priority is determined based on at least one of the update time and the address source.
Optionally, the apparatus further comprises:
a sending module, configured to send domain name resolution requests to at least two DNS servers based on domain names in the IP cache information, where different DNS servers correspond to different address sources;
and the first updating module is used for updating the updating time and the address source of the IP address corresponding to each domain name in the IP cache information based on the domain name resolution results fed back by at least two DNS servers.
Optionally, the apparatus further comprises:
the receiving module is used for receiving an optimal IP address sent by a target server, wherein the target server is a server corresponding to the target IP address, and the optimal IP address is superior to the target IP address;
a third obtaining module, configured to obtain a network resource based on the preferred IP address;
and the second updating module is used for updating the IP cache information in the memory cache based on the preferred IP address.
Optionally, the apparatus further comprises:
a third updating module, configured to update the IP cache information in the memory cache based on the target domain name and the target IP address;
and the fourth updating module is used for updating the disk cache based on the updated IP cache information.
To sum up, in the embodiment of the present application, the IP cache information is stored in the disk cache, when the application is started, the IP cache information in the disk cache is stored in the memory cache, and the IP address corresponding to the domain name can be obtained from the IP cache information in the memory cache when the network resource obtaining request is received. Because the disk cache can persistently store the IP cache information, when the IP cache information does not exist in the applied memory cache, the IP cache information can be acquired in the disk cache, so that the domain name can be quickly resolved without being resolved by the DNS server again, and the acquisition efficiency of the IP address is improved.
It should be noted that: the device provided in the above embodiment is only illustrated by dividing the functional modules, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and details of the implementation process are referred to as method embodiments, which are not described herein again.
An embodiment of the present application provides a computer device, which includes a processor and a memory, where at least one instruction, at least one program, a set of codes, or a set of instructions is stored in the memory, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the domain name resolution method according to the above aspect.
Embodiments of the present application provide a computer-readable storage medium, in which at least one instruction, at least one program, a code set, or a set of instructions is stored, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by a processor to implement the domain name resolution method according to the above aspect.
Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the domain name resolution method provided in the various alternative implementations of the above aspects.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (11)

1. A domain name resolution method, the method comprising:
responding to an application starting instruction, storing IP cache information in a disk cache to a memory cache, wherein the IP cache information comprises a corresponding relation between a domain name and an IP address;
responding to a network resource acquisition request, and inquiring a target IP address in the IP cache information cached in the memory based on a target domain name;
responding to the target IP address, and acquiring network resources based on the target IP address;
and responding to the condition that the target IP address is not inquired, acquiring the target IP address from a DNS (domain name server) based on the target domain name, and acquiring network resources based on the target IP address.
2. The method according to claim 1, wherein the IP cache information includes a correspondence between network connection information, a domain name, and an IP address;
the querying a target IP address in the IP cache information cached in the memory based on a target domain name in response to a network resource acquisition request includes:
responding to the network resource acquisition request, and acquiring current network connection information;
and inquiring the target IP address in the IP cache information cached in the memory based on the current network connection information and the target domain name, wherein the target IP address corresponds to the target domain name and the current network connection information.
3. The method of claim 2, wherein the obtaining network resources based on the target IP address in response to querying the target IP address comprises:
in response to at least two of the target IP addresses being queried, determining a priority of each of the target IP addresses;
and acquiring network resources based on the target IP address with the highest priority.
4. The method of claim 3, wherein said determining the priority of each of the target IP addresses comprises:
determining the priority based on at least one of historical connection parameters, update time, and address source for each of the target IP addresses.
5. The method of claim 4, wherein determining the priority based on historical connection parameters for each of the target IP addresses comprises:
determining an address score of each target IP address based on the historical connection parameters of each target IP address, wherein the historical connection parameters comprise at least one of historical connection success rate, historical connection delay and historical connection duration;
determining the priority of each target IP address based on the address score, wherein the priority is in positive correlation with the address score.
6. The method of claim 4, wherein the priority is determined based on at least one of the update time and the address source, the method further comprising:
sending domain name resolution requests to at least two DNS servers based on the domain name in the IP cache information, wherein different DNS servers correspond to different address sources;
and updating the updating time and the address source of the IP address corresponding to each domain name in the IP cache information based on the domain name resolution results fed back by at least two DNS servers.
7. The method according to any one of claims 1 to 6, wherein after acquiring the network resource based on the target IP address, the method further comprises:
receiving an optimal IP address sent by a target server, wherein the target server is a server corresponding to the target IP address, and the optimal IP address is superior to the target IP address;
acquiring network resources based on the preferred IP address;
and updating the IP cache information in the memory cache based on the preferred IP address.
8. The method according to any one of claims 1 to 6, wherein after obtaining the target IP address from the DNS server based on the target domain name, the method further comprises:
updating the IP cache information in the memory cache based on the target domain name and the target IP address;
and updating the disk cache based on the updated IP cache information.
9. A domain name resolution apparatus, the apparatus comprising:
the storage module is used for responding to an application starting instruction, and storing IP cache information in the disk cache to a memory cache, wherein the IP cache information comprises a corresponding relation between a domain name and an IP address;
the query module is used for responding to a network resource acquisition request and querying a target IP address in the IP cache information cached in the memory based on a target domain name;
the first acquisition module is used for responding to the inquiry of the target IP address and acquiring network resources based on the target IP address;
and the second acquisition module is used for responding to the condition that the target IP address is not inquired, acquiring the target IP address from the DNS based on the target domain name and acquiring network resources based on the target IP address.
10. A computer device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by the processor to implement a domain name resolution method according to any one of claims 1 to 8.
11. A computer-readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement a domain name resolution method according to any one of claims 1 to 8.
CN202110724967.4A 2021-06-29 2021-06-29 Domain name resolution method, device, equipment and storage medium Active CN113452808B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110724967.4A CN113452808B (en) 2021-06-29 2021-06-29 Domain name resolution method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110724967.4A CN113452808B (en) 2021-06-29 2021-06-29 Domain name resolution method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113452808A true CN113452808A (en) 2021-09-28
CN113452808B CN113452808B (en) 2023-06-23

Family

ID=77813735

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110724967.4A Active CN113452808B (en) 2021-06-29 2021-06-29 Domain name resolution method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113452808B (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114327672A (en) * 2021-12-14 2022-04-12 中国平安财产保险股份有限公司 Data caching time setting method and device, computer equipment and storage medium
CN114448990A (en) * 2021-12-23 2022-05-06 天翼云科技有限公司 Resource scheduling method, device and equipment based on fusion CDN
CN114844866A (en) * 2022-03-29 2022-08-02 武汉斗鱼鱼乐网络科技有限公司 Network request connection method and related equipment
CN114884917A (en) * 2022-04-26 2022-08-09 北京华信傲天网络技术有限公司 Control system and method for address resolution protocol message
CN115102923A (en) * 2022-06-09 2022-09-23 Oppo广东移动通信有限公司 AGPS positioning starting method, device, equipment, medium and program product

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100228853A1 (en) * 2009-03-06 2010-09-09 Phanse Madhavi R Cluster-free techniques for enabling a directory protocol-based domain name system (dns) service for high availability
US20100332680A1 (en) * 2009-06-24 2010-12-30 Broadcom Corporation Fault tolerance approaches for dns server failures
WO2012109852A1 (en) * 2011-07-29 2012-08-23 华为技术有限公司 Node ranking and selection method, device and system
CN102750174A (en) * 2012-06-29 2012-10-24 Tcl集团股份有限公司 Method and device for loading file
CN103051717A (en) * 2012-12-25 2013-04-17 北京小米科技有限责任公司 Method, device and equipment for processing http request
CN103699554A (en) * 2012-09-27 2014-04-02 深圳云富网络科技有限公司 Webpage data calling method and device
US20140173123A1 (en) * 2012-12-14 2014-06-19 Apple Inc. Address family preference in multiple network interface environments
CN106331213A (en) * 2016-08-29 2017-01-11 广东欧珀移动通信有限公司 Domain name system DNS processing method and apparatus
WO2017076327A1 (en) * 2015-11-04 2017-05-11 中兴通讯股份有限公司 Method and apparatus for processing domain name resolution request, and server
CN108228818A (en) * 2017-12-29 2018-06-29 网易（杭州）网络有限公司 Web page resources loading method and device, electronic equipment and storage medium
CN108509501A (en) * 2018-02-28 2018-09-07 努比亚技术有限公司 A kind of inquiry processing method, server and computer readable storage medium
CN109067936A (en) * 2018-09-05 2018-12-21 网宿科技股份有限公司 A kind of method and device of domain name mapping
CN109597568A (en) * 2018-09-18 2019-04-09 天津字节跳动科技有限公司 A kind of date storage method, device, terminal device and storage medium
CN110049145A (en) * 2018-11-23 2019-07-23 阿里巴巴集团控股有限公司 Address acquiring method, device, electronic equipment and computer readable storage medium
US20200220840A1 (en) * 2018-02-28 2020-07-09 Wangsu Science & Technology Co., Ltd. Method, server and system for resolving domain name
CN111541799A (en) * 2020-05-11 2020-08-14 中移（杭州）信息技术有限公司 Domain name resolution method, system, terminal and storage medium
CN111803917A (en) * 2020-06-30 2020-10-23 北京金山云网络技术有限公司 Resource processing method and device
CN112929463A (en) * 2021-01-26 2021-06-08 网宿科技股份有限公司 Traffic proxy method, server and system based on DNS (Domain name System)

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100228853A1 (en) * 2009-03-06 2010-09-09 Phanse Madhavi R Cluster-free techniques for enabling a directory protocol-based domain name system (dns) service for high availability
US20100332680A1 (en) * 2009-06-24 2010-12-30 Broadcom Corporation Fault tolerance approaches for dns server failures
WO2012109852A1 (en) * 2011-07-29 2012-08-23 华为技术有限公司 Node ranking and selection method, device and system
CN102750174A (en) * 2012-06-29 2012-10-24 Tcl集团股份有限公司 Method and device for loading file
CN103699554A (en) * 2012-09-27 2014-04-02 深圳云富网络科技有限公司 Webpage data calling method and device
US20140173123A1 (en) * 2012-12-14 2014-06-19 Apple Inc. Address family preference in multiple network interface environments
CN103051717A (en) * 2012-12-25 2013-04-17 北京小米科技有限责任公司 Method, device and equipment for processing http request
WO2017076327A1 (en) * 2015-11-04 2017-05-11 中兴通讯股份有限公司 Method and apparatus for processing domain name resolution request, and server
CN106331213A (en) * 2016-08-29 2017-01-11 广东欧珀移动通信有限公司 Domain name system DNS processing method and apparatus
CN108228818A (en) * 2017-12-29 2018-06-29 网易（杭州）网络有限公司 Web page resources loading method and device, electronic equipment and storage medium
CN108509501A (en) * 2018-02-28 2018-09-07 努比亚技术有限公司 A kind of inquiry processing method, server and computer readable storage medium
US20200220840A1 (en) * 2018-02-28 2020-07-09 Wangsu Science & Technology Co., Ltd. Method, server and system for resolving domain name
CN109067936A (en) * 2018-09-05 2018-12-21 网宿科技股份有限公司 A kind of method and device of domain name mapping
CN109597568A (en) * 2018-09-18 2019-04-09 天津字节跳动科技有限公司 A kind of date storage method, device, terminal device and storage medium
CN110049145A (en) * 2018-11-23 2019-07-23 阿里巴巴集团控股有限公司 Address acquiring method, device, electronic equipment and computer readable storage medium
CN111541799A (en) * 2020-05-11 2020-08-14 中移（杭州）信息技术有限公司 Domain name resolution method, system, terminal and storage medium
CN111803917A (en) * 2020-06-30 2020-10-23 北京金山云网络技术有限公司 Resource processing method and device
CN112929463A (en) * 2021-01-26 2021-06-08 网宿科技股份有限公司 Traffic proxy method, server and system based on DNS (Domain name System)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
宋海瑞: "面向映射系统的关键技术研究", 中国优秀硕士学位论文全文数据库, no. 11 *
尹洋;刘振军;许鲁;: "一种基于磁盘介质的网络存储系统缓存", 软件学报, no. 10, pages 142 - 155 *
文秀林: "Web代埋服务器的研究与实现", 中国优秀博硕士学位论文全文数据库 (硕士), no. 02 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114327672A (en) * 2021-12-14 2022-04-12 中国平安财产保险股份有限公司 Data caching time setting method and device, computer equipment and storage medium
CN114327672B (en) * 2021-12-14 2024-04-05 中国平安财产保险股份有限公司 Data caching time setting method and device, computer equipment and storage medium
CN114448990A (en) * 2021-12-23 2022-05-06 天翼云科技有限公司 Resource scheduling method, device and equipment based on fusion CDN
CN114448990B (en) * 2021-12-23 2023-06-23 天翼云科技有限公司 Fusion CDN-based resource scheduling method, device and equipment
CN114844866A (en) * 2022-03-29 2022-08-02 武汉斗鱼鱼乐网络科技有限公司 Network request connection method and related equipment
CN114884917A (en) * 2022-04-26 2022-08-09 北京华信傲天网络技术有限公司 Control system and method for address resolution protocol message
CN114884917B (en) * 2022-04-26 2023-07-28 北京华信傲天网络技术有限公司 Control system and method for address resolution protocol message
CN115102923A (en) * 2022-06-09 2022-09-23 Oppo广东移动通信有限公司 AGPS positioning starting method, device, equipment, medium and program product
CN115102923B (en) * 2022-06-09 2024-04-02 Oppo广东移动通信有限公司 AGPS positioning starting method, device, equipment, medium and program product

Also Published As

Publication number Publication date
CN113452808B (en) 2023-06-23

Similar Documents

Publication Publication Date Title
US11451472B2 (en) Request routing based on class
CN113452808B (en) Domain name resolution method, device, equipment and storage medium
US11012892B2 (en) Resource obtaining method, apparatus, and system
US11811657B2 (en) Updating routing information based on client location
US11194719B2 (en) Cache optimization
US10491534B2 (en) Managing resources and entries in tracking information in resource cache components
EP3567881B1 (en) Request routing and updating routing information utilizing client location information
JP2013507694A (en) System and method for increasing data communication speed and efficiency
WO2021042673A1 (en) Dns resolution method, authoritative dns server and dns resolution system
JP2002525749A (en) Internet caching system, method and system configuration
CN107682281B (en) SDN switch and application management method thereof
CN109788075B (en) Private network system, data acquisition method and edge server
CN115004657B (en) Addressing method, addressing system and addressing device
CN113254203B (en) Service degradation processing method and device
CN114338720A (en) Distributed file storage and transmission method, system and storage medium
CN116248632A (en) File acquisition method, device, system and equipment, medium and product
CN114501080A (en) Service content updating method and device, storage medium and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant