Domain name access method, device, storage medium and apparatus

Abstract

This invention relates to the field of Internet technology and discloses a domain name access method, device, storage medium, and apparatus. The method includes: obtaining the domain name server policy corresponding to the target domain name; matching the domain name server list corresponding to the currently accessed domain name according to the domain name server policy; the domain name server list being pre-generated based on the historical successful access information of the target domain name; selecting a target IP address from the domain name server list; and accessing the target domain name based on the target IP address. Because this invention selects the target IP address based on the historical successful access information of the domain name and accesses the target domain name based on the target IP address when accessing the domain name, it avoids having to try to connect from the first IP address until a successful connection is found on each access, thereby shortening the network connection time and improving the user experience.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to a domain name access method, device, storage medium and apparatus. Background Technology

[0002] Current browsers typically resolve domain names based on the default Domain Name System (DNS) resolution order, which means they have to try to connect to the first IP address each time until one of them is successfully connected. This increases network connection time and reduces user experience.

[0003] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main objective of this invention is to provide a domain name access method, device, storage medium, and apparatus, which aims to solve the technical problem that in the prior art, browser domain name resolution is usually based on the default DNS resolution order, which leads to the need to try to connect from the first IP address each time until an IP address is successfully connected, thereby increasing network connection time and reducing user experience.

[0005] To achieve the above objectives, the present invention provides a domain name access method, which includes the following steps:

[0006] Obtain the domain name server policy corresponding to the target domain name;

[0007] The domain name server list corresponding to the currently accessed domain name is matched according to the domain name server policy. The domain name server list is pre-generated based on the historical successful access information of the target domain name.

[0008] Select a target IP address from the list of domain name servers, and access the target domain name based on the target IP address.

[0009] Optionally, the step of matching the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy includes:

[0010] Obtain a list of candidate domain name servers according to the domain name server policy;

[0011] Match the list of domain name servers corresponding to the currently accessed domain name in the candidate server list.

[0012] Optionally, the step of obtaining the candidate domain name server list according to the domain name server policy includes:

[0013] Determine the domain name type of the target domain name;

[0014] A candidate domain name server list is obtained based on the domain name server policy and the domain name type.

[0015] Optionally, the step of matching the list of domain name servers corresponding to the currently accessed domain name in the candidate server list includes:

[0016] Obtain the domain identifier of the currently accessed domain;

[0017] The candidate server list is matched with the domain name server list corresponding to the domain name identifier.

[0018] Optionally, after the step of selecting a target IP address from the list of domain name servers and accessing the target domain name based on the target IP address, the method further includes:

[0019] When the access result of the target domain name is successful, the target IP address is used as the header IP address of the domain name server list;

[0020] The list of domain name servers is updated based on the IP addresses in the header.

[0021] Optionally, after the step of selecting a target IP address from the list of domain name servers and accessing the target domain name based on the target IP address, the method further includes:

[0022] When the access result of the target domain name is access failure, the target IP address is used as the tail IP address of the domain name server list;

[0023] The list of domain name servers is updated based on the IP address at the end of the table.

[0024] Optionally, after the step of selecting a target IP address from the list of domain name servers and accessing the target domain name based on the target IP address, the method further includes:

[0025] If the access result for the target domain name is an access failure, a new target IP address is selected from the list of domain name servers;

[0026] Re-access the target domain name using the newly selected target IP address.

[0027] Optionally, the step of obtaining the domain name server policy corresponding to the target domain name includes:

[0028] Find the management platform corresponding to the current browser;

[0029] Obtain the domain name server policy corresponding to the target domain name from the management platform.

[0030] Optionally, the step of obtaining the domain name server policy corresponding to the target domain name from the management platform includes:

[0031] Establish a communication connection with the management platform;

[0032] Based on the communication connection, the domain name server policy corresponding to the target domain name is obtained from the management platform.

[0033] Optionally, after the step of matching the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy, the method further includes:

[0034] If no matching domain name server list is found for the currently accessed domain name, obtain the default DNS resolution order;

[0035] The target domain name is accessed based on the default DNS resolution order.

[0036] Optionally, after the step of obtaining the domain name server policy corresponding to the target domain name, the method further includes:

[0037] If the domain name server policy corresponding to the target domain name is not obtained, the default DNS resolution order is obtained;

[0038] The target domain name is accessed based on the default DNS resolution order.

[0039] In addition, to achieve the above objectives, the present invention also proposes a domain name access device, which includes a memory, a processor, and a domain name access program stored in the memory and executable on the processor, the domain name access program being configured to implement the domain name access method as described above.

[0040] In addition, to achieve the above objectives, the present invention also proposes a storage medium storing a domain name access program, which, when executed by a processor, implements the domain name access method as described above.

[0041] In addition, to achieve the above objectives, the present invention also proposes a domain name access device, which includes: a policy acquisition module, a list matching module, and a domain name access module;

[0042] The policy acquisition module is used to acquire the domain name server policy corresponding to the target domain name;

[0043] The list matching module is used to match the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy. The list of domain name servers is pre-generated based on the historical successful access information of the target domain name.

[0044] The domain name access module is used to select a target IP address from the list of domain name servers and access the target domain name based on the target IP address.

[0045] Optionally, the list matching module is further configured to obtain a list of candidate domain name servers according to the domain name server policy;

[0046] The list matching module is also used to match the list of domain name servers corresponding to the currently accessed domain name in the candidate server list.

[0047] Optionally, the list matching module is further configured to determine the domain name type of the target domain name;

[0048] The list matching module is also used to obtain a list of candidate domain name servers based on the domain name server policy and the domain name type.

[0049] Optionally, the list matching module is further configured to obtain the domain name identifier of the currently accessed domain name;

[0050] The list matching module is also used to match the list of domain name servers corresponding to the domain name identifier in the candidate server list.

[0051] Optionally, the domain name access device further includes: a list update module;

[0052] The list update module is used to use the target IP address as the header IP address of the domain name server list when the access result of the target domain name is successful.

[0053] The list update module is also used to update the list of domain name servers based on the IP address in the table header.

[0054] Optionally, the list update module is further configured to use the target IP address as the tail IP address of the domain name server list when the access result of the target domain name is access failure;

[0055] The list update module is also used to update the domain name server list based on the IP address at the end of the list.

[0056] Optionally, the domain name access device further includes: a re-access module;

[0057] The re-access module is used to reselect the target IP address from the list of domain name servers when the access result of the target domain name is an access failure.

[0058] The re-access module is also used to re-access the target domain name based on the reselected target IP address.

[0059] This invention discloses a strategy for obtaining the domain name server corresponding to the target domain name. The strategy matches a list of domain name servers corresponding to the currently accessed domain name. This list is pre-generated based on historical successful access information of the target domain name. A target IP address is selected from the list, and the target domain name is accessed based on that IP address. Because this invention selects the target IP address based on the historical successful access information of the domain name and accesses the target domain name based on that IP address, it avoids having to try to connect from the first IP address until a successful connection is found on each access, thereby shortening network connection time and improving user experience. Attached Figure Description

[0060] Figure 1 This is a schematic diagram of the structure of the domain name access device in the hardware operating environment involved in the embodiments of the present invention;

[0061] Figure 2 This is a flowchart illustrating the first embodiment of the domain name access method of the present invention;

[0062] Figure 3 This is a flowchart illustrating the second embodiment of the domain name access method of the present invention;

[0063] Figure 4 This is a flowchart illustrating the third embodiment of the domain name access method of the present invention;

[0064] Figure 5 This is a structural block diagram of the first embodiment of the domain name access device of the present invention.

[0065] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0066] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0067] Reference Figure 1 , Figure 1 This is a schematic diagram of the domain name access device structure of the hardware operating environment involved in the embodiments of the present invention.

[0068] like Figure 1As shown, the domain name access device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen, and optionally, it may also include a standard wired interface or a wireless interface. In this invention, the wired interface of the user interface 1003 may be a USB interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (RAM) or a non-volatile memory (NVM), such as a disk drive. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.

[0069] Those skilled in the art will understand that Figure 1 The structure shown does not constitute a limitation on the domain name access device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0070] like Figure 1 As shown, the memory 1005, which is identified as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a domain name access program.

[0071] exist Figure 1 In the domain name access device shown, the network interface 1004 is mainly used to connect to the backend server and communicate data with the backend server; the user interface 1003 is mainly used to connect to the user equipment; the domain name access device calls the domain name access program stored in the memory 1005 through the processor 1001 and executes the domain name access method provided in the embodiment of the present invention.

[0072] Based on the above hardware structure, an embodiment of the domain name access method of the present invention is proposed.

[0073] Reference Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the domain name access method of the present invention, which presents the first embodiment of the domain name access method of the present invention.

[0074] In the first embodiment, the domain name access method includes the following steps:

[0075] Step S10: Obtain the domain name server policy corresponding to the target domain name.

[0076] It should be understood that existing browsers typically access domain names based on the default DNS resolution order. This means that each time a connection is attempted, it starts from the first IP address until one IP address is successfully connected. When accessing the same domain name again, the already connected IP address will not be placed first, which increases network connection time and reduces user experience.

[0077] Therefore, in order to overcome the above-mentioned defects, in this embodiment, when accessing a domain name, the target IP address is selected based on the historical successful access information of the domain name, and the target domain name is accessed according to the target IP address. This avoids having to try to connect from the first IP address until a successful connection is found on each access, thereby shortening the network connection time and improving the user experience.

[0078] It should be understood that the execution subject of the method in this embodiment can be a domain name access device with data processing, network communication and program running functions, such as a terminal device with a browser, or other electronic devices that can achieve the same or similar functions. This embodiment does not limit this.

[0079] It should be noted that the target domain name can be any domain name that needs to be accessed.

[0080] Domain name server policies can be pre-configured by the administrators of the management platform; or they can be automatically generated by the management platform based on the terminal situation. This embodiment does not impose any restrictions on this.

[0081] Furthermore, to ensure normal access, after step S10, the following steps are also included:

[0082] If the domain name server policy corresponding to the target domain name is not obtained, the default DNS resolution order is obtained;

[0083] The target domain name is accessed based on the default DNS resolution order.

[0084] It is understandable that, in order to ensure normal access, in this embodiment, when the domain name server policy corresponding to the target domain name is not obtained, the target domain name is accessed based on the default DNS resolution order.

[0085] It should be noted that the default DNS resolution order can be preset.

[0086] Step S20: Match the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy. The list of domain name servers is pre-generated based on the historical successful access information of the target domain name.

[0087] It should be understood that pre-generating a domain name server list based on the historical successful access information of the target domain name can be achieved by determining the IP addresses of successful access and the IP addresses of failed access based on the historical successful access information of the target domain name, setting the IP addresses of successful access at the head of the domain name server list, and setting the IP addresses of failed access at the tail of the domain name server list, thus obtaining the domain name server list.

[0088] It is understandable that matching the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy can be done by checking whether the current accessed domain name is included in the server list according to the domain name server policy, and if so, using that server list as the list of domain name servers corresponding to the current accessed domain name.

[0089] Furthermore, to ensure normal access, after step S20, the following steps are also included:

[0090] If no matching domain name server list is found for the currently accessed domain name, obtain the default DNS resolution order;

[0091] The target domain name is accessed based on the default DNS resolution order.

[0092] It should be understood that, in order to ensure normal access, in this embodiment, when no matching domain name server list is found for the currently accessed domain name, the target domain name is accessed based on the default DNS resolution order.

[0093] It should be noted that the default DNS resolution order can be preset.

[0094] Step S30: Select a target IP address from the list of domain name servers, and access the target domain name based on the target IP address.

[0095] It's understandable that selecting a target IP address from a list of domain name servers can be based on the order in which the IP addresses are listed. For example, the IP address that appears first in the list could be used as the target IP address.

[0096] Furthermore, to avoid access failure, after step S30, the following steps are also included:

[0097] If the access result for the target domain name is an access failure, a new target IP address is selected from the list of domain name servers;

[0098] Re-access the target domain name using the newly selected target IP address.

[0099] It should be understood that, in order to avoid access failure, in this embodiment, when the access result of the target domain name is access failure, the target IP address is reselected from the list of domain name servers to access the target domain name again.

[0100] It is understandable that reselecting a target IP address from the list of domain name servers can be based on the order in which the IP addresses in the list are arranged.

[0101] In the first embodiment, a strategy for obtaining the domain name server corresponding to the target domain name is disclosed. The strategy matches a list of domain name servers corresponding to the currently accessed domain name. This list is pre-generated based on historical successful access information of the target domain name. A target IP address is selected from the list, and the target domain name is accessed based on that IP address. Because this embodiment selects the target IP address based on the historical successful access information of the domain name and accesses the target domain name based on that IP address during domain name access, it avoids having to try to connect from the first IP address until a successful connection is found on each access, thereby shortening network connection time and improving user experience.

[0102] Reference Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the domain name access method of the present invention, based on the above. Figure 2 The first embodiment shown presents a second embodiment of the domain name access method of the present invention.

[0103] In the second embodiment, step S10 includes:

[0104] Step S101: Locate the management platform corresponding to the current browser.

[0105] It should be understood that, in order to ensure the unified distribution of domain name server policies, in this embodiment, the domain name server policy corresponding to the target domain name can be obtained from the management platform.

[0106] It should be noted that the management platform can be a platform for backend management of the browser.

[0107] Understandably, finding the management platform corresponding to the current browser can be done by searching a preset platform table. This preset platform table includes the mapping between browsers and management platforms, and this mapping can be pre-defined.

[0108] Step S102: Obtain the domain name server policy corresponding to the target domain name from the management platform.

[0109] It should be understood that the domain name server policy can be pre-configured by the administrators of the management platform; or it can be automatically generated by the management platform according to the terminal situation. This embodiment does not limit this.

[0110] It is understood that obtaining the domain name server policy corresponding to the target domain name from the management platform can be achieved by establishing a communication connection with the management platform and obtaining the domain name server policy corresponding to the target domain name from the management platform based on the communication connection.

[0111] In the second embodiment, the method of finding the management platform corresponding to the current browser and obtaining the domain name server policy corresponding to the target domain name from the management platform is disclosed. Since this embodiment obtains the domain name server policy corresponding to the target domain name from the management platform, it can ensure the unified distribution of domain name server policies.

[0112] In the second embodiment, step S20 includes:

[0113] Step S201: Obtain a list of candidate domain name servers according to the domain name server policy.

[0114] It should be understood that, in order to improve the matching speed of the domain name server list, in this embodiment, a candidate domain name server list can be obtained first according to the domain name server policy, and then the domain name server list corresponding to the domain name identifier can be matched in the candidate server list.

[0115] Furthermore, to improve the accuracy of the candidate domain name server list, step S201 includes:

[0116] Determine the domain name type of the target domain name;

[0117] A candidate domain name server list is obtained based on the domain name server policy and the domain name type.

[0118] Understandably, in order to improve the accuracy of the candidate domain name server list, this embodiment also obtains the candidate domain name server list based on the domain name type of the target domain name.

[0119] It should be noted that domain names can be classified according to different languages; they can also be classified according to different domains; they can also be classified according to different management organizations; and they can also be classified according to different suffixes. This embodiment does not limit these categories.

[0120] It should be understood that obtaining a candidate name server list based on name server policies and name types can be achieved by first matching the initial name server list corresponding to the name type from the overall name server table, and then obtaining a candidate name server list from the initial name server list based on the name server policies.

[0121] Step S202: Match the list of domain name servers corresponding to the currently accessed domain name in the candidate server list.

[0122] It is understandable that matching the list of domain name servers corresponding to the currently accessed domain name in the candidate server list can be done by checking whether the candidate server list includes the currently accessed domain name, and if so, then using the candidate server list as the list of domain name servers corresponding to the currently accessed domain name.

[0123] Furthermore, in order to improve the matching speed, step S202 includes:

[0124] Obtain the domain identifier of the currently accessed domain;

[0125] The candidate server list is matched with the domain name server list corresponding to the domain name identifier.

[0126] It should be understood that, in order to improve the matching speed, in this embodiment, the corresponding list of domain name servers can be matched in the candidate server list based on the domain name identifier of the currently accessed domain name.

[0127] It should be noted that domain name identifiers can be used to distinguish different domain names.

[0128] In the second embodiment, a candidate domain name server list is obtained according to the domain name server policy, and the domain name server list corresponding to the currently accessed domain name is matched in the candidate server list. Since this embodiment first obtains the candidate domain name server list according to the domain name server policy, and then matches the domain name server list corresponding to the domain name identifier in the candidate server list, the matching speed can be improved.

[0129] Reference Figure 4 , Figure 4 This is a flowchart illustrating the third embodiment of the domain name access method of the present invention. Based on the above embodiments, the third embodiment of the domain name access method of the present invention is proposed.

[0130] In the third embodiment, after step S30, the method further includes:

[0131] Step S40: When the access result of the target domain name is successful, the target IP address is used as the header IP address of the domain name server list.

[0132] It should be understood that, in order to ensure that the IP address of a successful access is at the head of the domain name server list and to improve the access speed of subsequent accesses, in this embodiment, when the access result of the target domain name is successful, the target IP address is also placed at the head of the domain name server list.

[0133] Step S50: Update the list of domain name servers according to the IP address in the header.

[0134] It is understandable that updating the DNS server list based on the header IP address could be achieved by setting the header IP address in the header of the DNS server list.

[0135] In the third embodiment, it is disclosed that when the access result of the target domain name is successful, the target IP address is used as the header IP address of the domain name server list, and the domain name server list is updated according to the header IP address. Since this embodiment also places the target IP address at the header of the domain name server list when the access result of the target domain name is successful, it can ensure that the IP address of successful access is at the header of the domain name server list, thereby improving the access speed of the next access.

[0136] In the third embodiment, after step S30, the method further includes:

[0137] Step S40': When the access result of the target domain name is access failure, the target IP address is used as the tail IP address of the domain name server list.

[0138] It should be understood that, in order to ensure that the IP address of the failed access is at the end of the domain name server list and to improve the access speed of the next access, in this embodiment, when the access result of the target domain name is failed, the target IP address is also placed at the end of the domain name server list.

[0139] Step S50': Update the domain name server list based on the IP address at the end of the table.

[0140] It is understandable that updating the DNS server list based on the tail IP address could be done by setting the tail IP address at the end of the DNS server list.

[0141] In the third embodiment, when the access result of the target domain name is access failure, the target IP address is used as the tail IP address of the domain name server list, and the domain name server list is updated according to the tail IP address. Since this embodiment also places the target IP address at the tail of the domain name server list when the access result of the target domain name is access failure, it can ensure that the IP address of the access failure is at the tail of the domain name server list, thereby improving the access speed of the next access.

[0142] Furthermore, this embodiment of the invention also proposes a storage medium storing a domain name access program, which, when executed by a processor, implements the domain name access method as described above.

[0143] In addition, refer to Figure 5The present invention also proposes a domain name access device, which includes: a policy acquisition module 10, a list matching module 20, and a domain name access module 30.

[0144] The policy acquisition module 10 is used to acquire the domain name server policy corresponding to the target domain name.

[0145] It should be understood that existing browsers typically access domain names based on the default DNS resolution order. This means that each time a connection is attempted, it starts from the first IP address until one IP address is successfully connected. When accessing the same domain name again, the already connected IP address will not be placed first, which increases network connection time and reduces user experience.

[0146] Therefore, in order to overcome the above-mentioned defects, in this embodiment, when accessing a domain name, the target IP address is selected based on the historical successful access information of the domain name, and the target domain name is accessed according to the target IP address. This avoids having to try to connect from the first IP address until a successful connection is found on each access, thereby shortening the network connection time and improving the user experience.

[0147] It should be noted that the target domain name can be any domain name that needs to be accessed.

[0148] Domain name server policies can be pre-configured by the administrators of the management platform; or they can be automatically generated by the management platform based on the terminal situation. This embodiment does not impose any restrictions on this.

[0149] Furthermore, to ensure normal access, the domain name access device also includes: a regular access module;

[0150] The regular access module is used to obtain the default DNS resolution order when the domain name server policy corresponding to the target domain name is not obtained.

[0151] The regular access module is also used to access the target domain name based on the default DNS resolution order.

[0152] It is understandable that, in order to ensure normal access, in this embodiment, when the domain name server policy corresponding to the target domain name is not obtained, the target domain name is accessed based on the default DNS resolution order.

[0153] It should be noted that the default DNS resolution order can be preset.

[0154] The list matching module 20 is used to match the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy. The list of domain name servers is pre-generated based on the historical successful access information of the target domain name.

[0155] It should be understood that pre-generating a domain name server list based on the historical successful access information of the target domain name can be achieved by determining the IP addresses of successful access and the IP addresses of failed access based on the historical successful access information of the target domain name, setting the IP addresses of successful access at the head of the domain name server list, and setting the IP addresses of failed access at the tail of the domain name server list, thus obtaining the domain name server list.

[0156] It is understandable that matching the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy can be done by checking whether the current accessed domain name is included in the server list according to the domain name server policy, and if so, using that server list as the list of domain name servers corresponding to the current accessed domain name.

[0157] Furthermore, to ensure normal access, the domain name access device also includes: a regular access module;

[0158] The regular access module is used to obtain the default DNS resolution order when no match is found in the list of domain name servers corresponding to the currently accessed domain name;

[0159] The regular access module is also used to access the target domain name based on the default DNS resolution order.

[0160] It should be understood that, in order to ensure normal access, in this embodiment, when no matching domain name server list is found for the currently accessed domain name, the target domain name is accessed based on the default DNS resolution order.

[0161] It should be noted that the default DNS resolution order can be preset.

[0162] The domain name access module 30 is used to select a target IP address from the list of domain name servers and access the target domain name based on the target IP address.

[0163] It's understandable that selecting a target IP address from a list of domain name servers can be based on the order in which the IP addresses are listed. For example, the IP address that appears first in the list could be used as the target IP address.

[0164] Furthermore, to avoid access failure, the domain name access device also includes a re-access module;

[0165] The re-access module is used to reselect the target IP address from the list of domain name servers when the access result of the target domain name is an access failure.

[0166] The re-access module is also used to re-access the target domain name based on the reselected target IP address.

[0167] It should be understood that, in order to avoid access failure, in this embodiment, when the access result of the target domain name is access failure, the target IP address is reselected from the list of domain name servers to access the target domain name again.

[0168] It is understandable that reselecting a target IP address from the list of domain name servers can be based on the order in which the IP addresses in the list are arranged.

[0169] In this embodiment, a strategy for obtaining the domain name server corresponding to the target domain name is disclosed. The strategy matches the list of domain name servers corresponding to the currently accessed domain name. This list is pre-generated based on the historical successful access information of the target domain name. A target IP address is selected from the list, and the target domain name is accessed based on that IP address. Because this embodiment selects the target IP address based on the historical successful access information of the domain name and accesses the target domain name based on that IP address during domain name access, it avoids having to try to connect from the first IP address until a successful connection is found on each access, thereby shortening network connection time and improving user experience.

[0170] Other embodiments or specific implementations of the domain name access device described in this invention can be found in the above-described method embodiments, and will not be repeated here.

[0171] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0172] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0173] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as a read-only memory image (ROM) / random access memory (RAM), magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0174] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A domain name access method characterized by, The domain name access method includes the following steps: Obtain the domain name server policy corresponding to the target domain name; The domain name server list is matched according to the domain name server policy to the list of domain name servers corresponding to the currently accessed domain name. The list of domain name servers is pre-generated based on the historical successful access information of the target domain name. Select a target IP address from the list of domain name servers, and access the target domain name based on the target IP address; The step of selecting a target IP address from the list of domain name servers and accessing the target domain name based on the target IP address further includes: When the access result of the target domain name is successful, the target IP address is used as the header IP address of the domain name server list, and the domain name server list is updated according to the header IP address; When the access result of the target domain name is access failure, the target IP address is used as the tail IP address of the domain name server list, and the domain name server list is updated according to the tail IP address; Selecting a target IP address from the list of domain name servers includes: Use the IP address that appears first in the list of domain name servers as the target IP address.

2. The domain name access method of claim 1, wherein, The step of matching the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy includes: Obtain a list of candidate domain name servers according to the domain name server policy; Match the list of domain name servers corresponding to the currently accessed domain name in the candidate server list.

3. The domain name access method as described in claim 2, characterized in that, The step of obtaining the candidate domain name server list according to the domain name server policy includes: Determine the domain name type of the target domain name; A candidate domain name server list is obtained based on the domain name server policy and the domain name type.

4. The domain name access method as described in claim 2, characterized in that, The step of matching the list of domain name servers corresponding to the currently accessed domain name in the candidate server list includes: Obtain the domain identifier of the currently accessed domain; The candidate server list is matched with the domain name server list corresponding to the domain name identifier.

5. The domain name access method as described in any one of claims 1 to 4, characterized in that, After the step of selecting a target IP address from the list of domain name servers and accessing the target domain name based on the target IP address, the method further includes: If the access result for the target domain name is an access failure, a new target IP address is selected from the list of domain name servers; Re-access the target domain name using the newly selected target IP address.

6. The domain name access method as described in any one of claims 1 to 4, characterized in that, The step of obtaining the domain name server policy corresponding to the target domain name includes: Find the management platform corresponding to the current browser; Obtain the domain name server policy corresponding to the target domain name from the management platform.

7. The domain name access method as described in claim 6, characterized in that, The step of obtaining the domain name server policy corresponding to the target domain name from the management platform includes: Establish a communication connection with the management platform; Based on the communication connection, the domain name server policy corresponding to the target domain name is obtained from the management platform.

8. The domain name access method as described in any one of claims 1 to 4, characterized in that, After the step of matching the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy, the method further includes: If no matching domain name server list is found for the currently accessed domain name, obtain the default DNS resolution order; The target domain name is accessed based on the default DNS resolution order.

9. The domain name access method as described in any one of claims 1 to 4, characterized in that, Following the step of obtaining the domain name server policy corresponding to the target domain name, the method further includes: If the domain name server policy corresponding to the target domain name is not obtained, the default DNS resolution order is obtained; The target domain name is accessed based on the default DNS resolution order.

10. A domain name access device, characterized in that, The domain name access device includes: a memory, a processor, and a domain name access program stored in the memory and executable on the processor, wherein the domain name access program, when executed by the processor, implements the domain name access method as described in any one of claims 1 to 9.

11. A storage medium, characterized in that, The storage medium stores a domain name access program, which, when executed by a processor, implements the domain name access method as described in any one of claims 1 to 9.

12. A domain name access device, characterized in that, The domain name access device includes: a policy acquisition module, a list matching module, and a domain name access module; The policy acquisition module is used to acquire the domain name server policy corresponding to the target domain name; The list matching module is used to match the list of domain name servers corresponding to the currently accessed domain name according to the domain name server policy. The list of domain name servers is pre-generated based on the historical successful access information of the target domain name. The domain name access module is used to select a target IP address from the list of domain name servers and access the target domain name based on the target IP address; The list update module is further configured to, when the access result of the target domain name is access failure, use the target IP address as the tail IP address of the domain name server list and update the domain name server list according to the tail IP address; The list update module is further configured to, when the access result of the target domain name is access failure, use the target IP address as the tail IP address of the domain name server list, and update the domain name server list according to the tail IP address; The domain name access module is also used to select the IP address that appears first in the list of domain name servers as the target IP address.

13. The domain name access device as described in claim 12, characterized in that, The list matching module is also used to obtain a list of candidate domain name servers according to the domain name server policy; The list matching module is also used to match the list of domain name servers corresponding to the currently accessed domain name in the candidate server list.

14. The domain name access device as described in claim 13, characterized in that, The list matching module is also used to determine the domain name type of the target domain name; The list matching module is also used to obtain a list of candidate domain name servers based on the domain name server policy and the domain name type.

15. The domain name access device as described in claim 13, characterized in that, The list matching module is also used to obtain the domain name identifier of the currently accessed domain name; The list matching module is also used to match the list of domain name servers corresponding to the domain name identifier in the candidate server list.

16. The domain name access device as claimed in any one of claims 12 to 15, characterized in that, The domain name access device further includes: a re-access module; The re-access module is used to reselect the target IP address from the list of domain name servers when the access result of the target domain name is an access failure. The re-access module is also used to re-access the target domain name based on the reselected target IP address.

Images