WO2018081963A1

WO2018081963A1 - Method and device for dns resolution and network system

Info

Publication number: WO2018081963A1
Application number: PCT/CN2016/104389
Authority: WO
Inventors: 代明
Original assignee: 达闼科技（北京）有限公司
Priority date: 2016-11-02
Filing date: 2016-11-02
Publication date: 2018-05-11
Also published as: CN107223329A; CN107223329B

Abstract

Embodiments of the present invention relate to the field of communications and can simplify a domain name system (DNS) resolution process of the prior art. Disclosed are a method and device for DNS resolution and a network system. The method comprises: a local domain name server receives a DNS resolution request transmitted by a client, where the DNS resolution request comprises a first domain name and context information; the local domain name server, when the first domain name cannot be found in a customized configuration and the context information comprises a second domain name, searches in the customized configuration for an IP address corresponding to the second domain name in the context information; and the local domain name server feeds back to the client a DNS resolution response comprising the IP address found. The embodiments of the present invention are used for DNS resolution.

Description

DNS analysis method, device and network system

Technical field

Embodiments of the present invention relate to the field of communications, and in particular, to a DNS (English name: Domain Name System, Chinese: Domain Name System) parsing method, apparatus, and network system.

Background technique

In the existing network system architecture, when the client requests data content from the network server, the local domain name server (English: Local Domain Name Server) needs to first resolve the domain name requested by the client to IP (English full name: Internet Protocol, Chinese: Network Interconnection Protocol) address to request data content based on the IP address. Specifically, the local domain name server receives the domain name resolution request (DNS request) sent by the client in the local network, recursively queries the upper-level domain name server, and resolves the domain name into an IP address and carries the feedback to the client in the DNS response; sometimes the local domain name is required. On the server, some domain names are resolved to other IP addresses through a custom configuration, such as the IP address of the network proxy server (such as 2.2.2.2 in Figure 1), after which the client requests the local proxy server through the HTTP request according to the IP address. Data content, the local proxy server requests data content from the HTTP web server through an HTTP request and feeds back to the client via an HTTP response. Currently, most local domain name servers support domain name servers for such custom configuration, but current web pages generally contain many elements. In order to better support concurrent acquisition of resources, these elements usually come from multiple different domain names. The domain name of the homepage is not under the same top-level domain name; with the revision of the webpage, elements from the new domain name may be added. When performing domain name resolution based on a custom configuration, each domain name resolution request resolves an IP address. If you need to resolve these domain names to the same custom IP address, you first need to find these domain names and add them to the local domain name. In the custom configuration of the server, the domain names are all corresponding to the same IP address, and then the domain name resolution request corresponding to the domain name is obtained by the domain name resolution request corresponding to the domain name, and the corresponding IP address in the custom configuration is obtained. It is cumbersome and difficult to maintain.

Summary of the invention

Embodiments of the present invention provide a DNS resolution method, apparatus, and network system for simplifying the DNS resolution process in the prior art.

The first aspect provides a DNS resolution method, including:

The local domain name server receives the DNS domain name system resolution request sent by the client, where the DNS resolution request includes the first domain name and the context information;

When the local domain name server does not query the first domain name in the custom configuration, and the second domain name is included in the context information, querying, in the customized configuration, the second domain name in the context information IP address;

The local domain name server feeds back a DNS resolution response containing the queried IP address to the client.

The second aspect provides a DNS resolution method, including:

The client sends a DNS resolution request to the local domain name server, where the DNS resolution request includes a first domain name and the context information, the context information is used to deliver a second domain name, and the second domain name is used by the local domain name server When the first domain name is not found in the custom configuration, and the second domain name is included in the context information, the IP address corresponding to the second domain name in the context information is queried in the customized configuration.

The client receives a DNS resolution response including the queried IP address fed back by the local domain name server according to the DNS resolution request.

In a third aspect, a local domain name server is provided, including:

a receiving unit, configured to receive a DNS resolution request sent by the client, where the DNS resolution request includes the first domain name and the context information;

a processing unit, configured to query, in the customized configuration, the context information in the custom configuration, when the local domain name server does not query the first domain name in a custom configuration, and the context information includes a second domain name The IP address corresponding to the second domain name;

And a sending unit, configured to feed back a DNS resolution response that includes the IP address queried by the processing unit to the client.

The fourth aspect provides a client, including:

a sending unit, configured to send a DNS resolution request to the local domain name server, where the DNS resolution request includes a first domain name and the context information, where the context information is used to deliver a second domain name, where the second domain name is used by the When the local domain name server does not query the first domain name in the custom configuration, and the second domain name is included in the context information, query the second domain name in the context information in the customized configuration. IP address;

a receiving unit, configured to receive a DNS resolution response that includes the queried IP address fed back by the local domain name server according to the DNS resolution request;

The sending unit is further configured to send a data content request according to the IP address received by the receiving unit.

In a fifth aspect, a local domain name server is provided, comprising: a memory, a communication interface, and a processor, the memory is configured to store computer execution code, and the processor is configured to execute the computer to perform code control to perform the foregoing first aspect The DNS resolution method is used for data transmission between the local domain name server and an external device.

A sixth aspect provides a client, including: a storage interface, a communication interface, and a processing interface, where the storage interface is configured to store computer execution code, and the processing interface is configured to execute the computer to perform code control to execute the foregoing second Aspects provide a DNS resolution method for data transmission between the client and an external device.

A seventh aspect provides a network system, including: a network server, a local proxy server, any of the above local domain name servers, and any of the foregoing clients.

In the above solution, after the client sends a DNS resolution request to the local domain name server, When the domain name server fails to query the first domain name in the custom configuration and the second domain name is included in the context information, the IP address corresponding to the second domain name in the context information is queried in the custom configuration; thus, the client is based on the query. The IP address sends a data content request to request the data content, wherein the context information is used to deliver the second domain name, so the DNS resolution request may carry multiple domain names. When only one domain name resolution is involved, the context information may be configured to be empty. When the domain name is parsed, the domain name may be carried in the DNS resolution request, and the IP address is queried in the custom configuration by referring to the first domain name and the context information when parsing the DNS resolution request, and the second domain name is included in the context information. The first domain name can be resolved to the IP address corresponding to the second domain name without manually adding the domain name in the custom configuration of the local domain name server, which simplifies the DNS resolution process in the prior art.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only some of the present invention. For the embodiments, those skilled in the art can obtain other drawings according to the drawings without any creative work.

1 is an architectural diagram of a network system provided by the prior art;

2 is a structural diagram of a network system according to an embodiment of the present invention;

FIG. 3 is a flowchart of a DNS resolution method according to an embodiment of the present invention;

FIG. 4 is a signaling interaction diagram of a DNS resolution method according to another embodiment of the present invention; FIG.

FIG. 5 is a flowchart of a DNS resolution method according to still another embodiment of the present invention;

FIG. 6 is a flowchart of a DNS resolution method according to still another embodiment of the present invention;

FIG. 7 is a structural diagram of a local domain name server according to an embodiment of the present invention;

FIG. 8 is a structural diagram of a client according to an embodiment of the present invention;

FIG. 9 is a structural diagram of a client according to another embodiment of the present invention; FIG.

FIG. 10A is a structural diagram of a local domain name server according to another embodiment of the present invention; FIG.

FIG. 10B is a structural diagram of a local domain name server according to still another embodiment of the present invention; FIG.

FIG. 11 is a structural diagram of a client according to another embodiment of the present invention; FIG.

FIG. 11B is a structural diagram of a client according to still another embodiment of the present invention.

detailed description

The system architecture and the service scenario described in the embodiments of the present invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and do not constitute a limitation of the technical solutions provided by the embodiments of the present invention. The technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.

It should be noted that, in the embodiments of the present invention, the words "exemplary" or "such as" are used to mean an example, an illustration, or a description. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the invention should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplary" or "such as" is intended to present the concepts in a particular manner.

In order to facilitate the clear description of the technical solutions of the embodiments of the present invention, in the embodiments of the present invention, the words "first", "second" and the like are used to distinguish the same or similar items whose functions and functions are substantially the same, in the field. The skilled person will understand that the words "first", "second" and the like do not limit the number and order of execution. In the description of the present invention, "a plurality" means two or more unless otherwise stated.

It should be noted that, in the embodiment of the present invention, "(English: of)", "corresponding (relevant)" and "corresponding" may sometimes be mixed. It should be noted that When the difference is not emphasized, the meaning to be expressed is the same.

Technical terms to which the embodiments of the present invention relate include the following:

HTTP, Chinese: Hypertext Transfer Protocol, English: HyperText Transfer Protocol.

Context, also known as written language environment, English: context.

Referer field, Chinese: reference page field, HTTP Referer is a standard HTTP header (header) in HTTP. When the browser sends a request to the web server, it usually brings a Referer to tell the server which page I linked from. The server can thereby obtain some information for processing. In the embodiment of the present invention, the context information used by the domain name is sent to the local domain name server through the Referer, and the HTTP DNS resolution request is extended to notify the local domain name server of a domain name request. Source domain name.

The client provided by the embodiment of the present invention may be a personal computer (English name: personal computer, abbreviation: PC), a netbook, a personal digital assistant (PDA: PDA), or the client may be A software client or a software system or a software application PC or the like can be installed, and the specific hardware implementation environment can be a general computer form, an ASIC method, an FPGA, or some The extended platform for programming is, for example, the Xtensa platform of Tensilica, etc. The server provided by the embodiment of the present invention includes a local domain name server, a local proxy server, and a network server, and an embodiment of the present invention provides a server for providing a computing service in response to a service request. It includes a processor, hard disk, memory, system bus, etc., similar to a general-purpose computer architecture.

The basic principle of the present invention is that when a client requests data content from a network server, it first needs to send a DNS resolution request to the local domain name server, so that the local domain name server resolves the domain name requested by the client into an IP address, and the DNS resolution in the implementation of the present invention. The request carries the first domain name and the context information, where the context information is used to deliver the second domain name, so the DNS resolution request may carry multiple domain names. When only one domain name resolution is involved, the context information may be configured to be empty, when needed. When the domain name is parsed, the domain name may be carried in the DNS resolution request, and the IP address is obtained by referring to the first domain name and the second domain name passed in the context information when parsing the DNS resolution request, for example, the second domain name can be parsed. When the IP address is configured, the first domain name is also resolved to the IP address corresponding to the second domain name. When the first domain name is not customized, the first domain name is stored in the local DNS server. Context information to resolve multiple domain names to the same IP address without Adding a domain name to a custom configuration of a local domain name server simplifies the DNS resolution process in the prior art.

Referring to FIG. 2, the network system architecture provided by the embodiment of the present invention includes: a local domain name server 21, a client terminal 22, and a network server 23, and may also include a local proxy server 24 for a certain scenario. The difference is that when the IP address resolved by the local domain name server is the address of the network server, the client can directly access the network server through the IP address and request data content from the IP address. When the IP address resolved by the local domain name server is the address of the local proxy server, The client can request data content from the local proxy server through the IP address, and the local proxy server agent requests the data content from the web server and feeds back to the client. Since the embodiment of the present invention does not involve the improvement of the client requesting the data content according to the IP address, it can be considered that the above-mentioned In one method, the data content is acquired. In the following scheme, only the IP address is used as the address of the local proxy server as an example.

Based on the foregoing network system, as shown in FIG. 3, an embodiment of the present invention provides a DNS resolution method, including the following steps:

101. The client sends a DNS resolution request to the local domain name server.

The DNS resolution request includes a first domain name and context information, and the context information is used to deliver the second domain name. An example of this is that the DNS resolution request is an HTTP DNS resolution request, and the context information is a referer reference page field in HTTP.

Exemplary:

The form of providing a DNS resolution request is as follows:

GET/dns? Domain=www.example.com HTTP/1.1* Obtain DNS domain name www.example.com* under HTTP protocol version 1.1

Host: 192.168.1.1* The host name of the local domain name server is 192.168.1.1*

Referer: www.referer.com* Contextual information carries the domain name www.referer.com*

Provide a form of DNS resolution response as follows:

HTTP/1.1 200 OK* protocol version information*

Server: 192.168.1.1* The host address of the local domain name server is 192.168.1.1*

Date:Fri,26 Aug 2016 09:25:50 GMT*Time Information*

Content-Type: text/json* context information type*

Content-Length: 25* Context Length*

{

"www.example.com":"2.2.2.2"

}* The IP address of the proxy server corresponding to the domain name www.example.com 2.2.2.2*

102. The local domain name server receives the DNS domain name system parsing request sent by the client.

103. The local domain name server queries the IP address corresponding to the second domain name in the context information in the custom configuration when the first domain name is not found in the custom configuration and the second domain name is included in the context information.

104. The local domain name server feeds back the DNS resolution response including the queried IP address to the client.

105. The client receives a DNS resolution response that includes the queried IP address fed back by the local domain name server according to the DNS resolution request.

Finally, the client can send a data content request based on the queried IP address.

In the above solution, after the client sends a DNS resolution request to the local domain name server, the local domain name server does not query the first domain name in the custom configuration and the second domain name is included in the context information, and the context information is queried in the custom configuration. The IP address corresponding to the second domain name; in this way, the client sends a data content request according to the queried IP address to request the data content, wherein the context information is used to deliver the second domain name, so the DNS resolution request may carry multiple domain names, when When only one domain name is parsed, the context information can be configured to be empty. When multiple domain names need to be parsed, two domain names can be carried in the DNS resolution request, and the first domain name and the context are simultaneously referred to when parsing the DNS resolution request. The information is queried in the custom configuration. When the context information includes the second domain name, the first domain name can be resolved to the IP address corresponding to the second domain name without manually adding the domain name in the custom configuration of the local domain name server. There is a DNS resolution process in the technology.

Specifically, referring to the signaling interaction diagram shown in FIG. 4, when the embodiment of the present invention is applied to the HTTP protocol, the context information uses a referer field in HTTP to take a request for a webpage content data including multiple domain names as an example. For example, www.example.com is the primary domain name of the webpage, the primary domain name is used for the request of the parent content, and www.static.com is the domain name of a sub-content of the webpage, where www.example.com is included locally. In the custom configuration of the domain name server, www.static.com is not included in the custom configuration of the local domain name server. The DNS resolution method provided by the embodiment of the present invention is as follows for a domain name resolution process, where the domain name may be the primary domain name www.example.com included in the webpage (where only the keywords of each step are shown in FIG. 4 and The complete steps are not shown, the specific steps are described in detail in the examples):

201. The client sends a DNS resolution request to the local domain name server locally.

The DNS resolution request includes a domain name www.example.com and context information, where the context information is empty.

202. The local domain name server receives the DNS resolution request.

203. The local domain name server queries the IP address 2.2.2.2 corresponding to www.example.com in the custom configuration.

The custom configuration can be a system configuration file, such as a configuration list containing mappings between domain names and IP addresses.

204. The local domain name server feeds back the DNS resolution response including the IP address 2.2.2.2 to the client.

205. The client sends an HTTP data content request to a local proxy server whose IP address is 2.2.2.2.

206. The local proxy server sends an HTTP request to the HTTP data content source web server.

207. The source network server sends the requested data content to the local proxy server.

208. The local proxy server sends the data content to the client.

The client then performs the next action based on the received data content, such as a request for a sub-content in the data content.

In the following steps, the parsing process of the associated domain name www.static.com for www.example.com is mainly provided. When the client includes the sub-content in the data content of the last request, the sub-content and the parent content are respectively located at www. Under the two different domain names of .static.com and www.example.com, the resolution process for multiple domain names is as follows:

301. A client receives data content, where the data content includes sub-content and parent content.

302. The client sets the domain name www.example.com of the parent content in the context information in the DNS resolution request, and sets the domain name www.static.com of the child content to the first domain name.

303. The client sends a DNS resolution request to the local domain name server.

The DNS resolution request contains the domain name www.static.com, and the context information includes www.example.com.

304. The local domain name server receives the DNS resolution request sent by the client.

305. The local domain name server queries www.static.com in a custom configuration.

306. If the local domain name server cannot query www.static.com in the custom configuration, the local domain name server queries the context information in the custom configuration. The IP address corresponding to www.example.com is 2.2.2.2.

307. The local domain name server saves www.static.com to a custom configuration and maps www.static.com to the IP address 2.2.2.2 corresponding to www.example.com.

After the client obtains the IP address 2.2.2.2 after step 307, referring to the above steps 205-208, the client can obtain the content data according to the IP address 2.2.2.2. In addition, after step 307, the client and the local domain name server may continue to repeat the above steps 301-307 to obtain the data content by sending the DNS resolution request to the local domain name server by the client, and the domain name in the context information of the subsequent DNS resolution request is www. Static.com still resolves to IP address 2.2.2.2. In addition, by step 306, the mapping of www.static.com to the IP address 2.2.2.2 corresponding to www.example.com is automatically updated, and the first domain name is stored in the local domain name server as a subsequent DNS request. The context information ensures that the first domain name or the context information in the subsequent DNS resolution request is still resolved to the IP address 2.2.2.2 when the domain name is www.static.com.

The above solution is for the case where the first domain name or the second domain name in the DNS resolution request is included in the custom configuration. When the custom configuration does not include the above two domain names or any of them, the following steps are taken as shown in FIG. 6:

401. The client sends a DNS resolution request to the local domain name server.

The DNS resolution request includes the domain name www.test.com, and the context information, and the context information is empty.

402. The local domain name server receives the DNS resolution request sent by the client.

403. The local domain name server queries www.test.com in a custom configuration.

404. If the local domain name server does not query www.test.com in the custom configuration, and the local domain name server determines that the context information is empty, the upper domain name server sends a DNS domain name request to recursively resolve the DNS domain name request.

405. The local domain name server receives the IP address fed back by the upper-level domain name server, and carries the IP address in the DNS resolution response and feeds back to the client.

After the client obtains the IP address after step 405, the client can obtain the content data according to the IP address by referring to the above steps 205-208. You can also map www.test.com to this IP address to update your custom configuration.

The solution provided by the embodiment of the present invention is mainly introduced from the perspective of interaction between the network elements. It can be understood that each network element, such as a server, a client, etc., in order to implement the above functions, includes hardware structures and/or software modules corresponding to each function. Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The embodiment of the present invention may divide a function module of a local domain name server, a client, and the like according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. in. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.

FIG. 7 is a schematic diagram showing a possible structure of a local domain name server involved in the foregoing embodiment, where the local domain name server includes: a receiving unit 71, a processing unit 72, and a sending. Unit 73. The receiving unit 71 is configured to support the local domain name server to perform the process 102 in FIG. 3, the process 202 in FIG. 4, the process 304 in FIG. 5, and the process 402 in FIG. 6. The processing unit 72 is configured to support the local domain name server to execute FIG. The process 103 in the process, the process 203 in FIG. 4, the

process

305, 306, 307 in FIG. 5, the process 403 in FIG. 6; the sending unit 73 is configured to support the local domain name server to execute the process 104 in FIG. 3, in FIG. Process 204, process 404 in FIG. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

FIG. 8 is a schematic diagram showing a possible structure of the client involved in the foregoing embodiment, where the client includes: a sending unit 81 and a receiving unit 82. The sending unit 81 is configured to support the client to perform the processes 101 and 106 in FIG. 3, the processes 201 and 205 in FIG. 4, the process 303 in FIG. 5, and the process 401 in FIG. 6. The receiving unit 82 is configured to support the client to execute. Process 105 in FIG. 3, process 208 in FIG. 4, process 301 in FIG. 5, process 405 in FIG. Or as shown in Figure 9, the client When the configuration unit 83 is further included, the configuration unit 83 is configured to support the client to perform step 302 in FIG. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

In the case of employing an integrated unit, FIG. 10A shows a possible structural diagram of the local domain name server involved in the above embodiment. The local domain name server includes a communication module 101 and a processing module 102. The processing module 102 is configured to control and manage the actions of the local domain name server. For example, the processing module 102 is configured to support the local domain name server to perform the process 103 in FIG. 3, the process 203 in FIG. 4, and the

processes

305, 306 in FIG. 307, process 403 in FIG. 6, and/or other processes for the techniques described herein. The communication module 101 is for supporting data transmission between a local domain name server and other external devices, such as communication with the functional modules or network entities shown in Figures 2, 10A. The local domain name server may further include a storage module 103 for storing program codes and data of the local domain name server.

The processing module 102 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication module 101 can be a transceiver, a transceiver circuit, a communication interface, or the like. The storage module 103 can be a memory.

When the processing module 102 is a processor, the communication module 101 is a communication interface, and the storage module 103 is a memory, the local domain name server involved in the embodiment of the present invention may be the local domain name server shown in FIG. 10B.

Referring to FIG. 10B, the local domain name server includes a processor 1011, a communication interface 1012, a memory 1013, and a bus 1014. The communication interface 1012, the processor 1011, and the memory 1013 are connected to each other through a bus 1014. The bus 1014 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only Figure 10B It is indicated by a thick line, but does not mean that there is only one bus or one type of bus.

In the case of employing an integrated unit, FIG. 11A shows a possible structural diagram of the client involved in the above embodiment. The client includes a communication module 111 and a processing module 112. The processing module 111 is configured to perform control management on the actions of the client. For example, the processing module 11 is configured to support the control communication module 111 to execute the processes 101 and 106 in FIG. 3, the processes 201 and 205 in FIG. 4, and the process 303 in FIG. Process 401 in FIG. 6; process 105 in FIG. 3, process 208 in FIG. 4, process 301 in FIG. 5, and process 405 in FIG. Or the processing module 112 is further configured to support the client to perform step 302 in FIG. And/or other processes for the techniques described herein. The communication module 101 is for supporting data transmission between a local domain name server and other external devices, such as communication with the functional modules or network entities shown in Figures 2, 11A. The client may also include a storage module 113 for storing program code and data of the local domain name server.

The processing module 112 may be a processor or a controller, for example, may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application specific integrated circuit (Application-Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication module 111 can be a transceiver, a transceiver circuit, a communication interface, or the like. The storage module 113 can be a memory.

When the processing module 112 is a processor, the communication module 111 is a communication interface, and the storage module 113 is a memory, the client involved in the embodiment of the present invention may be the client shown in FIG. 11B.

Referring to FIG. 11B, the client includes a processor 1111, a communication interface 1112, a memory 1113, and a bus 1114. The communication interface 1112, the processor 1111, and the memory 1113 are mutually connected by a bus 1114; the bus 1114 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 11B, but it does not mean that there is only one bus or one type of bus.

The steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions. The software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a core network interface device. Of course, the processor and the storage medium may also exist as discrete components in the core network interface device.

Those skilled in the art will appreciate that in one or more examples described above, the functions described herein can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

The specific embodiments of the present invention have been described in detail with reference to the preferred embodiments of the present invention. The scope of the protection, any modifications, equivalent substitutions, improvements, etc., which are made on the basis of the technical solutions of the present invention, are included in the scope of the present invention.

Claims

A DNS parsing method, comprising:

The local domain name server receives the DNS domain name system resolution request sent by the client, where the DNS resolution request includes the first domain name and context information;

When the local domain name server does not query the first domain name in the custom configuration, and the second domain name is included in the context information, querying, in the customized configuration, the second domain name in the context information IP address;

The local domain name server feeds back a DNS resolution response containing the queried IP address to the client.
The method according to claim 1, further comprising: saving the first domain name to the custom configuration, and mapping the first domain name to an IP address corresponding to the second domain name.
The method of claim 1 further comprising:

If the local domain name server does not query the first domain name in the custom configuration, and the local domain name server determines that the context information is empty, the upper domain name server sends the DNS domain name request to recursively analyze the Said DNS domain name request;

The local domain name server receives the IP address fed back by the upper-level domain name server.
The method according to claim 1, further comprising: the context information is empty, and the local domain name server queries the IP address corresponding to the first domain name in a custom configuration.
The method according to any one of claims 1 to 4, wherein the DNS resolution request is an HTTP DNS resolution request, and the context information is a referer reference page field in HTTP.
Method according to any of claims 1-4, characterized in that said IP address The address of the local proxy server.
A DNS parsing method, comprising:

The client sends a DNS resolution request to the local domain name server, where the DNS resolution request includes a first domain name and the context information, the context information is used to deliver a second domain name, and the second domain name is used by the local domain name server When the first domain name is not found in the custom configuration, and the second domain name is included in the context information, the IP address corresponding to the second domain name in the context information is queried in the customized configuration.

The client receives a DNS resolution response including the queried IP address fed back by the local domain name server according to the DNS resolution request.
The method according to claim 7, wherein before the client sends a DNS resolution request to the local domain name server, the method includes:

The client receives data content, the data content including sub-content and parent content;

The client sets the domain name of the parent content as the second domain name in the context information in the DNS resolution request, and sets the domain name of the child content to the first domain name.
A local domain name server, comprising:

a receiving unit, configured to receive a DNS resolution request sent by the client, where the DNS resolution request includes the first domain name and the context information;

a processing unit, configured to query, in the customized configuration, the context information in the custom configuration, when the local domain name server does not query the first domain name in a custom configuration, and the context information includes a second domain name The IP address corresponding to the second domain name;

And a sending unit, configured to feed back a DNS resolution response that includes the IP address queried by the processing unit to the client.
The local domain name server according to claim 9, wherein the processing unit is further configured to save the first domain name to the custom configuration, and map the first domain name to the second domain name. The corresponding IP address.
The local domain name server according to claim 9, wherein the processor is specifically configured to query the first domain name in a custom configuration; if the first domain name is not queried in a custom configuration, and When the context information is determined to be empty, the sending unit sends the DNS domain name request to the upper-level domain name server to recursively resolve the DNS domain name request; and the receiving unit receives the IP address fed back by the upper-level domain name server.
The local domain name server according to claim 9, wherein the context information is empty, and the processing unit is configured to query an IP address corresponding to the first domain name in a custom configuration.
A client, comprising:

a sending unit, configured to send a DNS resolution request to the local domain name server, where the DNS resolution request includes a first domain name and the context information, where the context information is used to deliver a second domain name, where the second domain name is used by the When the local domain name server does not query the first domain name in the custom configuration, and the second domain name is included in the context information, query the second domain name in the context information in the customized configuration. IP address;

The receiving unit is configured to receive a DNS resolution response that includes the queried IP address that is fed back by the local domain name server according to the DNS resolution request.
A client according to claim 13 wherein:

The receiving unit is further configured to receive data content, where the data content includes sub-content and parent content;

The client further includes a configuration unit, configured to set, in the DNS resolution request, a domain name of the parent content as the second domain name in the context information, and set a domain name of the child content to the first domain domain name.
A local domain name server, comprising: a memory, a communication interface, and a processor, wherein the memory is used to store computer execution code, and the processor is configured to execute the computer to execute code control to perform any of claims 1-6 The DNS resolution method, wherein the communication interface is used for data transmission between the local domain name server and an external device.
A client, comprising: a memory for communicating computer execution code, and a processor for executing the computer to perform code control to perform any one of claims 7 or 9. The DNS resolution method is used for data transmission between the client and an external device.
A network system, comprising: the local domain name server according to any one of claims 9-12, and the client according to claim 13 or 14; or the network system comprises The local domain name server of claim 15 and the client of claim 16.