WO2021042673A1 - Dns解析方法、权威dns服务器和dns解析系统 - Google Patents

Dns解析方法、权威dns服务器和dns解析系统 Download PDF

Info

Publication number
WO2021042673A1
WO2021042673A1 PCT/CN2020/074967 CN2020074967W WO2021042673A1 WO 2021042673 A1 WO2021042673 A1 WO 2021042673A1 CN 2020074967 W CN2020074967 W CN 2020074967W WO 2021042673 A1 WO2021042673 A1 WO 2021042673A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
target domain
name resolution
content information
records
Prior art date
Application number
PCT/CN2020/074967
Other languages
English (en)
French (fr)
Inventor
陈单江
Original Assignee
网宿科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 网宿科技股份有限公司 filed Critical 网宿科技股份有限公司
Priority to EP20776061.2A priority Critical patent/EP3809676A4/en
Priority to US17/061,510 priority patent/US11245661B2/en
Publication of WO2021042673A1 publication Critical patent/WO2021042673A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/58—Caching of addresses or names
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • This application relates to the technical field of domain name resolution, in particular to a DNS resolution method, an authoritative DNS server and a DNS resolution system.
  • Domain name resolution is to resolve the domain name into the corresponding IP address, so that the client can access the domain name by accessing the IP address, and obtain the content contained in the domain name.
  • the client When performing domain name resolution, the client first sends the target domain name resolution request to the LDNS (Local DNS) server. If the LDNS server does not cache the target domain name resolution result, the LDNS server sends the target domain name resolution request to the authoritative DNS server for resolution. In the process of resolving the target domain name, both the LDNS server and the authoritative DNS server query the target domain name, and use the IP addresses of all CDN servers that provide services for the target domain name as the target domain name resolution result.
  • LDNS Local DNS
  • the CDN server can provide services for the target domain name, it may not cache the content required by the client. At this time, the client still needs to pass Go back to the source to get the content you need, and increase back-to-source bandwidth consumption.
  • the embodiments of the present application provide a DNS resolution method, an authoritative DNS server, and a DNS resolution system.
  • the technical solution is as follows.
  • a DNS resolution method including:
  • Target domain name resolution request sent by an LDNS server, where the target domain name resolution request includes content information
  • a target domain name resolution result is determined, and the target domain name resolution result is returned to the LDNS server.
  • determining the target domain name resolution result according to the content information includes:
  • the method before the receiving the target domain name resolution request sent by the LDNS server, the method further includes:
  • the A record corresponding to the content information is pre-configured locally.
  • the method further includes:
  • the A records corresponding to the content information are deleted.
  • the method further includes:
  • the determining the A record corresponding to the content information and using all the A records as the target domain name resolution result includes:
  • the number of historical requests determine that the number of A records corresponding to the content information is N from the relationship table of the number of historical requests-the number of A records;
  • the content information includes the URL corresponding to the target domain name resolution request.
  • a DNS resolution method including:
  • the target domain name resolution request is forwarded to the authoritative DNS server.
  • determining the target domain name resolution result in the locally cached LDNS resolution record according to the content information includes:
  • the resolution record corresponding to the content information is used as the target domain name resolution result.
  • the method further includes:
  • a DNS resolution method including:
  • an authoritative DNS server including:
  • the transceiver module is configured to receive the target domain name resolution request sent by the LDNS server, and return the target domain name resolution result to the LDNS server, wherein the target domain name resolution request includes content information;
  • the parsing module is used to determine the A record corresponding to the content information, and use all the A records as the target domain name resolution result.
  • the authoritative DNS server may further include a configuration module, configured to locally pre-configure the A record corresponding to the content information or the historical request number-A record number relationship table.
  • a configuration module configured to locally pre-configure the A record corresponding to the content information or the historical request number-A record number relationship table.
  • an authoritative DNS server includes a memory and a processor.
  • the memory stores at least one instruction, at least one program, code set, or instruction set.
  • the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the DNS resolution method described in the first aspect.
  • a DNS resolution system in a sixth aspect, includes a client, an LDNS server, and an authoritative DNS server.
  • the client is configured to execute the DNS resolution method described in the third aspect.
  • the LDNS server It is used to execute the DNS resolution method described in the above second aspect, and the authoritative DNS server is used to execute the DNS resolution method described in the above first aspect.
  • the authoritative DNS server receives the target domain name resolution request sent by the LDNS server, wherein the target domain name resolution request includes content information; the authoritative DNS The server determines the target domain name resolution result according to the content information, and returns the target domain name resolution result to the LDNS server.
  • the authoritative DNS server can obtain more accurate target domain name resolution results for the content information contained in the target domain name resolution request when resolving the target domain name, and ensure that the target domain name resolution results point to
  • the CDN server stores the access content corresponding to the content information, which prevents the client from returning to the source and reduces the bandwidth consumption of the returning to the source.
  • Fig. 1 is a flowchart of a DNS resolution method provided by an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of an authoritative DNS server provided by an embodiment of the present application.
  • Fig. 3 is a schematic structural diagram of an authoritative DNS server provided by an embodiment of the present application.
  • the embodiment of the present application provides a DNS resolution method, which can be implemented by a client, an LDNS server, and an authoritative DNS server.
  • the client can be a terminal device such as a personal computer and a smart phone.
  • the client can obtain the resolution result of the target domain name through the LDNS server and the authoritative DNS server, and access the target domain name according to the resolution result of the target domain name.
  • the LDNS server and the authoritative DNS server can resolve the target domain name resolution request sent by the client.
  • the application scenario of this embodiment may be: when a user accesses a target domain name including file download, video-on-demand, video live broadcast and other types of content through the client, the client sends a target domain name resolution request to the LDNS server and resolves the target domain name.
  • the LDNS server After receiving the target domain name resolution request, the LDNS server determines the target domain name resolution result in the local cache according to the content information contained in the target domain name resolution request; if the target domain name resolution result is not cached locally, the LDNS server forwards the target domain name resolution request to Authoritative DNS server.
  • the authoritative DNS server also determines the target domain name resolution result according to the content information contained in the target domain name resolution request, and returns the target domain name resolution result to the LDNS server.
  • the LDNS server caches the target domain name resolution result locally and forwards the target domain name resolution result to the client at the same time. In this way, after receiving the target domain name resolution result, the client can determine the target CDN server according to the target domain name resolution result, and send subsequent data requests of the target domain name to the target CDN server.
  • Step 101 The client sends a target domain name resolution request to the LDNS server.
  • the target domain name resolution request contains content information.
  • the client when a user accesses content under the target domain name through the client, the client first sends a target domain name resolution request to the LDNS server, and obtains the IP address of the CDN server that provides services for the target domain name by performing DNS resolution on the target domain name . Then the client can send a data request to the CDN server to obtain the user's access to the target domain name.
  • the client can add the content information of the accessed content in the additional block of the target domain name resolution request.
  • the content information can indicate the specific content that the user wants to obtain in subsequent data requests.
  • the URL corresponding to the target domain name resolution request can be used as the content information.
  • the URL can identify the name, domain name, data path and other information of the accessed content, so as to avoid the confusion of the access content of the same name or data path under different domain names.
  • the client needs to resolve the domain name of http://app.wangsu.com/1.exe to obtain the target domain name
  • the client can add the URL corresponding to the target domain name resolution request: http://app.wangsu.com/1.exe as content information.
  • Step 102 The LDNS server receives the target domain name resolution request sent by the client, determines the target domain name resolution result in the locally cached LDNS resolution record according to the content information, and sends the target domain name resolution result to the client.
  • the LDNS server is locally provided with LDNS resolution records, and the LDNS resolution records are used to cache the resolution records of some domain names.
  • the LDNS resolution record may take the form of a DNS resolution table as shown in Table 1. As shown in Table 1, each resolution record in the DNS resolution table contains four items: client IP network segment, domain name information, content information, and A record. Of course, other content can be added as required.
  • the LDNS server After receiving the target domain name resolution request from the client, the LDNS server obtains the content information contained in the target domain name resolution request. The LDNS server determines the resolution result of the target domain name from the DNS resolution table according to the content information.
  • determine the target domain name resolution result in the locally cached LDNS resolution record according to the content information.
  • the specific processing may be as follows: determine the client IP network segment according to the target domain name resolution request; locally cache LDNS resolution In the record, find all the resolution records corresponding to the client IP network segment; determine the resolution record corresponding to the content information from all the resolution records corresponding to the client IP network segment; use the resolution record corresponding to the content information as the target domain name resolution result.
  • the LDNS server after receiving the target domain name resolution request, obtains the client IP (source IP) and content information from the target domain name resolution request.
  • the LDNS server obtains the corresponding client IP network segment through the client IP.
  • the LDNS server queries the client IP network segment in the locally cached LDNS resolution records, and obtains all the resolution records corresponding to the client IP network segment.
  • the LDNS server queries all the resolution records corresponding to the client's IP network segment with content information. If at least one analysis record is finally obtained, all A records contained in the analysis record are the analysis records corresponding to the content information.
  • the LDNS server uses these A records as the result of the target domain name resolution.
  • the LDNS server After receiving the target domain name resolution request of app.wangsu.com, the LDNS server obtains the client IP (source IP) 192.168.0.1 and content information http://app.wangsu.com/1 from the target domain name resolution request. .exe.
  • the LDNS server obtains the corresponding client IP network segment 192.168.0.0/24 through 192.168.0.1.
  • the LDNS server queries the client IP network segment field with 192.168.0.0/24 in the DNS resolution table (Table 1), and obtains two resolution records with serial numbers 1 and 2.
  • the LDNS server further queries the content information field with http://app.wangsu.com/1.exe for these two parsing records. Finally, the resolution record with serial number 1 is obtained.
  • the resolution record contains four A records: 1.1.1.1, 2.2.2.2, 3.3.3.3 and 4.4.4.4. These four A records are the resolution records corresponding to the content information.
  • the LDNS server Use these four A records as the target domain name resolution result of app.wangsu.com.
  • Step 103 If there is no target domain name resolution result in the locally cached LDNS resolution record, the LDNS server forwards the target domain name resolution request to the authoritative DNS server.
  • the LDNS server searches through the above methods, if there is no resolution record corresponding to the client IP network segment in the locally cached LDNS resolution record, or there is no resolution record corresponding to the client IP network segment in all the resolution records corresponding to the client IP network segment.
  • the resolution record corresponding to the content information indicates that there is no target domain name resolution result in the resolution record locally cached by the LDNS server. Therefore, LDNS forwards the target domain name resolution request to the authoritative DNS server, so that the authoritative DNS server can resolve the target domain name and obtain the target domain name resolution result.
  • Step 104 The authoritative DNS server receives the target domain name resolution request sent by the LDNS server, and determines the target domain name resolution result according to the content information.
  • the LDNS server forwards the target domain name resolution request to the authoritative DNS server after being unable to obtain the target domain name resolution result locally.
  • the authoritative DNS server receives the target domain name resolution request, and obtains the content information included in the target domain name resolution request. After that, the authoritative DNS server determines the resolution result of the target domain name according to the content information.
  • the CDN server may not store the content required by the client, which results in the need to retrieve it back to the source.
  • the corresponding processing can be as follows: Determine the A record corresponding to the content information, and use all A records as the target domain name resolution result.
  • the authoritative DNS server stores a large number of A records of the target domain name. If these A records are directly sent to the client as the result of the target domain name resolution.
  • the client sends data requests for the target domain name to the CDN server corresponding to these A records according to the result of the target domain name resolution, the content required by the client may not be stored on these CDN servers, which will cause the client to get back to the source.
  • a process similar to that of the LDNS server can be used.
  • the authoritative DNS server obtains the content information from the target domain name resolution request. After that, it determines all the A records of the target domain name, and then further determines the A records corresponding to the content information from all the A records of the target domain name, and all the A records corresponding to the content information As the result of the target domain name resolution.
  • the authoritative DNS server since the authoritative DNS server stores a large number of A records of the target domain name, in order to be able to more accurately cache the A records corresponding to the CDN server with the content required by the client, and send it to the client as the result of the target domain name resolution ,
  • the corresponding processing can be as follows: pre-configure the A record corresponding to the content information locally.
  • the authoritative DNS server may locally configure the A record corresponding to the content information locally, that is, the A record of the CDN server storing the content corresponding to the content information as the A record corresponding to the content information.
  • the authoritative DNS server receives the domain name resolution request, it can obtain the content information from the domain name resolution request, and then obtain the corresponding A record according to the content information. In this way, it can be ensured as far as possible that the client can obtain the content from the corresponding CDN server when sending a data request to obtain the content under the target domain name through the resolution result of the target domain name, thereby reducing the occurrence of client returning to the source.
  • the number of A records corresponding to the content information can be dynamically adjusted to save bandwidth and avoid waste of the CDN server.
  • the corresponding processing can be as follows: calculate the target domain name resolution request received before the current time node, including the content The number of target domain name resolution requests for the information is used as the number of historical requests for content information; the number of A records corresponding to the content information is determined as the number of A records for content information; if the number of historical requests is greater than or equal to the preset request number threshold, and the A record If the number is less than the preset maximum number of A records, the A record corresponding to the content information will be added; if the number of historical requests is less than the preset request number threshold, and the number of A records is greater than the preset minimum number of A records, then the content corresponding to the content information will be deleted A record.
  • the authoritative DNS server after the authoritative DNS server returns the target domain name resolution result to the LDNS server, it can use the current time as the node to calculate the number of target domain name resolution requests that contain the same content information in the target domain name resolution requests received before, and get The result is the number of historical requests for the content information.
  • the authoritative DNS server can also count the number of A records corresponding to the content information, and use the obtained result as the number of A records of the content information.
  • the authoritative DNS server compares the number of historical requests with the preset threshold of the number of requests. If the number of historical requests is greater than or equal to the threshold of the preset number of requests, it means that the access content corresponding to the content information has higher access requirements, and the corresponding content information can be increased. A record number. In this way, the authoritative DNS server can return more A records to the client through the resolution result of the target domain name. This allows the client to subsequently send a data request to the target domain name, and when obtaining the access content, there are more CDN servers to choose from, thereby reducing the load of a single CDN server and improving the carrying capacity and performance of the CDN server.
  • the maximum number of A records can also be preset.
  • the authoritative DNS server compares the number of A records of the content information with the maximum number of A records.
  • the authoritative DNS server can return fewer A records to the client through the resolution result of the target domain name, thereby concentrating such access content with lower access requirements in one or several CDN servers.
  • the access volume of such access content on a single CDN server can be increased, and the CDN server can avoid being deleted, thereby preventing the client from returning to the source, and at the same time, saving the cache space of other CDN servers.
  • the minimum number of A records can also be set in advance.
  • the authoritative DNS server compares the number of A records of the content information with the minimum number of A records. If the number of A records of the content information is greater than the preset minimum number of A records, it will be deleted. The A record corresponding to the content information is subtracted; if the number of A records of the content information is less than or equal to the preset minimum value of the number of A records, there is no need to process the A records of the content information.
  • the minimum number of A records should be greater than or equal to 1, and the minimum number of A records should not be set too small, otherwise it may cause excessive access to the CDN server storing this type of access content. , The load is too high.
  • the authoritative DNS server may also pre-configure the historical request number-A record number relationship table locally, and then determine the target domain name resolution result according to the historical request number-A record number relationship table, and the corresponding processing may be as follows: Among the target domain name resolution requests received before the current time node, the number of target domain name resolution requests containing content information is used as the number of historical requests for content information; according to the number of historical requests, determine from the relationship table of the number of historical requests-the number of records in A The number of A records corresponding to the content information is N; N A records are selected from all A records of the target domain name as the A records corresponding to the content information; all A records corresponding to the content information are used as the target domain name resolution result.
  • the authoritative DNS server can also pre-configure a relationship table of the number of historical requests-the number of A records locally (as shown in Table 2). After the authoritative DNS server obtains the content information from the target domain name resolution request, it uses the current time as the node to calculate the number of target domain name resolution requests that contain the same content information in the target domain name resolution request received before, and use the obtained result as the target domain name resolution request. The number of historical requests for content information. After that, the authoritative DNS server queries the relationship table between the number of historical requests and the number of A records, and finds the number of A records related to the number of historical requests as the number of A records N corresponding to the content information.
  • the authoritative DNS server selects N A records from all A records of the target domain name according to preset selection rules (such as random, order, reverse order, weight, etc.) as the A records corresponding to the content information.
  • the authoritative DNS server uses the A record corresponding to the content information as the target domain name resolution result.
  • Number of historical requests Number of A records (N) 0-10 1 11-100 3 101-500 5 501-1000 10
  • Step 105 The authoritative DNS server returns the resolution result of the target domain name to the LDNS server.
  • the authoritative DNS server returns the target domain name resolution result to the LDNS server after obtaining the target domain name resolution result, so that the LDNS server forwards the target domain name resolution result to the client.
  • Step 106 The LDNS server receives the target domain name resolution result sent by the authoritative DNS server, and stores the target domain name resolution result in the LDNS resolution record.
  • the authoritative DNS server After the authoritative DNS server obtains the resolution result of the target domain name, it sends it to the LDNS server.
  • the LDNS server receives the target domain name resolution result, and stores the target domain name resolution result in the aforementioned LDNS resolution record locally cached by the LDNS server. In this way, when the LDNS server receives the target domain name resolution request again, it can obtain the corresponding target domain name resolution result from the locally cached LDNS resolution record.
  • Step 107 The LDNS server forwards the resolution result of the target domain name to the client.
  • the LDNS server forwards the target domain name resolution result to the client.
  • Step 108 The client receives the target domain name resolution result returned by the LDNS server, and sends a data request for the target domain name to the corresponding CDN server according to the target domain name resolution result.
  • the client after receiving the target domain name resolution result returned by the LDNS server, the client can select an IP address from the target domain name resolution result as the destination IP, and send a data request for the target domain name to the CDN server corresponding to the destination IP. To access the content under the target domain name.
  • the authoritative DNS server receives the target domain name resolution request sent by the LDNS server, wherein the target domain name resolution request contains content information; the authoritative DNS server determines the target domain name resolution result according to the content information, and The target domain name resolution result is returned to the LDNS server.
  • the authoritative DNS server can obtain more accurate target domain name resolution results for the content information contained in the target domain name resolution request when resolving the target domain name, and ensure that the target domain name resolution results point to
  • the CDN server stores the access content corresponding to the content information, which prevents the client from returning to the source and reduces the bandwidth consumption of the returning to the source.
  • the embodiment of the present application also provides an authoritative DNS server, as shown in FIG. 2, including:
  • the transceiver module 201 is configured to receive a target domain name resolution request sent by an LDNS server, and return the target domain name resolution result to the LDNS server, wherein the target domain name resolution request includes content information.
  • the parsing module 202 is configured to determine the A record corresponding to the content information, and use all the A records as the target domain name resolution result.
  • the authoritative DNS server further includes a configuration module 203, configured to locally pre-configure the A record corresponding to the content information or the historical request number-A record number relationship table.
  • the embodiments of the present application also provide an authoritative DNS server.
  • the authoritative DNS server may have greater differences due to different configurations or performances.
  • the authoritative DNS server includes one or more memories and processors. It can be short-term storage or permanent storage.
  • the memory may store at least one instruction, at least one program, code set or instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the above-mentioned DNS resolution method.
  • an embodiment of the present application also provides a DNS resolution system.
  • the DNS resolution system includes a client, an LDNS server, and an authoritative DNS server.
  • the client, the LDNS server, and the authoritative DNS server Used to perform the DNS resolution method described above.
  • the authoritative DNS server provided in the above embodiment realizes DNS resolution
  • only the division of the above functional modules is used as an example.
  • the above functions can be allocated by different functional modules as needed. That is, the internal structure of the authoritative DNS server is divided into different functional modules to complete all or part of the functions described above.
  • the authoritative DNS server provided in the foregoing embodiment and the DNS resolution method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be realized by hardware.
  • the above technical solution essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM/RAM, magnetic A disc, an optical disc, etc., include a number of instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute each embodiment or some part of the method of the embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种DNS解析方法、权威DNS服务器和DNS解析系统，涉及域名解析技术领域。所述方法包括：权威DNS服务器接收LDNS服务器发来的目标域名解析请求，其中，所述目标域名解析请求中包含内容信息；权威DNS服务器根据所述内容信息，确定目标域名解析结果(104)，并将所述目标域名解析结果返回所述LDNS服务器(105)。本申请能够减少客户端回源，降低回源带宽消耗。

Description

DNS解析方法、权威DNS服务器和DNS解析系统
交叉引用
本申请引用于2019年09月05日递交的名称为“DNS解析方法、权威DNS服务器和DNS解析系统”的第201910838225.7号中国专利申请，其通过引用被全部并入本申请
技术领域
本申请涉及域名解析技术领域，尤其涉及一种DNS解析方法、权威DNS服务器和DNS解析系统。
背景技术
域名解析是把域名解析为对应的IP地址，使得客户端可以通过访问该IP地址，实现对域名的访问，获取该域名包含的内容。
在进行域名解析时，客户端先将目标域名解析请求发送给LDNS(Local DNS)服务器。如果LDNS服务器未缓存有目标域名解析结果，LDNS服务器则将目标域名解析请求发送给权威DNS服务器进行解析。在对目标域名解析的过程中LDNS服务器和权威DNS服务器都是通过查询目标域名，将所有为目标域名提供服务的CDN服务器的IP地址作为目标域名解析结果。
在实现本申请的过程中，发明人发现现有技术中至少存在以下问题：CDN服务器虽然能够为目标域名提供服务，但可能并未缓存客户端所需的内容，此时，客户端仍需要通过回源获取所需内容，增加回源带宽消耗。
发明内容
为了解决现有技术的问题，本申请实施例提供了一种DNS解析方法、权威DNS服务器和DNS解析系统。所述技术方案如下。
第一方面，提供了一种DNS解析方法，包括：
接收LDNS服务器发来的目标域名解析请求，其中，所述目标域名解析请求中包含内容信息；
根据所述内容信息，确定目标域名解析结果，并将所述目标域名解析结果返回所述LDNS服务器。
例如，所述根据所述内容信息，确定目标域名解析结果，包括：
确定所述内容信息对应的A记录，将全部所述A记录作为所述目标域名解析结果。
例如，在所述接收LDNS服务器发来的目标域名解析请求之前，所述方法还包括：
在本地预先配置所述内容信息对应的A记录。
例如，所述方法还包括：
计算当前时间节点之前接收到的目标域名解析请求中，包含所述内容信息的目标域名解析请求的数量，作为所述内容信息的历史请求数；
确定所述内容信息对应的A记录的数量，作为所述内容信息的A记录数；
如果所述历史请求数大于等于预设请求数阈值，且所述A记录数小于预设A记录数最大值，则增加所述内容信息对应的A记录；
如果所述历史请求数小于预设请求数阈值，且所述A记录数大于预设A记录数最小值，则删减所述内容信息对应的A记录。
例如，所述方法还包括：
在本地预先配置历史请求数-A记录数关系表；
所述确定所述内容信息对应的A记录，将全部所述A记录作为所述目标域名解析结果，包括：
计算当前时间节点之前接收到的目标域名解析请求中，包含所述内容信息 的目标域名解析请求的数量，作为所述内容信息的历史请求数；
根据所述历史请求数，从所述历史请求数-A记录数关系表中，确定所述内容信息对应的A记录数为N；
从所述目标域名的全部A记录中选择N个A记录，作为所述内容信息对应的A记录；
将所述内容信息对应的全部A记录作为所述目标域名解析结果。
例如，所述内容信息包括所述目标域名解析请求对应的URL。
第二方面，提供了一种DNS解析方法，包括：
接收客户端发来的目标域名解析请求，其中，所述目标域名解析请求中包含内容信息；
根据所述内容信息，在本地缓存的LDNS解析记录中，确定目标域名解析结果，并将所述目标域名解析结果发送给所述客户端；
如果本地缓存的LDNS解析记录中没有所述目标域名解析结果，则将所述目标域名解析请求转发给权威DNS服务器。
例如，所述根据所述内容信息，在本地缓存的LDNS解析记录中，确定目标域名解析结果，包括：
根据所述目标域名解析请求，确定客户端IP网段；
在所述本地缓存的LDNS解析记录中，查找所述客户端IP网段对应的全部解析记录；
从所述客户端IP网段对应的全部解析记录中，确定所述内容信息对应的解析记录；
将所述内容信息对应的解析记录作为所述目标域名解析结果。
例如，在所述将所述目标域名解析请求转发给权威DNS服务器之后，所述方法还包括：
接收所述权威DNS服务器发来的所述目标域名解析结果；
将所述目标域名解析结果存储在所述LDNS解析记录中；
将所述目标域名解析结果转发给所述客户端。
第三方面，提供了一种DNS解析方法，包括：
向所述LDNS服务器发送目标域名解析请求，其中，所述目标域名解析请求中包含内容信息，以使所述LDNS服务器或权威DNS服务器根据所述内容信息，确定目标域名解析结果；
接收所述LDNS服务器返回的所述目标域名解析结果，根据所述目标域名解析结果向对应的CDN服务器发送目标域名数据请求。
第四方面，提供了一种权威DNS服务器，包括：
收发模块，用于接收LDNS服务器发来的目标域名解析请求，将目标域名解析结果返回所述LDNS服务器，其中，所述目标域名解析请求中包含内容信息；
解析模块，用于确定所述内容信息对应的A记录，将全部所述A记录作为所述目标域名解析结果。
例如，所述权威DNS服务器，还包括配置模块，用于：在本地预先配置所述内容信息对应的A记录或历史请求数-A记录数关系表。
第五方面，提供了一种权威DNS服务器，所述权威DNS服务器包括存储器和处理器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现上述第一方面所述的DNS解析方法。
第六方面，提供了一种DNS解析系统，所述DNS解析系统包括客户端、LDNS服务器和权威DNS服务器，所述客户端用于执行上述第三方面所述的DNS解析方法，所述LDNS服务器用于执行上述第二方面所述的DNS解析方法，所述权威DNS服务器用于执行上述第一方面所述的DNS解析方法。
本申请实施例提供的技术方案带来的有益效果是：本申请实施例中，权威DNS服务器接收LDNS服务器发来的目标域名解析请求，其中，所述目标域名解析请求中包含内容信息；权威DNS服务器根据所述内容信息，确定目标域 名解析结果，并将所述目标域名解析结果返回所述LDNS服务器。这样，通过在域名解析请求中加入内容信息，使得权威DNS服务器可以在对目标域名进行解析时，针对目标域名解析请求包含的内容信息，得到更准确的目标域名解析结果，保障目标域名解析结果指向的CDN服务器上存储有内容信息对应的访问内容，避免客户端回源，降低回源带宽消耗。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的一种DNS解析方法的流程图；
图2是本申请实施例提供的一种权威DNS服务器的结构示意图；
图3是本申请实施例提供的一种权威DNS服务器的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施例作进一步地详细描述。
本申请实施例提供了一种DNS解析方法，该方法可以由客户端、LDNS服务器和权威DNS服务器共同实现。其中，客户端可以是个人计算机、智能手机等终端设备。客户端可以通过LDNS服务器和权威DNS服务器获得目标域名解析结果，并根据目标域名解析结果，访问目标域名。LDNS服务器和权威DNS服务器可以对客户端发来的目标域名解析请求进行解析。本实施例的应用场景可以是：当用户通过客户端对目标域名进行包括文件下载、视频点播、视频直播等类型的内容访问时，客户端向LDNS服务器发送目标域名解析请求，并在目标域名解析请求中加入内容信息。LDNS服务器接收到目标域名解析请求后， 根据目标域名解析请求中包含的内容信息，在本地缓存中确定目标域名解析结果；如果本地没有缓存目标域名解析结果，LDNS服务器则将目标域名解析请求转发给权威DNS服务器。权威DNS服务器同样根据目标域名解析请求中包含的内容信息，确定目标域名解析结果，并将目标域名解析结果返回LDNS服务器。LDNS服务器在接收到目标域名解析结果后，在本地缓存目标域名解析结果，同时将目标域名解析结果转发给客户端。这样，客户端在接收到目标域名解析结果后，就可以根据目标域名解析结果确定目标CDN服务器，将目标域名后续的数据请求发往目标CDN服务器。
下面将结合具体实施例，对图1所示的一种DNS解析流程进行详细的说明，内容可以如下。
步骤101：客户端向LDNS服务器发送目标域名解析请求。其中，目标域名解析请求中包含内容信息。
在实施中，用户通过客户端对目标域名下的内容进行访问时，客户端首先向LDNS服务器发送目标域名解析请求，通过对目标域名进行DNS解析，获得为目标域名提供服务的CDN服务器的IP地址。然后客户端才能向该CDN服务器发送数据请求，以获得用户对目标域名的访问内容。客户端在构造目标域名解析请求时，可以在目标域名解析请求的附加块中加入访问内容的内容信息。内容信息可以标示用户后续数据请求所想要得到的具体内容。通常，可以使用目标域名解析请求对应的URL作为内容信息。URL可以标识访问内容的名称、所属域名、数据路径等信息，避免不同域名下相同名称或数据路径的访问内容混淆。
例如，用户通过客户端对http://app.wangsu.com/1.exe进行访问时，客户端需要对http://app.wangsu.com/1.exe进行域名解析，以获得为目标域名app.wangsu.com提供服务的CDN服务器的IP地址。客户端在目标域名解析请求中，可以加入目标域名解析请求对应的URL：http://app.wangsu.com/1.exe作为内容信息。
步骤102：LDNS服务器接收客户端发来的目标域名解析请求，根据内容信息，在本地缓存的LDNS解析记录中，确定目标域名解析结果，并将目标域名解析结果发送给客户端。
在实施中，LDNS服务器本地设置有LDNS解析记录，LDNS解析记录用于缓存部分域名的解析记录。LDNS解析记录可以采用如表1所示的DNS解析表的形式。如表1所示，DNS解析表中每一条解析记录包含有客户端IP网段、域名信息、内容信息和A记录四项内容，当然，也可以根据需求添加其他内容。LDNS服务器在接收到客户端发来的目标域名解析请求后，获取目标域名解析请求中包含的内容信息。LDNS服务器根据内容信息，从DNS解析表中，确定目标域名解析结果。
表1 DNS解析表
Figure PCTCN2020074967-appb-000001
在一个实施例中，根据内容信息，在本地缓存的LDNS解析记录中，确定目标域名解析结果，具体的处理可以如下：根据目标域名解析请求，确定客户端IP网段；在本地缓存的LDNS解析记录中，查找客户端IP网段对应的全部解析记录；从客户端IP网段对应的全部解析记录中，确定内容信息对应的解析记录；将内容信息对应的解析记录作为目标域名解析结果。
在实施中，在接收到目标域名解析请求后，LDNS服务器从目标域名解析请求中获取客户端IP(源IP)和内容信息。LDNS服务器通过客户端IP，得到 对应的客户端IP网段。之后，参考表1，LDNS服务器在本地缓存的LDNS解析记录中，以客户端IP网段进行查询，获得该客户端IP网段对应的全部解析记录。LDNS服务器再从该客户端IP网段对应的全部解析记录中以内容信息进行查询。如果最终得到至少一条解析记录，则解析记录中包含的所有A记录即是内容信息对应的解析记录。LDNS服务器将这些A记录作为目标域名解析结果。
例如，在接收到app.wangsu.com的目标域名解析请求后，LDNS服务器从目标域名解析请求中获取客户端IP(源IP)192.168.0.1和内容信息http://app.wangsu.com/1.exe。LDNS服务器通过192.168.0.1，得到对应的客户端IP网段192.168.0.0/24。LDNS服务器在DNS解析表(表1)中，以192.168.0.0/24查询客户端IP网段字段，获得序号为1和2两条解析记录。LDNS服务器进一步对这两条解析记录，以http://app.wangsu.com/1.exe查询内容信息字段。最终得到序号为1这条解析记录，该解析记录中包含有四条A记录：1.1.1.1，2.2.2.2，3.3.3.3和4.4.4.4，这四条A记录就是内容信息对应的解析记录，LDNS服务器将这四条A记录作为app.wangsu.com的目标域名解析结果。
步骤103：如果本地缓存的LDNS解析记录中没有目标域名解析结果，LDNS服务器则将目标域名解析请求转发给权威DNS服务器。
在实施中，LDNS服务器在通过上述方法进行查找的过程中，如果本地缓存的LDNS解析记录中没有客户端IP网段对应的解析记录，或者，客户端IP网段对应的全部解析记录中，没有内容信息对应的解析记录，则表示LDNS服务器本地缓存的解析记录中，没有目标域名解析结果。因此，LDNS将目标域名解析请求转发给权威DNS服务器，以使权威DNS服务器对目标域名进行解析，获得目标域名解析结果。
步骤104：权威DNS服务器接收LDNS服务器发来的目标域名解析请求，根据内容信息，确定目标域名解析结果。
在实施中，LDNS服务器在无法从本地得到目标域名解析结果后，向权威DNS服务器转发目标域名解析请求。权威DNS服务器接收目标域名解析请求， 获得该目标域名解析请求中包含的内容信息。之后，权威DNS服务器根据该内容信息，确定目标域名解析结果。
在一个实施例中，当客户端根据目标域名解析结果，向CDN服务器发送针对目标域名的数据请求时，由于CDN服务器可能没有存储客户端所需要的内容，从而导致需要回源获取，为了降低这种情况的发生，相应的处理可以如下：确定内容信息对应的A记录，将全部A记录作为目标域名解析结果。
在实施中，权威DNS服务器中存储有大量目标域名的A记录，如果直接将这些A记录作为目标域名解析结果发送给客户端。客户端在根据目标域名解析结果，向这些A记录对应的CDN服务器发送针对目标域名的数据请求时，由于这些CDN服务器上可能没有存储客户端所需要的内容，会导致客户端需要回源获取。为了降低这种情况的发生，可以采用与LDNS服务器相似的处理过程。权威DNS服务器从目标域名解析请求中获得内容信息，之后，确定目标域名的所有A记录，再进一步从目标域名的所有A记录中，确定内容信息对应的A记录，将内容信息对应的所有A记录作为目标域名解析结果。
在一个实施例中，由于权威DNS服务器中存储有大量目标域名的A记录，为了能够更准确的将缓存有客户端所需内容的CDN服务器对应的A记录，作为目标域名解析结果发送给客户端，相应的处理可以如下：在本地预先配置内容信息对应的A记录。
在实施中，权威DNS服务器可以预先在本地配置内容信息对应的A记录，即将存储有内容信息对应内容的CDN服务器的A记录，作为内容信息对应的A记录。当权威DNS服务器接收到域名解析请求后，就可以从域名解析请求中获取内容信息，再根据内容信息得到对应的A记录。这样，可以尽量保证客户端通过目标域名解析结果，发送数据请求获取目标域名下的内容时，能够从对应的CDN服务器获取该内容，减少客户端回源发生。
在一个实施例中，可以通过动态调整内容信息对应的A记录的数量，以节省带宽，避免CDN服务器浪费，相应的处理可以如下：计算当前时间节点之 前接收到的目标域名解析请求中，包含内容信息的目标域名解析请求的数量，作为内容信息的历史请求数；确定内容信息对应的A记录的数量，作为内容信息的A记录数；如果历史请求数大于等于预设请求数阈值，且A记录数小于预设A记录数最大值，则增加内容信息对应的A记录；如果历史请求数小于预设请求数阈值，且A记录数大于预设A记录数最小值，则删减内容信息对应的A记录。
在实施中，权威DNS服务器在将目标域名解析结果返回LDNS服务器之后，可以以当前时间作为节点，计算之前接收到的目标域名解析请求中，包含同样内容信息的目标域名解析请求的数量，将得到的结果作为该内容信息的历史请求数。权威DNS服务器还可以统计该内容信息对应的A记录的数量，将得到的结果作为该内容信息的A记录数。
权威DNS服务器将历史请求数与预设的请求数阈值比较，如果历史请求数大于等于预设请求数阈值，表示该内容信息对应的访问内容具有较高的访问需求，可以增加该内容信息对应的A记录数量。这样，权威DNS服务器可以通过目标域名解析结果，返回更多的A记录给客户端。使得客户端后续向目标域名发送数据请求，获取该访问内容时，有更多的CDN服务器可以选择，从而降低单台CDN服务器的负载，提高CDN服务器的承载能力和性能。然而，如果无限制的增加A记录数量，将可能导致大量CDN服务器都缓存该访问内容，单台CDN服务器的负载过低，浪费CDN服务器资源，甚至可能由于访问量不足，使得该访问内容被CDN服务器删除，从而导致客户端需要回源获取。因此，还可以预先设置A记录数最大值，权威DNS服务器将该内容信息的A记录数与A记录数最大值比较，如果该内容信息的A记录数小于预设A记录数最大值，则增加内容信息对应的A记录；如果该内容信息的A记录数已经大于或等于预设A记录数最大值，则不需对该内容信息的A记录进行处理。
相似的，如果历史请求数小于预设请求数阈值，表示该内容信息对应访问内容的访问需求较低，可以减少该内容信息对应的A记录数量。这样，权威 DNS服务器可以通过目标域名解析结果，返回更少的A记录给客户端，从而将这类访问需求较低的访问内容集中在一台或几台CDN服务器中。这样，能够提高这类访问内容在单台CDN服务器上的访问量，避免被CDN服务器删除，从而避免客户端回源，同时，也能够节约其他CDN服务器的缓存空间。当然，如果无限制的减少A记录数量，最终可能导致该内容信息对应的A记录数量为零，使得客户端每次都需要回源获取。因此，还可以预先设置A记录数最小值，权威DNS服务器将该内容信息的A记录数与A记录数最小值比较，如果该内容信息的A记录数大于预设A记录数最小值，则删减内容信息对应的A记录；如果该内容信息的A记录数已经小于或等于预设A记录数最小值，则不需对该内容信息的A记录进行处理。需要说明的是，如前文所述，A记录数最小值应当大于等于1，并且，A记录数最小值不应当设置太小，否则可能反而导致存储这类访问内容的CDN服务器的访问量过大，负载过高。
在一个实施例中，权威DNS服务器还可以在本地预先配置历史请求数-A记录数关系表，然后根据历史请求数-A记录数关系表，确定目标域名解析结果，相应的处理可以如下：计算当前时间节点之前接收到的目标域名解析请求中，包含内容信息的目标域名解析请求的数量，作为内容信息的历史请求数；根据历史请求数，从历史请求数-A记录数关系表中，确定内容信息对应的A记录数为N；从目标域名的全部A记录中选择N个A记录，作为内容信息对应的A记录；将内容信息对应的全部A记录作为目标域名解析结果。
在实施中，权威DNS服务器还可以在本地预先配置历史请求数-A记录数关系表(如表2所示)。权威DNS服务器在从目标域名解析请求中获取内容信息后，以当前时间作为节点，计算之前接收到的目标域名解析请求中，包含同样内容信息的目标域名解析请求的数量，将得到的结果作为该内容信息的历史请求数。之后，权威DNS服务器查询历史请求数-A记录数关系表，找到该历史请求数相关的A记录数，作为该内容信息对应的A记录数N。权威DNS服务器按照预先设定的选择规则(如随机，顺序，倒序、权重等)，从目标域名的全部 A记录中，选择N个A记录，作为内容信息对应的A记录。权威DNS服务器再将这些内容信息对应的A记录作为目标域名解析结果。
表2历史请求数-A记录数关系表
历史请求数 A记录数(N)
0-10 1
11-100 3
101-500 5
501-1000 10
步骤105：权威DNS服务器将目标域名解析结果返回LDNS服务器。
在实施中，权威DNS服务器在得到目标域名解析结果后，将目标域名解析结果返回给LDNS服务器，以使LDNS服务器将该目标域名解析结果转发给客户端。
步骤106：LDNS服务器接收权威DNS服务器发来的目标域名解析结果，将目标域名解析结果存储在LDNS解析记录中。
在实施中，权威DNS服务器在获得目标域名解析结果后，将其发送给LDNS服务器。LDNS服务器接收到该目标域名解析结果，将目标域名解析结果存储在前文所述的LDNS服务器本地缓存的LDNS解析记录中。这样，当LDNS服务器再次接收到该目标域名解析请求时，就可以从本地缓存的LDNS解析记录获取对应的目标域名解析结果。
步骤107：LDNS服务器将目标域名解析结果转发给客户端。
在实施中，LDNS服务器在存储目标域名解析结果后，将目标域名解析结果转发给客户端。
步骤108：客户端接收LDNS服务器返回的目标域名解析结果，根据目标域名解析结果向对应的CDN服务器发送针对目标域名的数据请求。
在实施中，在接收到LDNS服务器返回的目标域名解析结果后，客户端 就可以从目标域名解析结果中选择一个IP地址作为目的IP，向目的IP对应的CDN服务器发送针对目标域名的数据请求，以对目标域名下的内容进行访问。
本申请实施例中，权威DNS服务器接收LDNS服务器发来的目标域名解析请求，其中，所述目标域名解析请求中包含内容信息；权威DNS服务器根据所述内容信息，确定目标域名解析结果，并将所述目标域名解析结果返回所述LDNS服务器。这样，通过在域名解析请求中加入内容信息，使得权威DNS服务器可以在对目标域名进行解析时，针对目标域名解析请求包含的内容信息，得到更准确的目标域名解析结果，保障目标域名解析结果指向的CDN服务器上存储有内容信息对应的访问内容，避免客户端回源，降低回源带宽消耗。
基于相同的技术构思，本申请实施例还提供了一种权威DNS服务器，如图2所示，包括：
收发模块201，用于接收LDNS服务器发来的目标域名解析请求，将目标域名解析结果返回所述LDNS服务器，其中，所述目标域名解析请求中包含内容信息。
解析模块202，用于确定所述内容信息对应的A记录，将全部所述A记录作为所述目标域名解析结果。
在一个实施例中，如图3所示，所述权威DNS服务器，还包括配置模块203，用于在本地预先配置所述内容信息对应的A记录或历史请求数-A记录数关系表。
基于相同的技术构思，本申请实施例还提供了一种权威DNS服务器，所述权威DNS服务器可因配置或性能不同而产生较大的差异，包括一个和一个以上存储器和处理器，其中，存储器可以是短暂存储或永久存储。存储器可以存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现上述DNS解析方法。
基于相同的技术构思，本申请实施例还提供了一种DNS解析系统，所述 DNS解析系统包括客户端、LDNS服务器和权威DNS服务器，所述客户端、所述LDNS服务器和所述权威DNS服务器用于执行上所述的DNS解析方法。
需要说明的是：上述实施例提供的权威DNS服务器在实现DNS解析时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将权威DNS服务器的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。同时，上述实施例提供的权威DNS服务器与DNS解析方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
通过以上的实施例的描述，本领域的技术人员可以清楚地了解到各实施例可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务端，或者网络设备等)执行各个实施例或者实施例的某些部分的方法。
以上仅为本申请的较佳实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (14)

  1. 一种DNS解析方法，包括：
    接收LDNS服务器发来的目标域名解析请求，其中，所述目标域名解析请求中包含内容信息；
    根据所述内容信息，确定目标域名解析结果，并将所述目标域名解析结果返回所述LDNS服务器。
  2. 根据权利要求1所述的方法，其中，所述根据所述内容信息，确定目标域名解析结果，包括：
    确定所述内容信息对应的A记录，将全部所述A记录作为所述目标域名解析结果。
  3. 根据权利要求2所述的方法，其中，在所述接收LDNS服务器发来的目标域名解析请求之前，所述方法还包括：
    在本地预先配置所述内容信息对应的A记录。
  4. 根据权利要求3所述的方法，其中，所述方法还包括：
    计算当前时间节点之前接收到的目标域名解析请求中，包含所述内容信息的目标域名解析请求的数量，作为所述内容信息的历史请求数；
    确定所述内容信息对应的A记录的数量，作为所述内容信息的A记录数；
    如果所述历史请求数大于等于预设请求数阈值，且所述A记录数小于预设A记录数最大值，则增加所述内容信息对应的A记录；
    如果所述历史请求数小于预设请求数阈值，且所述A记录数大于预设A记录数最小值，则删减所述内容信息对应的A记录。
  5. 根据权利要求2所述的方法，其中，所述方法还包括：
    在本地预先配置历史请求数-A记录数关系表；
    所述确定所述内容信息对应的A记录，将全部所述A记录作为所述目标域名解析结果，包括：
    计算当前时间节点之前接收到的目标域名解析请求中，包含所述内容信息的目标域名解析请求的数量，作为所述内容信息的历史请求数；
    根据所述历史请求数，从所述历史请求数-A记录数关系表中，确定所述内容信息对应的A记录数为N；
    从所述目标域名的全部A记录中选择N个A记录，作为所述内容信息对应的A记录；
    将所述内容信息对应的全部A记录作为所述目标域名解析结果。
  6. 根据权利要求1所述的方法，其中，所述内容信息包括所述目标域名解析请求对应的URL。
  7. 一种DNS解析方法，包括：
    接收客户端发来的目标域名解析请求，其中，所述目标域名解析请求中包含内容信息；
    根据所述内容信息，在本地缓存的LDNS解析记录中，确定目标域名解析结果，并将所述目标域名解析结果发送给所述客户端；
    如果本地缓存的LDNS解析记录中没有所述目标域名解析结果，则将所述目标域名解析请求转发给权威DNS服务器。
  8. 根据权利要求7所述的方法，其中，所述根据所述内容信息，在本地缓存的LDNS解析记录中，确定目标域名解析结果，包括：
    根据所述目标域名解析请求，确定客户端IP网段；
    在所述本地缓存的LDNS解析记录中，查找所述客户端IP网段对应的全部解析记录；
    从所述客户端IP网段对应的全部解析记录中，确定所述内容信息对应的解析记录；
    将所述内容信息对应的解析记录作为所述目标域名解析结果。
  9. 根据权利要求7所述的方法，其中，在所述将所述目标域名解析请求转发给权威DNS服务器之后，所述方法还包括：
    接收所述权威DNS服务器发来的所述目标域名解析结果；
    将所述目标域名解析结果存储在所述LDNS解析记录中；
    将所述目标域名解析结果转发给所述客户端。
  10. 一种DNS解析方法，包括：
    向所述LDNS服务器发送目标域名解析请求，其中，所述目标域名解析请求中包含内容信息，以使所述LDNS服务器或权威DNS服务器根据所述内容信息，确定目标域名解析结果；
    接收所述LDNS服务器返回的所述目标域名解析结果，根据所述目标域名解析结果向对应的CDN服务器发送目标域名数据请求。
  11. 一种权威DNS服务器，包括：
    收发模块，用于接收LDNS服务器发来的目标域名解析请求，将目标域名解析结果返回所述LDNS服务器，其中，所述目标域名解析请求中包含内容信息；
    解析模块，用于确定所述内容信息对应的A记录，将全部所述A记录作为所述目标域名解析结果。
  12. 根据权利要求11所述的权威DNS服务器，其中，所述权威DNS服务器，还包括配置模块，用于：
    在本地预先配置所述内容信息对应的A记录或历史请求数-A记录数关系表。
  13. 一种权威DNS服务器，所述权威DNS服务器包括存储器和处理器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如权利要求1-6任一项所述的DNS解析方法。
  14. 一种DNS解析系统，所述DNS解析系统包括客户端、LDNS服务器和权威DNS服务器，所述客户端用于执行如权利要求10所述的DNS解析方法，所述LDNS服务器用于执行如权利要求7-9任一项所述的DNS解析方法，所述权威DNS服务器用于执行如1-6任一项所述的DNS解析方法。
PCT/CN2020/074967 2019-09-05 2020-02-12 Dns解析方法、权威dns服务器和dns解析系统 WO2021042673A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20776061.2A EP3809676A4 (en) 2019-09-05 2020-02-12 DNS RESOLUTION METHODS, AUTHORITATIVE DNS SERVER AND DNS RESOLUTION SYSTEM
US17/061,510 US11245661B2 (en) 2019-09-05 2020-10-01 DNS resolution method, authoritative DNS server and DNS resolution system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910838225.7A CN110557464A (zh) 2019-09-05 2019-09-05 Dns解析方法、权威dns服务器和dns解析系统
CN201910838225.7 2019-09-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/061,510 Continuation US11245661B2 (en) 2019-09-05 2020-10-01 DNS resolution method, authoritative DNS server and DNS resolution system

Publications (1)

Publication Number Publication Date
WO2021042673A1 true WO2021042673A1 (zh) 2021-03-11

Family

ID=68739257

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/074967 WO2021042673A1 (zh) 2019-09-05 2020-02-12 Dns解析方法、权威dns服务器和dns解析系统

Country Status (4)

Country Link
US (1) US11245661B2 (zh)
EP (1) EP3809676A4 (zh)
CN (1) CN110557464A (zh)
WO (1) WO2021042673A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110557464A (zh) * 2019-09-05 2019-12-10 网宿科技股份有限公司 Dns解析方法、权威dns服务器和dns解析系统
CN111200667B (zh) * 2019-12-18 2021-08-10 网宿科技股份有限公司 一种域名解析方法、权威域名服务器和本地域名服务器
CN113395369B (zh) * 2021-06-10 2022-12-13 北京天融信网络安全技术有限公司 一种缓存管理方法、装置、电子设备及存储介质
CN114221934B (zh) * 2021-12-13 2024-05-07 牙木科技股份有限公司 域名解析缓存方法、dns服务器及计算机可读存储介质
CN115297086A (zh) * 2022-08-03 2022-11-04 明阳产业技术研究院(沈阳)有限公司 一种域名地址解析方法、装置、设备和介质
CN116489128B (zh) * 2023-06-02 2024-06-07 北京云宽志业网络技术有限公司 域名解析方法和电子设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102077189A (zh) * 2008-06-30 2011-05-25 亚马逊技术有限公司 使用网络计算组件的请求路由
CN201985882U (zh) * 2011-01-24 2011-09-21 鞠洪尧 一种服务器群成员自动管控单元
US8832283B1 (en) * 2010-09-16 2014-09-09 Google Inc. Content provided DNS resolution validation and use
CN108900648A (zh) * 2018-06-13 2018-11-27 网宿科技股份有限公司 一种控制多cname流量比例的方法和装置
CN109995887A (zh) * 2018-01-02 2019-07-09 中国移动通信有限公司研究院 一种dns解析方法、装置及计算机可读存储介质
CN110557464A (zh) * 2019-09-05 2019-12-10 网宿科技股份有限公司 Dns解析方法、权威dns服务器和dns解析系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090292824A1 (en) * 2005-01-21 2009-11-26 Internap Network Services Corporation System And Method For Application Acceleration On A Distributed Computer Network
US8347100B1 (en) * 2010-07-14 2013-01-01 F5 Networks, Inc. Methods for DNSSEC proxying and deployment amelioration and systems thereof
US10284677B2 (en) * 2014-01-31 2019-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for obtaining content from a media server
FR3061388A1 (fr) * 2016-12-23 2018-06-29 Orange Procedes de validation de livraison de contenu et de verification d'une delegation de livraison d'un contenu, dispositifs et produits programme d'ordinateur correspondants.
US11070513B2 (en) * 2017-06-26 2021-07-20 Zedly, Inc. DNS-based method of transmitting data
US10708220B2 (en) * 2017-12-11 2020-07-07 GM Global Technology Operations LLC System and method for directing a tethered device to an in-vehicle stored landing page based on an available credit or data balance

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102077189A (zh) * 2008-06-30 2011-05-25 亚马逊技术有限公司 使用网络计算组件的请求路由
US8832283B1 (en) * 2010-09-16 2014-09-09 Google Inc. Content provided DNS resolution validation and use
CN201985882U (zh) * 2011-01-24 2011-09-21 鞠洪尧 一种服务器群成员自动管控单元
CN109995887A (zh) * 2018-01-02 2019-07-09 中国移动通信有限公司研究院 一种dns解析方法、装置及计算机可读存储介质
CN108900648A (zh) * 2018-06-13 2018-11-27 网宿科技股份有限公司 一种控制多cname流量比例的方法和装置
CN110557464A (zh) * 2019-09-05 2019-12-10 网宿科技股份有限公司 Dns解析方法、权威dns服务器和dns解析系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3809676A4 *

Also Published As

Publication number Publication date
US20210075762A1 (en) 2021-03-11
CN110557464A (zh) 2019-12-10
EP3809676A1 (en) 2021-04-21
EP3809676A4 (en) 2021-06-16
US11245661B2 (en) 2022-02-08

Similar Documents

Publication Publication Date Title
WO2021042673A1 (zh) Dns解析方法、权威dns服务器和dns解析系统
US11290418B2 (en) Hybrid content request routing system
US11811657B2 (en) Updating routing information based on client location
US11194719B2 (en) Cache optimization
US10904205B2 (en) Content delivery network optimization system
US8572214B2 (en) System and method for discovering information objects and information object repositories in computer networks
US9549038B1 (en) Cacheable resource location selection
US7725596B2 (en) System and method for resolving network layer anycast addresses to network layer unicast addresses
US7565450B2 (en) System and method for using a mapping between client addresses and addresses of caches to support content delivery
US7343422B2 (en) System and method for using uniform resource locators to map application layer content names to network layer anycast addresses
US7908337B2 (en) System and method for using network layer uniform resource locator routing to locate the closest server carrying specific content
US7925782B2 (en) Request routing using network computing components
US9264358B2 (en) Alias resource record sets
US20080208961A1 (en) Parallel retrieval system
US20130332569A1 (en) Service provider registration by a content broker
CN113452808B (zh) 域名解析方法、装置、设备及存储介质
WO2013104172A1 (zh) 实现负载均衡的方法、dns服务器和客户端
US20230128125A1 (en) Systems and methods for processing requests for content of a content distribution network
SG188372A1 (en) Request routing in a networked environment
US10075553B1 (en) Systems and methods for automatically rewriting network page code
US20230022183A1 (en) Systems and methods for processing requests for content of a content distribution network
CN116074282A (zh) 数据报文的响应方法、装置、电子设备及存储介质
WO2001084800A2 (en) System and method for using network layer uniform resource locator routing to locate the closest server carrying specific content
WO2001084803A2 (en) System and method for resolving network layer anycast addresses to network layer unicast addresses

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2020776061

Country of ref document: EP

Effective date: 20201002

NENP Non-entry into the national phase

Ref country code: DE