Content delivery network-based domain name resolution method and apparatus, device, and medium

By determining the target hosted domain based on the domain name suffix in authoritative DNS and matching the subdomain name, the domain name resolution results are directly obtained, and the delay and efficiency problems caused by iterative queries during the domain name resolution process are solved, which significantly improves the query efficiency and success rate.

WO2024245073A1PCT designated stage expired Publication Date: 2024-12-05BEIJING VOLCANO ENGINE TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/094722
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-06-02
Filing Date
2024-05-22
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

In authoritative DNS, the domain name resolution process requires multiple iterations of query, resulting in an increase in query latency and an increase in timeout probability, affecting network efficiency and response speed.

Method used

By receiving the domain name to be parsed, determining the target hosted domain based on its domain name suffix, and matching the domain name to be parsed with multiple subdomains, the resolution result is directly determined, reducing the number of iterative queries for authoritative DNS and improving query efficiency.

Benefits of technology

It effectively reduces network overhead and response delay, improves domain name resolution efficiency and success rate, and improves server performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024094722_05122024_PF_FP_ABST
    Figure CN2024094722_05122024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a content delivery network-based domain name resolution method and apparatus, a device, and a medium. The domain name resolution method is applied to an authoritative domain name system and comprises: receiving a domain name to be resolved sent by a local domain name system; according to the domain name suffix of said domain name, determining a target hosting domain, a plurality of first sub-domain names being recorded in the target hosting domain; matching the domain name to be resolved with the plurality of first sub-domain names to determine a first sub-domain name that matches said domain name; on the basis of the first sub-domain name that matches said domain name, determining a resolution result of the domain name to be resolved, and feeding back the resolution result to the local domain name system, the local domain name system being used for sending the resolution result to a client.
Need to check novelty before this filing date? Find Prior Art

Description

Domain name resolution method, device, equipment and medium based on content distribution network

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on and claims priority to the Chinese patent application with application number 202310652533.7 and application date June 2, 2023. The disclosed content of the Chinese patent application is hereby introduced as a whole into this application. Technical Field

[0003] The present disclosure relates to the field of domain name resolution, and in particular to a method, apparatus, device, and medium for domain name resolution based on a content distribution network. Background Art

[0004] In Content Delivery Networks (CDNs), it is a common technology to achieve local user access by resolving domain names through the Domain Name System (DNS).

[0005] Summary of the Invention

[0006] The present disclosure provides a method, apparatus, device and medium for domain name resolution based on a content distribution network.

[0007] In a first aspect, the present disclosure provides a domain name resolution method, applied to an authoritative domain name system, comprising:

[0008] Receive the domain name to be resolved sent by the local domain name system. The domain name to be resolved is sent by the client to the local domain name system;

[0009] Determine a target hosting domain according to the domain name suffix of the domain name to be resolved, where the target hosting domain has multiple first subdomain names recorded therein;

[0010] Matching the domain name to be resolved with multiple first subdomains to determine the first subdomain that matches the domain name to be resolved;

[0011] Based on the first subdomain name that matches the domain name to be resolved, a resolution result of the domain name to be resolved is determined, and the resolution result is fed back to a local domain name system, which is used to send the resolution result to the client.

[0012] In a second aspect, the present disclosure provides a domain name resolution device, which is applied to an authoritative domain name system, and includes:

[0013] A receiving module is used to receive a domain name to be resolved sent by a local domain name system. The domain name to be resolved is sent by a client to the local domain name system.

[0014] A first execution module is configured to determine a target hosting domain according to a domain name suffix of the domain name to be resolved, wherein the target hosting domain has a plurality of first subdomain names recorded therein;

[0015] A second execution module is configured to match the domain name to be resolved with the plurality of first subdomain names, and determine a first subdomain name that matches the domain name to be resolved;

[0016] The first feedback module is used to determine the resolution result of the domain name to be resolved based on the first subdomain name matching the domain name to be resolved, and to feed back the resolution result to the local domain name resolution system, which is used to send the resolution result to the client.

[0017] In a third aspect, the present disclosure provides an electronic device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the domain name resolution method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0018] In a fourth aspect, the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the domain name resolution method of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0020] FIG1 is a schematic diagram of domain name resolution interaction in related technology;

[0021] FIG2 is a flow chart of a domain name resolution method according to an embodiment of the present disclosure;

[0022] FIG3 is a flow chart of another domain name resolution method according to an embodiment of the present disclosure;

[0023] FIG4 is a schematic diagram of a hosting domain recording method according to an embodiment of the present disclosure;

[0024] FIG5 is a schematic diagram of domain name resolution interaction according to an embodiment of the present disclosure;

[0025] FIG6 is another diagram of domain name resolution interaction according to an embodiment of the present disclosure;

[0026] FIG7 is a flow chart of another domain name resolution method according to an embodiment of the present disclosure;

[0027] FIG8 is a structural block diagram of a domain name resolution device according to an embodiment of the present disclosure;

[0028] FIG9 is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] To make the purpose, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present disclosure.

[0030] In related technologies, authoritative DNS configures a corresponding alias record (Canonical Name, CNAME) type for an exposed domain name to point it to another domain name. The domain name pointed to by the CNAME can be directly configured as another record type such as A / AAAA, or it can continue to point to the next level CNAME to achieve secondary or tertiary scheduling. When the local DNS attempts to obtain the original domain name resolution, the authoritative DNS will return a CNAME, and the local DNS will continue to iterate the query until the complete resolution link is obtained.

[0031] For example, the domain name resolution process can be shown as in Figure 1. The client sends the domain name to be resolved (for example, www.a.com) to the Local DNS. The Local DNS sends a query to the authoritative DNS based on the received domain name to be resolved, so that it can be resolved through the authoritative DNS. The authoritative DNS resolves the domain name to be resolved based on the received domain name to be resolved and the built-in CNAME record, and obtains the mapped domain name (www.a.com.gslb.com) pointed to by the domain name to be resolved, and feeds the mapped domain name back to the Local DNS. The Local DNS sends another query to the authoritative DNS based on the received mapped domain name, and sends the mapped domain name to the authoritative DNS to determine the mapping address. The authoritative DNS queries again based on the received mapped domain name, obtains the mapping address (1.1.1.1) corresponding to the mapped domain name, and sends the mapping address to the Local DNS. The Local DNS uses the mapped domain name and the mapped address as the resolution result of the domain name to be resolved, and then sends the resolution result to the client, thereby completing the resolution.

[0032] From the above implementation process, it can be seen that the Local DNS needs to iterate and query the authoritative DNS multiple times before obtaining the resolution result of the domain name resolution, which will increase the corresponding delay of the domain name query and also cause the probability of timeout.

[0033] In view of this, the embodiment of the present disclosure provides a domain name resolution method applied to an authoritative domain name system, including: receiving a domain name to be resolved sent by a local domain name system, the domain name to be resolved is sent by a client to the local domain name system; determining a target hosting domain based on the domain name suffix of the domain name to be resolved, wherein a plurality of first subdomain names are recorded in the target hosting domain; matching the domain name to be resolved with the plurality of first subdomain names to determine the first subdomain name that matches the domain name to be resolved; determining a resolution result of the domain name to be resolved based on the first subdomain name that matches the domain name to be resolved, and feeding back the resolution result to the local domain name system, which is used to send the resolution result to the client. The target hosting domain is determined by the suffix of the domain name to be resolved, and then based on the plurality of first subdomain names in the target hosting domain, the resolution result of the domain name to be resolved is obtained and sent to the local domain name system, so that the local domain name system only needs to query the authoritative domain name system once to obtain the resolution result, thereby effectively improving the query efficiency and greatly reducing the network overhead and response delay.

[0034] According to an embodiment of the present disclosure, an embodiment of a domain name resolution method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0035] In this embodiment, a domain name resolution method is provided, which can be used in an authoritative domain name system deployed on an electronic device or a server. FIG2 is a flow chart of the domain name resolution method according to an embodiment of the present disclosure. As shown in FIG2 , the process includes the following steps:

[0036] Step S201: receiving a domain name to be resolved sent by a local domain name system.

[0037] In the embodiment of the present disclosure, the domain name to be resolved is sent by the client to the local domain name system. The domain name to be resolved can be any domain name that the client needs to request access to. For example, the domain name to be resolved can be www.a.com.

[0038] Step S202: determining the target hosting domain according to the domain name suffix of the domain name to be resolved.

[0039] In the embodiment of the present disclosure, the authoritative DNS includes multiple hosted domains (zones), each of which records multiple first subdomains, and each first subdomain is a complete subdomain. That is, the authoritative DNS uses CNAME records to perform domain name resolution.

[0040] To facilitate quick query, the target hosting domain is determined from the authoritative DNS according to the domain name suffix of the domain name to be resolved, so as to perform domain name resolution through multiple first subdomains in the target hosting domain, thereby improving query efficiency.

[0041] Step S203: Match the domain name to be resolved with multiple first subdomain names to determine a first subdomain name that matches the domain name to be resolved.

[0042] In the embodiment of the present disclosure, since each first subdomain name is a complete subdomain name, the domain name to be resolved is matched with each first subdomain name in the target hosting domain respectively, and the first subdomain name that matches the domain name to be resolved is determined from multiple first subdomain names, and then it can be determined that the resolution result can be directly obtained through the target hosting domain.

[0043] Step S204: determining a resolution result of the domain name to be resolved based on the first subdomain name that matches the domain name to be resolved, and feeding back the resolution result to the local domain name system.

[0044] In the embodiment of the present disclosure, the resolution result of the domain name to be resolved can be quickly obtained through the first subdomain name that matches the domain name to be resolved, and then the resolution result is fed back to the local domain name system, so that the local domain name system can directly send the resolution result to the client without having to iterate the query to the authoritative DNS again, thereby effectively improving the efficiency of domain name resolution and quickly completing the domain name query.

[0045] The domain name resolution method provided in this embodiment can effectively reduce the number of times the local domain name system queries the authoritative DNS, so that the local domain name system can obtain the resolution result sent to the client by querying the authoritative DNS once, thereby greatly reducing network overhead and response delay, thereby effectively improving domain name resolution efficiency, quickly completing domain name queries, and helping to improve server performance.

[0046] In this embodiment, a domain name resolution method is provided, which can be used in an authoritative domain name system deployed on an electronic device or a server. FIG3 is a flow chart of the domain name resolution method according to an embodiment of the present disclosure. As shown in FIG3 , the process includes the following steps:

[0047] Step S301: Receive a domain name to be resolved sent by a local domain name system. Please refer to step S201 of the embodiment shown in FIG2 for details, which will not be repeated here.

[0048] Step S302: Determine the target hosting domain according to the domain name suffix of the domain name to be resolved.

[0049] Specifically, the above step S302 includes:

[0050] Step S3021: Determine the domain name suffix with the longest character length as the second subdomain name of the domain name to be resolved.

[0051] In the embodiment of the present disclosure, in order to clarify the query direction and improve the query efficiency, the suffix with the longest character length in the domain name suffix is ​​determined as the second subdomain name of the domain name to be resolved, so that when the target hosting domain is subsequently determined, the longest suffix matching principle can be met.

[0052] Step S3022: Determine the target hosting domain based on the second subdomain name.

[0053] In the disclosed embodiment, multiple hosted domains are recorded in the authoritative DNS in a tree format. For example, a dictionary tree or a red-black tree format can be used. To improve matching efficiency, the target hosted domain is determined from the multiple hosted domains in the authoritative DNS based on the second subdomain name.

[0054] In some optional implementations, the above step S3022 includes:

[0055] In step a, in response to determining that a hosted domain corresponding to the second subdomain name exists in the authoritative domain name system, the hosted domain corresponding to the second subdomain name is determined as a target hosted domain.

[0056] Step b: in response to determining that there is no hosted domain corresponding to the second subdomain in the authoritative domain name system, determining a third subdomain according to the domain name suffix of the domain name to be resolved; and determining a target hosted domain according to the third subdomain.

[0057] In this method, if the hosted domain corresponding to the second subdomain name does not exist in the authoritative DNS, it indicates that the authoritative DNS cannot resolve the domain name to be resolved according to the second subdomain name. To avoid missed resolution, the third subdomain name is determined based on the domain name suffix of the domain name to be resolved, and then the target hosted domain is determined based on the third subdomain name. The character length of the domain name suffix of the third subdomain name is less than the character length of the domain name suffix of the second subdomain name. For example, the character length of the suffix to be queried can be shortened bit by bit, and the third subdomain name can be determined based on the domain name suffix of the domain name to be resolved, thereby improving the accuracy of resolution.

[0058] Step S303: Match the domain name to be resolved with multiple first subdomains to determine the first subdomain that matches the domain name to be resolved. For details, please refer to step S203 of the embodiment shown in FIG2 , which will not be described in detail here.

[0059] Step S304: determining a resolution result of the domain name to be resolved based on the first subdomain name that matches the domain name to be resolved, and feeding back the resolution result to the local domain name system.

[0060] In some optional implementations, in response to determining that the authoritative domain name system has multiple levels, the resolution result of the authoritative domain name system at the last level is fed back to the local domain name system, thereby achieving the purpose of hiding the query link and hiding technical details from users.

[0061] Step S305: In response to determining that the target hosted domain does not exist in the authoritative domain name system, generating resolution failure information.

[0062] In the embodiment of the present disclosure, if the target hosting domain does not exist in the authoritative DNS, it indicates that the authoritative DNS cannot resolve the domain name to be resolved, so a resolution failure message is generated. For example, the resolution failure message may be REFUSED, indicating that the target hosting domain does not exist.

[0063] Step S306: Feedback the resolution failure information to the local domain name system.

[0064] In the disclosed embodiment, resolution failure information is fed back to the local domain name system, allowing the local domain name system to re-determine the authoritative DNS based on the resolution failure information, thereby improving the success rate of domain name resolution. Alternatively, the local domain name system can notify the client of the resolution failure so that the client can re-determine whether the domain name to be resolved is correct.

[0065] The domain name resolution method provided in this embodiment enables the authoritative DNS to flexibly determine the target hosting domain, thereby improving the resolution efficiency and the success rate of domain name resolution during subsequent domain name resolution.

[0066] In some optional embodiments, determining the first subdomain matching the domain name to be resolved is performed in the following manner: within the target hosting domain, matching the domain name to be resolved with multiple first subdomains. In response to determining that a target subdomain matching the domain name to be resolved exists among the multiple first subdomains, the target subdomain is used as the first subdomain matching the domain name to be resolved.

[0067] In one implementation scenario, the recording method of each hosted domain in the authoritative DNS can be shown in Figure 4. Among them, ".", ".com", and ".cn" respectively represent each hosted domain. "a.com" and "glsb.com" are multiple first subdomains of "com". "test.a.com" is the first subdomain of "a". If ".com" is the target hosted domain, "www.a.com" is matched with "a.com", "glsb.com" and "test.a.com" respectively, and then it can be determined that "test.a.com" is the target subdomain that matches "www.a.com", and "test.a.com" is used as the first subdomain that matches the domain name to be resolved.

[0068] In response to determining that a target subdomain matching the domain name to be resolved does not exist among the multiple first subdomains, the target hosted domain is re-determined to improve resolution accuracy. In some optional implementation scenarios, if a target subdomain matching the domain name to be resolved still does not exist after re-determining the target hosted domain, the target hosted domain is re-determined again until a valid target subdomain is obtained. To avoid excessive resolution time, the number of target hosted domain determinations is counted. If the target subdomain is still not determined after a specified number of determinations, a prompt message indicating that the domain name does not exist is generated and sent to the local domain name system to avoid a timeout response. The prompt message may include the following: NXDOMAIN.

[0069] In other optional implementations, the mapping address corresponding to each first subdomain name is also recorded in the target hosting domain. Therefore, after determining the first subdomain name that matches the domain name to be resolved, the target mapping address corresponding to the target subdomain name can be determined based on the correspondence between the preset multiple first subdomain names and the mapping addresses. The target subdomain name is the first subdomain name that matches the domain name to be resolved. For the sake of simplicity, "target subdomain name" will be used instead of "first subdomain name that matches the domain name to be resolved" below. The target subdomain name and the target mapping address are used as the resolution result of the domain name to be resolved, thereby achieving the purpose of improving query efficiency and success rate.

[0070] For example, the domain name resolution process is shown in Figure 5: The local domain name system receives the domain name "www.a.com" from the client and sends it to the authoritative DNS for resolution. After the authoritative DNS completes the resolution, the results are: the target subdomain ("www.a.com.glsb.com") and the target mapping address ("1.1.1.1"). "www.a.com.glsb.com" and "1.1.1.1" are fed back to the local domain name system. The local domain name system then feeds back "www.a.com.glsb.com" and "1.1.1.1" to the client.

[0071] In some other optional implementations, the authoritative DNS can be understood as a domain name system provided by the manufacturer, and some subdomains may be confidential and need to be protected. Therefore, multiple subdomains to be hidden can be configured in advance so that when the resolution result is fed back, the subdomain can be hidden. Therefore, after obtaining the target subdomain, it is identified whether the target subdomain is the domain name to be hidden. In response to identifying that the target subdomain is not the domain name to be hidden, the target subdomain and the target mapping address are used as the resolution result of the domain name to be resolved, so that the client can clearly understand the domain name to which the domain name to be resolved points after resolution.

[0072] For example, the domain name resolution process is shown in Figure 6: The local DNS receives the domain name "www.a.com" from the client and sends it to the authoritative DNS for resolution. After the authoritative DNS completes the resolution, the resulting target subdomain is "www.a.com.glsb.com" and the target mapping address is "1.1.1.1." In response to identifying "www.a.com.glsb.com" as the domain name to be hidden, "www.a.com.glsb.com" is hidden and "1.1.1.1" is fed back to the local DNS. The local DNS then sends the resulting "1.1.1.1" back to the client.

[0073] In some examples, in response to identifying that the target subdomain is a domain name to be hidden, the target subdomain is hidden, and the target mapping address is used as the resolution result of the domain name to be resolved, thereby effectively protecting the target subdomain from being leaked, thereby achieving the purpose of hiding technical details from users, so that users will not feel the existence of the CNAME link during the domain name resolution process.

[0074] In this embodiment, a domain name resolution method is provided, which can be used in an authoritative domain name system deployed on an electronic device or a server. FIG7 is a flow chart of the domain name resolution method according to an embodiment of the present disclosure. As shown in FIG7 , the process includes the following steps:

[0075] Step S701: receiving a domain name to be resolved sent by a local domain name system. The domain name to be resolved is sent by a client to the local domain name system.

[0076] Step S702: Determine the target hosting domain according to the domain name suffix of the domain name to be resolved.

[0077] Step S703: Match the domain name to be resolved with multiple first subdomain names to determine a first subdomain name that matches the domain name to be resolved.

[0078] Step S704: Determine a resolution result of the domain name to be resolved based on the first subdomain name that matches the domain name to be resolved.

[0079] Step S705: Determine the lifetime of the first subdomain name that matches the domain name to be resolved.

[0080] In the embodiment of the present disclosure, in order to ensure the validity of the client accessing the first subdomain (target subdomain) matching the domain name to be resolved, the time to live (TTL) of the first subdomain matching the domain name to be resolved is determined.

[0081] In some optional embodiments, in response to determining that the target subdomain includes multiple matching domain names, the minimum of the lifetimes of the matching domain names is used as the lifetime of the target subdomain, thereby helping to ensure the validity of the target subdomain and allowing the client to successfully access the target subdomain. For example, if the lifetimes of the matching domain names are 600, 300, and 400, respectively, 300 is used as the lifetime of the multiple matching domain names. That is, 300 is used as the lifetime of the target subdomain.

[0082] Step S706: Add the expiration time to the resolution result of the domain name to be resolved.

[0083] Step S707: Feedback the resolution result to the local domain name system.

[0084] In the embodiment of the present disclosure, the resolution result with the added expiration time is fed back to the local domain name system, so that the local domain name system can feed back the expiration time of the target subdomain to the client, so that the client can clearly understand the effective access time of the target subdomain, thereby helping to improve the user experience of the client.

[0085] In some optional implementation scenarios, taking the target subdomain "www.a.com.glsb.com" with a TTL of 300 as an example, if the target subdomain is not a domain to be hidden, the resolution result includes: "www.a.com.glsb.com", "1.1.1.1" (the target mapping address of the target subdomain), and a TTL of 300. If the target subdomain is a domain to be hidden, the resolution result includes: "1.1.1.1" and a TTL of 300.

[0086] The domain name resolution method provided in this embodiment can improve the query speed and success rate, and can also inform the client of the lifespan of the target subdomain name, thereby effectively assisting the client user to access the target subdomain name within the valid time, thereby helping to improve the client user's user experience.

[0087] In some optional implementations, the domain names that require domain name resolution acceleration can be set according to needs. That is, which domain names need to execute the domain name resolution method provided by the present disclosure are pre-configured in the authoritative DNS. In response to determining that the domain name to be resolved received by the authoritative DNS is a domain name pre-configured as requiring domain name resolution acceleration, the domain name resolution method provided by the present disclosure is executed. In response to determining that the domain name to be resolved received by the authoritative DNS is not a domain name pre-configured as requiring domain name resolution acceleration, the traditional resolution method can be used for resolution. This makes the domain name resolution acceleration method more flexible.

[0088] In some examples, to provide greater flexibility in domain acceleration and domain hiding, the following configuration can be pre-configured in the authoritative DNS: a field control is added to each hosted domain, and the entire link follows the settings of the originating hosted domain. That is, if acceleration is configured at the originating hosted domain, all subsequent hosted domains are also accelerated. If hiding is configured at the originating hosted domain, all links within the hosted domain are hidden.

[0089] In some optional application scenarios, the process of domain name resolution by the authoritative DNS may be as follows: receiving a domain name to be resolved. Determining a target hosted domain corresponding to the domain name to be resolved. Determining whether the target hosted domain is a domain name requiring domain name resolution acceleration. In response to determining that the target hosted domain is not a domain name requiring domain name resolution acceleration, performing resolution using a traditional resolution method, and feeding back the resolution result to the local domain name system. In response to determining that the target hosted domain is a domain name requiring domain name resolution acceleration, querying the target subdomain within the target hosted domain. If the target subdomain is not found, feeding back NXDOMAIN to the local domain name system. If the target subdomain is found, determining whether the target subdomain is a domain name to be hidden. If the target subdomain is not a domain name to be hidden, using the target subdomain, target mapping address, and expiration time as the resolution result, and then feeding back the resolution result to the local domain name system. If the target subdomain is a domain name to be hidden, using the target mapping address and expiration time as the resolution result, and then feeding back the resolution result to the local domain name system.

[0090] In other optional application scenarios, during the process of domain name resolution by the authoritative DNS, if the authoritative DNS fails to determine the target hosted domain corresponding to the domain name to be resolved, the traditional resolution method is used for resolution, and the resolution result is fed back to the local domain name system.

[0091] This embodiment also provides a domain name resolution device for implementing the above-mentioned embodiments and preferred implementations. Details that have already been described will not be repeated. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0092] This embodiment provides a domain name resolution device, which is applied to an authoritative domain name system, as shown in FIG8 , including:

[0093] Receiving module 801, used to receive the domain name to be resolved sent by the local domain name system, the domain name to be resolved is sent by the client to the local domain name system;

[0094] A first execution module 802 is configured to determine a target hosting domain according to the domain name suffix of the domain name to be resolved, where the target hosting domain has multiple first subdomain names recorded therein;

[0095] The second execution module 803 is configured to match the domain name to be resolved with the plurality of first subdomain names, and determine a first subdomain name that matches the domain name to be resolved;

[0096] The first feedback module 804 is configured to determine a resolution result of the domain name to be resolved based on the first subdomain name matching the domain name to be resolved, and to feed back the resolution result to the local domain name resolution system, which is configured to send the resolution result to the client.

[0097] In some optional implementations, the first execution module 802 includes:

[0098] A domain name determination unit, configured to determine the domain name suffix with the largest character length as the second subdomain name of the domain name to be resolved;

[0099] The hosting domain determining unit is configured to determine a target hosting domain according to the second subdomain name.

[0100] In some optional implementations, the hosting domain determining unit includes:

[0101] a first determining unit, configured to, in response to determining that a hosted domain corresponding to the second subdomain name exists in the authoritative domain name system, determine the hosted domain corresponding to the second subdomain name as a target hosted domain;

[0102] The second determining unit is configured to, in response to determining that there is no hosted domain corresponding to the second subdomain in the authoritative domain name system, determine a third subdomain based on the domain name suffix of the domain name to be resolved, where the character length of the domain name suffix of the third subdomain is less than the character length of the domain name suffix of the second subdomain; and determine the target hosted domain based on the third subdomain.

[0103] In some optional embodiments, the device further comprises:

[0104] an information generating module for generating a resolution failure message in response to determining that the target hosted domain does not exist in the authoritative domain name system;

[0105] The second feedback module is used to feed back the resolution failure information to the local domain name system.

[0106] In some optional implementations, the second execution module 803 includes:

[0107] a first matching unit, configured to match the domain name to be resolved with the plurality of first subdomains, and in response to determining that a target subdomain matching the domain name to be resolved exists among the plurality of first subdomains, use the target subdomain as a first subdomain matching the domain name to be resolved;

[0108] The adjusting unit is configured to, in response to determining that no target subdomain matching the domain name to be resolved exists in the plurality of first subdomain names, redetermine the target hosted domain.

[0109] In some optional implementations, the first feedback module 804 includes:

[0110] An address determining unit, configured to determine a target mapping address corresponding to a target subdomain name based on a preset correspondence between a plurality of first subdomain names and mapping addresses;

[0111] The result determination unit is used to use the target subdomain name and the target mapping address as the resolution result of the domain name to be resolved.

[0112] In some optional embodiments, the result determination unit includes:

[0113] An identification unit, used to identify whether the target subdomain is a domain name to be hidden;

[0114] The first determining subunit is configured to, in response to determining that the target subdomain name is not the domain name to be hidden, use the target subdomain name and the target mapping address as a resolution result of the domain name to be resolved.

[0115] In some optional embodiments, the device further comprises:

[0116] The second determining sub-unit is configured to, in response to determining that the target subdomain is the domain name to be hidden, hide the target subdomain and use the target mapping address as a resolution result of the domain name to be resolved.

[0117] In some optional embodiments, the device further comprises:

[0118] Time determination module, used to determine the lifetime of the target subdomain;

[0119] The update module is used to add the expiration time to the resolution result of the domain name to be resolved.

[0120] In some optional implementations, the time determination module includes:

[0121] The time determination unit is configured to, in response to determining that the target subdomain includes multiple matching domain names, use the minimum value of the survival times of the matching domain names as the survival time of the target subdomain.

[0122] In some optional implementations, the first feedback module 804 includes:

[0123] The feedback unit is configured to, in response to determining that the authoritative domain name system has multiple levels, feed back the resolution result of the authoritative domain name system at the last level to the local domain name system.

[0124] The domain name resolution device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0125] The further functional description of each of the above modules and units matches the above corresponding embodiments and will not be repeated here.

[0126] An embodiment of the present disclosure further provides an electronic device having the domain name resolution device shown in FIG8 .

[0127] Please refer to Figure 9, which is a structural diagram of an electronic device provided by an optional embodiment of the present disclosure. As shown in Figure 9, the electronic device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses and can be installed on a common motherboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 9 takes a processor 10 as an example.

[0128] The processor 10 may be a central processing unit, a network processor, or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic, or any combination thereof.

[0129] The memory 20 stores instructions that can be executed by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0130] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created based on the use of an electronic device presented by a small program landing page, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely located relative to the processor 10, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0131] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0132] The electronic device further includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30, and the output device 40 may be connected via a bus or other means, with FIG9 taking the bus connection as an example.

[0133] The input device 30 can receive input digital or character information and generate key signal input related to user settings and function control of the electronic device, such as a touch screen, a keypad, a mouse, a trackpad, a touch pad, an indicator stick, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 can include a display device, an auxiliary lighting device (e.g., an LED), and a tactile feedback device (e.g., a vibration motor). The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display, and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0134] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the method shown in the above embodiment is implemented.

[0135] Although the embodiments of the present disclosure have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A domain name resolution method based on a content distribution network, applied to an authoritative domain name system, the method comprising: Receiving a domain name to be resolved sent by a local domain name system, wherein the domain name to be resolved is sent by a client to the local domain name system; Determine a target hosting domain according to the domain name suffix of the domain name to be resolved, wherein the target hosting domain has multiple first subdomain names recorded therein; Matching the domain name to be resolved with the multiple first subdomain names to determine a first subdomain name that matches the domain name to be resolved; as well as Based on the first subdomain name matching the domain name to be resolved, a resolution result of the domain name to be resolved is determined, and the resolution result is fed back to the local domain name system, and the local domain name system is used to send the resolution result to the client.

2. According to the method of claim 1, determining the target hosting domain according to the domain name suffix of the domain name to be resolved comprises: Determine the suffix with the largest character length among the domain name suffixes as the second subdomain name of the domain name to be resolved; as well as The target hosting domain is determined according to the second subdomain name.

3. The method according to claim 2, wherein determining the target hosting domain according to the second subdomain name comprises: In response to determining that there is a hosted domain corresponding to the second subdomain name in the authoritative domain name system, the hosted domain corresponding to the second subdomain name is determined as the target hosted domain.

4. The method according to claim 2, wherein determining the target hosting domain according to the second subdomain name comprises: In response to determining that there is no hosted domain corresponding to the second subdomain in the authoritative domain name system, determining a third subdomain according to the domain name suffix of the domain name to be resolved, wherein the character length of the domain name suffix of the third subdomain is less than the character length of the domain name suffix of the second subdomain; and The target hosting domain is determined according to the third subdomain name.

5. The method according to any one of claims 2 to 4, further comprising: In response to determining that the target hosted domain does not exist in the authoritative domain name system, generating a resolution failure information; as well as The resolution failure information is fed back to the local domain name system.

6. According to the method of claim 1, matching the domain name to be resolved with the multiple first subdomain names to determine the first subdomain name matching the domain name to be resolved comprises: Matching the domain name to be resolved with the multiple first subdomain names; as well as In response to determining that there is a target subdomain name matching the domain name to be resolved among the multiple first subdomain names, the target subdomain name is used as a first subdomain name matching the domain name to be resolved.

7. The method according to claim 6, wherein determining the resolution result of the domain name to be resolved based on the first subdomain name matching the domain name to be resolved comprises: Determining a target mapping address corresponding to the target subdomain name according to a preset correspondence relationship between the plurality of first subdomain names and mapping addresses; as well as The target subdomain name and the target mapping address are used as the resolution result of the domain name to be resolved.

8. The method according to claim 7, wherein the step of using the target subdomain name and the target mapping address as the resolution result of the domain name to be resolved comprises: Identify whether the target subdomain is a domain name to be hidden; as well as In response to identifying that the target subdomain name is not the domain name to be hidden, the target subdomain name and the target mapping address are used as the resolution result of the domain name to be resolved.

9. The method according to claim 7, further comprising: Identify whether the target subdomain is a domain name to be hidden; as well as In response to identifying that the target subdomain is a domain name to be hidden, the target subdomain is hidden, and the target mapping address is used as a resolution result of the domain name to be resolved.

10. The method according to claim 7, further comprising: Determine the lifetime of the target subdomain; The expiration time is added to the resolution result of the domain name to be resolved.

11. The method according to claim 10, wherein determining the lifetime of the target subdomain name comprises: In response to determining that the target subdomain includes multiple matching domain names, a minimum value among the lifetimes of the matching domain names is used as the lifetime of the target subdomain.

12. The method according to claim 1, wherein matching the domain name to be resolved with the multiple first subdomain names to determine the first subdomain name matching the domain name to be resolved comprises: Matching the domain name to be resolved with the multiple first subdomain names; as well as In response to determining that there is no target subdomain name matching the to-be-resolved domain name in the plurality of first subdomain names, the target hosting domain is re-determined.

13. The method according to claim 1, wherein feeding back the resolution result to the local domain name system comprises: In response to determining that the authoritative domain name system has multiple levels, the resolution result of the authoritative domain name system at the last level is fed back to the local domain name system.

14. The method according to claim 1, wherein: Each first subdomain in the plurality of first subdomains is a complete subdomain.

15. The method according to claim 1, wherein: The step of matching the domain name to be resolved with the multiple first subdomain names to determine the first subdomain name that matches the domain name to be resolved includes: In response to determining that the target hosting domain is a domain name requiring accelerated domain name resolution, a first subdomain name matching the domain name to be resolved is queried in the target hosting domain.

16. A domain name resolution device based on a content distribution network, applied to an authoritative domain name system, the device comprising: A receiving module, used for receiving a domain name to be resolved sent by a local domain name system, wherein the domain name to be resolved is sent by a client to the local domain name system; A first execution module, configured to determine a target hosting domain according to a domain name suffix of the domain name to be resolved, wherein the target hosting domain has a plurality of first subdomain names recorded therein; A second execution module is used to match the domain name to be resolved with the multiple first subdomain names, and determine a first subdomain name that matches the domain name to be resolved; as well as The first feedback module is used to determine the resolution result of the domain name to be resolved based on the first subdomain name matching the domain name to be resolved, and to feed back the resolution result to the local domain name system, and the local domain name resolution system is used to send the resolution result to the client.

17. An electronic device comprising: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the domain name resolution method according to any one of claims 1 to 15 by executing the computer instructions.

18. A computer-readable storage medium having computer instructions stored thereon, wherein the computer instructions are used to enable a computer to execute the domain name resolution method according to any one of claims 1 to 15.

Citation Information

Patent Citations

  • Domain name resolution method and apparatus, electronic device, and readable storage medium

    CN108574744A

  • A CNAME acceleration method applied to a DNS authoritative server

    CN109936632A

  • Domain name resolution method, authoritative domain name server and local domain name server

    CN111200667A

  • Domain name resolution method and device, equipment and storage medium

    CN115643234A

  • Domain name resolution method and device based on content distribution network, equipment and medium

    CN116708365A