CN114338630B

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

Info

Publication number: CN114338630B
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: 2024-04-19
Anticipated expiration: 2041-12-13
Also published as: CN114338630A

Abstract

The application 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. Comprising the following steps: reading HTTPDNS a cache file from a local disk and storing the cache file into a memory cache; an access request carrying a first domain name of a first server is received. If no first domain name is available in the HTTPDNS cache file and the IP address or IP is not available, the first domain name is resolved through the HTTPDNS server and the local DNS server; if the local DNS server is successfully resolved and HTTPDNS server resolution fails, using the IP address obtained by the local DNS server resolution to establish connection with the server; after the connection between the IP address and the server is established successfully, the mapping relation between the first domain name and the IP address is stored into a memory cache and HTTPDNS cache files in a local disk. The application improves 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 accessing a website (e.g., website a), the electronic device may typically receive a domain name of website a entered by a user. The electronic device may then connect over the internet with A server capable of providing an internet protocol (Internet Protocol, IP) address corresponding to the domain name to obtain from the server an IP address corresponding to the domain name of website A. 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 performing a domain name system (domain NAME SYSTEM, DNS) service (HTTPDNS) through a hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) protocol. However, when the HTTPDNS server cannot perform domain name resolution due to a failure or the like, the electronic device cannot obtain the IP address corresponding to the domain name through the HTTPDNS 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, where the method is applied to an electronic device, and the method includes:

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

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

If the HTTPDNS cache file has no first mapping relation between the first domain name and the IP address or the first mapping relation is unavailable, resolving the first domain name through a HTTPDNS server and a local DNS server;

If the local DNS server is successfully resolved and the HTTPDNS server is failed to resolve, 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;

after the local DNS server is used for resolving the IP address obtained by the first domain name and is successfully connected with the first server, the mapping relation between the first domain name and the IP address is stored into a memory cache of the electronic equipment and HTTPDNS cache files in a local disk.

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

Acquiring the survival time of the IP address;

and determining that the lifetime of the IP address is not overtime.

Optionally, the method further comprises:

If the HTTPDNS server successfully analyzes, the HTTPDNS server is used for analyzing the IP address obtained by the first domain name, connection is established with the first server, and the mapping relation between the first domain name and the IP address is stored in a memory cache of the electronic equipment and a HTTPDNS cache file in a local disk.

Optionally, the HTTPDNS cache file further includes: the survival time of each IP address, the method further comprises:

Determining a target updating period according to the survival time of each IP address; the target update 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 HTTPDNS servers and local DNS servers to obtain an IP address corresponding to each updated domain name and the survival time of the IP address;

And 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 survival time of the updated IP address corresponding to the domain name is different from the survival time of the pre-updated IP address corresponding to the domain name, replacing the survival time of the pre-updated IP address and the survival time 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 survival time of the IP address corresponding to the domain name.

Optionally, if the survival time of the updated IP address and the IP address is obtained based on the resolution of the local DNS server, before the survival time of the updated 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 is replaced, 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 parsing, by the HTTPDNS server, the first domain name includes:

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

If the HTTPDNS cache file stores the second mapping relation 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 relation, or if the stored second mapping relation is unavailable, resolving the second domain name through the local DNS server to obtain an IP address corresponding to the second domain name;

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

Optionally, the method further comprises:

Initializing the HTTPDNS cache file in the memory cache.

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

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

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

The processing module is configured to resolve, when the HTTPDNS cache file does not have a first mapping relationship between the first domain name and the IP address, or the first mapping relationship is unavailable, the first domain name through a HTTPDNS server and a local DNS server; when the local DNS server is successfully resolved and the HTTPDNS server is failed to resolve, using an IP address obtained by the local DNS server to resolve the first domain name to establish 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 into a memory cache of the electronic equipment and HTTPDNS cache files 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, memory;

the memory stores computer-executable instructions;

The at least one processor executes computer-executable instructions stored in the memory to cause the electronic device to perform the method of any one of the first aspects.

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

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 of the first aspects.

According to the domain name access method, the device, the electronic equipment, the storage medium and the program product, the electronic equipment can read HTTPDNS the cache file from the local disk of the electronic equipment and store the 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 HTTPDNS server fails to resolve and the local DNS server successfully resolves, the electronic equipment establishes connection with the first server by using the IP address obtained by resolving the first domain name by the local DNS server, so that the situation that the electronic equipment cannot access the domain name due to the HTTPDNS server fault and other reasons is avoided, and the stability and the efficiency of the domain name access of the electronic equipment are further improved. After the fact that connection between the IP address obtained by analyzing the first domain name by using the local DNS server and the first server is established successfully is determined, the mapping relation between the first domain name and the IP address is stored in a memory cache of the electronic equipment and HTTPDNS cache files in a local disk, and accuracy and safety of connection between the subsequent use of the IP address and the first server are improved.

Drawings

In order to more clearly illustrate the application or the technical solutions of the prior art, the following description will be given for a brief introduction to the drawings used in the embodiments or the description of the prior art, it being obvious that the drawings in the following description are some embodiments of the application and that other drawings can be obtained from these drawings without inventive effort for a person skilled in the art.

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

FIG. 2 is a schematic flow chart of a domain name access method provided by the application;

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

Fig. 4 is a schematic structural diagram of a domain name access device provided by the present application;

Fig. 5 is a schematic structural diagram of an electronic device according to 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. Those skilled in the art can adapt it as desired to suit a particular application.

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The term concept to which the present application relates is explained first:

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

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

Taking an electronic device as a mobile phone or a tablet computer as an example, fig. 1 is a schematic view of a scenario in which the electronic device performs domain name access. As shown in fig. 1, the electronic device may receive a domain name a (as "www.xxx.com" in fig. 1) of a server corresponding to website a entered by the user. The electronic device may then connect with a local DNS server through network communication in response to the user clicking on the "search" control to send a request message to the local DNS server requesting the acquisition of the IP address corresponding to the domain name a.

Then, the electronic device may receive the IP address corresponding to the domain name a from the local DNS server through the network communication. By using the IP address, the electronic equipment can be connected with the server corresponding to the website A, so that the electronic equipment can access the server, and the display interface of the website A corresponding to the domain name a is displayed, so that a user can 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 communication method such as mobile communication, wi-Fi, or wired communication.

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

In addition, some embodiments also propose domain name resolution by a HTTPDNS server with a higher security level than the local DNS server to reduce the problem of domain name hijacking.

In performing domain name resolution via HTTPDNS servers, HTTPDNS servers also need to interact with electronic devices via network communications.

Therefore, when the network quality where the HTTPDNS server is located is poor, or when the HTTPDNS server fails, the efficiency of domain name access by the electronic device based on the HTTPDNS server is low, and domain name access based on the HTTPDNS server is not possible. 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 obtaining an IP address corresponding to a domain name based on a local DNS server and a HTPPDNS server. When HTPPDNS servers fail in domain name resolution, domain name resolution is performed through a local DNS server, and after the fact that the IP address obtained by using the local DNS server in domain name resolution is successfully connected with the server corresponding to the domain name is determined, the IP address is stored in the electronic equipment, so that accuracy of acquiring the IP address corresponding to the domain name by the electronic equipment is improved, stability and efficiency of domain name access by the electronic equipment are improved, and user experience is further improved. The main execution body of the method is, for example, the electronic device.

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

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

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

Alternatively, the electronic device may read HTTPDNS the cached file from the local disk of the electronic device, for example, according to a preset storage path for representing HTTPDNS the storage location of the cached file on the local disk of the electronic device. The preset storage path may be predetermined by the electronic device when the HTTPDNS cache file is created, for example.

Alternatively, the electronic device may store the HTTPDNS cache file in the memory cache when the HTTPDNS cache file exists in the local disk and the HTTPDNS cache file is legal. Or the electronic device can also directly store the HTTPDNS cache file into the memory cache when the HTTPDNS cache file exists in the local disk.

The manner in which the electronic device determines whether the HTTPDNS cache file in the local disk is legal may be, for example, to determine whether the IP address in the HTTPDNS cache file includes only numbers. If the IP address includes only digits, the electronic device may determine HTTPDNS that the cache file is legitimate. If the IP address includes a string (e.g., letter) other than a number, the electronic device may determine HTTPDNS that the cache file is illegal. Or if the electronic device determines HTTPDNS that the lifetime of the IP address in the cache file is not timeout, determining HTTPDNS that the cache file is legal. If the electronic device determines HTTPDNS that the lifetime of the IP address in the cache file is over, it may determine HTTPDNS that the cache file is illegal.

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

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 the first server.

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

Or the electronic device may further display an interface including the first domain name, and the electronic device may receive an operation of clicking on the first domain name by the 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, and the present application is not limited to how the electronic device receives the access request.

S103, determining HTTPDNS whether a first mapping relation between the first domain name and the IP address exists in the 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 a HTTPDNS 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 HTTPDNS that the first mapping relationship between the first domain name and the IP address exists in the cache file. If the mapping relationship between the domain name and the IP address is not matched with the mapping relationship between the first domain name and the IP address, it may be determined HTTPDNS that the cache file does not have the first mapping relationship between the first domain name and the IP address.

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

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 HTTPDNS that the first mapping relationship between the first domain name and the IP address exists in the cache file. If the first domain name is a domain name 5, the mapping relationship between the domain name and the IP address does not include the domain name 5, the electronic device may determine HTTPDNS that the cache file does not have the first mapping relationship between the first domain name and the IP address.

It should be understood that the present application is not limited to the above-mentioned HTTPDNS cache locations in the electronic device. Optionally, the HTTPDNS cache file may be stored in a memory cache of the electronic device, or may be stored in a local disk of the electronic device, for example.

Alternatively, whether the first mapping relationship is available may refer to whether the lifetime of the IP address in the first mapping relationship is overtime, for example. If the lifetime of the IP address is not timed out, indicating that the first server may be connected using the IP address, the electronic device may determine that the first mapping relationship is available. If the lifetime of the IP address is over, indicating that the first server cannot be connected using the IP address, the electronic device may determine that the first mapping relationship is not available.

In this implementation manner, optionally, the HTTPDNS cache file may further store a mapping relationship between a domain name, an IP address, and a lifetime, for example. Through the mapping relation among the three and the first domain name, the electronic equipment can acquire the survival time of the IP address, and then determine whether the first mapping relation is available or not based on the survival time of the IP address.

Or whether the first mapping relationship is available may also refer to whether the IP address in the first mapping relationship satisfies validity, for example. By way of example, whether an IP address meets legitimacy as referred to herein may refer to whether the IP address includes only digits, for example. If the IP address includes only digits, the electronic device may determine that the IP address satisfies the 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 the legitimacy, and may further determine that the first mapping relationship is not available.

Further, whether the first mapping relationship is usable may also refer to whether the IP address in the first mapping relationship satisfies validity, and whether the lifetime of the IP address in the first mapping relationship is overtime, for example. If the electronic device determines that the IP address meets the validity, and the lifetime of the IP address is not overtime, 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 if 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 not available.

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

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

S104, the first domain name is resolved through the HTTPDNS server and the local DNS server.

In some embodiments, the electronic device may send the above access request to a HTTPDNS server, for example, to resolve the first domain name by the HTTPDNS server; the access request is sent to a local DNS server to resolve the first domain name with the local DNS server.

Alternatively, the electronic device may resolve the first domain name through both the HTTPDNS server and the local DNS server. Or the electronic device may first resolve the first domain name through the HTTPDNS server and then resolve the first domain name through the local DNS server. Or the electronic device may first resolve the first domain name by using the local DNS server, and then resolve the first domain name by using the HTTPDNS server.

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

Alternatively, the electronic device may determine whether the local DNS server resolves successfully and whether the HTTPDNS server resolves successfully, for example, by receiving the IP addresses of the first domain name fed back by the local DNS server and HTTPDNS server within a preset duration. Taking the example of determining HTTPDNS whether the server resolution is successful, if the electronic device does not receive HTTPDNS the IP address of the first domain name fed back by the server within the preset duration, it may be determined HTTPDNS that the server resolution fails. If the electronic device receives HTTPDNS the IP address of the first domain name fed back in the preset duration, it may be determined HTTPDNS that the server resolution is successful.

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

If the local DNS server resolution is successful and HTTPDNS server resolution fails, the electronic device may execute step S106 to establish a connection with the first server using the IP address obtained by the local DNS server resolving the first domain name.

If the local DNS server resolution is successful and HTTPDNS server resolution is successful, or the local DNS server resolution is failed and HTTPDNS server resolution is successful, because the security level of the HTTPDNS server is higher than that of the local DNS server, optionally, the electronic device may use the IP address obtained by resolving the first domain name with the HTTPDNS server to establish a connection with the first server. By the method, domain name hijacking is avoided while stability and efficiency of domain name access of the electronic equipment are guaranteed, and accuracy and safety of domain name access of the electronic equipment are improved. As a possible implementation manner, if the HTTPDNS server resolves successfully, 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 a HTTPDNS cache file in the local disk, so as to improve efficiency of storing the mapping relationship by the electronic device.

If the local DNS server fails to resolve and HTTPDNS server fails to resolve, optionally, the electronic device may output a prompt message for prompting the domain name access failure, so as to prompt the user that the domain name access fails, so that the user is prevented from waiting for no result for a long time, and further user experience is further improved. Optionally, the electronic device may output the prompt information, for example, through a display device of the electronic device or a display device externally connected to the electronic device.

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 IP address obtained by resolving the first domain name by using the local DNS server through any one of the foregoing communication methods, 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 between the electronic device and the first server is established successfully by using the IP address obtained by resolving the first domain name by the local DNS server, which indicates that the IP address obtained by resolving the first domain name by the local DNS server is correct, the electronic device may execute step S108. If the local DNS server is used to resolve the IP address of the first domain name, a connection cannot be established with the first server, which indicates that there may be an error in the IP address obtained by resolving the first domain name by the local DNS server, and optionally, the electronic device may update HTTPDNS the first mapping in the cache file without using the IP address, for example.

Alternatively, the electronic device may, for example, use the IP address fed back by the local DNS server to connect to the 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 to the server according to the IP address fed back by the local DNS server is the first server, the electronic device can determine that the connection with the first server is successfully established. If the electronic device determines that the server to which the IP address fed back by the local DNS server is connected is not the first server, the electronic device may determine that the connection establishment with the first server fails.

The present application is not limited to 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, the electronic device may send indication information for indicating that the server feeds back the verification code 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 can determine that the connected server 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 can determine that the connected server is not the first server.

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

Through the implementation manner, after the fact that the local DNS server is used for resolving to obtain the IP address of the first domain name and successfully establishing connection with the first server is determined, the first mapping relation between the first domain name and the corresponding IP address is stored in the memory cache and HTTPDNS cache files in the local disk, the situation that domain name hijacking is generated when domain name access is carried out based on the local DNS server is avoided, and the accuracy and safety of connection between the subsequent use of the IP address and the first server are improved.

Further, before performing step S108, as a possible implementation manner, the electronic device may further determine whether the lifetime of the IP address is timeout. Alternatively, the electronic device may, for example, first obtain the lifetime of the IP address, then determine whether the lifetime of the IP address is timeout, and execute the step S108 after determining that the lifetime of the IP address is not timeout. 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 lifetime of the IP address from the local DNS server, for example. Alternatively, the electronic device may receive the lifetime of the IP address from the local DNS server, for example, when the local DNS server performs domain name resolution successfully.

In some embodiments, the lifetime of the IP address may be, for example, a failure time 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 overtime when the current time is earlier than the failure time of the IP address; and when the current time is later than the failure time of the IP address, determining that the life time of the IP address is overtime.

S109, establishing connection 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 manner in which the electronic device establishes a connection with the first server using the IP address corresponding to the first domain name is not limited by the present application. Alternatively, the method of establishing a connection with the server using the IP address may be referred to any existing electronic device.

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

When the HTTPDNS server fails to resolve and the local DNS server successfully resolves, the electronic equipment establishes connection with the first server by using the IP address obtained by resolving the first domain name by the local DNS server, so that the situation that the electronic equipment cannot access the domain name due to the HTTPDNS server fault and other reasons is avoided, and the stability and the efficiency of the domain name access of the electronic equipment are further improved. After the fact that connection between the IP address obtained by analyzing the first domain name by using the local DNS server and the first server is established successfully is determined, the mapping relation between the first domain name and the IP address is stored in a memory cache of the electronic equipment and HTTPDNS cache files in a local disk, and accuracy and safety of connection between the subsequent use of the IP address and the first server are improved.

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

In this implementation, the electronic device may also determine the target update period according to the lifetime of each IP address. Wherein the target update period is less than or equal to any one of the lifetime of each IP address. For example, the electronic device may set, as the target update period, a product of a shortest lifetime among the lifetimes of the IP addresses and a preset coefficient. Wherein the preset coefficient is greater than 0 and less than 1 constant, for example 0.75.

In each target updating period, the electronic device can analyze each domain name through the HTTPDNS server and the local DNS server to obtain the updated IP address corresponding to each domain name and the survival time of the IP address. By enabling the target update period to be smaller than or equal to any one of the survival time of each IP address, the electronic equipment can update each IP address in the survival time of each IP address, the accuracy of the IP addresses stored by the electronic equipment is further improved, and the domain name access efficiency 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-update 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-update 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, then the electronic device may replace the pre-updated IP address corresponding to the domain name in the HTTPDNS cache file stored in the local disk and memory cache with the updated IP address corresponding to the domain name, and replace the lifetime of the pre-updated IP address corresponding to the domain name in the HTTPDNS cache file stored in the local disk and memory cache with the lifetime of the updated IP address corresponding to the domain name.

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

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

If the survival time of the updated IP address and the IP address is obtained based on the analysis of the local DNS server, the electronic device may further replace the survival time of the updated 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 survival time of the updated IP address and the IP address corresponding to the domain name after determining that the updated IP address and the server corresponding to the domain name are successfully connected. By the method, the safety of the updated IP address is ensured.

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

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

In some embodiments, taking the HTTPDNS cache file further storing the lifetime of each IP address as an example, the electronic device may further update the lifetime of each IP address. Taking the duration that the present time is equal to the duration that the IP address is invalid as an example, the electronic device may, for example, obtain the present time during the process of initializing the HTTPDNS cache file or after initializing the HTTPDNS cache file, and update the lifetime of each IP address using the present time.

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

How the electronic device resolves the first domain name through the HTTPDNS server is described in detail below:

Taking the example that the electronic device can access HTTPDNS the 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 HTTPDNS cache file.

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

If the HTTPDNS cache file does not have the second mapping relationship, or the stored second mapping relationship is not available, it indicates that the electronic device has no IP address that can be used for connecting to the HTTPDNS server. Optionally, the electronic device may resolve the second domain name through a local DNS server to obtain an IP address corresponding to the second domain name. Optionally, the method for resolving the first domain name by the local DNS server may be referred to the method for resolving the second domain name by the local DNS server in the foregoing embodiment, which is not described herein.

After obtaining the IP address corresponding to the second domain name, the electronic device may interact with the HTTPDNS server according to the IP address corresponding to the second domain name, so as to implement resolution of the first domain name by using the HTTPDNS server.

Taking HTTPDNS that the server is open to the outside for use in the form of an IP address, the electronic device may interact with the HTTPDNS server directly using the IP address of the HTTPDNS server. Alternatively, the electronic device may obtain, for example, the IP address of the HTTPDNS server entered by the user. Further, after receiving the IP address of the HTTPDNS server input by the user, the electronic device may further store the IP address, so as to improve the interaction efficiency of the electronic device and the HTTPDNS server, and further improve the user experience. Alternatively, the IP address of the HTTPDNS server may be, for example, an IP address of the HTTPDNS server may be stored in the electronic device in advance by downloading an application program corresponding to the HTTPDNS service in advance.

In this embodiment, when the HTTPDNS server accesses through the second domain name, a second mapping relationship between the second domain name and the corresponding IP address is stored in the HTTPDNS cache file, and when the second mapping relationship is available, the IP address connected to the HTTPDNS server is obtained from the HTTPDNS cache file. Or when the HTTPDNS cache file has no second mapping relation or the second mapping relation is not available, acquiring the IP address corresponding to the second domain name through the local DNS server. Through the method, the electronic equipment obtains the IP address connected with the HTTPDNS server, so that the electronic equipment can perform domain name resolution through the HTTPDNS server.

Further, as a possible implementation manner, after creating HTTPDNS the cache file in the memory cache, 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 when the HTTPDNS server accesses through the IP address.

By the implementation manner, after the second domain name and the corresponding IP address are determined to be available, the second domain name and the corresponding IP address are stored, so that the electronic equipment can be ensured to be directly connected with the HTTPDNS server by using the second domain name and the corresponding IP address, and the domain name access efficiency and the domain name access security of the electronic equipment based on the HTTPDNS server are improved.

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

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

After step 1 is performed, the electronic device may perform steps 2 and 16.

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

If so, executing the step 3. If not, executing the step 4.

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

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

And 4, creating HTTPDNS cache files in the memory cache.

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

And 6, determining HTTPDNS whether a first mapping relation between the first domain name and the IP address exists in the cache file, 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 HTTPDNS 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 HTTPDNS cache file, or the first mapping relationship exceeds the survival time, 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, analyzing the first domain name through the HTTPDNS server.

And 9, determining HTTPDNS whether the server analysis is successful.

If successful, step 10 is performed. If it fails, step 11 is performed.

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

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

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

And 12, using the local DNS server to analyze 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 available, step 14 is performed. If not, step 15 is performed.

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

And 15, outputting prompt information of domain name failure.

Step 16, polling HTTPDNS to buffer the survival time of the file is overtime.

If it times out, step 17 is performed. If not, the process returns to step 16.

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

Fig. 4 is a schematic structural diagram of a domain name access device provided by 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,

And the reading module 21 is used for reading HTTPDNS the cache file from the local disk of the electronic equipment and storing the cache file in the memory cache.

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

A processing module 23, configured to resolve, in the HTTPDNS cache file, the first domain name and the first mapping relationship of the IP address, or when the first mapping relationship is unavailable, the first domain name through a HTTPDNS server and a local DNS server; and when the local DNS server is successfully resolved and the HTTPDNS server is failed to resolve, establishing connection with the first server by using the IP address obtained by the local DNS server for resolving the first domain name.

And the storage module 24 is configured to store, after the connection between the IP address obtained by resolving the first domain name by using the local DNS server and the first server is established successfully, a mapping relationship between the first domain name and the IP address to a memory cache of the electronic device and a HTTPDNS cache file in a local disk.

Optionally, the processing module 23 is further configured to obtain a lifetime of the IP address before storing the mapping relationship between the first domain name and the IP address in a memory cache of the electronic device and a HTTPDNS cache file in a local disk; and determining that the lifetime of the IP address is not overtime.

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

Optionally, the HTTPDNS cache file further includes: the 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 HTTPDNS servers and local DNS servers 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 pre-updated IP address corresponding to the domain name, and/or when the survival time of the updated IP address corresponding to the domain name is different from the survival time of the pre-updated IP address corresponding to the domain name, replacing the survival time of the pre-updated IP address and the survival time of the IP address corresponding to the domain name in the HTTPDNS cache files stored in the local disk and the memory cache. Wherein the target update period is less than or equal to any one of the lifetime of each IP address.

Optionally, when the survival time of the updated IP address and the IP address is obtained based on the resolution of the local DNS server, the processing module 23 is further configured to determine that the server using the updated IP address and the corresponding domain name is successfully connected before the survival time of the updated 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 is replaced.

Optionally, the processing module 23 is specifically configured to query, when the HTTPDNS server accesses through a second domain name, whether a second mapping relationship between the second domain name and a corresponding IP address is stored in the HTTPDNS 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, by using the local DNS server, the second domain name, so as to obtain an IP address corresponding to the second domain name; and according to the IP address corresponding to the second domain name, interacting with the HTTPDNS server, and analyzing the first domain name.

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

The domain name access device provided in this embodiment may execute the above domain name access method embodiment, and its implementation principle and technical effects are similar, and will not be described herein again.

Fig. 5 is a schematic structural diagram of an electronic device according to 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 a program. In particular, the program may include program code including computer-operating instructions.

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

The processor 301 is configured to execute computer-executable instructions stored in the memory 302 to implement the domain name access method described in the foregoing method embodiment. The processor 301 may be a central processing unit (Central Processing Unit, abbreviated as CPU), or an Application SPECIFIC INTEGRATED Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present application.

Optionally, the electronic device 300 may further comprise 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 and perform communication with each other through buses. The bus may be an industry standard architecture (Industry Standard Architecture, abbreviated ISA) bus, an external device interconnect (PERIPHERAL COMPONENT, abbreviated PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) bus, among others. Buses may be divided into address buses, data buses, control buses, etc., but do not represent only one bus or one type of bus.

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

The present application also provides a computer-readable storage medium, which may include: a U-disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM, random Access Memory), a magnetic disk, or an optical disk, etc., in which program codes may be stored, and in particular, the computer-readable storage medium stores program instructions for the methods in the above 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 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 for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A domain name access method, wherein the method is applied to an electronic device, the method comprising:

2. The method of claim 1, wherein prior to storing the mapping between the first domain name and the IP address in the memory cache of the electronic device and the HTTPDNS cache file in the local disk, the method further comprises:

Acquiring the survival time of the IP address;

and determining that the lifetime of the IP address is not overtime.

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 HTTPDNS cache files further comprise: the survival time of each IP address, the method further comprises:

5. The method of claim 4, wherein if the lifetime of the updated IP address and the IP address is obtained based on the resolution of the local DNS server, before replacing the lifetime of the updated 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, further comprising:

6. The method according to claim 1 or 2, wherein the parsing, by the HTTPDNS server, of the first domain name comprises:

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

Initializing the HTTPDNS cache file in the memory cache.

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

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

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

the memory stores computer-executable instructions;

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

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

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