CN110149388B

CN110149388B - Method, device and equipment for connecting HTTPDNS (hypertext transport protocol version transport protocol DNS) server

Info

Publication number: CN110149388B
Application number: CN201910410694.9A
Authority: CN
Inventors: 刘威波; 潘贵国; 曹志华; 王韬
Original assignee: Beijing ByteDance Network Technology Co Ltd
Current assignee: Beijing ByteDance Network Technology Co Ltd
Priority date: 2019-05-16
Filing date: 2019-05-16
Publication date: 2023-02-24
Anticipated expiration: 2039-05-16
Also published as: CN110149388A

Abstract

The present disclosure provides a method, a device and a device for connecting an HTTPDNS server, wherein the method comprises the following steps: the HTTPDNS server receives a connection request sent by a client based on a QUIC protocol; and the HTTPDNS server responds to the connection request and establishes connection with the client. The HTTPDNS server responds to the connection request sent by the client based on the QUIC protocol and establishes connection with the client, so that the connection of the HTTPDNS server based on the QUIC protocol is realized, the connection delay of the HTTPDNS server can be effectively reduced, and the delay of the HTTPDNS service is reduced.

Description

Method, device and equipment for connecting HTTPDNS (hypertext transport protocol version transport protocol DNS) server

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a method, an apparatus, and a device for connecting an http dns server.

Background

With the rapid development of internet technology, web services become an indispensable service in people's lives, and currently, internet enterprises generally use domain names to provide services for users. However, the existing service providing methods are more or less unable to avoid the problems of various domain names being cached, slow cross-network access of users, and the like in the internet environment. This is likely to cause significant losses to the internet enterprise.

In order to solve the problems in the prior art, HTTP dns (domain name system based on HTTP protocol) is developed, and HTTP dns is a traffic scheduling solution customized for a mobile client based on HTTP protocol and domain name resolution, and is used to solve the problems of abnormal resolution of local domain name system (local domain name system), inaccurate traffic scheduling, and the like in the prior art. Compared with the traditional DNS, the HTTPDNS has the advantages of hijacking prevention, accurate scheduling, 0ms analysis delay, quick effect and the like.

In the prior art, the http dns service is based on TCP and TLS protocols, a TCP/TLS handshake needs to be established, and an initial handshake needs 3 or 4 RTTs (Round-Trip Time), which results in a high delay of the http dns service.

Disclosure of Invention

The disclosure provides a method, a device and equipment for connecting an HTTPDNS server, which are used for solving the defects of high delay and the like of the HTTPDNS service in the prior art.

A first aspect of the present disclosure provides a method for connecting an http dns server, including:

the HTTPDNS server receives a connection request sent by a client based on a QUIC protocol;

and the HTTPDNS server responds to the connection request and establishes connection with the client.

A second aspect of the present disclosure provides a connection device for an http dns server, comprising:

the receiving module is used for the HTTPDNS server to receive a connection request sent by a client based on a QUIC protocol;

and the response module is used for responding the connection request by the HTTPDNS server and establishing connection with the client.

A third aspect of the present disclosure provides an electronic device, comprising: at least one processor and memory;

the memory stores a computer program; the at least one processor executes the computer program stored by the memory to implement the method provided by the first aspect.

A fourth aspect of the disclosure provides a computer-readable storage medium having stored thereon a computer program which, when executed, implements the method provided by the first aspect.

According to the method, the device and the equipment for connecting the HTTPDNS server, the HTTPDNS server responds to the connection request sent by the client based on the QUIC protocol, and establishes connection with the client, so that the connection of the HTTPDNS server based on the QUIC protocol is realized, and the connection delay of the HTTPDNS server can be effectively reduced.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise.

Fig. 1 is a schematic flowchart of a connection method of an http dns server according to an embodiment of the present disclosure;

fig. 2 is a schematic flowchart of a connection method of an http dns server according to another embodiment of the present disclosure;

FIG. 3 is an interaction diagram of QUIC handshake provided by an embodiment of the present disclosure;

fig. 4 is an interaction diagram of HTTP get data according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of a connection device of an http dns server according to an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure;

fig. 7 is an exemplary structural schematic diagram of an electronic device according to an embodiment of the present disclosure.

Specific embodiments of the present disclosure have been shown by way of example in the drawings and will be described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.

Detailed Description

To make the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are some, but not all embodiments of the present disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

The nouns to which this disclosure relates will be explained first:

DNS: the Domain Name System, a service of the internet. It acts as a distributed database that maps domain names and IP addresses to each other, enabling users to more conveniently access the internet. The DNS uses TCP and UDP ports 53.

HTTPDNS: the domain name system based on the HTTP carries out domain name resolution by using the HTTP, and a domain name resolution request is directly sent to an HTTPDNS server, so that a local domain name system LocalDNS of an operator is bypassed.

QUIC: quick UDP Internet Connection, UDP-based low latency Internet transport layer protocol. QUIC addresses well the various requirements faced by the transport and application layers, including handling more connections, security, and low latency. QUIC incorporates features of protocols including TCP, TLS, HTTP/2, etc., but is based on UDP transport. One of the main objectives of the QUIC is to reduce connection latency, which only requires 1RTT of latency to establish a reliable and secure connection when the client first connects to the server, which is faster than 1-3 RTTs for TCP + TLS. The client may then locally cache the encrypted authentication information, and may implement a 0-RTT connection establishment delay when establishing a connection with the server again. QUIC simultaneously multiplexes the Multiplexing function of HTTP/2 protocol (Multiplexing), but avoids the Head-of-Line Blocking (Head-of-Line Blocking) problem of HTTP/2 since QUIC is based on UDP. Because the QUIC is based on UDP and runs in a user domain instead of a system kernel, the QUIC protocol can be updated and deployed rapidly, and the difficulty of TCP protocol deployment and updating is well solved.

The method for connecting the HTTPDNS server is suitable for establishing connection between the client and the HTTPDNS server, and the HTTPDNS provides service scenes for client users.

Furthermore, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or to implicitly indicate a number of the indicated technical features. In the description of the following examples, "plurality" means two or more unless specifically limited otherwise.

The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.

An embodiment of the disclosure provides a method for connecting an http dns server, which is used for establishing a connection between a client and the http dns server. The execution subject of the embodiment of the present disclosure is a connection device of the http dns server, which may be provided in the http dns server.

As shown in fig. 1, a schematic flowchart of a connection method for an http dns server provided in an embodiment of the present disclosure is shown, where the method includes:

in step 101, the http dns server receives a connection request sent by a client based on the QUIC protocol.

Specifically, when a client needs an http dns server to provide a domain name resolution service for the client, a connection needs to be established with the http dns server, the client may obtain an IP address of the http dns server, and send a connection request to the http dns server according to the IP address of the http dns server, and in order to reduce a connection delay, the client sends the connection request to the http dns server based on a QUIC protocol. The http dns server may then receive the connection request sent by the client based on the QUIC protocol.

The connection request may include messages required to establish the connection and may also include encryption information transmitted by the client and the http dns server after the connection is established. For example, the connection request may include: connection identifiers, client parameters, verification association information and other information defined in the QUIC protocol are not described in detail. The connection request may be a connection request for the first time the client establishes a connection with the http dns server and may include a preliminary client handshake message. After the client sends the connection request, it waits to receive the http dns Server return response message, for example, waits for the http dns Server to return an accept message Server Reject message.

Illustratively, the Client sends a Client Hello QUIC packet to the http dns server based on the QUIC protocol, and the Client Hello QUIC packet may include a protocol version, client parameters, and some other related information.

In step 102, the http dns server establishes a connection with the client in response to the connection request.

Specifically, after receiving a connection request sent by the client based on the QUIC protocol, the http dns Server may respond to the connection request of the client, for example, return a Server Reject QUIC packet, which may include service configuration information Server config, complete a QUIC handshake with the client, and establish a secure connection with the client.

According to the method for connecting the HTTPDNS server, the HTTPDNS server responds to the connection request sent by the client based on the QUIC protocol, and establishes connection with the client, so that the connection of the HTTPDNS server based on the QUIC protocol is realized, and the connection delay of the HTTPDNS server can be effectively reduced.

The method provided by the above embodiment is further explained in an additional embodiment of the present disclosure.

Fig. 2 is a schematic flow chart of a connection method of an http dns server according to an embodiment of the present disclosure.

As a practical manner, on the basis of the foregoing embodiment, optionally, the step 101 may specifically include:

in step 1011, the http dns server receives the Client Hello QUIC packet sent by the Client.

Correspondingly, step 102 may specifically include:

and step 1021, the HTTPDNS Server returns a Server Reject QUIC data packet according to the Client Hello QUIC data packet, completes the QUIC handshake and establishes connection with the Client.

As shown in fig. 3, an interaction diagram of QUIC handshake provided for the embodiment of the present disclosure is shown. Wherein the service end refers to an HTTP DNS server. When the client side is connected with the HTTPDNS server for the first time, one RTT is reduced by adopting handshaking based on a QUIC protocol, and the delay of the HTTPDNS service can be reduced. The data volume carried by the HTTPDNS is small, and is generally smaller than one MTU (maximum transmission unit), namely, the transmission of the HTTPDNS data can be completed by one data packet, and the RTT consumed by handshaking directly determines the delay of the HTTPDNS service.

As another practicable manner, on the basis of the foregoing embodiment, optionally after the step 102, the method may further include:

in step 103, the HTTP dns server receives the HTTP request sent by the client.

In step 104, the HTTP dns server returns an HTTP response based on the HTTP request.

Specifically, after the QUIC handshake is completed and the HTTP dns server establishes a secure connection with the client, the client needs to send an HTTP request to the HTTP dns server, and the HTTP dns server responds to the HTTP request of the client to complete HTTP dns data transmission.

As shown in fig. 4, an interaction diagram of HTTP acquiring data is provided for the embodiment of the present disclosure.

As another practicable manner, on the basis of the foregoing embodiment, optionally after step 104, the method may further include:

and 105, the HTTPDNS server receives a domain name resolution request sent by the client, wherein the domain name resolution request comprises a target domain name to be resolved.

And step 106, the HTTPDNS server determines a corresponding target IP address according to the target domain name.

And step 107, the HTTPDNS server returns the target IP address to the client so that the client accesses the corresponding server according to the target IP address.

Specifically, after the HTTPDNS server establishes a connection with the client, the HTTPDNS server may provide a domain name resolution service for the client. The client side can carry a domain name (called a target domain name) of a network to be accessed in a domain name resolution request and send the domain name resolution request to the HTTPDNS server, after the HTTPDNS server receives the domain name resolution request sent by the client side, the target domain name is resolved, a target IP address corresponding to the target domain name is determined and sent to the client side, after the client side receives the target IP address, the client side can access the target server to be accessed according to the target IP address, and the target server can provide network service for the client side. The method for resolving the target domain name by the http dns server may be any implementable method in the prior art, and this embodiment is not limited.

The domain name resolution request is in a message format based on HTTP, and the HTTPDNS server feeds back a domain name resolution result to the client in the message format of HTTP.

Optionally, step 106 may specifically include:

the HTTPDNS server analyzes the target domain name based on a preset IP library to obtain a target IP address corresponding to the target domain name.

Specifically, an IP library may be preset in the http dns server, and the client queries the preset IP library of the http dns server through a remote Query based on a database, for example, a domain name resolution result pre-stored in the http dns server may be queried through SQL (Structured Query Language).

Optionally, the domain name resolution result in the http dns server may also be stored in the local cache region by the http dns server in advance. The method can be specifically set according to actual requirements.

It should be noted that, the modes that can be implemented in the embodiments of the present disclosure may be implemented individually, or may be implemented in combination in any combination without conflict and are not limited.

Still another embodiment of the present disclosure provides a connection device of an http dns server, configured to perform the method of the foregoing embodiment.

Fig. 5 is a schematic structural diagram of a connection device of an http dns server according to an embodiment of the present disclosure. The connection means 30 of the http dns server comprises a receiving module 31 and a response module 32.

The receiving module is used for the HTTPDNS server to receive a connection request sent by the client based on a QUIC protocol; and the response module is used for the HTTPDNS server to respond to the connection request and establish connection with the client.

The specific manner in which the various modules perform operations with respect to the apparatus in the embodiments of the present disclosure has been described in detail in relation to the embodiments of the method, and will not be described in detail herein.

According to the connecting device of the HTTPDNS server, which is provided by the embodiment of the disclosure, the HTTPDNS server responds to the connection request sent by the client based on the QUIC protocol and establishes connection with the client, so that the connection of the HTTPDNS server based on the QUIC protocol is realized, and the connection delay of the HTTPDNS server can be effectively reduced.

The present disclosure further provides a supplementary description of the apparatus provided in the above embodiments, so as to perform the method provided in the above embodiments.

As an implementable manner, on the basis of the foregoing embodiment, optionally, the receiving module is specifically configured to:

the HTTPDNS server receives a Client Hello QUIC data packet sent by a Client;

the response module is specifically configured to:

and the HTTPDNS Server returns a Server Reject QUIC data packet according to the Client Hello QUIC data packet, completes QUIC handshake and establishes connection with the Client.

As another implementable manner, on the basis of the foregoing embodiment, optionally, the receiving module is further configured to:

the HTTP DNS server receives an HTTP request sent by a client;

a response module further to:

the HTTP dns server returns an HTTP response according to the HTTP request.

As another implementable manner, on the basis of the foregoing embodiment, optionally, the receiving module is further configured to: the method comprises the steps that an HTTPDNS server receives a domain name resolution request sent by a client, wherein the domain name resolution request comprises a target domain name to be resolved;

a response module further to: the HTTPDNS server determines a corresponding target IP address according to the target domain name; and the HTTPDNS server returns the target IP address to the client so that the client accesses the corresponding server according to the target IP address.

Optionally, the response module is specifically configured to:

According to the connecting device of the HTTPDNS server, the HTTPDNS server responds to the connection request sent by the client based on the QUIC protocol, and establishes connection with the client, so that the connection of the HTTPDNS server based on the QUIC protocol is realized, and the connection delay of the HTTPDNS server can be effectively reduced.

Yet another embodiment of the present disclosure provides an electronic device for performing the method provided by the above embodiment. The electronic device may be an http dns server.

Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. The electronic device 50 includes: at least one processor 51 and memory 52;

the memory stores a computer program; at least one processor executes the computer program stored in the memory to implement the methods provided by the above-described embodiments.

According to the electronic equipment disclosed by the embodiment of the disclosure, the HTTPDNS server responds to the connection request sent by the client based on the QUIC protocol, and establishes connection with the client, so that the connection of the HTTPDNS server based on the QUIC protocol is realized, and the connection delay of the HTTPDNS server can be effectively reduced.

As an exemplary embodiment, optionally, as shown in fig. 7, an exemplary structural diagram of an electronic device provided in the embodiment of the present disclosure is shown. The electronic device 800 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 801 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage means 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the electronic apparatus 800 are also stored. The processing apparatus 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

Generally, the following devices may be connected to the I/O interface 805: input devices 806 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 807 including, for example, a Liquid Crystal Display (LCD), speakers, vibrators, and the like; storage 808 including, for example, magnetic tape, hard disk, etc.; and a communication device 809. The communication means 809 may allow the electronic device 800 to communicate wirelessly or by wire with other devices to exchange data. While fig. 7 illustrates an electronic device 800 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may be alternatively implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication means 809, or installed from the storage means 808, or installed from the ROM 802. The computer program, when executed by the processing apparatus 801, performs the above-described functions defined in the methods of the embodiments of the present disclosure.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

Yet another embodiment of the present disclosure provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed, the method provided by any one of the above embodiments is implemented.

According to the computer-readable storage medium of the embodiment of the disclosure, the HTTPDNS server responds to the connection request sent by the client based on the QUIC protocol, and establishes connection with the client, so that the connection of the HTTPDNS server based on the QUIC protocol is realized, and the connection delay of the HTTPDNS server can be effectively reduced.

In the several embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present disclosure.

In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or in the form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present disclosure. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

It is obvious to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiment, which is not described herein again.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present disclosure, and not for limiting the same; while the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present disclosure.

Claims

1. A method for connecting an HTTP DNS server, wherein the HTTP DNS server is used for domain name resolution by using HTTP protocol, and the method comprises the following steps:

the HTTPDNS server receives a Client Hello QUIC data packet sent by a Client; the HTTPDNS Server returns a Server Reject QUIC data packet according to the Client Hello QUIC data packet, completes QUIC handshake and establishes connection with the Client;

the HTTPDNS server receives an HTTP request sent by the client;

the HTTPDNS server returns an HTTP response according to the HTTP request;

the HTTPDNS server receives a domain name resolution request sent by the client, wherein the domain name resolution request comprises a target domain name to be resolved, and is in a message format based on HTTP;

the HTTPDNS server analyzes the target domain name based on a preset IP database on the HTTPDNS server to obtain a target IP address corresponding to the target domain name;

the HTTPDNS server returns the target IP address to the client in an HTTP message format so that the client accesses the corresponding server according to the target IP address;

the analyzing the target domain name based on a preset IP database on the HTTPDNS server to obtain the target IP address corresponding to the target domain name includes:

and obtaining the target IP address corresponding to the target domain name by inquiring a preset IP database on the HTTPDNS server.

2. A connection device of an HTTP dns server for domain name resolution using HTTP protocol, comprising:

the receiving module is used for receiving a Client Hello QUIC data packet sent by a Client by the HTTPDNS server;

the response module is used for returning a Server Reject QUIC data packet to the HTTPDNS Server according to the Client Hello QUIC data packet, completing QUIC handshake and establishing connection with the Client;

the receiving module is further configured to:

the HTTPDNS server receives an HTTP request sent by the client;

the response module is further configured to:

the HTTPDNS server returns an HTTP response according to the HTTP request;

the receiving module is further configured to: the HTTPDNS server receives a domain name resolution request sent by the client, wherein the domain name resolution request comprises a target domain name to be resolved, and is in a message format based on HTTP;

the response module is further configured to: the HTTPDNS server determines a corresponding target IP address according to the target domain name; the HTTPDNS server returns the target IP address to the client in an HTTP message format so that the client accesses the corresponding server according to the target IP address;

the response module is specifically configured to:

the HTTPDNS server analyzes the target domain name based on a preset IP database on the HTTPDNS server to obtain the target IP address corresponding to the target domain name; the analyzing the target domain name based on a preset IP database on the HTTPDNS server to obtain the target IP address corresponding to the target domain name includes: and obtaining the target IP address corresponding to the target domain name by inquiring a preset IP database on the HTTPDNS server.

3. An electronic device, comprising: at least one processor and memory;

the memory stores a computer program; the at least one processor executes the computer program stored by the memory to implement the method of claim 1.

4. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when executed, implements the method of claim 1.