WO2019028683A1

WO2019028683A1 - Method and system for acquiring and collecting client local dns server

Info

Publication number: WO2019028683A1
Application number: PCT/CN2017/096485
Authority: WO
Inventors: 代明
Original assignee: 深圳前海达闼云端智能科技有限公司
Priority date: 2017-08-08
Filing date: 2017-08-08
Publication date: 2019-02-14
Also published as: CN108702397A; CN108702397B

Abstract

A method for acquiring and collecting a client local DNS server, comprising the following steps: at an authoritative server, when a parsing request for a detected domain name is received, redirecting same to a pre-set application server; at an application server, when an HTTP request for the detected domain name is received, redirecting the HTTP access request to a second domain name, the second domain name including the detected domain name and an IP address of a request end which has sent the HTTP request; and at the authoritative server, when a parsing request for the second domain name is received, establishing a correlation between the IP address of the request end included in the second domain name and the IP address of the local domain name server which has sent the second domain name parsing request.

Description

Method and system for acquiring and collecting client local DNS server

Technical field

The present application relates to the field of network domain name resolution, and specifically relates to a method and system for acquiring and collecting a client local DNS server.

Background technique

With the development of network technology, more and more commercial businesses have realized networked transactions. Such as banks, e-commerce platforms, etc. These networked services generally require support from a delivery network or a content distribution network.

The Application Delivery Network (ADN) leverages the appropriate network optimization/acceleration equipment to ensure that business applications are delivered to internal employees and external service groups quickly, securely and reliably. The Content Delivery Network (CDN) avoids bottlenecks and links on the Internet that may affect the speed and stability of data transmission, making content transmission faster and more stable. By placing a layer of intelligent virtual network based on the existing Internet on the network, the content distribution network system can real-time according to the network traffic and the connection of each node, the load status and the distance to the user. Comprehensive information such as response time directs the user's request to the service node closest to the user. Relying on the edge servers deployed in various places, through the load balancing, content distribution, scheduling and other functional modules of the central platform, users can obtain the required content nearby, reduce network congestion, and improve user access response speed.

In the existing Internet, the local domain name server (LDNS) receives the domain name resolution request of the local network client, recursively queries the upper-level domain name server, and finally resolves the domain name into an IP address from the authoritative server of the domain name being queried. In some network systems such as a content distribution network and an application delivery network, the authoritative server determines the network location of the client by sending the address of the local domain name server of the domain name resolution request, and returns to the content distribution network or the application delivery network that is closest to the client. The content distribution network or the IP address of the delivery network node is used as a response to the name resolution request query; the authoritative server here is also called GSLB (Global Service Load Balancer) in the content distribution network and the application delivery network. Since the global network environment has been changing, the local domain name server IP address library in the authoritative server needs to be constantly updated, but always encounters the non-existent or even the wrong local domain name server IP address, at which time the client is directed to A non-optimal access node makes the service performance of the content distribution network or application delivery network node worse.

Moreover, although the network client can view the local domain name server IP address of the network configuration of the client, but because of the complexity of the networking, the IP address may be the intranet IP, and the authoritative server of the content distribution network or the application delivery network needs to be based on The local domain name server with the public IP address closest to the client determines the location of the client. For the complex networking mode, it is difficult for the prior art to accurately determine the public IP address of the user.

Therefore, the domain name resolution technology of the existing content distribution network or application delivery network has yet to be improved.

Summary of the invention

In a first aspect, the embodiment of the present application provides a method for obtaining and collecting a local DNS server of a client, including the following steps: redirecting to a preset application when receiving an analysis request for detecting a domain name at an authoritative server At the application server, when receiving the HTTP request for detecting the domain name, redirecting the HTTP access request to the second domain name; the second domain name includes detecting the domain name and the IP address of the requesting end sending the HTTP request; And, when receiving the parsing request for the second domain name, establishing a correspondence between the requesting end IP address included in the second domain name and the local domain name server IP address that sends the second domain name resolution request.

In a second aspect, the embodiment of the present application provides a system for acquiring and collecting a local DNS server of a client, including a first module and a second module:

The first module is configured to, at the authoritative server, redirect to a preset application server when receiving the parsing request for detecting the domain name;

The first module is configured to redirect, at the application server, the HTTP access request to the second domain name when receiving the HTTP request for detecting the domain name; the second domain name includes detecting the domain name and the IP address of the requesting end sending the HTTP request ;

The first module is further configured to: at the authoritative server, when receiving the parsing request for the second domain name, establishing a requesting end IP address included in the second domain name and a local domain name server IP address sending the second domain name resolution request Correspondence between the two.

In a third aspect, the embodiment of the present application further provides a server cluster, including an authoritative server, an application server, and a storage server;

The authoritative server is configured to redirect to a preset application server when receiving the parsing request for detecting the domain name;

The application server is configured to: when receiving an HTTP request for detecting a domain name, the HTTP access Redirecting to the second domain name; the second domain name includes the probe domain name and the IP address of the requesting end that sends the HTTP request;

The authoritative server is further configured to: when receiving the parsing request for the second domain name, establish a correspondence between the requesting end IP address included in the second domain name and the local domain name server IP address that sends the second domain name resolution request.

In a fourth aspect, the embodiment of the present application further provides a server cluster, including a requesting end, a local domain name server, an authoritative server, an application server, and a storage server.

Each of the authoritative servers, application servers, and storage servers includes:

At least one processor; and,

a memory communicatively coupled to the at least one processor and a communication component; wherein

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to establish a data channel through the communication component to enable the at least one processor to perform the method as described above.

In a fifth aspect, the embodiment of the present application further provides a non-transitory computer readable storage medium, where the computer-readable storage medium is stored, where the computer-executable instructions are used to cause a computer to execute the above The method described.

The method and system for obtaining and collecting a client local DNS server provided by the embodiment of the present application are to detect the domain name and the second domain name as media, and the redirection method is simple and fast. Obtain and collect the IP address of the requesting end and the associated local domain name server; in the system, the authoritative server connects to the storage server, which acquires and collects the IP address of the requesting end and the associated local domain name server, and continuously updates with data analysis and consolidation. Optimize the IP address mapping database used by the authoritative server to provide users with optimal network access nodes and provide efficient and accurate domain name resolution services. The application cooperates with the customized authoritative server and the application server to obtain the public network IP address of the public network exit of the client and the local domain name server, stores the correspondence between the client IP address and the local domain name server, and establishes a database for the authoritative server to query and use. In the accurate and efficient provision of the domain name resolution service, the IP address can be returned to the requesting system and displayed to the client.

DRAWINGS

One or more embodiments are exemplarily illustrated by the pictures in the accompanying drawings, these The exemplifications are not intended to limit the embodiments, and the elements in the drawings are denoted by the same reference numerals, and the figures in the drawings are not to be construed as limiting.

1 is a flowchart of obtaining an IP address of a requesting end of a method for acquiring and collecting a local DNS server of a client according to an embodiment of the present application;

2 is a flowchart of obtaining an IP address of a local domain name server of a method for acquiring and collecting a local DNS server of a client according to an embodiment of the present application;

3 is a block diagram of a system for obtaining and collecting a client local DNS server according to an embodiment of the present application;

4 is a main flowchart of a method for acquiring and collecting a local DNS server of a client according to an embodiment of the present application;

5 is a flowchart of first address extraction, confirmation, and verification of a method for acquiring and collecting a client local DNS server according to an embodiment of the present application;

6 is a verification flowchart of a method for establishing a correspondence relationship between a method for acquiring and collecting a local DNS server of a client according to an embodiment of the present application;

FIG. 7 is a hardware framework diagram of each server node device for implementing a method for acquiring and collecting a client local DNS server according to an embodiment of the present application.

Detailed ways

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

Referring to FIG. 3, the system for obtaining and collecting the client local DNS server provided by the embodiment of the present application includes a requesting end 50, a local domain name server 60, an authoritative server 70, an application server 80, and a storage server 90. The requester 50 recursively resolves to the authoritative server 70 via the local domain name server 60. The application server 80 and the authoritative server 70 are connected to the storage server 90.

In terms of software settings, the system for acquiring and collecting the client local DNS server includes the first module A, the second module B, and the third module C. From the hardware correspondence, the first module A is disposed on the authoritative server 70, the second module B is disposed on the application server 80, and the third module C is disposed on the storage server 90.

The first module A is used at the authoritative server, when receiving the parsing request for detecting the domain name, Redirect to the default application server;

The second module B is configured to redirect, at the application server, the HTTP access request to the second domain name when receiving the HTTP request for detecting the domain name; the second domain name includes detecting the domain name and the IP of the requesting end sending the HTTP request address;

The first module A is further configured to: at the authoritative server, when receiving the parsing request for the second domain name, establishing a requesting end IP address included in the second domain name and a local domain name server IP address sending the second domain name resolution request Correspondence between them.

The third module C is configured to store, at the storage server, a correspondence relationship library formed by the confirmed correspondence relationship; and the first module A is further configured to provide the requesting end with effective information at the authoritative server based on the correspondence relationship library The IP address of the local domain name server.

On the basis of the existing domain name resolution system, the embodiment of the present invention provides a customized authority server 70, an application server 80, and a storage server 90, based on the access mechanism of the probe domain name and the second domain name, and is quickly and easily obtained through the redirection method. The IP address of the requesting end 50 and the associated local domain name server 60 is collected. The authoritative server 70, the application server 80, and the storage server 90 take special treatment for the parsing request for detecting the domain name and its second domain name to enhance the accuracy rate of the authoritative server in parsing the user request.

It should be noted that the database function of the storage server 90 may be set on the authoritative server 70 or may be set on the application server 80. In order to clearly illustrate the technical solution of the present application, the following embodiments are exemplified by a separately provided storage server 90.

The deployment of the system for acquiring and collecting the client local DNS server in the content distribution network or the application delivery network is as follows. In this embodiment, the HTTP protocol (HyperText Transfer Protocol, HTTP) communication is used between the requesting end 50 and the application server 80. The response of the server 80 to the requester 50 is in HTML (HyperText Markup Language, HTML) format. It will be appreciated that other protocols may be used as the protocol for communication between the requesting terminal 50 and the application server 80. The response of the application server 80 to the requesting end 50 can also use other formats, such as the JSON format. To simplify the description of the technical solution of the present application, the requesting end 50 in the following embodiment has an IP address, and the IP address in the embodiment refers to a public network address, and the public network address refers to an outgoing public IP address of the client, which is also called an LDNS address. If the requesting end 50 is in the internal network, the IP address of the requesting end in the example refers to the IP address of the public network egress.

Example 1

With reference to FIG. 1, in the system for obtaining and collecting the local DNS server of the client provided in this embodiment, the process of establishing each correspondence is as follows:

When receiving the parsing request for detecting the domain name, the authoritative server 70 redirects to the preset application server 80; when receiving the HTTP request for detecting the domain name, the application server 80 redirects the HTTP access request to the second domain name.

The second domain name includes a probe domain name and an IP address of the requester that sends the HTTP request.

When receiving the parsing request for the second domain name, the authoritative server 70 establishes a correspondence between the IP address of the requesting end 50 included in the second domain name and the IP address of the local domain name server 60 that sends the second domain name resolution request. .

When the application server 80 receives the HTTP request for detecting the domain name from the requesting end 50, the application server 80 acquires the IP address of the requesting end 50 and saves it to the storage server 90, and the application server 80 redirects the requesting end 50 to the second. domain name. The requesting end 50 initiates a resolution request to the authoritative server 70 for the redirected second domain name. The authoritative server 70 obtains the IP address of the requesting terminal 50 and the local domain name server 60 to which it is connected. The IP address in this embodiment refers to the public network address. The public network address refers to the public IP address of the egress of the client, which is also called the LDNS (Local Domain Name System, LDNS) address.

The authoritative server 70 verifies the IP address of the requesting terminal 50 and queries the storage server 90 whether the IP address has just initiated a request to the application server 80, and if so, the verification passes.

After the verification is passed, the authoritative server 70 establishes a correspondence between the requesting end IP address and the local domain name server IP address and saves it to the storage server 90.

At the same time, the authoritative server 70 redirects the requester 50 to the IP address of the application server 80. The requesting end 50 then initiates an HTTP request to the application server 80 for the second domain name, and the application server 80 confirms the correspondence and returns the confirmed IP address of the local domain name server 60.

A number of confirmed correspondences form a correspondence library.

The storage server 90 stores each piece of data of the confirmed correspondence and forms a correspondence library. The authoritative server 70 can read and query the corresponding relational library, and provide an associated valid local domain name server IP address for any requesting end based on the corresponding relational library.

In this embodiment, the authoritative server 70 configures the probe domain name and the second domain name as media for communication. The authoritative server 70 and the application server 80 perform domain name resolution optimization processing when receiving the request for parsing the domain name and the second domain name. The requesting end 50 detects the domain name and uses the local domain name service. The server 60 and the authoritative server 70 obtain the IP address of the application server 80; the requester 50 is redirected by the application server 80 to the second domain name. Then, the requesting end 50 completes the operation of extracting, verifying, and obtaining the address of the IP address of the requesting terminal 50 and the IP address of the local domain name server 60 between the systems through the second domain name. The system for obtaining and collecting the local DNS server of the client in this embodiment implements collection and delivery of information by configuring the probed domain name and the redirected second domain name.

In this embodiment, the probe domain name is as follows: www.example.com. The second domain name is exemplified by: c.c.c.c.www.example.com, where c.c.c.c represents the IP address of the requesting terminal 50.

Please refer to FIG. 3 together, wherein the local domain name server 60 includes a recursive parsing module 61. The requesting end 50 resolves to the authoritative server 70 via the recursive parsing module 61 based on the probed domain name.

The authoritative server includes a pre-stored module 71 and a second extraction module 72. The pre-stored module 71 is configured to provide the IP address of the application server 80 to the requesting end 50, so that the requesting end 50 obtains the IP address of the application server 80, and accesses the application server 80 through the probed domain name.

The application server 80 includes a first extraction module 81, a verification module 82, and a redirection module 83. The first extraction module 81 is configured to extract the IP address of the requesting end 50 and save it to the storage server 90. The redirection module 83 is configured to redirect the requesting end 50 to the second domain name.

The storage server 90 includes a correspondence relationship library 91, a marking module 92, and a screening module 93. It can be understood that the correspondence library 91, the marking module 92, and the screening module 93 can also be a software module disposed on the authoritative server 70 or a software module disposed on the application server 80.

Referring to FIG. 1, when the authoritative server 70 receives the parsing request for the probe domain name, it returns the IP address (bbbb) of the application server working with the authoritative server 70 to the requesting terminal 50. To simplify the description of the technical solution, the IP address is also For the LDNS address. Then, based on the probe domain name requesting end 50, an HTTP request is sent to the application server 80, and the probe carries the probe domain name www.example.com. After receiving the HTTP request, the application server 80 extracts the source IP address of the requesting end 50 from the data packet. The client IP address and the timestamp when the request was received are saved to the storage server 90. The application server 80 then sends a redirect response to the second domain name to the requesting end 50. The redirected destination domain name is: the requesting IP address + the probed domain name, and the middle is divided by "." to form a second domain name.

Referring to FIG. 2 together, the requester 50 then resolves to the authoritative server 70 via the recursive parsing module 61 of the local domain name server 60 based on the redirected second domain name c.c.c.c.www.example.com. The second extraction module 72 of the authoritative server 70 extracts the IP address (a.a.a.a) of the local domain name server 60 and obtains the IP address of the requesting end (c.c.c.c) from the second domain name. Simultaneously, The authoritative server 70 checks whether the accessed second domain name is a subdomain of the original probe domain name, and completes the address extraction, confirmation, and verification process. After the verification is passed, the authoritative server 70 extracts the IP address of the local domain name server 60 from the data message in the domain name resolution request of the second domain name. The authoritative server 70 establishes a correspondence between the requesting end IP address and the local domain name server IP address and saves it to the storage server 90. The marking module 92 of the storage server 90 marks the correspondence as to be confirmed.

The process of first address extraction, confirmation, and verification is as follows:

After receiving the redirect response of the second domain name, the requesting end 50 initiates a domain name resolution request to the authoritative server 70 again. After receiving the parsing request, the authoritative server 70 detects whether the second domain name is a subdomain name of the probe domain name, and if so, After removing the suffix detection domain name from the second domain name, the IP address (cccc) of the requesting end is obtained, and the authoritative server 70 queries the storage server whether the IP address has just initiated a request to the application server 80, and if so, the verification passes. The IP address (aaaa) of the local domain name server 60 is extracted from the domain name resolution request data packet of the second domain name, and then the client IP address and the local domain name server IP address are stored together in the corresponding relationship database of the storage server 90. . After the storage operation is completed, the IP address (b.b.b.b) of the application server 80 is returned to the requesting terminal 50 as a domain name response again. If the validity check fails, the domain name resolution request is not responded.

The confirmation process for the first address extraction is as follows:

The requesting end 50 initiates an HTTP request to the application server 80 for the second domain name. After receiving the request, the application server 80 extracts an IP address from the second domain name, and the verification module 82 obtains the IP address and the requester IP address extracted from the HTTP request data packet according to the suffix detection domain name in the second domain name. When the address is verified and the check is passed, the corresponding relationship is modified to be confirmed and recorded in the corresponding relationship database; when the check fails, the request is not responded to.

The verification process after establishing the corresponding relational library is as follows:

The requesting end 50 initiates an HTTP request to the application server 80 for the second domain name. After receiving the HTTP request, the first extraction module 81 of the application server 80 obtains the IP address of the requesting end 50, and the verification module 82 according to the corresponding The relationship library 91 performs address verification. When the error access is found or the IP address extraction fails, the redirection module 83 is further configured to redirect the requester 50 to the local domain name server 60 by detecting the domain name.

The specific process is: after receiving the domain name resolution result of the authoritative server 70, the requesting end 50 initiates an HTTP request to the application server 80 again, and the second domain name is used as the requested domain name in the request, and the application server 80 finds the request after receiving the HTTP request. The domain name is the second domain name, and the application server 80 is from the second domain. The IP address of the port is extracted from the name, and the IP address of the requesting end is extracted from the HTTP data packet, and the two IP addresses are checked for consistency. After the verification is passed, the client IP is queried from the corresponding relational library 91 of the storage server 90. The IP address of the local domain name server 60 corresponding to the address is returned to the requesting terminal 50 as a response content.

The storage server 90 further includes a screening module 93 for combing all the correspondences to be confirmed, and deleting the unconfirmed correspondences after storing the set time.

Example 2

Please refer to FIG. 4 together. In this embodiment, a method for obtaining and collecting a local DNS server of a client is provided. The method mainly includes the following steps:

Step 101: At the authoritative server, when receiving the parsing request for detecting the domain name, redirecting to the preset application server;

Step 102: At the application server, when receiving the HTTP request for detecting the domain name, redirecting the HTTP access request to the second domain name; the second domain name includes detecting the domain name and the IP address of the requesting end sending the HTTP request;

Step 103: At the authoritative server, when receiving the parsing request for the second domain name, establishing a correspondence between the requesting end IP address included in the second domain name and the local domain name server IP address sending the second domain name resolution request .

The method also includes the following steps:

The confirmed correspondence is stored in the corresponding relationship library;

Based on the correspondence library, the requesting end is provided with a valid IP address.

Please refer to FIG. 5, which details the method of obtaining and collecting the client local DNS server.

The method for obtaining and collecting the client local DNS server obtains and collects the requesting end by using the customized authoritative server 70, the application server 90, and the storage server 90, based on the access mechanism for detecting the domain name and the second domain name, by using the redirecting method. 50 and the IP address of the associated local domain name server 60. Upon receiving the resolution request for the probe domain name and the second domain name, the customized authoritative server 70, the application server 90, and the storage server 90 start domain name resolution optimization processing.

In this embodiment, the method for obtaining and collecting the local DNS server of the client is configured to detect the domain name and the second domain name as a medium for optimizing communication. An example of the probe domain name is www.example.com. The second domain name is exemplified by: c.c.c.c.www.example.com, where c.c.c.c represents the IP address of the requesting terminal 50.

Step 201: The authoritative server is redirected to the preset application server when receiving the request for parsing the domain name by the requesting end;

Step 202: The requesting end accesses the application server by using the probed domain name, including:

The requesting end initiates a domain name resolution request to the local domain name server, requesting to parse www.example.com;

The local domain name resolution server initiates a domain name resolution request to the authoritative domain name resolution server of www.example.com;

The authoritative domain name resolution server of www.example.com returns the IP address of the application server to the local domain name server;

The local domain name server returns the IP address of the application server to the requesting end;

The requesting end accesses the application server through the probe domain name, and initiates a request to the application server;

Step 203: When receiving the HTTP request for detecting the domain name, the application server extracts and saves the IP address of the requesting end, and redirects the requesting end to the second domain name, including:

The application server receives the request and finds that it is a request for www.example.com, extracts the IP address of the requesting end (c.c.c.c) and stores it in the storage server;

The application server sends a redirect response to the client, redirecting to the second domain name: c.c.c.c.www.example.com;

Step 204: The requester recursively to the authoritative server by using the local domain name server for the second domain name, including:

The requesting end initiates a domain name resolution request to the local domain name server, requesting to parse c.c.c.c.www.example.com;

The local domain name resolution server initiates a domain name resolution request to the authoritative domain name resolution server of c.c.c.c.www.example.com;

Step 205: The authoritative server obtains the IP address of the requesting end and the IP address of the local domain name server by using the second domain name.

Step 206: After verifying the IP address of the requesting end, the authoritative server establishes a correspondence between the IP address of the requesting end and the IP address of the local domain name server, and saves the corresponding relationship to be confirmed. The authoritative server extracts the IP address (aaaa) of the local domain name server, extracts the IP address of the requesting end through the second domain name, and verifies the IP address extracted from the second domain name. After the verification is passed, the IP address of the requesting end is established. The mapping between the IP address of the local domain name server is saved and includes:

Detecting whether the second domain name c.c.c.c.www.example.com is a subdomain of the probe domain name;

If yes, the suffix detection domain name is removed from the second domain name to obtain the IP address of the requesting end (c.c.c.c);

Query to the storage server whether this IP address has just initiated a request to the application server 80, and if so, the verification is passed;

After the verification is passed, the authoritative domain name resolution server of c.c.c.c.www.example.com saves the correspondence between c.c.c.c. and a.a.a.a to the storage server;

Mark the correspondence as to be confirmed, including:

The authoritative domain name resolution server of c.c.c.c.www.example.com marks the correspondence between the stored c.c.c.c. and a.a.a.a as the status to be confirmed;

The authoritative domain name resolution server of c.c.c.c.www.example.com returns the IP address of the application server to the local domain name server;

Step 207: The requesting end initiates an HTTP request to the application server by using the second domain name.

The requester initiates a request to the application server, and the requested domain name is c.c.c.c.www.example.com.

Step 208: When the application server receives the HTTP request for the second domain name, the IP address is extracted from the second domain name and the address verification is performed with the parsed requester IP address. When the verification is successful, the associated data is modified and confirmed. Belonged to the associated database, including:

The application server receives the request and finds that it is a request for c.c.c.c.www.example.com, and extracts the IP address of the requester (c.c.c.c);

Compared with the IP address stored by the storage server, the extracted IP address and the real IP address are verified to prevent malicious access;

Query the IP address of the local application server corresponding to the IP address of the requester (c.c.c.c) (a.a.a.a);

In the storage server, the correspondence relationship between the IP address (c.c.c.c) and the IP address (a.a.a.a) is changed to the confirmation status;

The storage server returns the local domain name server IP address of the requesting end (a.a.a.a);

The application server returns the requester IP address (c.c.c.c) and the requesting local domain name server IP address (a.a.a.a) to the requesting end;

Step 209: When the verification fails, the request of the requesting end is not responded;

Step 210: Screening all the correspondences to be confirmed, the unconfirmed correspondence is deleted after the storage set time, and the method for obtaining and collecting the local DNS server of the client further includes screening all the waiting The correspondence relationship confirmed, the unconfirmed correspondence is deleted after the storage set time.

The method for obtaining and collecting the local DNS server of the client in this embodiment, in addition to the first address extraction, confirmation, and verification, requires the domain name resolution and the second domain name to complete the domain name resolution optimization operation, and after the correspondence library is established, any request terminal also Local DNS server optimization and verification operations can be performed by detecting the domain name and redirecting to the second domain name.

Referring to FIG. 6, the verification process after the correspondence library is established includes:

Step 301: The requesting end initiates an HTTP request to the application server by using the second domain name.

Step 302: The application server extracts the IP address of the requesting end and performs address verification according to the corresponding relational library.

Step 303: Determine whether an erroneous access is found.

Step 304: Determine whether the IP address extraction fails.

Step 305: When the judgment is that the error is accessed or the IP address extraction fails, the request end is redirected to the local domain name server by detecting the domain name.

The method and system for obtaining and collecting a client local DNS server are used to detect a domain name and a second domain name as a medium, and the IP address of the requesting end and the associated local domain name server are obtained and collected simply and quickly by the redirecting method. In the system, the authoritative server is connected to the storage server, which acquires and collects the IP address of the requesting end and the associated local domain name server, and continuously updates and updates the correspondence database of the IP address used by the authoritative server in combination with data analysis and merging to provide the user with The optimal network access node, as well as providing efficient and more accurate domain name resolution services, can return the IP address to the requesting system and display it to the client.

Example 3

7 is a schematic diagram of a hardware structure of each server node device 600 for obtaining and collecting a client local DNS server according to an embodiment of the present application. As shown in FIG. 7, the server cluster includes a requesting end, a local domain name server, Authoritative server, application server, and storage server,

Each of the authoritative servers, the application server, and the storage server includes: at least one or more processors 610, a memory 620, and a communication component 650. One processor 610 is exemplified in FIG. The memory 620 stores instructions executable by the at least one processor 610, the instructions being executed by the at least one processor, establishing a data channel through the communication component 650 to enable the at least one processor to perform the acquisition and collect the client The method of the local DNS server.

The processor 610, the memory 620, and the communication component 650 may be connected by a bus or other means, as exemplified by a bus connection in FIG.

The memory 620 is used as a non-volatile computer readable storage medium for storing non-volatile software programs, non-volatile computer executable programs, and modules, such as obtaining and collecting client local DNS in the embodiment of the present application. The program instruction/module corresponding to the method of the server (for example, the pre-stored module 71, the second extraction module 72 shown by the authoritative server of FIG. 3, the first extraction module 81, the redirection module 82, and the verification module 82 shown by the application server The correspondence relationship library 91, the marking module 92, and the screening module 93) shown in the storage server are stored. The processor 610 executes various functional applications and data processing of the server by running non-volatile software programs, instructions, and modules stored in the memory 620, that is, obtaining and collecting the client local DNS server in the foregoing method embodiment. Methods.

The memory 620 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to the use of the domain name resolution system, and the like. Moreover, memory 620 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 620 can optionally include memory remotely located relative to processor 610, which can be connected to the robotic interactive electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The one or more modules are stored in the memory 620, and when executed by the one or more processors 610, perform the method of obtaining and collecting a client local DNS server in any of the above method embodiments, for example, Performing the method steps 101 to 103 of FIG. 4 described above, performing the method steps 201 to 210 of FIG. 5 described above and performing the method steps 301 to 305 of FIG. 6 described above; implementing the authority of FIG. The pre-stored module 71, the second extraction module 72, and the first extraction module 81, the redirection module 82, the verification module 82, and the corresponding relationship library 91, the labeling module 92 and the screen shown by the server are shown by the server. Check the function of module 93 and so on.

The above products can perform the methods provided by the embodiments of the present application, and have the corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the method provided by the embodiments of the present application.

Embodiments of the present application provide a non-transitory computer readable storage medium storing computer-executable instructions that are executed by one or more processors Executing, for example, performing the method steps 101 to 103 of FIG. 4 described above, performing the method steps 201 to 210 of FIG. 5 described above, and performing the method steps 301 to 305 of FIG. 6 described above; 3 is a pre-stored module 71, a second extraction module 72, and a first extraction module 81, a redirection module 82, a verification module 82, and a corresponding relationship library 91 shown by the application server. The functions of the module 92 and the screening module 93 and the like.

The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

Through the description of the above embodiments, those skilled in the art can clearly understand that the embodiments can be implemented by means of software plus a general hardware platform, and of course, by hardware. A person skilled in the art can understand that all or part of the process of implementing the above embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and are not limited thereto; in the idea of the present application, the technical features in the above embodiments or different embodiments may also be combined. The steps may be carried out in any order, and there are many other variations of the various aspects of the present application as described above, which are not provided in the details for the sake of brevity; although the present application has been described in detail with reference to the foregoing embodiments, The skilled person should understand that the technical solutions described in the foregoing embodiments may be modified, or some of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the embodiments of the present application. The scope of the technical solution.

Claims

A method for obtaining and collecting a client local DNS server, comprising the steps of:

At the authoritative server, when receiving the parsing request for detecting the domain name, redirecting to the preset application server;

At the application server, when receiving the HTTP request for detecting the domain name, redirecting the HTTP access request to the second domain name; the second domain name includes detecting the domain name and the IP address of the requesting end sending the HTTP request;

And at the authoritative server, when receiving the parsing request for the second domain name, establishing a correspondence between the requesting end IP address included in the second domain name and the local domain name server IP address sending the second domain name resolution request.
The method of claim 1 further comprising:

At the application server, when receiving an HTTP request for detecting a domain name, obtaining an IP address and a timestamp of the requesting end and saving the same;

Obtaining, by the second domain name, the requesting end IP address and the IP address of the local domain name server, verifying the requesting end IP address, and establishing the requesting end IP address and the local Corresponding relationship between the IP address of the domain name server is saved, and the corresponding relationship is marked as to be confirmed;

At the application server, the corresponding relationship is confirmed by the second domain name, and the confirmed IP address of the local domain name server is obtained.
The method for obtaining and collecting a client local DNS server according to claim 2, wherein the method further comprises: storing the confirmed correspondence relationship to a correspondence relationship library;

Providing a valid local domain name server IP address for the requesting end based on the corresponding relational library.
The method for obtaining and collecting a client local DNS server according to claim 2, further comprising:

At the application server, when receiving the HTTP request for detecting the domain name, extracting the IP address from the second domain name and performing address verification with the parsed requesting IP address, and verifying that the correspondence is Confirmed and classified into the corresponding relational library; when the verification fails, the request of the requesting end is not responded.
A method for obtaining and collecting a client local DNS server according to claim 3 The levy also includes:

At the application server, when receiving the HTTP request for detecting the domain name, parsing the IP address of the requesting end and performing address verification according to the corresponding relational library, and detecting the domain name by failing to detect the domain name when the error access or IP address extraction fails The endpoint is redirected to the local domain name server.
The method for obtaining and collecting a client local DNS server according to any one of claims 2-5, further comprising:

All correspondences to be confirmed are screened, and the unconfirmed correspondence is deleted after storing the set time.
A system for obtaining and collecting a client local DNS server, comprising: a first module and a second module:

The first module is configured to, at the authoritative server, redirect to a preset application server when receiving a parsing request for detecting the domain name;

The second module is configured to, at the application server, redirect the HTTP access request to a second domain name when receiving an HTTP request for detecting a domain name; the second domain name includes a probe domain name and a request for sending an HTTP request End IP address;

The first module is further configured to: at the authoritative server, when receiving the parsing request for the second domain name, establish a requesting end IP address included in the second domain name and a local domain name server IP that sends the second domain name resolution request The correspondence between addresses.
A system for obtaining and collecting a client local DNS server according to claim 7, wherein

The second module is further configured to: at the application server, obtain an IP address and a timestamp of the requesting end and save the HTTP request for detecting the domain name;

The first module is further configured to: at the authoritative server, obtain the IP address of the requesting end and the IP address of the local domain name server by using the second domain name, verify the IP address of the requesting end, and establish a Corresponding relationship between the IP address of the requesting end and the IP address of the local domain name server is saved, and the corresponding relationship is marked as to be confirmed;

The second module is further configured to: at the application server, confirm the corresponding relationship by using the second domain name, and obtain the confirmed IP address of the local domain name server.
The system for obtaining and collecting a client local DNS server according to claim 8, further comprising a third module, wherein the third module is configured to store the confirmed pair at the storage server Corresponding relationship library formed by relationship; and

The first module is further configured to provide, at the authoritative server, an IP address of a valid local domain name server for the requesting end based on the corresponding relational library.
The system for obtaining and collecting a client local DNS server according to claim 9, wherein the application server further comprises a verification module, which is initiated by the requesting end to the application server by using the second domain name. When requested, the verification module is configured to perform address verification according to the IP address extracted by the application server from the second domain name and the parsed requester IP address; when the verification is successful, the marking module of the storage server is further used. The correspondence is modified to be confirmed.
The system for obtaining and collecting a client local DNS server according to claim 9, wherein when the request is initiated to the application server by using the second domain name, the first extraction module of the application server is configured to parse The IP address of the requesting end, the verification module is further configured to perform address verification according to the correspondence relationship library, and when the error access is found or the IP address extraction fails, the redirection module is further configured to detect the domain name by using the The requester is redirected to the local domain name server.
The system for acquiring and collecting a client local DNS server according to any one of claims 8-11, wherein the storage server further comprises a screening module, and the screening module is configured to comb all the corresponding to be confirmed. Relationships, unconfirmed correspondences are deleted after the set time is stored.
A server cluster, comprising: an authoritative server, an application server, and a storage server;

The authoritative server is configured to redirect to a preset application server when receiving a parsing request for detecting a domain name;

The application server is configured to redirect the HTTP access request to a second domain name when receiving an HTTP request for detecting a domain name; the second domain name includes a probe domain name and an IP address of a requesting end that sends an HTTP request;

The authoritative server is further configured to: when receiving the parsing request for the second domain name, establish a correspondence between the requesting end IP address included in the second domain name and the local domain name server IP address that sends the second domain name resolution request .
A server cluster according to claim 13 wherein:

The application server is further configured to acquire an IP address and a timestamp of the requesting end and save the HTTP request for detecting the domain name;

The authoritative server is further configured to obtain the IP address of the requesting end and the location by using the second domain name. After the IP address of the local domain name server is verified, the corresponding relationship between the IP address of the requester and the IP address of the local domain name server is established and saved, and the corresponding relationship is marked as to be confirmed;

The application server is further configured to confirm the correspondence by using the second domain name, and obtain the confirmed IP address of the local domain name server.
The server cluster according to claim 14, wherein the storage server is configured to store a correspondence library formed by the confirmed correspondence relationship;

The first module is further configured to provide, at the authoritative server, an IP address of a valid local domain name server for the requesting end based on the corresponding relational library.
The server cluster according to claim 15, wherein the application server further comprises a verification module, when the request is initiated by the requesting end to the application server by using the second domain name, the verification module And performing, by the application server, an IP address extracted from the second domain name and performing address verification with the parsed requester IP address; when the verification is successful, the marking module of the storage server is further configured to modify the correspondence to be confirm.
The server cluster according to claim 15, wherein the first extraction module of the application server is configured to parse the IP address of the requesting end when the request is initiated by the second domain name to the application server. The verification module is further configured to perform address verification according to the correspondence relationship library. When the error access is found or the IP address extraction fails, the redirection module is further configured to redirect the request end to the local domain name by detecting the domain name. server.
The server cluster according to any one of claims 13-17, wherein the storage server further comprises a screening module, wherein the screening module is configured to comb all correspondences to be confirmed, and the unconfirmed correspondence relationship Delete after storing the set time.
A server cluster, characterized in that

Authoritative server, application server, and storage server,

Each of the authoritative servers, application servers, and storage servers includes:

At least one processor, a memory communicatively coupled to the at least one processor, and a communication component, the memory storing instructions executable by the at least one processor, the instructions being executed by the at least one processor, by communication The component establishes a data channel to enable the at least one processor to perform the method of any of claims 1-6.
A non-transitory computer readable storage medium, wherein the computer readable storage medium is stored There is stored computer executable instructions for causing a computer to perform the method of any of claims 1-6.