CN114338630A

CN114338630A - Domain name access method, device, electronic equipment, storage medium and program product

Info

Publication number: CN114338630A
Application number: CN202111518170.5A
Authority: CN
Inventors: 贾守强; 田书才
Original assignee: Haier Smart Home Co Ltd; Haier Uplus Intelligent Technology Beijing Co Ltd
Current assignee: Haier Smart Home Co Ltd; Haier Uplus Intelligent Technology Beijing Co Ltd
Priority date: 2021-12-13
Filing date: 2021-12-13
Publication date: 2022-04-12
Anticipated expiration: 2041-12-13

Abstract

The present application belongs to the field of communications technologies, and in particular, relates to a domain name access method, apparatus, electronic device, storage medium, and program product. The method comprises the following steps: reading an HTTPDNS cache file from a local disk, and storing the HTTPDNS cache file into a memory cache; an access request carrying a first domain name of a first server is received. If the HTTPDNS cache file does not have the first domain name and the IP address or the IP is unavailable, the first domain name is analyzed through an HTTPDNS server and a local DNS server; if the local DNS server is successfully analyzed and the HTTPDNS server is failed to analyze, an IP address obtained by analyzing the local DNS server is used for establishing connection with the server; and after the connection between the server and the IP address is successfully established by using the IP address, storing the mapping relation between the first domain name and the IP address into an HTTPDNS cache file in a memory cache and a local disk. The method and the device improve the stability and efficiency of domain name access.

Description

Domain name access method, device, electronic equipment, storage medium and program product

Technical Field

The embodiment of the invention belongs to the technical field of communication, and particularly relates to a domain name access method, a domain name access device, electronic equipment, a storage medium and a program product.

Background

When an electronic device accesses a website (e.g., accesses website a), the electronic device may typically receive a domain name of the website a input by a user. Then, the electronic device may connect, via the Internet, to a server capable of providing an Internet Protocol (IP) address corresponding to the domain name, to acquire an IP address corresponding to the domain name of the website a from the server. Using the IP address, the electronic device may connect with a server corresponding to website a to enable access to website a.

The server capable of providing the IP address corresponding to the Domain Name may be a server that performs Domain Name System (DNS) service (HTTP DNS) according to a hypertext Transfer Protocol (HTTP). However, when the http dns server fails to perform domain name resolution due to a failure or the like, the electronic device cannot acquire an IP address corresponding to the domain name through the http dns server.

Therefore, the existing domain name access method has the problems of poor stability and low efficiency.

Disclosure of Invention

In order to solve the above problems in the prior art, the present application provides a domain name access method, apparatus, electronic device, storage medium, and program product.

In a first aspect, the present application provides a domain name access method, which is applied to an electronic device, and includes:

reading an HTTPDNS cache file from a local disk of the electronic equipment, and storing the HTTPDNS cache file into a memory cache;

receiving an access request aiming at a first server, wherein the access request is triggered by a user and carries a first domain name of the first server;

if the first mapping relation between the first domain name and the IP address does not exist in the HTTPDNS cache file, or the first mapping relation is unavailable, the first domain name is analyzed through an HTTPDNS server and a local DNS server;

if the local DNS server is successfully analyzed and the HTTPDNS server is failed to analyze, using the local DNS server to analyze the IP address obtained by the first domain name, and establishing connection with the first server;

and after the local DNS server is used for analyzing the IP address obtained by the first domain name and establishing a connection with the first server successfully, storing the mapping relation between the first domain name and the IP address into a memory cache of the electronic equipment and an HTTPDNS cache file in a local disk.

Optionally, before the storing the mapping relationship between the first domain name and the IP address in a memory cache of the electronic device and an http dns cache file in a local disk, the method further includes:

acquiring the survival time of the IP address;

determining that the lifetime of the IP address has not timed out.

Optionally, the method further includes:

and if the HTTPDNS server is successfully analyzed, the HTTPDNS server is used for analyzing the IP address obtained by the first domain name, establishing connection with the first server, and storing the mapping relation between the first domain name and the IP address to a memory cache of the electronic equipment and an HTTPDNS cache file in a local disk.

Optionally, the http dns cache file further includes: a lifetime of each IP address, the method further comprising:

determining a target updating period according to the survival time of each IP address; the target updating period is less than or equal to any one of the survival times of the IP addresses;

in each target updating period, analyzing each domain name through an HTTPDNS server and a local DNS server to obtain an IP address corresponding to each updated domain name and the survival time of the IP address;

for any domain name, if the updated IP address corresponding to the domain name is different from the pre-updated IP address corresponding to the domain name, and/or the lifetime of the updated IP address corresponding to the domain name is different from the lifetime of the pre-updated IP address corresponding to the domain name, replacing the pre-updated IP address and the lifetime of the IP address corresponding to the domain name in the HTTPDNS cache file stored in the local disk and the memory cache with the updated IP address and lifetime of the IP address corresponding to the domain name.

Optionally, if the updated IP address and the lifetime of the IP address are obtained by resolution based on the local DNS server, before replacing the updated IP address and the lifetime of the IP address corresponding to the domain name in the HTTPDNS cache file stored in the local disk and the memory cache by using the updated IP address and the lifetime of the IP address corresponding to the domain name, the method further includes:

and determining that the server corresponding to the domain name is successfully connected by using the updated IP address.

Optionally, the resolving the first domain name through the http dns server includes:

if the HTTPDNS server is accessed through a second domain name, inquiring whether a second mapping relation between the second domain name and a corresponding IP address is stored in the HTTPDNS cache file;

if the second mapping relation is stored in the HTTPDNS cache file and the stored second mapping relation is available, acquiring an IP address corresponding to the second domain name from the HTTPDNS cache file, interacting with the HTTPDNS server according to the IP address corresponding to the second domain name, and analyzing the first domain name;

or if the HTTPDNS cache file does not have the second mapping relationship, or the stored second mapping relationship is unavailable, resolving the second domain name through the local DNS server to obtain an IP address corresponding to the second domain name;

and interacting with the HTTPDNS server according to the IP address corresponding to the second domain name, and analyzing the first domain name.

Optionally, the method further includes:

and initializing the HTTPDNS cache file in the memory cache.

In a second aspect, the present application provides a domain name access apparatus, the apparatus comprising:

the reading module is used for reading the HTTPDNS cache file from the local disk of the electronic equipment and storing the HTTPDNS cache file into the memory cache;

the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an access request which is triggered by a user and aims at a first server, and the access request carries a first domain name of the first server;

the processing module is used for resolving the first domain name through an HTTPDNS server and a local DNS server when the first mapping relation between the first domain name and the IP address does not exist in the HTTPDNS cache file or the first mapping relation is unavailable; when the local DNS server is successfully analyzed and the HTTPDNS server is failed to analyze, using the local DNS server to analyze the IP address obtained by the first domain name, and establishing connection with the first server;

and the storage module is used for storing the mapping relation between the first domain name and the IP address to a memory cache of the electronic equipment and an HTTPDNS cache file in a local disk after the IP address obtained by analyzing the first domain name by using the local DNS server is successfully connected with the first server.

In a third aspect, the present application provides an electronic device, comprising: at least one processor, a memory;

the memory stores computer-executable instructions;

the at least one processor executing the computer-executable instructions stored by the memory causes the electronic device to perform the method of any of the first aspects.

In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon computer-executable instructions that, when executed by a processor, implement the method of any one of the first aspect.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of any one of the first aspects.

According to the domain name access method, the domain name access device, the electronic equipment, the storage medium and the program product, the electronic equipment can read the HTTPDNS cache file from the local disk of the electronic equipment and store the HTTPDNS cache file into the memory cache, so that the electronic equipment can read the HTTPDNS cache file from the memory cache, and the subsequent domain name access efficiency of the electronic equipment based on the HTTPDNS cache file is improved. When the resolution of the HTTPDNS server fails and the resolution of the local DNS server succeeds, the electronic equipment establishes connection with the first server by using the IP address obtained by resolving the first domain name by using the local DNS server, so that the condition that the electronic equipment cannot access the domain name due to faults of the HTTPDNS server and the like is avoided, and the stability and the efficiency of the electronic equipment for accessing the domain name are further improved. After the connection between the IP address obtained by analyzing the first domain name by using the local DNS server and the first server is successfully established, the mapping relation between the first domain name and the IP address is stored into a memory cache of the electronic equipment and an HTTPDNS cache file in a local disk, so that the accuracy and the safety of the connection between the IP address and the first server in the subsequent use are improved.

Drawings

In order to more clearly illustrate the technical solutions in the present application or the prior art, the following briefly introduces the drawings needed to be used in the description of the embodiments or the prior art, and obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive labor.

Fig. 1 is a schematic view of a scenario in which an electronic device performs domain name access;

fig. 2 is a schematic flowchart of a domain name access method provided in the present application;

fig. 3 is a schematic flow chart of another domain name access method provided in the present application;

fig. 4 is a schematic structural diagram of a domain name access apparatus provided in the present application;

fig. 5 is a schematic structural diagram of an electronic device provided in the present application.

Detailed Description

First, it should be understood by those skilled in the art that these embodiments are merely for explaining the technical principles of the present invention, and are not intended to limit the scope of the present invention. And can be adjusted as needed by those skilled in the art to suit particular applications.

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The following first explains the noun concept related to the present application:

domain name hijacking: the electronic device initiates request information for requesting to acquire an IP address corresponding to domain name 1, whereas the received IP address is an IP address corresponding to domain name 2. Using the IP address corresponding to domain name 2, the electronic device cannot connect to the server corresponding to domain name 1. The above situation may be referred to as domain name hijacking.

Survival time: time-to-live (TTL) is used to indicate the time an IP address can be used in the network, after which it can be discarded.

Taking an electronic device as a mobile phone or a tablet computer as an example, fig. 1 is a scene schematic diagram of domain name access performed by the electronic device. As shown in fig. 1, the electronic device may receive a user input of a domain name a ("www.xxx.com" as shown in fig. 1) of a server corresponding to website a. Then, in response to the operation of clicking the "search" control by the user, the electronic device may connect with the local DNS server through network communication to send a request message for requesting to acquire the IP address corresponding to the domain name a to the local DNS server.

Then, the electronic device may receive an IP address corresponding to the domain name a from the local DNS server through the network communication. By using the IP address, the electronic device may be connected to the server corresponding to the website a, so that the electronic device may access the server, display a display interface of the website a corresponding to the domain name a, and further enable the user to browse the website a.

The local DNS server may be a server corresponding to a DNS service provided by an operator. The communication method of the network communication may be, for example, a mobile communication method, a Wi-Fi communication method, or a communication method such as a wired communication method.

In addition, it should be understood that fig. 1 is only an exemplary illustration of a domain name access scenario, which is taken as an example of an electronic device, such as a mobile phone or a tablet computer, and the type of the electronic device is not limited in the present application. Optionally, the electronic device may be an electronic device such as a computer.

In addition, some embodiments also provide that domain name resolution is performed by an http DNS server with a higher security level than the local DNS server, so as to reduce the problem of domain name hijacking.

When performing domain name resolution through the http dns server, the http dns server also needs to communicate with the electronic device through a network.

Therefore, when the network quality of the http dns server is poor or the http dns server fails, the electronic device may perform domain name access based on the http dns server less efficiently and may not perform domain name access based on the http dns server. Therefore, the existing domain name access method has the problems of poor stability and low efficiency.

In view of the above problems of the existing domain name access method, the present application provides a method for acquiring an IP address corresponding to a domain name based on a local DNS server and an HTPPDNS server. When the domain name resolution of the HTPPDNS server fails, the domain name resolution is carried out through the local DNS server, and after the IP address obtained by carrying out the domain name resolution by using the local DNS server is determined to be successfully connected with the server corresponding to the domain name, the IP address is stored in the electronic equipment, so that the accuracy of the electronic equipment for obtaining the IP address corresponding to the domain name is improved, the stability and the efficiency of the electronic equipment for carrying out the domain name access are improved, and further the user experience is improved. The execution subject of the method is, for example, the electronic device.

The technical solution of the present application will be first described in detail with reference to specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.

Fig. 2 is a schematic flowchart of a domain name access method provided in the present application. As shown in fig. 2, the method comprises the steps of:

s101, reading an HTTPDNS cache file from a local disk of the electronic equipment, and storing the HTTPDNS cache file into a memory cache.

Optionally, the electronic device may read the http dns cache file from the local disk of the electronic device according to a preset storage path indicating a storage location of the http dns cache file in the local disk of the electronic device, for example. The preset storage path may be predetermined, for example, when the HTTPDNS cache file is created by the electronic device.

Optionally, the electronic device may store the http dns cache file in the memory cache when the http dns cache file exists in the local disk and the http dns cache file is legal. Or, the electronic device may further directly store the http dns cache file in the memory cache when the http dns cache file exists in the local disk.

The way for the electronic device to determine whether the http dns cache file in the local disk is legal may be, for example, determining whether the IP address in the http dns cache file only includes a number. If the IP address includes only numbers, the electronic device may determine that the http dns cache file is legitimate. If the IP address includes a string other than a number (e.g., a letter), the electronic device may determine that the http dns cache file is not legitimate. Or if the electronic equipment determines that the survival time of the IP address in the HTTPDNS cache file is not overtime, determining that the HTTPDNS cache file is legal. If the electronic equipment determines that the survival time of the IP address in the HTTPDNS cache file is overtime, the HTTPDNS cache file can be determined to be illegal.

In some embodiments, if there is no http dns cache file in the local disk, optionally, the electronic device may create an http dns cache file in the memory cache, so that the electronic device may store the acquired domain name corresponding to the IP address and the domain name as a mapping relationship in the http dns cache file.

S102, receiving an access request aiming at a first server, wherein the access request is triggered by a user.

The access request carries a first domain name of a first server.

For example, taking the application scenario shown in fig. 1 as an example, the electronic device may receive a first domain name of the first server input by a user, and then the electronic device may use the received operation of clicking the search control by the user as an access request for the first server triggered by the user.

Or, the electronic device may further display an interface including a first domain name, and the electronic device may receive an operation of clicking the first domain name by a user as an access request for the first server triggered by the user.

It should be understood that the manner in which the electronic device receives the access request for the first server triggered by the user is only a possible implementation manner, and how the electronic device receives the access request is not limited in this application.

S103, determining whether a first mapping relation between the first domain name and the IP address exists in the HTTPDNS cache file, and determining whether the first mapping relation is available.

Optionally, after receiving the access request, the electronic device may obtain a mapping relationship between the domain name and the IP address from an http dns cache file cached by the electronic device. If the electronic device matches the mapping relationship between the first domain name and the IP address from the mapping relationship between the domain name and the IP address, it may be determined that the first mapping relationship between the first domain name and the IP address exists in the http dns cache file. If the mapping relationship between the first domain name and the IP address is not matched in the mapping relationship between the domain name and the IP address, it may be determined that the first mapping relationship between the first domain name and the IP address is not present in the http dns cache file.

For example, the mapping relationship between the domain name and the IP address may be as shown in table 1 below:

TABLE 1

Domain name	IP address
		Domain name
1	IP address 1
		Domain name 2	IP address 2
Domain name 3	IP address 3
		Domain name 4	IP address 4

Taking the mapping relationship shown in table 1 as an example, assuming that the first domain name is domain name 1, the electronic device may determine that the first mapping relationship between the first domain name and the IP address exists in the http dns cache file. If the first domain name is domain name 5 and the domain name 5 does not exist in the mapping relationship between the domain name and the IP address, the electronic device may determine that the http dns cache file does not have the first mapping relationship between the first domain name and the IP address.

It should be understood that the storage location of the http dns cache file in the electronic device is not limited in the present application. Optionally, the http dns cache file may be stored in, for example, a memory cache of the electronic device, or may be stored in a local disk of the electronic device.

Optionally, whether the first mapping relationship is available may refer to whether a lifetime of an IP address in the first mapping relationship is timeout, for example. If the lifetime of the IP address is not over time, which indicates that the first server can be connected to the IP address, the electronic device may determine that the first mapping relationship is available. If the lifetime of the IP address is over, which indicates that the first server cannot be connected to the first server using the IP address, the electronic device may determine that the first mapping relationship is unavailable.

In this implementation manner, optionally, the http dns cache file may further store a mapping relationship among a domain name, an IP address, and a lifetime, for example. Through the mapping relationship among the three and the first domain name, the electronic device can acquire the lifetime of the IP address, and then determine whether the first mapping relationship is available based on the lifetime of the IP address.

Alternatively, whether the first mapping relationship is available may also refer to whether an IP address in the first mapping relationship satisfies legitimacy, for example. Illustratively, whether an IP address satisfies legitimacy as referred to herein may refer to whether the IP address includes only numbers, for example. If the IP address only includes numbers, the electronic device may determine that the IP address satisfies legitimacy, and may further determine that the first mapping relationship is available. If the IP address includes a string (e.g., a letter) other than a number, the electronic device may determine that the IP address does not satisfy legitimacy, and may determine that the first mapping is not available.

Still alternatively, whether the first mapping relationship is available or not may also refer to whether the IP address in the first mapping relationship satisfies validity or not, and whether the lifetime of the IP address in the first mapping relationship is timeout or not, for example. If the electronic device determines that the IP address meets the validity and the lifetime of the IP address is not time out, the electronic device may determine that the first mapping relationship is available. If the electronic device determines that the IP address does not satisfy the validity or the lifetime of the IP address is overtime, or the electronic device determines that the IP address does not satisfy the validity and the lifetime of the IP address is overtime, the electronic device may determine that the first mapping relationship is unavailable.

If the electronic device determines that the first mapping relationship or the first mapping relationship between the first domain name and the IP address is not available in the http DNS cache file, or that the first mapping relationship between the first domain name and the IP address is not available and the first mapping relationship is not available in the http DNS cache file, which indicates that the electronic device does not have an IP address that can be used for connecting with the first server, the electronic device may execute step S104 to resolve the first domain name through the http DNS server and the local DNS server, and further obtain the IP address corresponding to the first domain name.

If a first mapping relationship between the first domain name and the IP address exists in the http dns cache file and the first mapping relationship is available, it indicates that the electronic device may use the IP address in the http dns cache file to connect to the first server. Optionally, the electronic device may execute step S109 to establish a connection with the first server using the IP address. Alternatively, taking whether the first mapping relationship is available or not as an example, which means whether the lifetime of the IP address in the first mapping relationship is time out or not, the electronic device may further perform the step S109 after determining that the IP address satisfies the validity, for example.

And S104, resolving the first domain name through the HTTPDNS server and the local DNS server.

In some embodiments, the electronic device may, for example, send the access request to an http dns server to resolve the first domain name by the http dns server; and sending the access request to a local DNS server so as to resolve the first domain name through the local DNS server.

Optionally, the electronic device may resolve the first domain name through the http DNS server and the local DNS server at the same time. Alternatively, the electronic device may also resolve the first domain name through the http DNS server first, and then resolve the first domain name through the local DNS server. Still alternatively, the electronic device may further resolve the first domain name through the local DNS server first, and then resolve the first domain name through the http DNS server.

S105, determining whether the local DNS server is successfully analyzed, and determining whether the HTTPDNS server is successfully analyzed.

Optionally, the electronic device may determine whether the resolution of the local DNS server is successful and whether the resolution of the http DNS server is successful, for example, by whether the IP address of the first domain name fed back by the local DNS server and the http DNS server is received within a preset time period. Taking the example of determining whether the http dns server is successfully resolved, if the electronic device does not receive the IP address of the first domain name fed back by the http dns server within the preset time period, it may be determined that the http dns server is failed in resolution. If the electronic device receives the IP address of the first domain name fed back by the http dns within the preset time period, it may be determined that the http dns server is successfully resolved.

It should be understood that the preset time duration corresponding to the local DNS server may be the same as or different from the preset time duration corresponding to the http DNS server.

If the local DNS server is successfully resolved and the http DNS server is failed to resolve, the electronic device may execute step S106 to use the local DNS server to resolve the IP address obtained by the first domain name, and establish a connection with the first server.

If the local DNS server is successfully resolved and the http DNS server is successfully resolved, or the local DNS server is failed and the http DNS server is successfully resolved, because the security level of the http DNS server is higher than the security level of the local DNS server, optionally, the electronic device may use the IP address obtained by the http DNS server resolving the first domain name to establish a connection with the first server. By the method, the stability and the efficiency of the electronic equipment for domain name access are ensured, and meanwhile, domain name hijacking is avoided, so that the accuracy and the safety of the electronic equipment for domain name access are improved. As a possible implementation manner, if the HTTPDNS server successfully resolves, the electronic device may further store the mapping relationship between the first domain name and the IP address obtained by resolving the first domain name by the HTTPDNS server to a memory cache of the electronic device and an HTTPDNS cache file in the local disk, so as to improve the efficiency of the electronic device in storing the mapping relationship.

If the local DNS server fails to resolve and the http DNS server fails to resolve, optionally, the electronic device may output a prompt message for prompting the domain name access failure to prompt the user that the domain name access failure occurs, so as to avoid that the user waits for a long time without a result, thereby further improving the user experience. Optionally, the electronic device may output the prompt information through a display device of the electronic device or an external display device of the electronic device, for example.

S106, the local DNS server is used for resolving the IP address obtained by the first domain name, and connection is established with the first server.

Optionally, the electronic device may use the local DNS server to resolve the IP address obtained by the first domain name through any one of the foregoing communication modes, and establish a connection with the first server.

S107, determining whether the connection with the first server is successfully established by using the IP address obtained by resolving the first domain name by the local DNS server.

If the connection with the first server can be successfully established by using the local DNS server to resolve the IP address obtained by the first domain name, which indicates that the IP address obtained by the local DNS server resolving the first domain name is correct, the electronic device may execute step S108. If the IP address obtained by analyzing the first domain name using the local DNS server cannot establish a connection with the first server, it indicates that there may be an error in the IP address obtained by analyzing the first domain name using the local DNS server, and optionally, the electronic device may not update the first mapping relationship in the http DNS cache file using the IP address, for example.

Alternatively, for example, the electronic device may connect to the server using the IP address fed back by the local DNS server after receiving the IP address, and then determine whether the connection between the electronic device and the first server is successful according to whether the connected server is the first server. If the electronic device determines that the server connected according to the IP address fed back by the local DNS server is the first server, the electronic device may determine that the connection with the first server is successfully established. If the electronic device determines that the server connected according to the IP address fed back by the local DNS server is not the first server, the electronic device may determine that the connection with the first server fails.

The present application does not limit how the electronic device determines whether the connected server is the first server. For example, after the electronic device is connected to the server through the IP address, indication information for indicating that the server feeds back the verification code may be sent to the server. If the electronic device determines that the verification code fed back by the server is the same as the verification code preset by the electronic device, the electronic device may determine that the server connected to the electronic device is the first server. If the electronic device determines that the verification code fed back by the server is different from the verification code preset by the electronic device, the electronic device may determine that the server connected to the electronic device is not the first server.

And S108, storing the mapping relation between the first domain name and the IP address into a memory cache of the electronic equipment and an HTTPDNS cache file in a local disk.

Through the implementation mode, after the IP address of the first domain name is determined to be obtained through resolution by using the local DNS server and the connection with the first server is successfully established, the first mapping relation between the first domain name and the corresponding IP address is stored in the memory cache and the HTTPDNS cache file in the local disk, the condition of domain name hijacking caused by domain name access based on the local DNS server is avoided, and the accuracy and the safety of the subsequent connection between the IP address and the first server are improved.

Further, before executing step S108, as a possible implementation manner, the electronic device may further determine whether the lifetime of the IP address is time out. Alternatively, for example, the electronic device may first obtain the lifetime of the IP address, then determine whether the lifetime of the IP address is time out, and after determining that the lifetime of the IP address is not time out, execute the step S108. By the method, the accuracy of the mapping relation stored in the HTTPDNS cache file is further guaranteed, and the subsequent domain name access efficiency of the electronic equipment based on the HTTPDNS cache file is further improved.

In some embodiments, the electronic device may obtain the time-to-live of the IP address, for example, from the local DNS server. Optionally, the electronic device may receive the lifetime of the IP address from the local DNS server, for example, when the domain name resolution performed by the local DNS server is successful.

In some embodiments, the lifetime of the IP address may be, for example, a time of failure of the IP address. The electronic device may, for example, obtain a current time, and determine that the lifetime of the IP address is not exceeded when the current time is earlier than the expiration time of the IP address; and when the current time is later than the failure time of the IP address, determining that the survival time of the IP address is overtime.

S109, connection is established with the first server by using the IP address corresponding to the first domain name in the first mapping relation.

It should be understood that, the application is not limited to the manner in which the electronic device establishes the connection with the first server by using the IP address corresponding to the first domain name. Alternatively, any existing method for establishing a connection between an electronic device and a server using an IP address may be referred to.

In this embodiment, the electronic device may read the http dns cache file from the local disk of the electronic device and store the http dns cache file in the memory cache, so that the electronic device may read the http dns cache file from the memory cache, thereby improving the efficiency of subsequent domain name access by the electronic device based on the http dns cache file. After receiving an access request carrying a first domain name of a first server, the electronic device may resolve the first domain name through an http DNS server and a local DNS server when there is no first mapping relationship between the first domain name and an IP address in an http DNS cache file, or the first mapping relationship is unavailable. Compared with the existing method for analyzing the domain name only based on one DNS server, the stability and the efficiency of the electronic equipment for acquiring the IP address corresponding to the first domain name are improved by analyzing the first domain name through the HTTPDNS server and the local DNS server.

When the resolution of the HTTPDNS server fails and the resolution of the local DNS server succeeds, the electronic equipment establishes connection with the first server by using the IP address obtained by resolving the first domain name by using the local DNS server, so that the condition that the electronic equipment cannot access the domain name due to faults of the HTTPDNS server and the like is avoided, and the stability and the efficiency of the electronic equipment for accessing the domain name are further improved. After the connection between the IP address obtained by analyzing the first domain name by using the local DNS server and the first server is successfully established, the mapping relation between the first domain name and the IP address is stored into a memory cache of the electronic equipment and an HTTPDNS cache file in a local disk, so that the accuracy and the safety of the connection between the IP address and the first server in the subsequent use are improved.

Further, as a possible implementation manner, the http dns cache file may further include: lifetime of each IP address.

In this implementation, the electronic device may further determine a target update period according to the lifetime of each IP address. Wherein, the target update cycle is less than or equal to any one of the survival time of each IP address. For example, the electronic device may use, as the target update period, a product of a shortest one of the lifetime of each IP address and a preset coefficient. The predetermined coefficient is a constant greater than 0 and less than 1, for example, 0.75.

In each target updating period, the electronic device may analyze each domain name through the HTTPDNS server and the local DNS server to obtain an IP address corresponding to each updated domain name and a lifetime of the IP address. By enabling the target updating period to be less than or equal to any one of the survival times of the IP addresses, the electronic equipment can update the IP addresses in the survival time of each IP address, the accuracy of the IP addresses stored by the electronic equipment is further improved, and the efficiency of domain name access of the electronic equipment based on the HTTPDNS cache file is further improved.

For any domain name, the electronic device may determine whether the updated IP address corresponding to the domain name is the same as the pre-updated IP address corresponding to the domain name, and whether the lifetime of the updated IP address corresponding to the domain name is the same as the lifetime of the pre-updated IP address corresponding to the domain name.

If the updated IP address corresponding to the domain name is different from the pre-updated IP address corresponding to the domain name, or, the lifetime of the updated IP address corresponding to the domain name is different from the lifetime of the pre-updated IP address corresponding to the domain name, or, the updated IP address corresponding to the domain name is different from the pre-updated IP address corresponding to the domain name and the lifetime of the updated IP address corresponding to the domain name is different from the lifetime of the pre-updated IP address corresponding to the domain name, the electronic device may replace the pre-update IP address corresponding to the domain name in the HTTPDNS cache file stored in the local disk and the memory cache with the updated IP address corresponding to the domain name, and replacing the lifetime of the IP address before updating corresponding to the domain name in the HTTPDNS cache file stored in the local disk and the memory cache by using the lifetime of the updated IP address corresponding to the domain name.

By the method, the accuracy of the IP address stored in the electronic equipment and the survival time of the IP address are further improved, and the efficiency of the domain name access of the electronic equipment based on the HTTPDNS cache file is further improved.

In this implementation, in some embodiments, the electronic device may update the http DNS cache file based on the http DNS and the local DNS server to improve the efficiency of updating the IP address.

If the updated IP address and the lifetime of the IP address are obtained by analyzing based on the local DNS server, the electronic device may further replace the pre-update IP address and the lifetime of the IP address corresponding to the domain name in the http DNS cache file stored in the local disk and the memory cache by using the updated IP address and the lifetime of the IP address corresponding to the domain name after determining that the connection between the updated IP address and the server corresponding to the domain name is successful. By the method, the safety of the updated IP address is guaranteed.

Further, as a possible implementation manner, the electronic device may further initialize the http dns cache file in a memory cache, so as to improve accuracy of domain name access performed by the electronic device based on the http dns cache file, and reduce waste of a memory cache space.

In this implementation, optionally, the electronic device may first initialize and empty the cache information of the memory. Optionally, the electronic device may initialize and clear the cache information of the memory at a preset time point, or when the electronic device is powered on.

In some embodiments, taking the example that the http dns cache file further stores the lifetime of each IP address, the electronic device may further update the lifetime of each IP address. Taking the time to live of the IP address as an example, the electronic device may obtain the current time and update the time to live of each IP address by using the current time, for example, in the process of initializing the http dns cache file or after initializing the http dns cache file.

Further, optionally, after the lifetime of each IP address is updated, the electronic device may further obtain an updated target update period according to the updated lifetime of the IP address. And updating the HTTPDNS cache file based on the updated target updating period, so that the updating accuracy of the HTTPDNS cache file by the electronic equipment is improved, and the timeliness and the safety of the IP address stored in the HTTPDNS cache file are further ensured, thereby further improving the domain name access efficiency of the electronic equipment based on the HTTPDNS cache file.

The following describes in detail how the electronic device resolves the first domain name through the http dns server:

taking an example that the electronic device can access the http dns server through the second domain name, as a possible implementation manner, the electronic device queries whether the second mapping relationship between the second domain name and the corresponding IP address is stored in the http dns cache file.

If the http dns cache file stores the second mapping relationship and the stored second mapping relationship is available, it indicates that the electronic device may be connected to the http dns server through the second domain name and the corresponding IP address stored in the http dns cache file. The electronic device obtains the IP address corresponding to the second domain name from the http dns cache file, interacts with the http dns server according to the IP address corresponding to the second domain name, and resolves the first domain name.

If the http dns cache file does not have the second mapping relationship, or the stored second mapping relationship is not available, it indicates that the electronic device does not have an IP address that can be used for connecting with the http dns server. Optionally, the electronic device may analyze the second domain name through the local DNS server to obtain an IP address corresponding to the second domain name. Optionally, the electronic device may refer to the method for resolving the first domain name through the local DNS server in the foregoing embodiment in a manner of resolving the second domain name through the local DNS server, which is not described herein again.

After the IP address corresponding to the second domain name is obtained, the electronic device may interact with the http dns server according to the IP address corresponding to the second domain name, so as to realize that the first domain name is resolved by the http dns server.

Taking the example that the http dns server is used in an open manner in the form of an IP address, the electronic device may directly use the IP address of the http dns server to interact with the http dns server. Alternatively, the electronic device may, for example, obtain the IP address of the http dns server entered by the user. Furthermore, after receiving the IP address of the http dns server input by the user, the electronic device may further store the IP address, so as to improve the efficiency of interaction between the electronic device and the http dns server, thereby further improving user experience. Alternatively, the IP address of the http dns server may be, for example, an IP address of the http dns server that is pre-stored in the electronic device by the electronic device downloading an application corresponding to the http dns service in advance.

In this embodiment, when the http dns server is accessed by the second domain name, a second mapping relationship between the second domain name and the corresponding IP address is stored in the http dns cache file, and when the second mapping relationship is available, the IP address connected to the http dns server is acquired from the http dns cache file. Or when the HTTPDNS cache file has no second mapping relationship or the second mapping relationship is unavailable, the IP address corresponding to the second domain name is acquired by the local DNS server. By the method, the electronic equipment obtains the IP address connected with the HTTPDNS server, and further the electronic equipment can perform domain name resolution through the HTTPDNS server.

Further, as a possible implementation manner, after the HTTPDNS cache file is created in the memory cache, when the HTTPDNS server accesses through the IP address, the electronic device may write the second mapping relationship between the second domain name of the HTTPDNS server and the corresponding IP address into the memory cache.

Through the implementation mode, the second domain name and the corresponding IP address are stored after the second domain name and the corresponding IP address are determined to be available, the fact that the electronic equipment can be directly connected with the HTTPDNS server by using the second domain name and the corresponding IP address is guaranteed, and the efficiency and the safety of domain name access of the electronic equipment based on the HTTPDNS server are improved.

Fig. 3 is a schematic flowchart of another domain name access method provided in the present application. As shown in fig. 3, the method comprises the steps of:

step 1, initializing and clearing cache information of a memory of the electronic equipment.

After performing step 1, the electronic device may perform step 2 and step 16.

And step 2, determining whether the initial HTTPDNS cache file exists in the local disk.

If yes, go to step 3. If not, go to step 4.

And 3, reading the initial HTTPDNS cache file into a memory cache to serve as the HTTPDNS cache file.

Optionally, the process includes reading the IP address of the http dns server into a memory cache of the electronic device. Then, step 6 is performed.

And 4, creating an HTTPDNS cache file in the memory cache.

And step 5, reading the IP address of the HTTPDNS server pre-stored in the application program corresponding to the HTTPDNS service into a memory cache of the electronic equipment.

And 6, determining whether the HTTPDNS cache file has a first mapping relation between the first domain name and the IP address, and determining whether the first mapping relation exceeds the survival time.

If the first mapping relationship between the first domain name and the IP address exists in the http dns cache file and the first mapping relationship does not exceed the lifetime, step 7 is executed.

If the first mapping relationship between the first domain name and the IP address does not exist in the http dns cache file, or the first mapping relationship exceeds the lifetime, step 8 is executed.

And 7, establishing connection with the first server by using the IP address corresponding to the first domain name in the first mapping relation.

And 8, resolving the first domain name through an HTTPDNS server.

And 9, determining whether the HTTPDNS server is successfully analyzed.

If successful, go to step 10. If the failure is detected, step 11 is executed.

And step 10, using an HTTPDNS server to analyze the IP address obtained by the first domain name, and establishing connection with the first server.

The electronic device may then perform step 14 to store the mapping of the first domain name to the corresponding IP address.

And 11, resolving the first domain name through a local DNS server.

And step 12, using the local DNS server to resolve the IP address obtained by the first domain name, and establishing connection with the first server.

And step 13, determining whether the IP address of the first domain name resolved by the local DNS server is available.

If so, step 14 is performed. If not, step 15 is performed.

And step 14, updating the mapping relation between the first domain name and the IP address in the HTTPDNS cache file.

And step 15, outputting prompt information of domain name failure.

And step 16, polling whether the survival time of the HTTPDNS cache file is overtime or not.

If time out, go to step 17. If not, the step 16 is executed.

And step 17, traversing and updating the mapping relation stored in the HTTPDNS cache file.

Fig. 4 is a schematic structural diagram of a domain name access device provided in the present application. The device is applied to electronic equipment. As shown in fig. 4, the apparatus includes: a reading module 21, a receiving module 22, a processing module 23, and a storage module 24. Wherein the content of the first and second substances,

the reading module 21 is configured to read an http dns cache file from a local disk of the electronic device, and store the http dns cache file in a memory cache.

A receiving module 22, configured to receive an access request for a first server, where the access request is triggered by a user and carries a first domain name of the first server.

The processing module 23 is configured to, when the http DNS cache file does not have the first mapping relationship between the first domain name and the IP address, or when the first mapping relationship is unavailable, resolve the first domain name through the http DNS server and the local DNS server; and when the local DNS server is successfully analyzed and the HTTPDNS server is failed to analyze, using the local DNS server to analyze the IP address obtained by the first domain name, and establishing connection with the first server.

The storage module 24 is configured to store the mapping relationship between the first domain name and the IP address to a memory cache of the electronic device and an http DNS cache file in a local disk after the IP address obtained by analyzing the first domain name using the local DNS server is successfully connected to the first server.

Optionally, the processing module 23 is further configured to obtain a lifetime of the IP address before the mapping relationship between the first domain name and the IP address is stored in a memory cache of the electronic device and an http dns cache file in a local disk; determining that the lifetime of the IP address has not timed out.

Optionally, the processing module 23 is further configured to, when the http dns server successfully resolves the http dns server, use the http dns server to resolve the IP address obtained by the first domain name, establish a connection with the first server, and store the mapping relationship between the first domain name and the IP address to the internal memory cache of the electronic device and the http dns cache file in the local disk.

Optionally, the http dns cache file further includes: lifetime of each IP address. In this implementation, the processing module 23 is further configured to determine a target update period according to the lifetime of each IP address; in each target updating period, analyzing each domain name through an HTTPDNS server and a local DNS server to obtain an IP address corresponding to each updated domain name and the survival time of the IP address; and for any domain name, when the updated IP address corresponding to the domain name is different from the IP address corresponding to the domain name before updating, and/or the survival time of the updated IP address corresponding to the domain name is different from the survival time of the IP address corresponding to the domain name before updating, replacing the survival time of the IP address and the IP address corresponding to the domain name in the HTTPDNS cache file stored in the local disk and the memory cache by using the updated IP address and the survival time of the IP address corresponding to the domain name after updating corresponding to the domain name. Wherein, the target update cycle is less than or equal to any one of the survival time of the IP addresses.

Optionally, when the updated IP address and the lifetime of the IP address are obtained based on the local DNS server, the processing module 23 is further configured to determine that the server using the updated IP address and the server using the updated IP address corresponding to the domain name is successfully connected before the local disk and the lifetime of the IP address and the IP address before updating corresponding to the domain name in the http DNS cache file stored in the memory cache are replaced by the updated IP address and the lifetime of the IP address corresponding to the domain name.

Optionally, the processing module 23 is specifically configured to, when the http dns server accesses through a second domain name, query whether a second mapping relationship between the second domain name and a corresponding IP address is stored in the http dns cache file; when the second mapping relation is stored in the HTTPDNS cache file and the stored second mapping relation is available, acquiring an IP address corresponding to the second domain name from the HTTPDNS cache file, interacting with the HTTPDNS server according to the IP address corresponding to the second domain name, and analyzing the first domain name;

or, the processing module 23 is specifically configured to, when the HTTPDNS cache file does not have the second mapping relationship, or the stored second mapping relationship is unavailable, resolve the second domain name through the local DNS server to obtain an IP address corresponding to the second domain name; and interacting with the HTTPDNS server according to the IP address corresponding to the second domain name, and analyzing the first domain name.

Optionally, the processing module 23 is further configured to initialize the http dns cache file in the memory cache.

The domain name access device provided in this embodiment may implement the above-mentioned domain name access method embodiment, and its implementation principle and technical effect are similar, which are not described herein again.

Fig. 5 is a schematic structural diagram of an electronic device provided in the present application. As shown in fig. 5, the electronic device 300 may include: at least one processor 301 and a memory 302.

A memory 302 for storing programs. In particular, the program may include program code including computer operating instructions.

Memory 302 may comprise high-speed RAM memory and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

Processor 301 is configured to execute computer-executable instructions stored in memory 302 to implement the domain name access methods described in the foregoing method embodiments. The processor 301 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement the embodiments of the present Application.

Optionally, the electronic device 300 may further include a communication interface 303. In a specific implementation, if the communication interface 303, the memory 302 and the processor 301 are implemented independently, the communication interface 303, the memory 302 and the processor 301 may be connected to each other through a bus and perform communication with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. Buses may be classified as address buses, data buses, control buses, etc., but do not represent only one bus or type of bus.

Alternatively, in a specific implementation, if the communication interface 303, the memory 302 and the processor 301 are integrated into a chip, the communication interface 303, the memory 302 and the processor 301 may complete communication through an internal interface.

The present application also provides a computer-readable storage medium, which may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and in particular, the computer-readable storage medium stores program instructions, and the program instructions are used in the method in the foregoing embodiments.

The present application also provides a program product comprising execution instructions stored in a readable storage medium. The at least one processor of the electronic device may read the execution instructions from the readable storage medium, and the execution of the execution instructions by the at least one processor causes the electronic device to implement the domain name access method provided by the various embodiments described above.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A domain name access method is applied to an electronic device, and comprises the following steps:

2. The method according to claim 1, wherein before storing the mapping relationship between the first domain name and the IP address in an in-memory cache of the electronic device and an http dns cache file in a local disk, the method further comprises:

acquiring the survival time of the IP address;

determining that the lifetime of the IP address has not timed out.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

4. The method according to claim 1 or 2, wherein the http dns cache file further comprises: a lifetime of each IP address, the method further comprising:

5. The method according to claim 4, wherein if the updated IP address and the lifetime of the IP address are obtained by the resolution of the local DNS server, before replacing the pre-update IP address and the lifetime of the IP address corresponding to the domain name in the http DNS cache file stored in the local disk and the memory cache by using the updated IP address and the lifetime of the IP address corresponding to the domain name, the method further comprises:

6. The method according to claim 1 or 2, wherein said resolving the first domain name by the http dns server comprises:

7. The method according to claim 1 or 2, characterized in that the method further comprises:

and initializing the HTTPDNS cache file in the memory cache.

8. A domain name access apparatus, the apparatus comprising:

9. An electronic device, comprising: at least one processor, a memory;

the memory stores computer-executable instructions;

the at least one processor executing the computer-executable instructions stored by the memory causes the electronic device to perform the method of any of claims 1-7.

10. A computer-readable storage medium having computer-executable instructions stored thereon which, when executed by a processor, implement the method of any one of claims 1-7.

11. A computer program product comprising a computer program, characterized in that the computer program realizes the method of any of claims 1-7 when executed by a processor.