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

Abstract

The embodiment of the invention discloses a domain name resolution method, device and system, equipment and a storage medium. The method comprises the following steps: receiving a service domain name resolution request sent by a client; if detecting that an IP address corresponding to the service domain name does not exist in a local cache based on the service domain name to be analyzed in the service domain name analysis request, performing recursive query on an authoritative DNS server according to the service domain name to obtain an analysis result corresponding to the service domain name, the analysis result comprises an alias record chain corresponding to the service domain name and an IP address corresponding to the service domain name in the CDN; and matching the CDN suffix of the terminal point domain name in the alias record chain with a preset guarantee domain CDN suffix, and carrying out differential response processing of domain name resolution according to a matching result. Through the technical scheme of the embodiment of the invention, the domain name management difficulty is greatly reduced, and differentiated services are realized.

Description

Technical Field

[0001] The embodiments of the present invention relate to computer technology, and more particularly to a domain name resolution method, apparatus, system, device, and storage medium. Background Technology

[0002] Domain name resolution is achieved by using a DNS (Domain Name System) server to resolve a domain name into an IP address that a computer can directly recognize, thereby enabling clients to access websites.

[0003] Currently, special handling is often required for certain business domains during the domain name resolution process. Existing methods control domain name resolution by matching exact domains or wildcard domains. However, business domains are frequently updated based on changing needs, with rapid online and offline changes. Furthermore, CDN (Content Delivery Network) domains carry business domains from different customers with different domain suffixes, lack specific characteristics, and undergo frequent changes, making domain management extremely difficult for DNS administrators. Therefore, existing methods cannot meet the security requirements of CDN service providers. Summary of the Invention

[0004] This invention provides a domain name resolution method, apparatus, system, device, and storage medium to greatly reduce the difficulty of domain name management and achieve differentiated services.

[0005] In a first aspect, embodiments of the present invention provide a domain name resolution method, including:

[0006] Receive business domain name resolution requests sent by clients;

[0007] If, based on the business domain name to be resolved in the business domain name resolution request, it is detected that the IP address corresponding to the business domain name does not exist in the local cache, then a recursive query is performed on the authoritative DNS server according to the business domain name to obtain the resolution result corresponding to the business domain name. The resolution result includes: the alias record chain corresponding to the business domain name and the IP address corresponding to the business domain name in the CDN network.

[0008] The CDN suffix of the endpoint domain name in the alias record chain is matched with the pre-set CDN suffix of the security domain, and differentiated response processing for domain name resolution is performed based on the matching result.

[0009] Secondly, embodiments of the present invention also provide a domain name resolution device, comprising:

[0010] The request receiving module is used to receive business domain name resolution requests sent by the client;

[0011] The recursive query module is used to perform a recursive query to the authoritative DNS server based on the business domain name to be resolved in the business domain name resolution request if it is detected that the IP address corresponding to the business domain name does not exist in the local cache. The resolution result includes: the alias record chain corresponding to the business domain name and the IP address corresponding to the business domain name in the CDN network.

[0012] The response processing module is used to match the CDN suffix of the endpoint domain name in the alias record chain with the pre-set CDN suffix of the security domain, and perform differentiated response processing for domain name resolution based on the matching result.

[0013] Thirdly, embodiments of the present invention also provide a domain name resolution system, the system comprising: a client, a local DNS server, and an authoritative DNS server;

[0014] The local DNS server is used to implement the domain name resolution method provided in any embodiment of the present invention.

[0015] Fourthly, embodiments of the present invention also provide an electronic device, the electronic device comprising:

[0016] At least one processor; and

[0017] A memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the domain name resolution method provided in any embodiment of the present invention.

[0019] Fifthly, embodiments of the present invention also provide a computer-readable storage medium storing computer instructions, which are used to cause a processor to execute and implement the domain name resolution method provided in any embodiment of the present invention.

[0020] One embodiment of the above invention has the following advantages or beneficial effects:

[0021] By pre-setting the CDN suffix of the endpoint domain in the alias record chain corresponding to the business domain that needs to provide differentiated services in the local DNS server—that is, the guarantee domain CDN suffix—administrators only need to maintain a small number of guarantee domain CDN suffixes, without having to maintain a large number of business domains and CDN domains, greatly reducing the difficulty of domain name management. In practical applications, by matching the CDN suffix of the endpoint domain in the alias record chain in the resolution result with the pre-set guarantee domain CDN suffix, it is possible to quickly and accurately determine whether differentiated services need to be provided for the business domain to be resolved, thereby achieving differentiated response processing for domain name resolution.

[0022] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a flowchart of a domain name resolution method provided in one embodiment of the present invention;

[0025] Figure 2 This is a flowchart of a domain name resolution method provided in one embodiment of the present invention;

[0026] Figure 3 This is a flowchart of a domain name resolution method provided in one embodiment of the present invention;

[0027] Figure 4 This is a flowchart of a domain name resolution method provided in one embodiment of the present invention;

[0028] Figure 5 This is a schematic diagram of the structure of a domain name resolution device provided in one embodiment of the present invention;

[0029] Figure 6 This is a schematic diagram of the structure of a domain name resolution system provided in one embodiment of the present invention;

[0030] Figure 7 This is a schematic diagram of the structure of an electronic device that implements the domain name resolution method of this invention. Detailed Implementation

[0031] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0033] Figure 1 This is a flowchart illustrating a domain name resolution method according to an embodiment of the present invention. This embodiment is applicable to situations involving differentiated response processing for domain name resolution of business domain names. The method can be executed by a domain name resolution device integrated into a local DNS server. This device can be implemented in software and / or hardware, and can be configured in an electronic device. Figure 1 As shown, the method specifically includes the following steps:

[0034] S110: Receive the business domain name resolution request sent by the client.

[0035] Here, the business domain name refers to the domain name of the resource service that the client needs to access. The local DNS server refers to the domain name resolution server configured in the local network, which is used to convert the business domain name into an IP address, thereby reducing dependence on external DNS servers and improving resolution speed and security.

[0036] Specifically, when the client does not find the IP address corresponding to the business domain name to be resolved in the local cache, it sends a resolution request for the business domain name to the local DNS server, which then responds based on the received business domain name resolution request.

[0037] S120. If, based on the business domain name to be resolved in the business domain name resolution request, it is detected that there is no IP address corresponding to the business domain name in the local cache, then a recursive query is performed to the authoritative DNS server based on the business domain name to obtain the resolution result corresponding to the business domain name. The resolution result includes: the alias record chain corresponding to the business domain name and the IP address corresponding to the business domain name in the CDN network.

[0038] Authoritative DNS servers are responsible for providing authoritative mapping information between domain names and IP addresses, ensuring stable and reliable access. Authoritative DNS servers can include: root domain authoritative DNS servers, top-level domain authoritative DNS servers, and target domain authoritative DNS servers. Target domains include business domains and CDN domains. The target domain authoritative DNS server is used to query the CDN domain corresponding to the business domain, the IP address corresponding to the CDN domain, or another CDN domain corresponding to the CDN domain, etc. The local DNS server uses recursive queries to progressively resolve the alias record chain and the final IP address corresponding to the business domain from the authoritative DNS servers.

[0039] The alias record chain consists of multiple alias records connected sequentially according to the recursive query order, forming a hierarchical chain structure during domain name resolution. An alias record, or CNAME (Canonical Name) record, is used to point one domain name to another, allowing one domain name to exist as an alias for another. Each recursive query corresponds to one alias record. For example, the resolution process of the business domain name v96-litea.xxxvod.com is as follows: The CNAME of v96-litea.xxxvod.com first points to the CDN service provider's primary domain name (v96-litea.xxxvod.com.cdn.yyy.com), enabling global traffic scheduling for this domain to access the CDN service. Secondly, the CNAME points to the CDN service provider's secondary domain name (v96-litea.xxxvod.com.e.cdn.yyy.com.), which points to a domain name for a specific geographical location and service provided by the CDN service provider. Finally, the CNAME record points back to the specific CDN resource server, namely the IP address corresponding to xxx-vod.e.cdn.yyy.com, thus achieving the final domain name to IP address conversion. Therefore, the alias record chain for this business domain name is: v96-litea.xxxvod.com → v96-litea.xxxvod.com.cdn.yyy.com → xxx-vod.e.cdn.yyy.com.

[0040] The IP address corresponding to the business domain name refers to the IP address of the endpoint domain name in the alias record chain. The IP address corresponding to the business domain name is also the IP address of the edge node in the CDN network. By mapping the business domain name to this IP address, clients can access resources from that edge node.

[0041] Specifically, when the local DNS server detects that the IP address corresponding to the business domain name does not exist in its local cache, it needs to perform a recursive query with the authoritative DNS server to obtain the resolution result for that business domain name. The specific process of the recursive query is as follows: First, the local DNS server queries the root domain authoritative DNS server based on the root domain name of the business domain name to obtain the address of the top-level domain authoritative DNS server. The local DNS server then queries the top-level domain authoritative DNS server to obtain the address of the target domain authoritative DNS server corresponding to the business domain name. Finally, the local DNS server queries the target domain authoritative DNS server to obtain the first-level CDN domain name of the business domain name, that is, the first-level domain name pointing to the CDN service provider, which is also the CNAME record. Based on the returned first-level CDN domain name, the local DNS server continues to query the root domain authoritative DNS server, the top-level domain authoritative DNS server, and the target domain authoritative DNS server in sequence. If the target domain authoritative DNS server returns a second-level CDN domain name, i.e., a CNAME record, then based on the returned second-level CDN domain name, it continues to query the root domain authoritative DNS server, the top-level domain authoritative DNS server, and the target domain authoritative DNS server in sequence, until the target domain authoritative DNS server returns an IP address, thus completing the recursive query for the business domain name. The authoritative DNS server of a CDN service provider may dynamically return the IP address of the nearest edge node based on the client's geographical location or load, thereby enabling global or regional CDN resource scheduling. The alias records obtained from each query are aggregated to obtain the alias record chain of the business domain name, and also to obtain the IP address corresponding to the business domain name in the CDN network.

[0042] S130. Match the CDN suffix of the endpoint domain name in the alias record chain with the pre-set CDN suffix of the security domain, and perform differentiated response processing for domain name resolution based on the matching result.

[0043] In this context, the endpoint domain in an alias record chain refers to the domain name of the last hop in the chain. For example, in the example above, the endpoint domain in the alias record chain is xxx-vod.e.cdn.yyy.com. The CDN suffix of the endpoint domain refers to the CDN domain suffix within the endpoint domain, specifically the CDN-related part of the endpoint domain. For instance, the CDN suffix of the endpoint domain xxx-vod.e.cdn.yyy.com is cdn.yyy.com.

[0044] It should be noted that research into the business domain name resolution process revealed that the endpoint domains in the alias record chains of some precise business domains converge to the CDN suffix domains. For example, only a few xxxvod.com suffix domains, such as v26-x.xxxvod.com, v5-gzb-c-hl-hw.xxxvod.com, and v99-hca.xxxvod.com, need differentiated services. Since there are a large number of subdomains under *.xxxvod.com, and the CDN service provider only serves fewer than ten domains, with most other precise xxxvod.com domains being served by other CDN service providers, differentiating by matching *.xxxvod.com wildcard domains is not feasible. Furthermore, business domain names change frequently, so matching precise domain names is also unsuitable due to the excessive time-consuming management required. In response, the alias record chain for each business domain above is as follows: v26-x.xxxvod.com→v26-x.xxxvod.com.c.cndhw.com→hc.z02.v6.d.cdn.yyy.com; where the CDN suffix of the endpoint domain is cdn.yyy.com;

[0045] v5-gzb-c-hl-hw.xxxvod.com→v5-gzb-c-hl-hw.xxxvod.com.1600.vmcdn.com→v5-gzb-c-hl-hw.xxxvod.com.z.glb.com→v5-gzb-c-hl-hw.xxxvod.com.34.cdnhw.com→hc.z02.v6.d.cdn.yyy.com; where the CDN suffix of the endpoint domain is cdn.yyy.com;

[0046] The sequence is: v99-hca.xxxvod.com → v99-hca.xxxvod.com.byt.com → v99-hca.xxxvod.com.cdn.yyy.com → v99-hca.xxxvod.com.b.cdn.yyy.com; where the CDN suffix of the endpoint domain is cdn.yyy.com. It can be seen that the endpoint domains of the alias record chains of the above three business domains all converge to the CDN suffix domain "*.cdn.yyy.com", meaning they share the same CDN suffix. Therefore, by matching the CDN suffix of the endpoint domain, all the original precise domains carried by the CDN resource area can be captured, achieving a "leveraging effect" by accurately converging the identification of thousands of business domains to the identification of a few CNAME suffix domains, achieving extremely high accuracy and convergence. Therefore, by matching the CDN suffix of the endpoint domain, multiple upstream business domains can be quickly identified, thereby accurately marking CDN resource domains in any region, flexibly controlling their resolution strategies, and providing differentiated DNS resolution services.

[0047] In this embodiment, the pre-configured CDN suffix for the protection domain refers to the CDN suffix of the endpoint domain in the alias record chain corresponding to the business domain that needs to provide differentiated services, pre-configured in the local DNS server. Differentiated services refer to services that provide different response results for domain name resolution. For example, differentiated services can refer to the differentiation of the time-to-live (TTL) cache time of the resolution results. For instance, different cache times can be set for different business domains; that is, a smaller cache time can be set for update-sensitive business domains (such as those in the financial industry) to prioritize TTL refresh and accelerate domain name refresh speed. Differentiated services can also refer to the differentiation of IP address responses. For example, the IP addresses of some business domains can be determined using a round-robin method, while the IP addresses of others can be determined using the previously set address priority information.

[0048] For example, the pre-configured protection domain CDN suffix includes at least one of the following: a first protection domain CDN suffix for ensuring domain name caching time, a second protection domain CDN suffix for ensuring IP address polling response, and a third protection domain CDN suffix for ensuring precise scheduling.

[0049] The first guarantee domain CDN suffix represents the TTL guarantee domain list. When the CDN suffix of the endpoint domain in the alias record chain corresponding to the business domain is the first guarantee domain CDN suffix, the TTL of that business domain needs to be prioritized for refresh. The second guarantee domain CDN suffix represents the address round-robin guarantee domain list. When the CDN suffix of the endpoint domain in the alias record chain corresponding to the business domain is the second guarantee domain CDN suffix, the business domain needs to undergo IP address round-robin responses so that traffic can be routed to all available IP addresses. The third guarantee domain CDN suffix represents the precise scheduling guarantee domain list. When the CDN suffix of the endpoint domain in the alias record chain corresponding to the business domain is the third guarantee domain CDN suffix, a dedicated recursive EDNS (Extension Mechanisms for DNS) server needs to be used to recursively query that business domain.

[0050] Specifically, in practical applications, the CDN suffix of the endpoint domain in the alias record chain is obtained and matched with the pre-set guarantee domain CDN suffix. Based on whether the CDN suffix matches the pre-set guarantee domain CDN suffix, it can be determined whether the business domain to be resolved is a guarantee domain. Then, different response processing methods are applied to the business domain, thus achieving differentiated services from the original processing methods. For example, if the CDN suffix of the endpoint domain in the alias record chain matches the pre-set guarantee domain CDN suffix, the domain name resolution response is performed based on the first response processing method. If the CDN suffix of the endpoint domain in the alias record chain does not match the pre-set guarantee domain CDN suffix, the domain name resolution response is performed based on the second response processing method, thus achieving differentiated domain name resolution response processing. The first response processing method differs from the second response processing method. The first response processing method can refer to a special resolution processing method for the business domain. The second response processing method can refer to the original resolution processing method for the business domain.

[0051] For example, a local DNS server may include a caching module and a recursive module. As one implementation, the specific domain name resolution process can be as follows: The caching module receives a business domain name resolution request from the client. When it detects that the IP address corresponding to the business domain name does not exist in the local cache, it sends a recursive query request to the recursive module. The recursive module then sends a recursive iteration request to the authoritative DNS server for iterative querying. The recursive module summarizes the query results to obtain the resolution result corresponding to the business domain name. The recursive module sends the resolution process to the caching module. The caching module, based on the alias record chain in the resolution result, matches the CDN suffix of the endpoint domain in the alias record chain with the pre-set CDN suffix of the protection domain. Based on the matching result, it performs differentiated response processing for domain name resolution. For example, it includes successfully matched business domain names in the protection domain and applies resolution effects to them; business domain names that fail to match do not need to be included in the protection domain and do not require resolution effects. This method only requires modification of the caching module's program code and is relatively easy to implement.

[0052] As an alternative implementation, the specific domain name resolution process can be as follows: The caching module receives the business domain name resolution request sent by the client. When it detects that the IP address corresponding to the business domain name does not exist in the local cache, it sends a recursive query request to the recursive module. The recursive module then sends a recursive iterative query request to the authoritative DNS server for iterative querying. The recursive module summarizes the query results to obtain the resolution result corresponding to the business domain name. Based on the alias record chain in the resolution result, the recursive module matches the CDN suffix of the endpoint domain name in the alias record chain with the pre-set guarantee domain CDN suffix, adds the matching result's tag information to the attachment field, and then sends the resolution result to the caching module. The caching module performs differentiated response processing for domain name resolution based on the matching result's tag information in the resolution result. For example, it includes successfully matched business domain names in the guarantee domain and applies resolution effects to them, while business domain names that fail to match do not need to be included in the guarantee domain and do not need to be applied resolution effects to them. Although this method requires modification to both the caching module and the recursive module, it can reduce the performance impact of the caching module and has extremely strong flexibility and scalability.

[0053] The technical solution in this embodiment pre-configures the CDN suffix of the endpoint domain in the alias record chain corresponding to the business domain that requires differentiated services in the local DNS server. This CDN suffix, also known as the guarantee domain CDN suffix, reduces the need for administrators to maintain only a small number of business domains and CDN domains, significantly simplifying domain management. In practical applications, by matching the CDN suffix of the endpoint domain in the alias record chain of the resolution result with the pre-configured guarantee domain CDN suffix, it is possible to quickly and accurately determine whether differentiated services are needed for the business domain to be resolved, thus achieving differentiated response processing for domain name resolution.

[0054] Based on the above technical solutions, when the pre-set protection domain CDN suffix includes the third protection domain CDN suffix used to ensure accurate scheduling, step S130 may include: if the CDN suffix of the endpoint domain name in the alias record chain matches the third protection domain CDN suffix, then the business domain name is added to the EDNS cache partition and forwarded to the EDNS dedicated recursive server for recursive query to obtain the IP address corresponding to the business domain name.

[0055] Specifically, when the CDN suffix of the endpoint domain in the alias record chain matches the CDN suffix of the third protection domain, it indicates that the resolved business domain is a domain precisely scheduled by EDNS. In this case, the business domain name resolution request is sent to the dedicated EDNS recursive server for recursive querying by using the client's IP address as the ECS (EdgeClient Subnet) attribute information. The dedicated EDNS recursive server identifies the client's real location through the ECS field and performs a recursive query, returning the nearest CDN node IP address, thereby reducing latency and achieving accurate content distribution. This embodiment only requires configuring the third protection domain CDN suffix and does not require configuring an EDNS precise scheduling whitelist, thus improving management efficiency. If the CDN suffix of the endpoint domain in the alias record chain does not match the third protection domain CDN suffix, the resolution result can be directly returned to the client; alternatively, when the pre-set protection domain CDN suffix includes the first protection domain CDN suffix and / or the second protection domain CDN suffix, differentiated response processing for domain name resolution can be performed based on the matching result with the first protection domain CDN suffix and / or the second protection domain.

[0056] Figure 2 This is a flowchart illustrating a domain name resolution method according to an embodiment of the present invention. Based on the above embodiments, this embodiment provides a detailed description of the differentiated response processing procedure for ensuring domain name caching time. Explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0057] See Figure 2 The other domain name resolution method provided in this embodiment specifically includes the following steps:

[0058] S210: Receive the business domain name resolution request sent by the client.

[0059] S220. If, based on the business domain name to be resolved in the business domain name resolution request, it is detected that the IP address corresponding to the business domain name does not exist in the local cache, then a recursive query is performed to the authoritative DNS server based on the business domain name to obtain the resolution result corresponding to the business domain name. The resolution result includes: the alias record chain corresponding to the business domain name, the IP address corresponding to the business domain name in the CDN network, and the original cache time.

[0060] The original cache time refers to the cache time of the resolution results set in the authoritative DNS server, i.e., the original TTL.

[0061] S230. Match the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the first protection domain, and determine the caching time of the resolution result in the local DNS server based on the matching result and the original caching time.

[0062] Specifically, the appropriate caching time for the DNS resolution results on the local DNS server can be determined based on different matching results. It's important to note that the caching time for the resolution results decreases second by second from the set value until it reaches 0, at which point the cached resolution results are deleted. Reducing the caching time allows authoritative DNS server data updates to take effect faster, while increasing the caching time reduces the resource consumption of the local DNS server. Since different business domain names have different caching time requirements, it is necessary to configure an appropriate caching time for the resolution results corresponding to each business domain name to provide differentiated caching time handling.

[0063] For example, step S230 may include: if the CDN suffix of the endpoint domain name in the alias record chain matches the CDN suffix of the first protection domain, then the cache time of the resolution result in the local DNS server is determined to be the original cache time; if the CDN suffix of the endpoint domain name in the alias record chain does not match the CDN suffix of the first protection domain, then the cache time of the resolution result in the local DNS server is determined according to the original cache time and the preset minimum cache time threshold.

[0064] Specifically, when the CDN suffix of the endpoint domain in the alias record chain matches the CDN suffix of the first guaranteed domain, it indicates that the business domain to be resolved is a cache-time sensitive domain, meaning that the business domain is in the TTL guaranteed domain list. In this case, the cache time of the resolution result in the local DNS server is directly determined as the original cache time, thus making the business domain follow the TTL value of the authoritative server, achieving the effect of TTL-first refresh. When the CDN suffix of the endpoint domain in the alias record chain does not match the CDN suffix of the first guaranteed domain, it indicates that the business domain to be resolved is not in the TTL guaranteed domain list. In this case, the original cache time can be compared with the pre-set minimum cache time threshold, and the cache time of the resolution result in the local DNS server can be determined based on the comparison result.

[0065] For example, determining the caching time of the resolution result in the local DNS server based on the original cache time and a pre-set minimum cache time threshold may include:

[0066] If the original cache time is greater than the preset minimum cache time threshold, the cache time of the resolution result in the local DNS server is determined to be the original cache time; if the original cache time is less than or equal to the preset minimum cache time threshold, the cache time of the resolution result in the local DNS server is determined to be the minimum cache time threshold.

[0067] When the business domain name to be resolved is not in the list of domain names with guaranteed TTL, the minimum cache time of the resolution result in the local DNS server is the minimum cache time threshold. No cache time less than the minimum cache time threshold will be set, thus ensuring the best balance between user experience and reducing system load.

[0068] S240. Return the IP address corresponding to the business domain name to the client.

[0069] Specifically, if there is only one IP address corresponding to a business domain name, that address is directly returned to the client. If there are multiple IP addresses corresponding to a business domain name, the target IP address can be determined according to the original IP address determination method. For example, all IP addresses corresponding to the business domain name can be sorted according to a preset address sorting strategy (such as a sortlist sorting strategy), the target IP address can be determined based on the sorting result, and the target IP address can be returned to the client, thus completing the entire domain name resolution process.

[0070] The technical solution of this embodiment matches the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the first protection domain. Based on different matching results, the appropriate caching time of the resolution result in the local DNS server can be determined, thereby realizing differentiated processing of caching time.

[0071] Figure 3 This is a flowchart illustrating a domain name resolution method according to an embodiment of the present invention. Based on the above embodiments, this embodiment provides a detailed description of the differentiated response processing procedure for ensuring IP address polling responses. Explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0072] See Figure 3 The other domain name resolution method provided in this embodiment specifically includes the following steps:

[0073] S310: Receive the business domain name resolution request sent by the client.

[0074] S320. If, based on the business domain name to be resolved in the business domain name resolution request, it is detected that there is no corresponding IP address in the local cache, then a recursive query is performed on the authoritative DNS server according to the business domain name to obtain the resolution result corresponding to the business domain name. The resolution result includes: the alias record chain corresponding to the business domain name and multiple IP addresses corresponding to the business domain name in the CDN network.

[0075] Specifically, the number of IP addresses corresponding to a business domain name is multiple. During recursive queries, the domain name of the last hop in the authoritative DNS server can return multiple IP addresses, meaning that the endpoint domain name in the alias record chain can correspond to multiple IP addresses. For example, the IP addresses corresponding to the endpoint domain name xxx-vod.e.cdn.yyy.com returned by the authoritative DNS server include: 39.13X.70.121, 39.13X.70.115, 39.13X.70.112, 39.13X.71.5, and 39.13X.71.3. With the same business resource configured on five edge nodes, clients can access the business resource by accessing any of the above IP addresses.

[0076] S330. Match the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the second protection domain, determine the target IP address from all IP addresses corresponding to the business domain name based on the matching result, and return the target IP address to the client.

[0077] Specifically, based on different matching results, the target IP address can be determined from all IP addresses using different IP address determination methods, and the target IP address can be returned to the client, thereby achieving differentiated processing of IP address determination.

[0078] For example, step S330 may include: if the CDN suffix of the endpoint domain name in the alias record chain matches the CDN suffix of the second protection domain, then the target IP address is determined by polling all IP addresses corresponding to the business domain name; if the CDN suffix of the endpoint domain name in the alias record chain does not match the CDN suffix of the second protection domain, then all IP addresses corresponding to the business domain name are sorted according to a preset address sorting strategy, and the target IP address is determined based on the sorting result.

[0079] Specifically, when the CDN suffix of the endpoint domain in the alias record chain matches the CDN suffix of the second protection domain, it indicates that the business domain to be resolved is a business domain that requires address round-robin response, meaning that the business domain is in the address round-robin protection domain list. In this case, by round-robining all IP addresses corresponding to the business domain, each IP address is returned as the target IP address, thus routing client traffic to all IP addresses. When the CDN suffix of the endpoint domain in the alias record chain does not match the CDN suffix of the second protection domain, it indicates that the business domain to be resolved is not in the address round-robin protection domain list. In this case, all IP addresses corresponding to the business domain can be sorted according to a preset address sorting strategy (such as a sortlist sorting strategy), and the target IP address is determined based on the sorting result. For example, the address priority of each IP address is determined according to the sortlist configuration information, and all IP addresses are sorted according to address priority. The IP address with the highest address priority is determined as the target IP address, thus routing client traffic only to the highest priority IP address and not to other IP addresses, thereby achieving differentiated processing for IP address determination.

[0080] The technical solution of this embodiment matches the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the second protection domain, and determines the target IP address from all IP addresses according to different IP address determination methods based on different matching results, and returns the target IP address to the client, thereby realizing differentiated processing of IP address determination.

[0081] Figure 4 This is a flowchart illustrating a domain name resolution method according to an embodiment of the present invention. Based on the above embodiments, this embodiment provides a detailed description of the differentiated response processing procedure for simultaneously ensuring domain name caching time and IP address polling responses. Explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0082] See Figure 4 The other domain name resolution method provided in this embodiment specifically includes the following steps:

[0083] S410: Receives a business domain name resolution request sent by the client.

[0084] S420. If, based on the business domain name to be resolved in the business domain name resolution request, it is detected that there is no corresponding IP address for the business domain name in the local cache, then a recursive query is performed to the authoritative DNS server based on the business domain name to obtain the resolution result corresponding to the business domain name. The resolution result includes: the alias record chain corresponding to the business domain name, multiple IP addresses corresponding to the business domain name in the CDN network, and the original cache time.

[0085] S430. Match the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the first protection domain, and determine the caching time of the resolution result in the local DNS server based on the matching result and the original caching time.

[0086] Specifically, if the CDN suffix of the endpoint domain in the alias record chain matches the CDN suffix of the first protection domain, the cache time of the resolution result in the local DNS server is determined to be the original cache time; if the CDN suffix of the endpoint domain in the alias record chain does not match the CDN suffix of the first protection domain, the cache time of the resolution result in the local DNS server is determined according to the original cache time and the pre-set minimum cache time threshold.

[0087] S440. Match the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the second protection domain, determine the target IP address from all IP addresses corresponding to the business domain name based on the matching result, and return the target IP address to the client.

[0088] Specifically, if the CDN suffix of the endpoint domain in the alias record chain matches the CDN suffix of the second protection domain, the target IP address is determined by polling all IP addresses corresponding to the business domain. If the CDN suffix of the endpoint domain in the alias record chain does not match the CDN suffix of the second protection domain, all IP addresses corresponding to the business domain are sorted according to a preset address sorting strategy, and the target IP address is determined based on the sorting result.

[0089] The technical solution of this embodiment matches the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the first protection domain and the CDN suffix of the second protection domain. Based on different matching results, the appropriate caching time of the resolution result in the local DNS server can be determined, and the target IP address can be determined from all IP addresses according to different IP address determination methods, thereby realizing differentiated processing of caching time and IP address determination.

[0090] The following are embodiments of the domain name resolution device provided in this invention. This device and the domain name resolution methods in the above embodiments belong to the same inventive concept. For details not described in detail in the embodiments of the domain name resolution device, please refer to the embodiments of the above domain name resolution methods.

[0091] Figure 5 This is a schematic diagram of a domain name resolution device provided in an embodiment of the present invention. This embodiment is applicable to situations where differentiated response processing is performed on business domain names. Figure 5 As shown, the device specifically includes: a request receiving module 510, a recursive query module 520, and a response processing module 530.

[0092] The system includes a request receiving module 510, used to receive a business domain name resolution request sent by a client; a recursive query module 520, used to perform a recursive query to an authoritative DNS server based on the business domain name to be resolved in the request, if it is detected that the IP address corresponding to the business domain name does not exist in the local cache, in order to obtain the resolution result corresponding to the business domain name, the resolution result including: the alias record chain corresponding to the business domain name and the IP address corresponding to the business domain name in the CDN network; and a response processing module 530, used to match the CDN suffix of the endpoint domain name in the alias record chain with the pre-set CDN suffix of the protection domain, and perform differentiated response processing for domain name resolution based on the matching result.

[0093] The technical solution in this embodiment pre-configures the CDN suffix of the endpoint domain in the alias record chain corresponding to the business domain that requires differentiated services in the local DNS server. This CDN suffix, also known as the guarantee domain CDN suffix, reduces the need for administrators to maintain only a small number of business domains and CDN domains, significantly simplifying domain management. In practical applications, by matching the CDN suffix of the endpoint domain in the alias record chain of the resolution result with the pre-configured guarantee domain CDN suffix, it is possible to quickly and accurately determine whether differentiated services are needed for the business domain to be resolved, thus achieving differentiated response processing for domain name resolution.

[0094] Optionally, the pre-configured CDN suffix for the protection domain includes at least one of the following:

[0095] The first CDN suffix is ​​used to guarantee domain name caching time, the second CDN suffix is ​​used to guarantee IP address polling response, and the third CDN suffix is ​​used to guarantee precise scheduling.

[0096] Optionally, when the pre-set protection domain CDN suffix includes the first protection domain CDN suffix, the parsing result further includes: the original cache time of the parsing result;

[0097] Response processing module 530 includes:

[0098] The cache time determination unit is used to match the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the first protection domain, and determine the cache time of the resolution result in the local DNS server based on the matching result and the original cache time.

[0099] The IP address return unit is used to return the IP address corresponding to the business domain name to the client.

[0100] Optionally, the cache time determination unit is specifically used for:

[0101] If the CDN suffix of the endpoint domain in the alias record chain matches the CDN suffix of the first protection domain, then the cache time of the resolution result in the local DNS server is determined to be the original cache time; if the CDN suffix of the endpoint domain in the alias record chain does not match the CDN suffix of the first protection domain, then the cache time of the resolution result in the local DNS server is determined according to the original cache time and the preset minimum cache time threshold.

[0102] Optionally, the cache time determination unit is specifically used for:

[0103] If the original cache time is greater than the preset minimum cache time threshold, then the cache time of the resolution result in the local DNS server is determined to be the original cache time.

[0104] If the original cache time is less than or equal to the preset minimum cache time threshold, then the cache time of the resolution result in the local DNS server is determined to be the minimum cache time threshold.

[0105] Optionally, when the pre-set protection domain CDN suffix includes the second protection domain CDN suffix, the number of IP addresses corresponding to the service domain name is multiple;

[0106] The response processing module 530 is configured to: match the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the second protection domain, determine the target IP address from all IP addresses corresponding to the business domain name based on the matching result, and return the target IP address to the client.

[0107] Optionally, the response processing module 530 is specifically used for:

[0108] If the CDN suffix of the endpoint domain name in the alias record chain matches the CDN suffix of the second protection domain, the target IP address is determined by polling all IP addresses corresponding to the business domain name.

[0109] If the CDN suffix of the endpoint domain name in the alias record chain does not match the CDN suffix of the second protection domain, then all IP addresses corresponding to the business domain name are sorted according to the preset address sorting strategy, and the target IP address is determined based on the sorting result.

[0110] Optionally, when the pre-set protection domain CDN suffix includes a third protection domain CDN suffix for ensuring accurate scheduling, the response processing module 530 is configured to: if the CDN suffix of the endpoint domain name in the alias record chain matches the third protection domain CDN suffix, add the service domain name to the EDNS cache partition and forward it to the EDNS dedicated recursive server for recursive query to obtain the IP address corresponding to the service domain name.

[0111] The domain name resolution device provided in the embodiments of the present invention can execute the domain name resolution method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the domain name resolution method.

[0112] It is worth noting that in the above-described embodiments of the domain name resolution device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0113] Figure 6 This is a schematic diagram of a domain name resolution system provided in an embodiment of the present invention. This embodiment is applicable to situations where differentiated response processing is performed on business domain names. Figure 6 As shown, the system specifically includes: client 610, local DNS server 620, and authoritative DNS server 630;

[0114] The client 610 is used to send a business domain name resolution request to the local DNS server; the local DNS server 620 is used to implement the domain name resolution method provided in any embodiment of the present invention.

[0115] The domain name resolution system in this embodiment of the invention pre-configures the CDN suffix of the endpoint domain in the alias record chain corresponding to the business domain that needs to provide differentiated services in the local DNS server 620. This CDN suffix, also known as the guarantee domain CDN suffix, eliminates the need for administrators to maintain only a small number of guarantee domain CDN suffixes, rather than a large number of business domains and CDN domains, significantly reducing the difficulty of domain name management. In practical applications, by matching the CDN suffix of the endpoint domain in the alias record chain of the resolution result with the pre-configured guarantee domain CDN suffix, it is possible to quickly and accurately determine whether differentiated services are needed for the business domain to be resolved, thereby achieving differentiated response processing for domain name resolution.

[0116] Figure 7A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0117] like Figure 7 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0118] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0119] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various domain name resolution methods and processes described above.

[0120] In some embodiments, the domain name resolution method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the domain name resolution method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the domain name resolution method by any other suitable means (e.g., by means of firmware).

[0121] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0122] Computer programs used to implement the domain name resolution method of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0123] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0124] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0125] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0126] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0127] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0128] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A domain name resolution method, characterized in that, Applied to local DNS servers, including: Receive business domain name resolution requests sent by clients; If, based on the business domain name to be resolved in the business domain name resolution request, it is detected that the IP address corresponding to the business domain name does not exist in the local cache, then a recursive query is performed on the authoritative DNS server according to the business domain name to obtain the resolution result corresponding to the business domain name. The resolution result includes: the alias record chain corresponding to the business domain name and the IP address corresponding to the business domain name in the CDN network. The CDN suffix of the endpoint domain name in the alias record chain is matched with the pre-set CDN suffix of the security domain, and differentiated response processing for domain name resolution is performed based on the matching result.

2. The method according to claim 1, characterized in that, The pre-configured CDN suffix for the protection domain includes at least one of the following: The first CDN suffix is ​​used to guarantee domain name caching time, the second CDN suffix is ​​used to guarantee IP address polling response, and the third CDN suffix is ​​used to guarantee precise scheduling.

3. The method according to claim 2, characterized in that, When the pre-set protection domain CDN suffix includes the first protection domain CDN suffix, the parsing result also includes: the original cache time of the parsing result; The step of matching the CDN suffix of the endpoint domain name in the alias record chain with the pre-set CDN suffix of the protection domain, and performing differentiated response processing for domain name resolution based on the matching result, includes: The CDN suffix of the endpoint domain name in the alias record chain is matched with the CDN suffix of the first protection domain, and the caching time of the resolution result in the local DNS server is determined based on the matching result and the original caching time. The IP address corresponding to the business domain name is returned to the client.

4. The method according to claim 3, characterized in that, The step of matching the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the first guaranteed domain, and determining the caching time of the resolution result in the local DNS server based on the matching result and the original caching time, includes: If the CDN suffix of the endpoint domain name in the alias record chain matches the CDN suffix of the first protected domain, then the cache time of the resolution result in the local DNS server is determined to be the original cache time. If the CDN suffix of the endpoint domain name in the alias record chain does not match the CDN suffix of the first protected domain, the cache time of the resolution result in the local DNS server is determined based on the original cache time and the preset minimum cache time threshold.

5. The method according to claim 4, characterized in that, The step of determining the cache time of the resolution result in the local DNS server based on the original cache time and a pre-set minimum cache time threshold includes: If the original cache time is greater than the preset minimum cache time threshold, then the cache time of the resolution result in the local DNS server is determined to be the original cache time. If the original cache time is less than or equal to the preset minimum cache time threshold, then the cache time of the resolution result in the local DNS server is determined to be the minimum cache time threshold.

6. The method according to claim 2, characterized in that, When the pre-set protection domain CDN suffix includes the second protection domain CDN suffix, the number of IP addresses corresponding to the service domain name is multiple; The step of matching the CDN suffix of the endpoint domain name in the alias record chain with the pre-set CDN suffix of the protection domain, and performing differentiated response processing for domain name resolution based on the matching result, includes: The CDN suffix of the endpoint domain name in the alias record chain is matched with the CDN suffix of the second protection domain. Based on the matching result, the target IP address is determined from all IP addresses corresponding to the business domain name, and the target IP address is returned to the client.

7. The method according to claim 6, characterized in that, The step of matching the CDN suffix of the endpoint domain name in the alias record chain with the CDN suffix of the second protection domain, and determining the target IP address from all IP addresses corresponding to the business domain name based on the matching result, includes: If the CDN suffix of the endpoint domain name in the alias record chain matches the CDN suffix of the second protection domain, the target IP address is determined by polling all IP addresses corresponding to the business domain name. If the CDN suffix of the endpoint domain name in the alias record chain does not match the CDN suffix of the second protection domain, then all IP addresses corresponding to the business domain name are sorted according to the preset address sorting strategy, and the target IP address is determined based on the sorting result.

8. The method according to claim 2, characterized in that, When the pre-set protection domain CDN suffix includes a third protection domain CDN suffix for ensuring precise scheduling, the step of matching the CDN suffix of the endpoint domain in the alias record chain with the pre-set protection domain CDN suffix, and performing differentiated response processing for domain name resolution based on the matching result, includes: If the CDN suffix of the endpoint domain name in the alias record chain matches the CDN suffix of the third protection domain, then the business domain name is added to the EDNS cache partition and forwarded to the EDNS dedicated recursive server for recursive query to obtain the IP address corresponding to the business domain name.

9. A domain name resolution device, characterized in that, include: The request receiving module is used to receive business domain name resolution requests sent by the client; The recursive query module is used to perform a recursive query to the authoritative DNS server based on the business domain name to be resolved in the business domain name resolution request if it is detected that the IP address corresponding to the business domain name does not exist in the local cache. The resolution result includes: the alias record chain corresponding to the business domain name and the IP address corresponding to the business domain name in the CDN network. The response processing module is used to match the CDN suffix of the endpoint domain name in the alias record chain with the pre-set CDN suffix of the security domain, and perform differentiated response processing for domain name resolution based on the matching result.

10. A domain name resolution system, characterized in that, The system includes: a client, a local DNS server, and an authoritative DNS server; The local DNS server is used to implement the domain name resolution method according to any one of claims 1-8.

11. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the domain name resolution method according to any one of claims 1-8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the domain name resolution method according to any one of claims 1-8.

Images