WO2019061522A1 - Procédé de résolution de nom de domaine, client, nœud d'extrémité, et système de résolution de nom de domaine - Google Patents

Procédé de résolution de nom de domaine, client, nœud d'extrémité, et système de résolution de nom de domaine Download PDF

Info

Publication number
WO2019061522A1
WO2019061522A1 PCT/CN2017/105083 CN2017105083W WO2019061522A1 WO 2019061522 A1 WO2019061522 A1 WO 2019061522A1 CN 2017105083 W CN2017105083 W CN 2017105083W WO 2019061522 A1 WO2019061522 A1 WO 2019061522A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
name resolution
http
server
client
Prior art date
Application number
PCT/CN2017/105083
Other languages
English (en)
Chinese (zh)
Inventor
王华涛
Original Assignee
深圳前海达闼云端智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳前海达闼云端智能科技有限公司 filed Critical 深圳前海达闼云端智能科技有限公司
Priority to CN201780003273.3A priority Critical patent/CN108353095B/zh
Priority to PCT/CN2017/105083 priority patent/WO2019061522A1/fr
Publication of WO2019061522A1 publication Critical patent/WO2019061522A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a domain name resolution method, a client, an edge node, and a domain name resolution system.
  • Http(s) domain name server for domain name resolution has become more and more widely used.
  • Many Internet operators support the use of http(s) for domain name resolution.
  • the Http(s) domain name server is a mobile application that uses the HTTP protocol to send a domain name resolution request to the Http(s) domain name server, which replaces the traditional way of initiating a resolution request to the operator LocalDNS based on the DNS protocol. Therefore, it can avoid the domain name caused by LocalDNS.
  • Hijacking and cross-network access issues solve the problems caused by abnormal domain name resolution in mobile Internet services.
  • the conventional technology has at least the following problem: the node that returns the IP to the client is not necessarily the optimal node.
  • centralized scheduling is a more common scheduling method. Because the Http(s) domain name server cannot obtain the running status and node usage of each global service node, the simple centralized scheduling results in inaccurate domain name resolution.
  • An object of the present application is to provide a domain name resolution method, a client, an edge node, and a domain name resolution system, which solve the technical problem that the analysis result of the domain name is not accurate enough in the conventional technology.
  • the embodiment of the present application provides a domain name resolution method, which is applied to a client, and the method includes: sending a first Http(s) domain name resolution request to a central domain name server, where the first Http(s) And receiving, by the central domain name server, a jump status code and a jump URL, where the domain name to be resolved is a distributed type, and the jump URL points to an edge node serving the area where the client is located;
  • the jump status code sends a second Http(s) domain name resolution request to the edge node, so that the edge node parses the IP address corresponding to the to-be-resolved domain name according to the second Http(s) domain name resolution request.
  • the embodiment of the present application provides a domain name parsing method, which is applied to an edge node.
  • the method includes: receiving a second Http(s) domain name resolution request sent by the client; parsing an IP address corresponding to the domain name to be resolved according to the second Http(s) domain name resolution request, and returning the IP address.
  • the embodiment of the present application provides a domain name resolution method, which is applied to a central domain name server, and the method includes: receiving a first Http(s) domain name resolution request sent by a client, the first Http(s) The domain name resolution request includes a domain name to be resolved; when the domain name to be resolved of the first Http(s) domain name resolution request belongs to a distributed type, returning a jump status code and a jump URL to the client, the jump URL Point to the edge node that serves the area where the client is located.
  • an embodiment of the present application provides a domain name resolution apparatus, which is applied to a client.
  • the domain name resolution device includes: a first sending module, configured to send a first Http(s) domain name resolution request to the central domain name server; and a first receiving module, configured to: in the first Http(s) domain name resolution request to be parsed
  • the domain name belongs to a distributed type
  • the jump status code and the jump URL returned by the central domain name server are received, and the jump URL points to an edge node serving the area where the client is located
  • the second sending module is configured to The jump status code sends a second Http(s) domain name resolution request to the edge node, so that the edge node parses the IP corresponding to the to-be-resolved domain name according to the second Http(s) domain name resolution request.
  • the second receiving module is configured to receive the IP address returned by the edge node.
  • the embodiment of the present application provides a domain name resolution device, which is applied to an edge node, where the domain name resolution device includes: a third receiving module, configured to receive a second Http(s) domain name resolution request sent by the client;
  • the parsing module is configured to parse an IP address corresponding to the domain name to be resolved according to the second Http(s) domain name resolution request, and return the IP address to the client.
  • the embodiment of the present application provides a domain name resolution device, which is applied to a central domain name server, and the domain name resolution device includes: a fourth receiving module, configured to receive a first Http(s) domain name resolution request sent by a client
  • the first Http(s) domain name resolution request includes a domain name to be resolved
  • the first returning module is configured to: when the domain name to be resolved of the first Http(s) domain name resolution request belongs to a distributed type, to the client
  • the terminal returns a jump status code and a jump URL, and the jump URL points to an edge node serving the area where the client is located.
  • the beneficial effect of the present application is that, when resolving a domain name, first, the client sends a first Http(s) domain name resolution request to the central domain name server, so that the central domain name server returns a jump URL according to the first Http(s) domain name resolution request.
  • Jump status code the first Http(s) domain name resolution request includes the domain name to be resolved.
  • the client sends the second Http(s) domain name to the edge node pointed to by the jump URL according to the jump status code. Parsing the request, so that the edge node parses the IP address corresponding to the domain to be resolved according to the second Http(s) domain name resolution request, and returns an IP address. Since the edge node knows the state of each content service node, the analysis result is more accurate, so it can recommend the optimal IP address for the client.
  • FIG. 1 is a schematic structural diagram of a conventional domain name resolution according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of another conventional domain name resolution architecture provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a domain name resolution system according to an embodiment of the present application.
  • FIG. 4 is a signaling diagram of a domain name resolution method according to an embodiment of the present application.
  • FIG. 5 is a signaling diagram of a method for parsing a domain name of an edge node according to an embodiment of the present application
  • FIG. 6 is a schematic structural diagram of a client according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a domain name resolution apparatus according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a domain name resolution apparatus according to another embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a domain name resolution apparatus according to still another embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a domain name resolution apparatus according to still another embodiment of the present application.
  • FIG. 11 is a schematic flowchart diagram of a domain name resolution method according to an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of a domain name resolution method according to another embodiment of the present application.
  • FIG. 13 is a schematic flowchart diagram of a domain name parsing method according to still another embodiment of the present application.
  • FIG. 14 is a schematic flowchart diagram of a method for analyzing a domain name according to still another embodiment of the present application.
  • Figure 15 is a schematic flow chart of step 82 in Figure 4.
  • FIG. 16 is a schematic flowchart diagram of a method for analyzing a domain name according to still another embodiment of the present application.
  • Domain Name is a specific one on the Internet consisting of a string of characters separated by "dot".
  • the name of a computer or group of computers for example, the domain name is www.ddd.com.
  • an Internet Service Provider ISP
  • ISP Internet Service Provider
  • IP address corresponding to the domain name www.ddd.com is 11.22.33.44.
  • the domain name is in a tree structure.
  • the domain name server to the direct service DNS server (Domain Name Server) is divided into multiple levels.
  • www.heli.edu.cn is a domain name.
  • the domain name is divided into four levels. It is the host name "www”, the third-level domain name is "heli”, the second-level domain name is "edu”, and the top-level domain name is "cn”.
  • the TCP/IP protocol completes the connection between the two parties based on the IP address. Therefore, when an Internet device communicates on the network, it can only recognize an IP address such as "196.168.31.21" but cannot recognize the domain name. Moreover, for the user, it is impossible to accurately remember the website with more than 10 IP addresses. Therefore, when the user visits the website, it is more to enter the domain name in the address bar of the browser to complete the acquisition of the desired content page. In the process of obtaining the desired content page, the DNS server can "translate" the domain name accessed by the user into a corresponding IP address, and then retrieve the desired content page from the IP address again.
  • TCP/IP protocol Transmission Control Protocol/Internet Protocol
  • a DNS server is a computer and network service naming system organized into a domain hierarchy for use in a TCP/IP network. The services it provides are used to translate host names and domain names into IP addresses.
  • the DNS server includes an authoritative DNS and a non-authoritative DNS.
  • the authoritative DNS has a mapping corresponding to the DNS request in the database.
  • the non-authoritative DNS has no corresponding mapping, and the corresponding cache query result exists.
  • FIG. 1 is a schematic structural diagram of a conventional domain name resolution according to an embodiment of the present application.
  • the architecture 10 includes Guangdong Mobile User 11, Shanghai Telecom User 12, Guangdong Mobile LDNS13 (Local Operator Domain Name Service, Local DNS), Shanghai Telecom LDNS14, and Authoritative DNS 15.
  • the Guangdong mobile subscriber 11 can use the mobile terminal to send a domain name resolution request to the Guangdong Mobile LDNS 13, for example, the domain name resolution request includes the domain name www.dd.com.
  • the Shanghai Telecom subscriber 12 can use the mobile terminal to send a domain name resolution request to the Shanghai Telecom LDNS 14, for example, the domain name resolution request includes the domain name www.ff.com.
  • both Guangdong Mobile LDNS13 and Shanghai Telecom LDNS14 cache corresponding domain name resolution results.
  • Guangdong Mobile LDNS13 or Shanghai Telecom LDNS14 receives a domain name resolution request, it retrieves the cache. Record, query whether the cache has a domain name resolution result. If cached, Guangdong Mobile LDNS13 or Shanghai Telecom LDNS14 directly returns the domain name resolution result to Guangdong Mobile User 11 or Shanghai Telecom User 12. If not cached, it initiates a DNS recursive resolution request to the authoritative DNS 15 to enable the authoritative DNS 15 to query the corresponding domain name resolution result, and will return the domain name resolution result to the Guangdong mobile user 11 or the Shanghai telecommunications user 12.
  • the traditional domain name resolution process has certain defects.
  • the LDNS cache has domain name resolution results, it does not initiate a DNS recursive resolution request to the authoritative DNS. If the domain name is served through the http(s) protocol or other ports, User access will fail. For example: payment service, game connection to the connect server service through a designated port.
  • the operation and maintenance level of the LDNS is uneven, and there is a problem that the cache server fails and the user access is abnormal.
  • the LDNS itself does not perform domain name recursive resolution, but forwards the domain name resolution request to the recursive DNS of other LDNS, it will cause the source IP of the domain name resolution request received by the authoritative DNS to become the IP of other LDNS. Eventually, user traffic is directed to the wrong I DC, and user access is slow.
  • FIG. 2 is a schematic diagram of another conventional domain name resolution architecture according to an embodiment of the present application.
  • the traditional domain name resolution architecture 20 includes a user terminal 21 and an HTTP domain name server 22, wherein the Http(s) domain name server 22 supports domain name resolution of the Http(s) protocol.
  • the user terminal 21 initiates a domain name resolution request to the HTTP (S) domain name server, wherein the IP address of the user terminal 21 is 202.106.2.2.
  • the Http(s) domain name server 22 finds the IP address corresponding to the domain name according to the domain name resolution request: 4.3.2.2.
  • the Http(s) protocol is used for domain name resolution, which can avoid the problem of domain name hijacking and cross-network access caused by LocalDNS, solve the problem caused by the abnormal domain name resolution in the mobile Internet service, and the positioning is relatively accurate, and the analysis is relatively normal. .
  • the node that the Http(s) domain name server returns to the client's IP is not necessarily the optimal node.
  • centralized scheduling is a more common scheduling method. Because the Http(s) domain name server cannot obtain the running status and node usage of each global service node, the simple centralized scheduling results in inaccurate domain name resolution.
  • FIG. 3 is a schematic diagram of a domain name resolution system according to an embodiment of the present application.
  • FIG. 4 is a signaling diagram of a domain name resolution method according to an embodiment of the present application.
  • the system 30 includes a client 31, a central domain name server 32, a mail server 33, and an edge node 34.
  • the client 31 can communicate with the central domain name server 32, the mail server 33, the edge node 34, and the mail server 35, respectively, by wire or wirelessly.
  • the wired transmission medium may be an optical fiber, a coaxial cable, a telephone line, a network cable, or the like
  • the wireless mode may be a wireless personal area network (WPAN), a wireless local area network (WLAN), and a cellular network (Cellular Network), wherein the wireless individual
  • the local area network includes, for example, infrared communication (IRDA), Bluetooth, ZigBee
  • the wireless local area network includes, for example, the 802.11b standard, the 802.11a standard, and the 802.11g standard
  • the cellular network includes, for example, GSM, CDMA, TD-SCDMA, WCDMA, and CDMA2000.
  • the central domain name server 32, the mail server 33, and the edge node 34 all support the resolution of the Http(s) domain name.
  • the domain name resolution method includes:
  • Step 301 During communication, the client 31 sends a first Http(s) domain name resolution request to the central domain name server 32.
  • the first Http(s) domain name resolution request includes a domain name to be resolved.
  • Step 302 The central domain name server 32 receives the first Http(S) domain name resolution request sent by the client, and determines whether the domain name service type of the domain name to be resolved belongs to a distributed type according to the source IP address of the client or the IP address in the parameter.
  • Step 303 If the domain name service type of the domain name to be resolved belongs to a non-distributed type, the central domain name server 32 returns the analysis result to the client 31 according to the first Http(s) domain name resolution request.
  • Step 304 The client 31 initiates an application content request to the corresponding server according to the analysis result.
  • the client 31 initiates a mailbox domain name resolution request to the central domain name server 32, and the central domain name server 32 parses out that the mailbox domain name resolution request belongs to a non-distributed type, that is, the mail application content requested by the client 31 is not distributedly stored in each Within the class application server, but stored in the proprietary mail server 33, the central domain name server 32 sends the parsing result to the client 31, so that the client 31 directly initiates the mail application content to the mail server 33 based on the parsing result.
  • Step 305 If the domain name service type of the domain name to be resolved belongs to a distributed type, the central domain name server 32 returns a jump status code and a jump URL (Uniform Resource Locator) to the client 31 according to the first Http(s) domain name resolution request.
  • a jump URL Uniform Resource Locator
  • the central domain name server 32 dynamically generates a jump URL, and returns a jump status code to the client 31, and populates the jump URL into the Location field of the http(s) response, wherein the http(s) The response is a response of the central domain name server 32 in response to the first Http(s) domain name resolution request.
  • the jump URL points to the edge node 34 serving the area where the client 31 is located
  • the jump status code is used to instruct the client 31 to re-jump to the edge node 34 pointed to by the jump URL, the jump state.
  • the code may include a status code such as 302 redirect, and the like. 302 redirection means that the response corresponding to the current request can be found on another URI, and the client should access that resource by means of GET.
  • Step 306 When the domain name service type of the domain name to be resolved belongs to a distributed type, and the client 31 receives the http(s) response returned by the central domain name server 32, the client 31 points to the jump URL according to the jump status code.
  • the edge node 34 sends a second Http(s) domain name resolution request.
  • Step 307 The edge node 34 parses the IP address corresponding to the domain name to be resolved according to the second Http(s) domain name resolution request.
  • Step 308 the edge node 34 returns an IP address to the client 31.
  • the edge node 34 knows the state of each content service node, the analysis result is more accurate, and therefore, it can recommend an optimal IP address for the client.
  • the edge node 34 includes an edge domain name server 341, an application server 342, and a scheduling server 343.
  • the client 31 communicates with the edge domain name server 341 and the application server 342, respectively, by wire or wirelessly, and the dispatch server 343 communicates with the application server 342.
  • the edge name server 341 can provide the client with a channel to enter the network and communicate with other servers.
  • the edge name server 341 is a group of servers that perform a single function, such as a firewall server, a cache server, a load balancing server, and the like.
  • the edge domain name server 341 is located at the edge node and is capable of providing a server based on the Http(s) protocol domain name resolution function.
  • the edge domain name server 341 communicates with the dispatch server 342, obtains an IP address by pushing or pulling, and returns the IP address to the client 31 in an HTTP response manner.
  • the application server 342 can provide the client 31 with a server that applies content services.
  • the application server 342 receives the resource query request sent by the scheduling server 342, the application server 342 queries the resource usage of the resource according to the resource query request, and feeds back the resource usage to the scheduling server 343, for example, the central processing unit (Central Processing) Unit, CPU), memory, bandwidth, number of connections, etc. Resource usage information.
  • the central processing unit Central Processing
  • CPU Central Processing
  • the dispatch server 343 receives feedback of the resource usage of the application server 342, according to the settings
  • the scheduling rule determines the IP address of the application server 342 that can provide the optimal service, and dynamically recommends to the edge domain name server 341, wherein the recommended manner may be active sending and/or passive sending.
  • the edge domain name server 341 or the application server 342 or the scheduling server 343 may be a physical server or a logical server virtualized by multiple physical servers, or may be interconnected.
  • FIG. 5 is a signaling diagram of a method for parsing a domain name of an edge node according to an embodiment of the present application.
  • the domain name resolution method includes:
  • Step 501 When the client 31 receives the jump status code and the jump URL returned by the central domain name server 32, the client 31 sends the second Http(s) domain name resolution request to the edge domain name server 341 again.
  • Step 502 The edge domain name server 341 triggers the scheduling server 343 according to the second Http(s) domain name resolution request.
  • Step 503 the dispatch server 343 accesses the application server 342 to obtain the resource usage of the application server 342.
  • Step 504 Each application server 342 feeds back the respective resource usage status to the scheduling server 343.
  • the scheduling server 343 feeds back the status of the application server 342 in the deactivated state to the edge.
  • the edge domain name server 341 accesses another preset edge node according to the second Http(s) domain name resolution request until accessing the preset edge node that can return the IP address to the client 31.
  • the additional preset edge node is adjacent to the previous preset edge node.
  • Step 505 When resources of the application servers 342 in the edge node 34 are available, the scheduling server 343 determines an IP address of the application server 342 capable of providing an optimal service according to a preset scheduling rule.
  • Step 506 The scheduling server 343 returns the IP address corresponding to the domain name to be resolved to the edge domain name server 341.
  • Step 507 The edge domain name server 341 returns the IP address corresponding to the domain name to be resolved to the client 31.
  • Step 508 The client 31 sends a content service request to the application server 342 pointed to by the IP address.
  • Step 509 The corresponding application server 342 returns a corresponding content service to the client 31 according to the content service request.
  • the edge domain name server 341 dynamically resolves the domain name and receives the optimal IP address fed back by the scheduling server 343, thereby recommending the optimal IP address for the client 31.
  • the embodiment of the present application further provides a client.
  • the client 31 includes at least one processor 311 and a memory 312 communicatively coupled to the at least one processor 311; wherein the memory 312 stores a memory 312 that is executable by the at least one processor 311.
  • the edge domain name server 341 or the central domain name server 32 may adopt a hardware architecture as shown in FIG. 6 to complete the control logic of the corresponding domain name resolution, and details are not described herein again.
  • the embodiment of the present application provides a domain name resolution device, which is applied to a client.
  • the domain name resolution device is a software system, which can be stored in the client 31 illustrated in FIG. 6.
  • the domain name resolution device includes a plurality of instructions stored in a memory, the processor can access the memory, and invoke the instructions to execute to complete the domain name resolution device.
  • the domain name resolution device 40 includes a first sending module 41, a first receiving module 42, a second sending module 43, and a second receiving module 44.
  • the first sending module 41 is configured to send a first Http(s) domain name resolution request to the central domain name server;
  • the first receiving module 42 is configured to receive a jump status code and a jump URL returned by the central domain name server when the domain to be resolved of the first Http(s) domain name resolution request belongs to a distributed type, and the jump URL points to serve the client.
  • the second sending module 43 is configured to send a second Http(s) domain name resolution request to the edge node according to the hop state code, so that the edge node parses the IP corresponding to the domain name to be resolved according to the second Http(s) domain name resolution request. Address and return the IP address.
  • the second receiving module 44 is configured to receive an IP address returned by the edge node.
  • the edge node Since the edge node knows the state of each content service node, the analysis result is more accurate, so it can recommend the optimal IP address for the client.
  • the domain name resolution apparatus 40 further includes: a jump module 45, wherein the jump module 45 is configured to belong to the non-distributed type of the domain name to be resolved in the first Http(s) domain name resolution request. Then, according to the Http(s) domain name resolution response returned by the central domain name server, jump to the corresponding server.
  • the domain name resolution device 40 further includes: a third sending module 46, configured to send a content service request to an edge node pointed by the IP address.
  • the jump status code is a 302 redirected status code.
  • the embodiment of the present application provides a domain name resolution apparatus, which is applied to an edge node.
  • the domain name resolution device is a software system, which can be stored in the stated edge domain name server.
  • the domain name resolution device includes a plurality of instructions stored in a memory, the processor can access the memory, and invoke the instructions to execute to complete the domain name resolution device.
  • the domain name resolution device 50 includes a third receiving module 51 and a parsing module 52.
  • the third receiving module 51 is configured to receive a second Http(s) domain name resolution request sent by the client;
  • the parsing module 52 is configured to parse the IP address corresponding to the domain to be resolved according to the second Http(s) domain name resolution request, and return the IP address to the client.
  • the edge node Since the edge node knows the state of each content service node, the analysis result is more accurate, so it can recommend the optimal IP address for the client.
  • the edge node includes an edge domain name server, a scheduling server, and an application server.
  • the parsing module 52 is configured to: the edge domain name server triggers the scheduling server to access the application server according to the second Http(s) domain name resolution request; and when the resource usage of the application server belongs to the available state, the scheduling server uses the resource usage of the application server and the pre- Set the scheduling rule to return the IP address corresponding to the domain name to be resolved to the edge domain name server; the edge domain name server returns the IP address to the client.
  • the manner in which the scheduling server returns the IP address corresponding to the domain name to be resolved includes active sending and/or passive sending.
  • the parsing module 52 is further configured to: when the resource usage of the application server belongs to the deactivated state, the edge domain name server returns the IP address according to the second Http(s) domain name resolution request until the access to the client Another preset edge node.
  • the embodiment of the present application provides a domain name resolution device, which is applied to a central domain name server.
  • the domain name resolution device is a software system that can be stored in the central name server that is described.
  • the domain name resolution device includes a plurality of instructions stored in a memory, the processor can access the memory, and invoke the instructions to execute to complete the domain name resolution device.
  • the domain name resolution device 60 includes a fourth receiving module 61 and a first returning module 62.
  • the fourth receiving module 61 is configured to receive a first Http(s) domain name resolution request sent by the client, where the first Http(s) domain name resolution request includes a domain name to be resolved.
  • the first returning module 62 is configured to return a jump status code and a jump URL to the client when the domain to be resolved of the first Http(s) domain name resolution request belongs to a distributed type, and the jump URL points to the area where the client is located. Edge node.
  • the jump status code is the 302 redirected status code.
  • the edge node Since the edge node knows the state of each content service node, the analysis result is more accurate, so it can recommend the optimal IP address for the client.
  • the domain name resolution device 60 further includes a second returning module 63, and the second returning module 63 is configured to: the domain name to be resolved in the first Http(s) domain name resolution request belongs to a non-distributed domain.
  • the Http(s) domain name resolution response is returned to the client, so that the client jumps to the corresponding server.
  • the device embodiment and the foregoing embodiments are based on the same concept, and the content of the device embodiment may refer to the foregoing embodiments, and the details are not described herein.
  • the embodiment of the present application provides a plurality of domain name resolution methods (refer to the domain name resolution method described in the following embodiments).
  • the function of the domain name resolution method of the embodiment of the present application is performed by the software system of the domain name resolution device described above with reference to FIG. 7 or FIG. 8 or FIG. 9 and FIG. 10, which can also be executed by means of a hardware platform.
  • the domain name resolution method can be executed in an electronic device of a suitable type of processor having a computing capability, such as a single chip microcomputer, a digital signal processing (DSP), or the like.
  • the functions corresponding to the domain name resolution method of the following embodiments are stored in the form of instructions on the memory of the client or the edge domain name server or the central domain name server.
  • the processor of the client or the edge name server or the central domain name server accesses the memory, and retrieves and executes the corresponding instructions to implement the functions corresponding to the domain name resolution methods of the following embodiments.
  • the memory is a non-volatile computer readable storage medium and can be used for storing a non-volatile software program, a non-volatile computer executable program, and a module, such as the domain name resolution device 40 or the domain name resolution device 50 in the above embodiment. Or the program instruction/module corresponding to the domain name resolution device 60, or the step corresponding to the domain name resolution method of the following embodiment.
  • the processor executes various functional applications and data processing of the domain name resolution device 40 or the domain name resolution device 50 or the domain name resolution device 60 by running non-volatile software programs, instructions, and modules stored in the memory, that is, implementing the above embodiments.
  • the memory may include a high speed random access memory, and may also include a non-volatile memory such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the memory optionally includes a memory remotely located relative to the processor, the remote memory being connectable to the processor over 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 program instructions/modules are stored in the memory, and when executed by the one or more processors, perform a domain name resolution method in any of the above method embodiments, for example, performing FIG. 11 described in the following embodiments.
  • the steps shown in Fig. 13 or Fig. 14 and Fig. 15 or Fig. 16 are shown.
  • FIG. 11 is a schematic flowchart diagram of a domain name resolution method according to an embodiment of the present application. As shown in FIG. 11, the domain name resolution method 70 includes:
  • Step 71 Send a first Http(s) domain name resolution request to the central domain name server, so that the central domain name server returns the jump status code and the hop when the to-be-resolved domain name of the first Http(s) domain name resolution request belongs to a distributed type.
  • Transfer URL the jump URL points to the edge node serving the client's area;
  • Step 72 Send a second Http(s) domain name resolution request to the edge node according to the jump status code, so that the edge node parses the IP address corresponding to the domain name to be resolved according to the second Http(s) domain name resolution request, and returns an IP address. .
  • the jump status code may be a 302 redirected status code.
  • the edge node Since the edge node knows the state of each content service node, the analysis result is more accurate, so it can recommend the optimal IP address for the client.
  • the domain name resolution method 70 further includes:
  • Step 73 When the domain name to be resolved of the first Http(s) domain name resolution request belongs to a non-distributed type, the Http(s) domain name resolution response returned by the central domain name server is redirected to the corresponding server.
  • the domain name resolution method 70 further includes:
  • Step 74 Send a content service request to an edge node pointed to by the IP address.
  • FIG. 14 is a schematic flowchart diagram of a domain name resolution method according to still another embodiment of the present application.
  • the domain name resolution method 80 includes:
  • Step 81 Receive a second Http(s) domain name resolution request sent by the client.
  • Step 82 Parse the IP address corresponding to the domain name to be resolved according to the second Http(s) domain name resolution request, and return the IP address to the client.
  • the edge node Since the edge node knows the state of each content service node, the analysis result is more accurate, therefore, It can recommend the best IP address for the client.
  • the edge node includes an edge domain name server, a scheduling server, and an application server.
  • step 82 includes:
  • Step 821 The edge domain name server triggers the scheduling server to access the application server according to the second Http(s) domain name resolution request.
  • Step 822 Determine whether the resource usage of the application server is in an available state.
  • Step 823 When the resource usage of the application server is in an available state, the scheduling server returns an IP address corresponding to the domain to be resolved to the edge domain name server according to the resource usage of the application server and the preset scheduling rule.
  • Step 823 The edge domain name server returns the IP address to the client.
  • Step 824 When the resource usage of the application server is in the deactivated state, the edge domain name server resolves the request according to the second Http(s) domain name until accessing another preset edge node that can return the IP address to the client.
  • FIG. 16 is a schematic flowchart diagram of a domain name resolution method according to still another embodiment of the present application. As shown in FIG. 16, the domain name resolution method 90 includes:
  • Step 91 Receive a first Http(s) domain name resolution request sent by the client, where the first Http(s) domain name resolution request includes the domain name to be resolved.
  • Step 92 Determine whether the domain name service type of the domain name to be resolved belongs to a distributed type.
  • Step 93 If the domain name service type of the domain name to be resolved belongs to a distributed type, return a jump status code and a jump URL to the client according to the first Http(s) domain name resolution request, and the jump URL points to the area where the client is located.
  • the jump status code is a 302 redirected status code.
  • Step 94 If the domain name service type of the domain name to be resolved belongs to a non-distributed type, return an Http(s) domain name resolution response to the client, so that the client jumps to the corresponding server.
  • the edge node Since the edge node knows the state of each content service node, the analysis result is more accurate, so it can recommend the optimal IP address for the client.
  • an embodiment of the present application provides a non-transitory computer readable storage medium, where the non-transitory computer readable storage medium stores computer executable instructions, The computer executable instructions are for causing an electronic device to perform the domain name resolution method of any of the above.
  • the edge node Since the edge node knows the state of each content service node, the analysis result is more accurate, so it can recommend the optimal IP address for the client.

Landscapes

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

Abstract

La présente invention relève du domaine technique des communications, et concerne un procédé de résolution de nom de domaine, un client, un nœud d'extrémité, et un système de résolution de nom de domaine. Le procédé de résolution de nom de domaine consiste à : envoyer une première demande de résolution de nom de domaine Http(s) à un serveur de nom de domaine central et, lorsqu'un nom de domaine devant être résolu de la première demande de résolution de nom de domaine Http(s) est d'un type distribué, recevoir un code d'état de saut et une URL de saut retournés par le serveur de nom de domaine central, l'URL de saut visant à desservir un nœud d'extrémité d'une zone où se trouve le client; envoyer une seconde demande de résolution de nom de domaine Http(s) au nœud d'extrémité selon le code d'état de saut, de sorte que le nœud d'extrémité résolve, d'après la seconde demande de résolution de nom de domaine Http(s), une adresse IP correspondant au nom de domaine devant être résolu; et recevoir l'adresse IP retournée par le nœud d'extrémité. Comme le nœud d'extrémité connaît l'état de chaque nœud de service de contenu, le résultat de la résolution est plus précis. Une adresse IP optimale peut ainsi être recommandée pour le client.
PCT/CN2017/105083 2017-09-30 2017-09-30 Procédé de résolution de nom de domaine, client, nœud d'extrémité, et système de résolution de nom de domaine WO2019061522A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201780003273.3A CN108353095B (zh) 2017-09-30 2017-09-30 域名解析方法、客户端、边缘节点及域名解析系统
PCT/CN2017/105083 WO2019061522A1 (fr) 2017-09-30 2017-09-30 Procédé de résolution de nom de domaine, client, nœud d'extrémité, et système de résolution de nom de domaine

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/105083 WO2019061522A1 (fr) 2017-09-30 2017-09-30 Procédé de résolution de nom de domaine, client, nœud d'extrémité, et système de résolution de nom de domaine

Publications (1)

Publication Number Publication Date
WO2019061522A1 true WO2019061522A1 (fr) 2019-04-04

Family

ID=62961531

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/105083 WO2019061522A1 (fr) 2017-09-30 2017-09-30 Procédé de résolution de nom de domaine, client, nœud d'extrémité, et système de résolution de nom de domaine

Country Status (2)

Country Link
CN (1) CN108353095B (fr)
WO (1) WO2019061522A1 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110221872A (zh) * 2019-04-22 2019-09-10 五八有限公司 页面跳转方法、装置、电子设备和存储介质
CN111641732A (zh) * 2020-06-01 2020-09-08 湖南快乐阳光互动娱乐传媒有限公司 智能调度方法及装置
CN113010610A (zh) * 2021-04-15 2021-06-22 上海绚显科技有限公司 一种数据同步方法及装置
CN113067907A (zh) * 2020-01-02 2021-07-02 中国移动通信有限公司研究院 一种边缘应用寻址的方法和相关设备
CN113067909A (zh) * 2020-01-02 2021-07-02 中国移动通信有限公司研究院 边缘节点寻址方法、装置、设备及存储介质
CN114157635A (zh) * 2020-09-07 2022-03-08 中国移动通信集团湖南有限公司 内容分发网络的域名回源方法和装置、设备和存储介质
CN114390060A (zh) * 2021-12-13 2022-04-22 杭州网鼎科技有限公司 一种边缘计算网络分发的方法及存储介质
CN114513487A (zh) * 2020-10-28 2022-05-17 武汉斗鱼网络科技有限公司 一种加速域名解析的方法、装置、电子设备及计算机可读存储介质
CN115189940A (zh) * 2022-07-08 2022-10-14 深圳依时货拉拉科技有限公司 一种域名解析方法、装置、计算机设备和计算机可读存储介质
CN115277380A (zh) * 2022-08-02 2022-11-01 北京有竹居网络技术有限公司 基于域名解析的容灾方法、装置、系统、设备及存储介质

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109788051A (zh) * 2019-01-02 2019-05-21 深圳市网心科技有限公司 基于分布式文件系统的网络资源传输方法及系统
CN111064713B (zh) * 2019-02-15 2021-05-25 腾讯科技（深圳）有限公司 一种分布式系统中的节点控制方法和相关装置
CN110933664B (zh) * 2019-12-01 2022-09-20 杭州云缔盟科技有限公司 一种加速获取终端公网ip的方法
CN111064821A (zh) * 2019-12-23 2020-04-24 北京达佳互联信息技术有限公司 边缘节点的ip地址的确定方法和装置
CN111327697B (zh) * 2020-02-18 2022-01-11 腾讯科技（深圳）有限公司 一种数据下载方法、装置、设备及存储介质
CN113873048B (zh) * 2020-06-12 2023-05-12 腾讯科技（上海）有限公司 应用下载平台中应用包的下载方法及系统
CN114095578B (zh) * 2020-08-03 2024-05-07 中国移动通信集团浙江有限公司 功能分发方法、统一调度平台、边缘节点及计算设备
CN114124888A (zh) * 2020-08-25 2022-03-01 中国移动通信有限公司研究院 一种域名解析方法及装置
CN112468607B (zh) * 2020-11-14 2023-01-31 北京网聚云联科技有限公司 一种基于编解码技术的dns解析方法及系统
CN112738289B (zh) * 2020-12-24 2023-04-07 北京网聚云联科技有限公司 基于编码dns的cdn节点调度方法及其系统
CN113821461B (zh) * 2021-09-24 2023-10-27 牙木科技股份有限公司 域名解析缓存方法、dns服务器及计算机可读存储介质
CN115277694B (zh) * 2022-06-29 2023-12-08 北京奇艺世纪科技有限公司 一种数据获取方法、装置、系统、电子设备及存储介质
CN119155279A (zh) * 2023-06-15 2024-12-17 华为云计算技术有限公司 一种域名管理方法及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242422A (zh) * 2007-02-06 2008-08-13 中国电信股份有限公司 适应多业务融合的内容分发网络系统和方法
US20100306368A1 (en) * 2007-12-13 2010-12-02 Highwinds Holdings, Inc. Content delivery network with customized tracking of delivery data
CN101984637A (zh) * 2010-11-02 2011-03-09 中兴通讯股份有限公司 内容分发实现方法及系统
CN104184775A (zh) * 2013-05-27 2014-12-03 电子科技大学 一种基于内容发布网络(cdn)的域名解析服务模型

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404378B (zh) * 2010-09-07 2014-11-05 成都索贝数码科技股份有限公司 一种流媒体分发传输网络系统
ES2425626B1 (es) * 2011-05-12 2014-06-05 Telefónica, S.A. Método para la resolución de dns de peticiones de contenido en un servicio cdn
WO2013078687A1 (fr) * 2011-12-02 2013-06-06 华为技术有限公司 Procédé d'acheminement de données sur un réseau de distribution de contenu, et système et terminal d'utilisateur correspondants
CN104320487B (zh) * 2014-11-11 2018-03-20 网宿科技股份有限公司 内容分发网络的http调度系统和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242422A (zh) * 2007-02-06 2008-08-13 中国电信股份有限公司 适应多业务融合的内容分发网络系统和方法
US20100306368A1 (en) * 2007-12-13 2010-12-02 Highwinds Holdings, Inc. Content delivery network with customized tracking of delivery data
CN101984637A (zh) * 2010-11-02 2011-03-09 中兴通讯股份有限公司 内容分发实现方法及系统
CN104184775A (zh) * 2013-05-27 2014-12-03 电子科技大学 一种基于内容发布网络(cdn)的域名解析服务模型

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110221872A (zh) * 2019-04-22 2019-09-10 五八有限公司 页面跳转方法、装置、电子设备和存储介质
CN110221872B (zh) * 2019-04-22 2022-09-09 五八有限公司 页面跳转方法、装置、电子设备和存储介质
CN113067907A (zh) * 2020-01-02 2021-07-02 中国移动通信有限公司研究院 一种边缘应用寻址的方法和相关设备
CN113067909A (zh) * 2020-01-02 2021-07-02 中国移动通信有限公司研究院 边缘节点寻址方法、装置、设备及存储介质
CN111641732B (zh) * 2020-06-01 2023-01-24 湖南快乐阳光互动娱乐传媒有限公司 智能调度方法及装置
CN111641732A (zh) * 2020-06-01 2020-09-08 湖南快乐阳光互动娱乐传媒有限公司 智能调度方法及装置
CN114157635A (zh) * 2020-09-07 2022-03-08 中国移动通信集团湖南有限公司 内容分发网络的域名回源方法和装置、设备和存储介质
CN114157635B (zh) * 2020-09-07 2023-08-15 中国移动通信集团湖南有限公司 内容分发网络的域名回源方法和装置、设备和存储介质
CN114513487A (zh) * 2020-10-28 2022-05-17 武汉斗鱼网络科技有限公司 一种加速域名解析的方法、装置、电子设备及计算机可读存储介质
CN113010610A (zh) * 2021-04-15 2021-06-22 上海绚显科技有限公司 一种数据同步方法及装置
CN114390060A (zh) * 2021-12-13 2022-04-22 杭州网鼎科技有限公司 一种边缘计算网络分发的方法及存储介质
CN115189940A (zh) * 2022-07-08 2022-10-14 深圳依时货拉拉科技有限公司 一种域名解析方法、装置、计算机设备和计算机可读存储介质
CN115277380A (zh) * 2022-08-02 2022-11-01 北京有竹居网络技术有限公司 基于域名解析的容灾方法、装置、系统、设备及存储介质

Also Published As

Publication number Publication date
CN108353095A (zh) 2018-07-31
CN108353095B (zh) 2021-10-22

Similar Documents

Publication Publication Date Title
WO2019061522A1 (fr) Procédé de résolution de nom de domaine, client, nœud d'extrémité, et système de résolution de nom de domaine
US11632420B2 (en) Point of presence management in request routing
US11461402B2 (en) Routing based request correlation
US10931738B2 (en) Point of presence management in request routing
US9160703B2 (en) Request routing management based on network components
US9800539B2 (en) Request routing management based on network components
US8503433B2 (en) Routing methods and systems using ENUM servers
US10097398B1 (en) Point of presence management in request routing
JP5739023B2 (ja) 割り当てられたネットワークアドレスを有するデバイスにアクセスするウェブプロキシサーバを使用したシステムおよび方法
US8326956B2 (en) System and method for handling persistence information in a network
US10305800B2 (en) Preferential selection of IP protocol version with domain name matching on proxy servers
US20160028644A1 (en) Request routing in a networked environment
US20120290724A1 (en) System and method for network redirection
CN101540759B (zh) 业务服务器地址获取方法及通信系统
WO2009124006A2 (fr) Routage de demandes
CN102739811B (zh) 域名解析的方法和设备
CN110392069B (zh) Cdn业务调度处理方法及cdn服务器
WO2024198419A1 (fr) Procédé et appareil d'accès à une application décentralisée, dispositif électronique et support de stockage
WO2015103738A1 (fr) Procédé, appareil, et système de distribution de contenu
WO2013120315A1 (fr) Procédé de traitement d'information de nom de domaine, routeur sans fil, et client
WO2017097092A1 (fr) Procédé et système de traitement d'un service de grappe de cache
CN107347100B (zh) 一种内容分发网络的透明代理转发方法
CN112532765A (zh) 一种网络访问方法及其系统
US11909920B2 (en) Converged voicemail provisioning and FQDN based voicemail call routing
CN107395778B (zh) 一种用户溯源的方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17926976

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 11.09.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17926976

Country of ref document: EP

Kind code of ref document: A1