Domain name resolution method, system and ECS recursive server

Abstract

The present invention discloses a domain name resolution method, system and ECS recursive server, and relates to the field of data communication technology. The domain name resolution method includes: the ECS recursive server obtains the ECS domain name request sent by the user's terminal; the ECS recursive server sends iterative recursive messages that do not carry ECS information to one or more domain name servers in turn until the ECS obtains a preset NS domain name; the ECS recursive server sends an iterative recursive message carrying ECS ​​information to the corresponding GSLB according to the preset NS domain name, so that the GSLB determines the corresponding IP address according to the ECS information; the ECS recursive server receives the IP address sent by the GSLB; the ECS recursive server sends the IP address to the terminal. The embodiment of the present invention minimizes the risk of user information leakage and improves the security of the system without reducing the precise scheduling of CDN.

Description

Technical Field

[0001] The present invention relates to the field of data communication technology, and in particular to a domain name resolution method, device and system. Background Art

[0002] With the rapid development of video services, it is a business trend for CDN (Content Delivery Network) to sink to the edge and achieve precise scheduling. LDNS systems usually use the ECS (EDNS-Clinet-Subnet) protocol to carry user subnet information to provide CDN GSLB (Global Server Load Balancing) with accurate user locations, thereby achieving precise CDN scheduling. According to the ECS protocol prototype, during the level-by-level iteration of LDNS (Local DNS), the additional field of the DNS (Domain Name System) recursive message carries ECS information. Summary of the invention

[0003] After analysis, the inventor found that the user subnet information of telecom operators is internal confidential information, and the DNS domain name servers at all levels belong to different operating entities, which can easily cause user subnet information leakage. Moreover, ECS information is only useful for GSLB, and is useless for root servers, authorization servers and other domain name servers. It is an invalid overhead and is easy to cause misjudgment and errors.

[0004] A technical problem to be solved by the embodiments of the present invention is: how to improve the security of user information and reduce the overhead of the domain name resolution process.

[0005] According to a first aspect of some embodiments of the present invention, a domain name resolution method is provided, including: an ECS recursive server obtains an ECS domain name request sent by a user's terminal; the ECS recursive server sends iterative recursive messages that do not carry ECS information to one or more domain name servers in turn until the ECS obtains a preset NS domain name; the ECS recursive server sends an iterative recursive message carrying ECS ​​information to a corresponding GSLB according to the preset NS domain name, so that the GSLB determines a corresponding IP address according to the ECS information; the ECS recursive server receives the IP address sent by the GSLB; and the ECS recursive server sends the IP address to the terminal.

[0006] In some embodiments, the preset NS domain name is specified by GSLB.

[0007] In some embodiments, the domain name resolution method also includes: the ECS recursive server receives update information sent by GSLB, wherein the update information includes information of the updated NS domain name; the ECS recursive server updates the NS domain name database according to the update information, wherein the NS domain name database is used to store preset NS domain names.

[0008] In some embodiments, the update information includes the NS domain name and the operation type, and the operation type includes adding, modifying and deleting.

[0009] In some embodiments, the ECS recursive server receives update information sent by the GSLB based on the SOAP protocol.

[0010] In some embodiments, the ECS recursive server sends iterative recursive messages without ECS information to one or more domain name servers in sequence until the ECS obtains a preset NS domain name, including: for each of the one or more domain name servers, the ECS recursive server sends an iterative recursive message without ECS information to the domain name server; the ECS recursive server obtains the domain name returned by the domain name server; the ECS recursive server determines whether the returned domain name is located in the NS domain name database, so as to send an iterative recursive message without ECS information to the next domain name server when the returned domain name is not located in the NS domain name database.

[0011] In some embodiments, the ECS information is user subnet information.

[0012] According to a second aspect of some embodiments of the present invention, there is provided an ECS recursive server, comprising: a request acquisition module, configured to acquire an ECS domain name request sent by a user's terminal; a message sending module, configured to sequentially send iterative recursive messages that do not carry ECS information to one or more domain name servers until the ECS obtains a preset NS domain name; and, according to the preset NS domain name, sending an iterative recursive message carrying ECS ​​information to a corresponding GSLB, so that the GSLB determines a corresponding IP address according to the ECS information; an IP address receiving module, configured to receive an IP address sent by the GSLB; and an IP address sending module, configured to send the IP address to the terminal.

[0013] In some embodiments, the ECS recursive server also includes: a domain name management module, configured to receive update information sent by GSLB, wherein the update information includes information of the updated NS domain name; based on the update information, the NS domain name database is updated, wherein the NS domain name database is used to store preset NS domain names.

[0014] According to a third aspect of some embodiments of the present invention, there is provided an ECS recursive server, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute any of the aforementioned domain name resolution methods based on instructions stored in the memory.

[0015] According to a fourth aspect of some embodiments of the present invention, a domain name resolution system is provided, comprising: any one of the aforementioned ECS recursive servers; and a GSLB configured to determine a corresponding IP address based on ECS information in an iterative recursive message sent by the ECS recursive server.

[0016] In some embodiments, the GSLB is further configured to send update information to the ECS recursive server, wherein the update information includes information of the updated NS domain name.

[0017] According to a fifth aspect of some embodiments of the present invention, there is provided a computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements any one of the aforementioned domain name resolution methods.

[0018] Some embodiments of the above invention have the following advantages or beneficial effects. Through the embodiments of the present invention, when a user initiates an ECS domain name request, the ECS recursive server does not need to carry ECS information in the iterative recursive message before iterating to the specified NS domain name; after iterating to the specified NS domain name, the ECS recursive server sends a recursive message carrying ECS ​​information. Therefore, the ECS information is only passed to the GSLB that needs the information, and is no longer passed to other domain name servers. While not reducing the precise scheduling of the CDN, the risk of user information leakage is minimized and the security of the system is improved.

[0019] Further features and advantages of the present invention will become apparent from the following detailed description of exemplary embodiments of the present invention with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0021] Figure 1 A schematic flow chart of a domain name resolution method according to some embodiments of the present invention is shown.

[0022] Figure 2 A schematic flow chart of a method for synchronizing an NS domain name according to some embodiments of the present invention is shown.

[0023] Figure 3 A schematic flow chart of a domain name resolution method according to some other embodiments of the present invention is shown.

[0024] Figure 4 A schematic diagram of the structure of an ECS recursive server according to some embodiments of the present invention is shown.

[0025] Figure 5 A schematic structural diagram of a domain name resolution system according to some embodiments of the present invention is shown.

[0026] Figure 6 A schematic diagram of the structure of an ECS recursive server according to some other embodiments of the present invention is shown.

[0027] Figure 7 A schematic diagram of the structure of an ECS recursive server according to some further embodiments of the present invention is shown. DETAILED DESCRIPTION

[0028] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is by no means intended to limit the present invention and its application or use. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0029] The relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.

[0030] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0031] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.

[0032] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0033] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0034] Figure 1 FIG. 2 is a flow chart showing a domain name resolution method according to some embodiments of the present invention. Figure 1 As shown, the domain name resolution method of this embodiment includes steps S102 to S110.

[0035] In step S102, the ECS recursive server obtains the ECS domain name request sent by the user's terminal.

[0036] In step S104, the ECS recursive server sends iterative recursive messages without ECS information to one or more domain name servers in sequence until the ECS obtains a preset NS (Name Server) domain name.

[0037] For example, for each of the one or more domain name servers: the ECS recursive server sends an iterative recursive message without ECS information to the domain name server; the ECS recursive server obtains the domain name returned by the domain name server; the ECS recursive server determines whether the returned domain name is located in the NS domain name database, so as to send an iterative recursive message without ECS information to the next domain name server when the returned domain name is not located in the NS domain name database.

[0038] In some embodiments, one or more domain name servers include root domain name servers, domain name servers at various levels, or authoritative domain name servers, etc.

[0039] In some embodiments, the preset NS domain name is specified by GSLB. For example, GSLB can synchronize the preset NS domain name to the ECS recursive server.

[0040] In step S106, the ECS recursive server sends an iterative recursive message carrying ECS ​​information to the corresponding GSLB according to the preset NS domain name, so that the GSLB determines the corresponding IP (Internet Protocol) address according to the ECS information.

[0041] In some embodiments, the ECS information is user subnet information.

[0042] In step S108, the ECS recursive server receives the IP address sent by the GSLB.

[0043] In step S110 , the ECS recursive server sends the IP address to the terminal.

[0044] Through the above embodiment, when a user initiates an ECS domain name request, the ECS recursive server does not need to carry ECS information in the iterative recursive message before iterating to the specified NS domain name; after iterating to the specified NS domain name, the ECS recursive server sends a recursive message carrying ECS ​​information. Therefore, the ECS information is only passed to the GSLB that needs the information, and is no longer passed to other domain name servers. While not reducing the precise scheduling of CDN, the risk of user information leakage is minimized and the security of the system is improved.

[0045] In some embodiments, a synchronization mechanism may also be established between the ECS recursive server and the GSLB so that the GSLB synchronizes the specified NS domain name to the ECS recursive server in a timely manner. Figure 2 An embodiment of the NS domain name synchronization method of the present invention is described.

[0046] Figure 2 FIG. 2 is a flow chart showing a method for synchronizing an NS domain name according to some embodiments of the present invention. Figure 2 As shown, the NS domain name synchronization method of this embodiment includes steps S202 to S204.

[0047] In step S202, the ECS recursive server receives the update information sent by the GSLB, wherein the update information includes information of the updated NS domain name.

[0048] In some embodiments, the update information includes the NS domain name and the operation type, and the operation type includes adding, modifying and deleting.

[0049] For example, the fields of the synchronization message sent by GSLB to the ECS recursive server include:

[0050] Index identification field, used to identify each record;

[0051] NsName field, used to carry NS domain name characters;

[0052] The Operation field indicates the operation type. For example, a value of 1 represents adding, a value of 2 represents deleting, and so on.

[0053] In some embodiments, the ECS recursive server receives the update information issued by GSLB based on SOAP (Simple Object Access Protocol). By using the general SOAP protocol to implement mapping information negotiation, it is easy for the existing LDNS manufacturers to achieve seamless upgrades, facilitate the development of ECS services, and accelerate the deployment of CDN precise service scheduling.

[0054] In step S204, the ECS recursive server updates the NS domain name database according to the update information, wherein the NS domain name database is used to store preset NS domain names.

[0055] After completing the update, the ECS recursive server can also send a confirmation to the GSLB.

[0056] In the process of carrying out CDN precise scheduling services, many NS domain names recursively to GSLB are gradually updated as the services are carried out. The above embodiment realizes the real-time update configuration of such NS domain names, avoids manually updating LDNS data one by one, and greatly improves the efficiency, real-time and operability of service operations.

[0057] Figure 3 FIG. 2 shows a flow chart of a domain name resolution method according to some other embodiments of the present invention. Figure 3 As shown, the domain name resolution method of this embodiment includes steps S300 to S318.

[0058] In step S300, GSLB sends the preset NS domain name "m.ctcdn.com" to the ECS recursive server.

[0059] In step S302, the user terminal wants to access www.dd.com and sends a request to the ECS cache to query the corresponding resolution address.

[0060] In step S304, the ECS cache finds that there is no corresponding cache, and sends an ECS recursive request to the ECS recursive server.

[0061] In step S306, the ECS recursive server sends ECS recursive requests to the root domain name server and other domain name servers at each level in turn to execute the iteration process at each level. When the return results of each level do not include the preset NS domain name, these ECS recursive requests do not carry ECS information.

[0062] In step S308, the ECS recursive server continues to send an ECS recursive request to the authoritative domain name server of dd company, which also does not carry ECS information.

[0063] In step S310, the authoritative domain name server of dd company returns the NS domain name to the ECS recursive server, CNAME = "www.dd.com.ctcdn.net".

[0064] In step S312, the ECS recursive server finds that the returned NS domain name is the preset one, and sends an ECS recursive request including ECS ​​information to the GSLB corresponding to "www.dd.com.ctcdn.net".

[0065] In step S314, GSLB performs precise scheduling based on the ECS information and returns the service address "9.9.9.2".

[0066] In step S316, the ECS recursive server sends "9.9.9.2" to the ECS cache.

[0067] In step S318, the ECS cache returns the resolved address "9.9.9.2" to the user terminal.

[0068] Through the above embodiment, the ECS information is only transmitted to the GSLB that needs the information, and is no longer transmitted to other domain name servers. While not reducing the CDN's precise scheduling, the risk of user information leakage is minimized and the security of the system is improved.

[0069] Reference below Figure 4 An embodiment of the ECS recursive server of the present invention is described.

[0070] Figure 4 FIG. 4 shows a schematic diagram of the structure of an ECS recursive server according to some embodiments of the present invention. Figure 4 As shown, the ECS recursive server 400 of this embodiment includes: a request acquisition module 4100, configured to obtain an ECS domain name request sent by a user's terminal; a message sending module 4200, configured to send iterative recursive messages that do not carry ECS information to one or more domain name servers in sequence until the ECS obtains a preset NS domain name; and, according to the preset NS domain name, sending an iterative recursive message carrying ECS ​​information to the corresponding GSLB, so that the GSLB determines the corresponding IP address according to the ECS information; an IP address receiving module 4300, configured to receive an IP address sent by the GSLB; and an IP address sending module, configured to send the IP address to the terminal.

[0071] In some embodiments, the preset NS domain name is specified by GSLB.

[0072] In some embodiments, the ECS recursive server also includes: a domain name management module 4400, configured to receive update information sent by GSLB, wherein the update information includes information of the updated NS domain name; based on the update information, the NS domain name database is updated, wherein the NS domain name database is used to store preset NS domain names.

[0073] In some embodiments, the update information includes the NS domain name and the operation type, and the operation type includes adding, modifying and deleting.

[0074] In some embodiments, the domain name management module 4400 is further configured to receive update information sent by GSLB based on the SOAP protocol.

[0075] In some embodiments, the message sending module 4200 is further configured such that for each of one or more domain name servers, the ECS recursive server sends an iterative recursive message without ECS information to the domain name server; the ECS recursive server obtains the domain name returned by the domain name server; the ECS recursive server determines whether the returned domain name is located in the NS domain name database, so as to send an iterative recursive message without ECS information to the next domain name server when the returned domain name is not located in the NS domain name database.

[0076] In some embodiments, the ECS information is user subnet information.

[0077] Figure 5 FIG. 1 shows a schematic diagram of the structure of a domain name resolution system according to some embodiments of the present invention. Figure 5 As shown, the domain name resolution system 50 of this embodiment includes an ECS recursive server 400 and a GSLB 500. The GSLB 500 is configured to determine a corresponding IP address according to the ECS information in the iterative recursive message sent by the ECS recursive server 400.

[0078] In some embodiments, the GSLB 500 is further configured to send update information to the ECS recursive server 400, wherein the update information includes information of the updated NS domain name.

[0079] Figure 6 FIG. 2 shows a schematic diagram of the structure of an ECS recursive server according to some other embodiments of the present invention. Figure 6 As shown, the ECS recursive server 60 of this embodiment includes: a memory 610 and a processor 620 coupled to the memory 610 , and the processor 620 is configured to execute the domain name resolution method in any of the aforementioned embodiments based on instructions stored in the memory 610 .

[0080] The memory 610 may include, for example, a system memory, a fixed non-volatile storage medium, etc. The system memory may store, for example, an operating system, an application program, a boot loader, and other programs.

[0081] Figure 7 FIG. 2 shows a schematic diagram of the structure of an ECS recursive server according to some other embodiments of the present invention. Figure 7As shown, the ECS recursive server 70 of this embodiment includes: a memory 710 and a processor 720, and may also include an input / output interface 730, a network interface 740, a storage interface 750, etc. These interfaces 730, 740, 750 and the memory 710 and the processor 720 may be connected, for example, via a bus 760. Among them, the input / output interface 730 provides a connection interface for input / output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 740 provides a connection interface for various networked devices. The storage interface 750 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0082] An embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein the program implements any of the aforementioned domain name resolution methods when executed by a processor.

[0083] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0084] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0085] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0086] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0087] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A domain name resolution method, comprising: The extended domain name system-client-subnet ECS recursive server obtains the ECS domain name request sent by the user's terminal; The ECS recursive server sequentially sends iterative recursive messages without ECS information to one or more domain name servers until the ECS recursive server obtains a preset domain name server NS domain name, including: for each of the one or more domain name servers, the ECS recursive server sends an iterative recursive message without ECS information to the domain name server; the ECS recursive server obtains the domain name returned by the domain name server; the ECS recursive server determines whether the returned domain name is located in the NS domain name database, so as to send an iterative recursive message without ECS information to the next domain name server when the returned domain name is not located in the NS domain name database; The ECS recursive server sends an iterative recursive message carrying ECS ​​information to the corresponding global load balancing GSLB according to the preset NS domain name, so that the GSLB determines the corresponding network protocol IP address according to the ECS information; The ECS recursive server receives the IP address sent by the GSLB; The ECS recursive server sends the IP address to the terminal.

2. The domain name resolution method according to claim 1, wherein: The preset NS domain name is specified by the GSLB.

3. The domain name resolution method according to claim 2, further comprising: The ECS recursive server receives the update information sent by the GSLB, wherein the update information includes information of the updated NS domain name; The ECS recursive server updates the NS domain name database according to the update information, wherein the NS domain name database is used to store preset NS domain names.

4. The domain name resolution method according to claim 3, wherein: The update information includes the NS domain name and the operation type, and the operation type includes adding, modifying and deleting.

5. The domain name resolution method according to claim 3, wherein: The ECS recursive server receives the update information sent by the GSLB based on the Simple Object Access Protocol (SOAP) protocol.

6. The domain name resolution method according to any one of claims 1 to 5, wherein: The ECS information is user subnet information.

7. An ECS recursive server, comprising: A request acquisition module, configured to acquire an ECS domain name request sent by a user's terminal; The message sending module is configured to send iterative recursive messages without ECS information to one or more domain name servers in sequence until the ECS recursive server obtains a preset NS domain name, including: for each of the one or more domain name servers, the ECS recursive server sends an iterative recursive message without ECS information to the domain name server; the ECS recursive server obtains the domain name returned by the domain name server; the ECS recursive server determines whether the returned domain name is located in the NS domain name database, so as to send an iterative recursive message without ECS information to the next domain name server when the returned domain name is not located in the NS domain name database; and, according to the preset NS domain name, sending an iterative recursive message with ECS information to the corresponding GSLB, so that the GSLB determines the corresponding IP address according to the ECS information; An IP address receiving module is configured to receive the IP address sent by the GSLB; The IP address sending module is configured to send the IP address to the terminal.

8. The ECS recursive server according to claim 7, further comprising: The domain name management module is configured to receive update information sent by the GSLB, wherein the update information includes information of the updated NS domain name; and update the NS domain name database according to the update information, wherein the NS domain name database is used to store preset NS domain names.

9. An ECS recursive server, comprising: Memory; as well as A processor coupled to the memory, the processor being configured to execute the domain name resolution method according to any one of claims 1 to 6 based on instructions stored in the memory.

10. A domain name resolution system, comprising: The ECS recursive server according to any one of claims 7 to 9; as well as GSLB is configured to determine the corresponding IP address based on the ECS information in the iterative recursive message sent by the ECS recursive server.

11. The domain name resolution system according to claim 10, wherein: The GSLB is further configured to send update information to the ECS recursive server, wherein the update information includes information of the updated NS domain name.

12. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the domain name resolution method according to any one of claims 1 to 6 is implemented.

Images