WO2021120969A1 - 域名解析方法、域名解析服务器及终端设备 - Google Patents

域名解析方法、域名解析服务器及终端设备 Download PDF

Info

Publication number
WO2021120969A1
WO2021120969A1 PCT/CN2020/129871 CN2020129871W WO2021120969A1 WO 2021120969 A1 WO2021120969 A1 WO 2021120969A1 CN 2020129871 W CN2020129871 W CN 2020129871W WO 2021120969 A1 WO2021120969 A1 WO 2021120969A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
domain name
server
user terminal
user
Prior art date
Application number
PCT/CN2020/129871
Other languages
English (en)
French (fr)
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 聚好看科技股份有限公司
Publication of WO2021120969A1 publication Critical patent/WO2021120969A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1021—Server selection for load balancing based on client or server locations
    • 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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1023—Server selection for load balancing based on a hash applied to IP addresses or costs

Definitions

  • This application relates to the field of Internet technology, and in particular to a domain name resolution method, domain name resolution server and terminal equipment.
  • the client user accesses the server corresponding to the target domain name through the Internet to obtain data resources.
  • domain name resolution is usually handled by the Domain Name System (DNS). It serves as a distributed database that can map domain names and IP (Internet Protocol) addresses to each other.
  • IP Internet Protocol
  • the IP address of the corresponding server is obtained by parsing, and returned to the client, so that the client can access data.
  • DNS Domain Name System
  • the client's data access process if the client user is physically far away from the server, it will cause high latency and high packet loss rates in the data access process, which will affect the user experience.
  • the remote multi-active technology deploys data center servers in different regions, synchronizes the data resources provided by CSP to data center servers in different regions, and can realize the nearest access of client users based on preset routing strategies, that is, route the client's access To the server closest to the client.
  • preset routing strategies that is, route the client's access To the server closest to the client.
  • different devices will inquire different access addresses, so that different devices using the same registered account will access Different servers. At this time, if the data on these accessed servers is inconsistent, the data requested by different devices will be inconsistent.
  • This application provides a domain name resolution method, domain name resolution server, and terminal equipment to solve the problem of data consistency when the same registered account is logged in on multiple devices in multiple regions.
  • this application provides a domain name resolution method, including:
  • the history analysis record it is searched whether there is a previous access address corresponding to the user identification, and when the previous access address corresponding to the user identification is the user terminal using the user identification for the previous access, The IP address of the server closest to the user terminal obtained according to the domain name resolution request;
  • the previous access address corresponding to the user ID is found in the historical analysis record, the previous access address is returned to the user terminal, so that the user terminal can use the previous access address and Perform data access.
  • this application provides a domain name access method, which includes:
  • the previous access address is the previous access address corresponding to the user identifier found in the historical analysis record by the server
  • the target The access address is the IP address of the server closest to the user terminal determined by the server according to the domain name resolution request
  • Data access is performed according to the previous access address or the target access address.
  • this application provides a domain name resolution server, including:
  • a receiving module configured to receive a domain name resolution request sent by a user terminal, where the domain name resolution request carries a user identifier for logging in to the user terminal;
  • the first parsing module is configured to find in the historical analysis records whether there is a previous access address corresponding to the user ID according to the user ID, and the previous access address corresponding to the user ID is the user who uses the user ID When the terminal performs prior access, the IP address of the server closest to the user terminal obtained according to the domain name resolution request;
  • the sending module is configured to return the previous access address to the user terminal if the previous access address corresponding to the user identification is found in the historical analysis record, so that the user terminal can follow the Access address and data access in advance.
  • this application provides a terminal device, including:
  • the generation module is used to generate a domain name query request carrying a user ID
  • a sending module used to send the domain name query request to the server
  • the receiving module is configured to receive the previous access address or the target access address returned by the server, where the previous access address is the previous access corresponding to the user ID found in the history analysis record by the server Address, where the target access address is the IP address of the server closest to the user terminal determined by the server according to the domain name resolution request;
  • the access module is used to perform data access according to the previous access address or the target access address.
  • the embodiments of the present application provide a domain name resolution method, a domain name access method, a domain name resolution server, and a terminal device.
  • the domain name resolution method receives a domain name resolution request, according to the user identification carried in the domain name resolution request, Look up whether there is a corresponding prior access address in the history analysis record. If the prior access address corresponding to the user ID is found, the prior access address will be returned to the user terminal so that the user terminal can use the prior access address Perform data access.
  • the server Since the previous access address corresponding to the user ID is the user terminal that uses the user ID for the previous access, the server resolves the address of the server closest to the user terminal that initiated the request, so when the same user ID is in multiple regions When logging in on the device, the user terminal accessed later and the user terminal accessed earlier can access the same server to obtain the required data. Furthermore, while ensuring the nearby access of the user terminal, it is possible to ensure that all devices with the same user ID are located at the same time. Obtain data consistency.
  • Fig. 1 is a schematic diagram of an implementation scenario exemplarily shown in this application according to some embodiments;
  • FIG. 2 is a flowchart of a domain name resolution method exemplarily shown in this application according to some embodiments
  • FIG. 3 is a flowchart of a domain name access method exemplarily shown in this application according to some embodiments
  • FIG. 4 is a block diagram of a domain name resolution server exemplarily shown according to some embodiments of the application.
  • Fig. 5 is a block diagram of a terminal device exemplarily shown according to some embodiments of the application.
  • CSP Content Service Provider
  • data resources such as videos, pictures, texts, etc.
  • client When a user terminal (client) needs to request data resources from the Internet, it needs to obtain the access address of the data resource, namely The IP address of the server where the data resource is located to communicate with the server.
  • the IP address is composed of 32-bit binary numbers, which is difficult for users to remember, so the server host name is mapped to the IP to form the mapping relationship between the server host name and the IP address, and the mapping relationship is used to obtain the known host name
  • the IP address of the server is a service system that saves the mapping relationship between all domain names and IPs on the Internet. It can respond to the domain name resolution request of the user terminal and resolve the target domain name (such as www.hisense.com) to obtain Correspond to the IP address of the server and return it to the user terminal so that the user terminal can access data.
  • DNS Domain Name System
  • the user terminal may initiate a recursive query or iterative query to the DNS, and the DNS performs the recursive query or iterative query in response to the request of the user terminal, and then returns the query result to the user terminal.
  • the DNS query result can be the IP address of the server corresponding to the domain name, or an error message indicates that the required IP address cannot be queried.
  • a terminal user wants to browse the data information provided by the data center server of the CSP, he needs to go through the backbone network, metropolitan area network, and access network of the Internet Service Provider (ISP) in turn, and finally arrive User terminal.
  • ISP Internet Service Provider
  • the network traffic pressure of the CSP server also increases, and if the user terminal is far away from the CSP server, there will be a higher delay and packet loss rate in network transmission.
  • Multi-active technology in different places, through the deployment of data center servers in different regions, the data resources provided by CSP are synchronized to data center servers in different regions, and then DNS is used for routing based on the export IP of the client, so that users can move from and to the nearest
  • the data resources are obtained on the server of the server, that is, the nearest access, so as to solve the problems of long delay and high packet loss rate in the data access process.
  • the user terminal may initiate a recursive query or iterative query to the DNS, and the DNS performs recursive query or iterative query in response to the request of the user terminal to obtain the IP address list of the server corresponding to the target domain name, and then determine the user based on the IP address of the user terminal The geographic location of the terminal, and finally the IP address of the server closest to the geographic location of the user terminal is selected from the IP address list obtained by the query, and the query result is returned to the client, so that the user terminal can visit nearby.
  • the IP address is mapped to a geographic location (region, such as an administrative region) to form a mapping relationship between the IP address and the geographic location, and the geographic location of the user terminal with a known export IP is obtained by using the mapping relationship.
  • a geographic location region, such as an administrative region
  • the resolution result of the DNS service for the domain name resolution request depends on the geographic location of the user terminal that made the request, which means that user terminals in different regions will be routed Go to data center servers in different regions to request data.
  • the data synchronization time may reach several seconds or even longer, so in a certain period of time, different The data on the regional data center servers is inconsistent.
  • the same registered account and its bound/associated account logs in to the Internet to request data on different devices in different regions, it will cause these devices to query different access addresses, making many users using the same registered account. Each device accesses different servers to obtain different data.
  • terminal device 1 uses the registered account ID-1 to log in to terminal device 1 (client U) in area D1
  • user B uses the same registered account ID-1 to log in to terminal device 2 (customer on area D2).
  • Terminal device 1 and terminal device 2 respectively request the DNS system to resolve the IP address of the target domain name (such as www.hisense.com); DNS responds to the request of the user terminal and performs recursive query or iterative query to obtain the IP address list of the server corresponding to the target domain name ; DNS judges the geographic location of terminal device 1 according to the IP address of terminal device 1, finds out the IP address of server 3 closest to terminal device 1 from the IP address list, and returns it to terminal device 1, according to the IP address of terminal device 2 The geographic location of the terminal device 2 is determined, the IP address of the server 4 closest to the terminal device 2 is found from the IP address list, and the IP address is returned to the terminal device 2.
  • the DNS server returns to terminal device 1 and terminal device 2 with different IP addresses, that is, server 3 and server 4 are different servers, terminal device 1 and terminal device 2 Inconsistent data may be requested.
  • the above-mentioned routing method for determining the geographic location of the user terminal based on the IP address of the user terminal may also enable the terminal user to access different data center servers, and then request to The data is inconsistent.
  • the IP address of the terminal device 1 in the region D1 is mapped to the region D1
  • the IP address is mapped to the region D2.
  • the server will think that the geographic location of the user terminal has changed from region D1 to region D2, so the user terminal may access data center servers in different regions before and after the mapping relationship changes, and the requested data is inconsistent .
  • an embodiment of the present application provides a domain name resolution method. This method can solve the problem when the same user logs in from multiple regions and multiple devices while ensuring the nearby access of the user terminal. Data consistency issues.
  • Fig. 2 is a flowchart of a domain name resolution method according to some embodiments of the application. As shown in Fig. 2, the method may include:
  • Step 110 The user terminal generates a domain name query request carrying the user identifier in response to the user operation.
  • the domain name query request includes information such as user identification, target domain name, client's exit IP address, terminal device identification, etc., where user identification refers to the registered account of the client logged in on the user terminal or other accounts that are associated or bound with the registered account. Such as mobile phone number.
  • Step 120 Send the domain name query request to the server.
  • step 130 the server receives a domain name resolution request sent by the user terminal, and the domain name resolution request carries a user identifier for logging in to the client on the user terminal.
  • Step 140 According to the user ID carried in the domain name resolution request, the server searches the history analysis record for whether there is a previous access address corresponding to the user ID.
  • the previous access address corresponding to the user ID is performed by the user terminal using the user ID.
  • the server obtains the IP address of the server closest to the geographic location of the user terminal according to the domain name resolution request.
  • the process of the user terminal requesting the server to resolve the target domain name in step 120 is defined as the current visit, and the access process of the user terminal or other user terminals that is earlier than the current visit is defined as the previous access.
  • step 150 is executed, and if the previous access address corresponding to the user ID is not found, step 160 is executed.
  • step 150 the previous access address is returned to the user terminal, so that the user terminal can use the previous access address and Data access is performed so that the client logged in using the user ID still accesses the server that it accessed earlier, so as to ensure the consistency of the data obtained when the same user account logs in on multiple devices in multiple regions.
  • step 160 the IP address of the server closest to the geographic location of the user terminal is determined as the target access according to the domain name resolution request. address. And in step 170, the determined target access address is returned to the user terminal, so that the user terminal performs data access according to the target access address.
  • the historical resolution record includes a number of information entries. Each information entry consists of a user ID and a corresponding previous access address.
  • the user ID is the user ID carried in the domain name resolution request sent by the user terminal that accessed previously.
  • the first access address is the analysis result returned by the server to the user terminal.
  • the previous access address is parsed by the server according to the domain name resolution request, and is the IP address of the server closest to the geographic location of the user terminal.
  • user A uses the registered account ID-1 to log in to the terminal device 1 (the client U) in the area D-1, and the terminal device 1 generates a domain name resolution request carrying the user identification ID-1 and sends it to On the server side, the domain name resolution request also includes the IP address of the terminal device 1 and the target domain name to be resolved.
  • the server receives the domain name resolution request sent by the terminal device 1, and first searches the historical resolution record to see if there is a prior access address corresponding to the user identification ID-1.
  • the server resolves the IP address IP-1 of the server 1 closest to the terminal device according to the IP address of the terminal device 1 and the target domain name. Return to the terminal device 1, and save the corresponding user ID-1 and IP-1 in the historical analysis record, as shown in Table 1:
  • the access time may be the time when the server receives the domain name resolution request sent by the client, or the time when the server returns the resolution result to the client, which is not limited by this application.
  • user B uses registered account ID-1 to log in to terminal device 2 (on the client U) in area D-2, and terminal device 2 generates a domain name resolution request carrying user identification ID-1 and sends it to On the server side, the domain name resolution request also includes the IP address of the terminal device 2 and the target domain name to be resolved.
  • the server receives the domain name resolution request sent by the terminal device 2, and first searches the historical resolution record to see if there is a prior access address corresponding to the user identification ID-1.
  • the historical analysis record includes an information entry about the user ID-1
  • the previous access address corresponding to the user ID-1 is IP-1
  • the server returns the previous access address IP-1 as the analysis result to the terminal device 2.
  • terminal devices 1 and 2 use the same registered account ID-1 to request the server to resolve the IP address of the target domain name.
  • the terminal device 2 accessed later accesses the server 1 according to IP-1 to obtain the data consistent with the terminal device 1, which solves the problem of the consistency of the data obtained when the same registered account is logged in from multiple regions and multiple devices.
  • the first mapping relationship and the second mapping relationship are obtained in advance.
  • the first mapping relationship is the mapping relationship between domain names and IP addresses, which is used to resolve the corresponding IP address according to the target domain name in the domain name resolution request
  • the second mapping relationship is the mapping relationship between IP addresses and geographic locations, which is used for The geographic location of the user terminal is determined according to the IP address of the user terminal in the domain name resolution request
  • the second mapping relationship is also used to determine the geographic location of the server based on the IP address of the server in the first mapping relationship, so that the When the geographic location of the user terminal and the geographic location of the server are known, the server closest to the user terminal is determined.
  • the server can determine the IP address of the server closest to the user terminal according to the following steps: first obtain an IP address list corresponding to the target domain name according to the first mapping relationship and the target domain name, and the IP address list includes at least one target domain name correspondence According to the second mapping relationship, the IP address of the user terminal and the IP address of the server in the IP address list, determine the geographic location of the user terminal and the geographic location of the server in the IP address list; finally, according to The geographic location of the user terminal and the geographic location of the server in the IP address list select the IP address of the server closest to the user terminal from the IP address list.
  • the previous access that exceeds the preset duration will be used.
  • the address and the corresponding user ID are deleted from the historical analysis record. Regularly check whether the information items in the historical analysis records are expired, and delete the expired information items, which can track the changes of the user's frequent geographic area in time, and prevent the user from still obtaining data based on the previous access address after migration.
  • the embodiments of the present application provide a domain name resolution method, a domain name access method, a domain name resolution server, and a terminal device.
  • the domain name resolution method receives a domain name resolution request, according to the user identification carried in the domain name resolution request, Look up whether there is a corresponding prior access address in the history analysis record. If the prior access address corresponding to the user ID is found, the prior access address will be returned to the user terminal so that the user terminal can use the prior access address Perform data access.
  • the server Since the previous access address corresponding to the user ID is the user terminal that uses the user ID for the previous access, the server resolves the address of the server closest to the user terminal that initiated the request, so when the same user ID is in multiple regions When logging in on the device, the user terminal accessed later and the user terminal accessed earlier can access the same server to obtain the required data. Furthermore, while ensuring the nearby access of the user terminal, it is possible to ensure that all devices with the same user ID are located at the same time. Obtain data consistency.
  • the domain name resolution method provided in the embodiments of the present application can be applied to a GSLB (Global Server Load Balance) cluster, and provide a control terminal and redis for the GSLB cluster.
  • GSLB Global Server Load Balance
  • Use the UI panel of the control terminal to import the aforementioned first mapping relationship data and the second mapping relationship data, and save the first mapping relationship data, the second mapping relationship data, and historical analysis records in redis.
  • an embodiment of the present application also provides a domain name access method applied to a client.
  • the method may include:
  • Step 210 Generate a domain name query request carrying a user identifier.
  • the domain name query request also includes the client's export IP address and target domain name.
  • Step 220 Send the domain name query request to the server.
  • Step 230 Receive the previous access address or the target access address returned by the server, where the previous access address is the previous access address corresponding to the user identifier that the server has found in the historical analysis record.
  • the target access address is the IP address of the server closest to the user terminal determined by the server according to the domain name resolution request.
  • Step 240 Perform data access according to the previous access address or the target access address.
  • an embodiment of the present application also provides a domain name resolution server.
  • the domain name resolution server may include:
  • the receiving module 410 is configured to receive a domain name resolution request sent by a user terminal, where the domain name resolution request carries a user identifier for logging in to the user terminal;
  • the first parsing module 420 is configured to find in the historical analysis records whether there is a previous access address corresponding to the user identification according to the user identification, and the previous access address corresponding to the user identification is the one using the user identification When the user terminal performs prior access, the IP address of the server closest to the user terminal obtained according to the domain name resolution request;
  • the sending module 430 is configured to, if the previous access address corresponding to the user identification is found in the historical analysis record, return the previous access address to the user terminal, so that the user terminal can be based on the previous access address. Describe the access address and data access in advance.
  • the domain name resolution server may further include: a second resolution module, configured to, if the previous access address corresponding to the user identifier is not found in the historical resolution record, perform a resolution request according to the domain name Determine the IP address of the server closest to the user terminal.
  • a second resolution module configured to, if the previous access address corresponding to the user identifier is not found in the historical resolution record, perform a resolution request according to the domain name Determine the IP address of the server closest to the user terminal.
  • the sending module is further configured to use the IP address of the server closest to the user terminal as the target access address, and return it to the user terminal, so that the user terminal performs data access according to the target access address .
  • the domain name resolution server may further include: a recording module, configured to correspondingly save the user identifier and the target access address in the historical resolution record.
  • the second parsing module is specifically configured to: obtain an IP address list corresponding to the target domain name, where the IP address list includes at least one IP address of a server corresponding to the target domain name;
  • the IP address of the terminal and the IP address of the server in the IP address list determine the geographic location of the user terminal and the geographic location of the server; according to the geographic location of the user terminal and the geographic location of the server in the IP address list Location, select the IP address of the server closest to the user terminal from the IP address list.
  • the second parsing module is specifically configured to: obtain a mapping relationship between an IP address and a geographic location; according to the IP address of the user terminal, search for the geographic location of the user terminal in the mapping relationship.
  • a GSLB cluster is built based on the domain name resolution server provided in the embodiments of the present application, and a control terminal and redis are provided for the GSLB cluster. Use the UI panel of the control terminal to import the aforementioned first mapping relationship data and the second mapping relationship data, and save the first mapping relationship data, the second mapping relationship data, and historical analysis records in redis.
  • an embodiment of the present application also provides a terminal device, which includes but is not limited to a display device, a portable smart user device, a head-mounted smart device, and the like.
  • a terminal device which includes but is not limited to a display device, a portable smart user device, a head-mounted smart device, and the like.
  • the terminal device provided by the embodiment of the present application includes:
  • the generating module 510 is used to generate a domain name query request carrying a user identifier
  • the sending module 520 is configured to send the domain name query request to the server
  • the receiving module 530 is configured to receive the previous access address or the target access address returned by the server, where the previous access address is the previous access address corresponding to the user ID found in the historical analysis record by the server Access address, where the target access address is the IP address of the server closest to the user terminal determined by the server according to the domain name resolution request;
  • the access module 540 is configured to perform data access according to the previous access address or the target access address.
  • this application also provides a computer storage medium, where the computer storage medium may store a program, and the program may include part or part of the domain name resolution method or domain name access method provided in this application when the program is executed.
  • the processor executes the steps of the domain name resolution method or the domain name access method described in this application.
  • the storage medium may be a magnetic disk, an optical disc, a read-only memory (English: read-only memory, abbreviated as: ROM) or a random access memory (English: random access memory, abbreviated as: RAM), etc.
  • the technology in the embodiments of the present application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solutions in the embodiments of the present application can be embodied in the form of software products in essence or parts that contribute to related technologies.
  • the computer software products can be stored in storage media, such as ROM/RAM, Magnetic disks, optical disks, etc., include several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments of the present application.

Landscapes

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

Abstract

本申请公开了域名解析方法、域名解析服务器及终端设备，该方法在接收到域名解析请求后，根据域名解析请求携带的用户标识，在历史解析记录中查找是否存在对应的在先访问地址，如果查找到对应的在先访问地址，则将该在先访问地址返回给用户终端，以使用户终端根据该在先访问地址进行数据访问。由于该用户标识对应的在先访问地址是使用该用户标识的用户终端进行在先访问时，解析出的的距离发起请求的用户终端最近的服务器地址，因此当同一用户标识在多地区多设备上登录时，能够使在后访问的用户终端与在先访问的用户终端访问同一服务器以获取所需的数据，进而，保证各个设备所获取数据的一致性。

Description

域名解析方法、域名解析服务器及终端设备
本申请要求在2020年02月21日提交中国专利局、申请号为202010108777.5、发明名称为“域名解析方法、域名解析服务器及终端设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网技术领域，尤其涉及一种域名解析方法、域名解析服务器及终端设备。
背景技术
相关技术中，客户端用户通过互联网访问目标域名对应的服务器以获取数据资源。其中，域名解析的工作通常由域名系统(Domain Name System，DNS)负责，它作为可以将域名和IP(Internet Protocol，网络之间互连的协议)地址相互映射的一个分布式数据库，能够对域名进行解析得到对应服务器的IP地址，并返回给客户端，以使客户端进行数据访问。在客户端进行数据访问的过程中，如果客户端用户距离服务器的物理距离较远，将导致数据访问过程存在高延时和高丢包率的问题，影响用户体验。
异地多活技术通过不同地区部署数据中心服务器，将CSP提供的数据资源同步到不同地区的数据中心服务器上，并可以基于预设路由策略实现客户端用户的就近访问，即，将客户端的访问路由到距离客户端最近的服务器。然而，当同一注册账号(和其绑定/关联的账号)在不同地区的不同设备上登录互联网时，将导致不同设备查询到不同的访问地址，从而使得使用同一注册账号的不同设备会访问到不同的服务器。此时，如果这些被访问的服务器上的数据不一致，将导致不同设备请求到的数据不一致。
发明内容
本申请提供一种域名解析方法、域名解析服务器及终端设备，以解决同一注册账号在多地区多设备上登录时获取数据的一致性问题。
第一方面，本申请提供一种域名解析方法，包括：
接收用户终端发送的域名解析请求，所述域名解析请求携带有登录所述用户终端的用户标识；
根据所述用户标识，在历史解析记录中查找是否存在所述用户标识对应的在先访问地址，所述用户标识对应的在先访问地址为使用所述用户标识的用户终端进行在先访问时，根据域名解析请求得到的距离所述用户终端最近的服务器的IP地址；
如果在所述历史解析记录中查找到所述用户标识对应的在先访问地址， 则将所述在先访问地址返回给所述用户终端，以使所述用户终端根据所述在先访问地址及进行数据访问。
第二方面，本申请提供一种域名访问方法，所述方法包括：
生成携带有用户标识的域名查询请求；
发送所述域名查询请求至服务端；
接收所述服务端返回的在先访问地址或者目标访问地址，所述在先访问地址为所述服务端在历史解析记录中查找到的与所述用户标识对应的在先访问地址，所述目标访问地址为所述服务端根据所述域名解析请求确定的距离用户终端最近的服务器的IP地址；
根据所述在先访问地址或者目标访问地址进行数据访问。
第三方面，本申请提供一种域名解析服务器，包括：
接收模块，用于接收用户终端发送的域名解析请求，所述域名解析请求携带有登录所述用户终端的用户标识；
第一解析模块，用于根据所述用户标识，在历史解析记录中查找是否存在所述用户标识对应的在先访问地址，所述用户标识对应的在先访问地址为使用所述用户标识的用户终端进行在先访问时，根据域名解析请求得到的距离所述用户终端最近的服务器的IP地址；
发送模块，用于如果在所述历史解析记录中查找到所述用户标识对应的在先访问地址，则将所述在先访问地址返回给所述用户终端，以使所述用户终端根据所述在先访问地址及进行数据访问。
第四方面，本申请提供一种终端设备，包括：
生成模块，用于生成携带有用户标识的域名查询请求；
发送模块，用于发送所述域名查询请求至服务端；
接收模块，用于接收所述服务端返回的在先访问地址或者目标访问地址，所述在先访问地址为所述服务端在历史解析记录中查找到的与所述用户标识对应的在先访问地址，所述目标访问地址为所述服务端根据所述域名解析请求确定的距离用户终端最近的服务器的IP地址；
访问模块，用于根据所述在先访问地址或者目标访问地址进行数据访问。
由以上技术方案可知，本申请实施例提供一种域名解析方法、域名访问方法、域名解析服务器以及终端设备，所述域名解析方法在接收到域名解析请求后，根据域名解析请求携带的用户标识，在历史解析记录中查找是否存在对应的在先访问地址，如果查找到该用户标识对应的在先访问地址，则将该在先访问地址返回给用户终端，以使用户终端根据该在先访问地址进行数据访问。由于该用户标识对应的在先访问地址是使用该用户标识的用户终端进行在先访问时，服务端解析出的的距离发起请求的用户终端最近的服务器 地址，因此当同一用户标识在多地区多设备上登录时，能够使在后访问的用户终端与在先访问的用户终端访问同一服务器以获取所需的数据，进而，在保障用户终端就近访问的同时，保证具有同一用户标识的各个设备所获取数据的一致性。
附图说明
为了更清楚地说明本申请的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，对于本领域普通技术人员而言，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请根据一些实施例示例性示出的实施场景示意图；
图2为本申请根据一些实施例示例性示出的域名解析方法流程图；
图3为本申请根据一些实施例示例性示出的域名访问方法流程图；
图4为本申请根据一些实施例示例性示出的域名解析服务器框图；
图5为本申请根据一些实施例示例性示出的终端设备框图。
具体实施方式
为了使本技术领域的人员更好地理解本申请中的技术方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
内容服务提供商(Content Service Provider，CSP)可以为互联网用户提供诸如视频、图片、文字等数据资源，当用户终端(客户端)需要向互联网请求数据资源时，需要获取数据资源的访问地址，即数据资源所在服务器的IP地址，以与该服务器进行通信。
实际上，IP地址由32位二进制数字组成，对于用户而言难以记忆，于是将服务器主机名映射到IP，形成服务器主机名与IP地址的映射关系，将该映射关系用以获取已知主机名的服务器的IP地址。域名系统(Domain Name System，DNS)即保存了互联网上所有域名与IP间映射关系的服务系统，它可以响应用户终端的域名解析请求，对目标域名(如www.hisense.com)进行解析，得到对应服务器的IP地址，并返回给用户终端，以使用户终端进行数据访问。
在一些实施例中，用户终端可以向DNS发起递归查询或者迭代查询，DNS响应用户终端的请求进行递归查询或者迭代查询，再将查询结果返回给用户终端。DNS的查询结果可以为域名对应服务器的IP地址，或者为报错，表示无法查询到所需的IP地址。
在一些实施例中，终端用户若要浏览到由CSP的数据中心服务器所提供的数据信息，需要依次经过互联网服务商(Internet ServiceProvider，ISP)的骨干网、城域网和接入网，最终到达用户终端。随着业务访问量的增多，CSP服务器的网络流量压力也增大，并且，如果用户终端与CSP服务器的距离较远，网络传输会存在较高的时延和丢包率。
异地多活技术，通过在不同地区部署数据中心服务器，将CSP提供的数据资源同步到不同地区的数据中心服务器上，再利用DNS基于客户端的出口IP进行路由，从而使用户可以从与距其最近的服务器上获取数据资源，即就近访问，进而解决数据访问过程中的延时长和丢包率高的问题。
在一些实施例中，用户终端可以向DNS发起递归查询或者迭代查询，DNS响应用户终端的请求进行递归查询或者迭代查询，得到目标域名对应服务器的IP地址列表，再根据用户终端的IP地址判断用户终端所在的地理位置，最后在查询得到的IP地址列表中选择出距离用户终端所在的地理位置最近的服务器的IP地址，作为查询结果返回给客户端，从而使用户终端就近访问。
在一些实施例中，将IP地址映射到地理位置(地区，如行政区域)，形成IP地址与地理位置之间的映射关系，利用该映射关系获得已知出口IP的用户终端所在的地理位置。
从以上实施例可以看出，DNS服务对域名解析请求的解析结果(目标域名的IP地址)，取决于发出请求的用户终端所在的地理位置，这就意味着，不同地区的用户终端会被路由到不同地区的数据中心服务器，来请求数据。
然而，由于不同地区的数据中心服务器间的数据同步过程周期性进行，且因不同地区的数据中心服务器距离较远，使得数据同步时间可能达到几秒甚至更长，因此在某一段时间内，不同地区的数据中心服务器上的数据是不一致的。在这段时间内，如果同一注册账号(和其绑定/关联的账号)在不同地区的不同设备上登录互联网请求数据，将导致这些设备查询到不同的访问地址，使得使用同一注册账号的多个设备访问到不同的服务器，进而获得不同的数据。
如图1所示，用户甲在地区D1使用注册账号为ID-1登录终端设备1(上的客户端U)，用户乙在地区D2使用同一注册账号ID-1登录终端设备2(上的客户端U)。终端设备1和终端设备2分别请求DNS系统解析目标域名(如www.hisense.com)的IP地址；DNS响应用户终端的请求，执行递归查询或者迭代查询，得到目标域名对应的服务器的IP地址列表；DNS根据终端设备1的IP地址判断终端设备1所在的地理位置，从IP地址列表中查找出距离终端设备1最近的服务器3的IP地址，返回给终端设备1，根据终端设备2的IP地址判断终端设备2所在的地理位置，从IP地址列表中查找出距离终端设备2最近的服务器4的IP地址，返回给终端设备2。
当由于终端设备1和终端设备2所在的地理位置不同而使得DNS服务器返回给终端设备1和终端设备2的IP地址不同，即服务器3与服务器4为不同的服务器时，终端设备1和终端设备2则可能请求到不一致的数据。
另外，当IP地址与地理位置之间的映射关系发生变化时，上述根据用户终端的IP地址判断用户终端所在地理位置的路由方式，也有可能使得终端用户访问到不同的数据中心服务器，进而请求到的数据不一致。
例如，IP地址与地理位置之间的映射关系发生变化前，终端设备1在地区D1的IP地址映射到地区D1，IP地址与地理位置之间的映射关系发生变化后，该IP地址映射到地区D2，此时，服务端将认为用户终端所在的地理位置由地区D1变化为地区D2，因此可能使得该用户终端在映射关系发生变化前后访问到不同地区的数据中心服务器，进而请求到的数据不一致。
为了保证使用同一注册账号的不同设备所请求的数据的一致性，本申请实施例提供一种域名解析方法，该方法在保障用户终端就近访问的同时，能够解决同一用户多地区多设备登录时的数据一致性问题。
图2为本申请根据一些实施例示出的域名解析方法流程图，如图2所示，该方法可以包括：
步骤110，用户终端响应于用户操作生成携带有用户标识的域名查询请求。
域名查询请求包括用户标识、目标域名、客户端的出口IP地址、终端设备标识等信息，其中，用户标识是指登录用户终端上客户端的注册账号或者与注册账号具有关联或者绑定关系的其他账号，如手机号。
步骤120，发送所述域名查询请求至服务端。
步骤130，服务端接收用户终端发送的域名解析请求，该域名解析请求携带有登录所述用户终端上客户端的用户标识。
步骤140，服务端根据域名解析请求携带的用户标识，在历史解析记录中查找是否存在该用户标识对应的在先访问地址，该用户标识对应的在先访问地址为使用该用户标识的用户终端进行在先访问时，服务端根据域名解析请求得到的距离用户终端所在地理位置最近的服务器的IP地址。
其中，为了便于对本申请实施例进行说明，将步骤120中用户终端请求服务端解析目标域名的过程定义为当前访问，将该用户终端或其他用户终端的早于当前访问的访问过程定义为在先访问。
如果查找到该用户标识对应的在先访问地址，则执行步骤150，如果未查找到该用户标识对应的在先访问地址，则执行步骤160。
如果在历史解析记录中查找到该用户标识对应的在先访问地址，则在步骤150中，将所述在先访问地址返回给所述用户终端，以使用户终端根据所述在先访问地址及进行数据访问，以使得使用该用户标识登录的客户端仍旧访问其在先访问的服务器，从而保证同一用户账号在多地区多设备上登录时获 取数据的一致性。
如果在历史解析记录中未查找到该用户标识对应的在先访问地址，则在步骤160中，根据所述域名解析请求确定距离所述用户终端所在的地理位置最近的服务器的IP地址为目标访问地址。并在步骤170中，将确定的所述目标访问地址返回给用户终端，以使用户终端根据所述目标访问地址进行数据访问。
历史解析记录包括若干信息条目，每一信息条目由用户标识和对应的在先访问地址组成，每一信息条目中，用户标识为在先访问的用户终端发送的域名解析请求携带的用户标识，在先访问地址为服务端返回给该用户终端的解析结果，该在先访问地址由服务端根据域名解析请求解析得到，是距离该用户终端所在地理位置最近的服务器的IP地址。
在一些实施例中，用户甲在地区D-1使用注册账号ID-1登录终端设备1(上的客户端U)，终端设备1生成携带有用户标识ID-1的域名解析请求，并发送至服务端，域名解析请求中还包括终端设备1的IP地址和要解析的目标域名。服务端接收到终端设备1发送的域名解析请求，首先在历史解析记录查找是否存在与用户标识ID-1对应的在先访问地址。
在历史解析记录不包括关于用户标识ID-1的信息条目的示例性情况中，，服务端根据终端设备1的IP地址和目标域名解析出距离终端设备最近的服务器1的IP地址IP-1，返回给终端设备1，并将用户标识ID-1和IP-1对应保存在历史解析记录中，如表1所示：
表1
用户标识 在先访问地址 访问时间
ID-1 IP-1 Time1
ID-2 IP-2 Time2
… … …
ID-n IP-n Timen
表1中，访问时间可以是服务端接收到客户端发送的域名解析请求的时间，或者是服务端向客户端返回解析结果的时间，本申请不予限定。
在一些实施例中，用户乙在地区D-2使用注册账号ID-1登录终端设备2(上的客户端U)，终端设备2生成携带有用户标识ID-1的域名解析请求，并发送至服务端，域名解析请求中还包括终端设备2的IP地址和要解析的目标域名。服务端接收到终端设备2发送的域名解析请求，首先在历史解析记录查找是否存在与用户标识ID-1对应的在先访问地址。
在历史解析记录包括关于用户标识ID-1的信息条目的示例性情况中，以上述表1示出的历史解析记录为例，用户标识ID-1对应的在先访问地址为IP-1，于是服务端将该在先访问地址IP-1作为解析结果返回给终端设备2。
从上述实施例可以看出，终端设备1和2使用同一注册账号ID-1先后请求服 务端解析目标域名的IP地址，在先访问的终端设备1根据IP-1就近服务器1以获取所需的数据，在后访问的终端设备2根据IP-1访问到服务器1以获取与终端设备1一致的数据，解决了同一注册账号多地区多设备登录时获取数据的一致性问题。
在一些实施例中，预先获取第一映射关系和第二映射关系。其中，第一映射关系为域名与IP地址间的映射关系，用于根据域名解析请求中的目标域名解析出对应的IP地址，第二映射关系为IP地址与地理位置间的映射关系，用于根据域名解析请求中用户终端的IP地址确定用户终端所在的地理位置；除此之外，第二映射关系还用于根据第一映射关系中服务器的IP地址确定服务器所在的地理位置，进而可以在用户终端所在地理位置和服务器所在地理位置已知的情况下，确定距离用户终端最近的服务器。
基于此，服务端可以按照下述步骤确定距离用户终端最近的服务器的IP地址：首先根据第一映射关系和目标域名获取与目标域名对应的IP地址列表，该IP地址列表包括至少一个目标域名对应的服务器的IP地址；再分别根据第二映射关系、用户终端的IP地址以及IP地址列表中服务器的IP地址，确定用户终端所在的地理位置和IP地址列表中服务器所在的地理位置；最后，根据用户终端的地理位置和IP地址列表中服务器的地理位置，从IP地址列表中选择距离用户终端最近的服务器的IP地址。
在一些实施例中，为了提高本申请域名解析方法的灵活性以更加适应用户需求，当历史解析记录中的在先访问地址的保存时长超过预设时长时，将超过预设时长的在先访问地址及对应的用户标识在历史解析记录中删除。定期检测历史解析记录中信息条目是否过期，并删除过期的信息条目，可以及时追踪到用户常在地理区域的变化，避免用户迁徙后仍旧根据在先访问地址获取数据。
由以上技术方案可知，本申请实施例提供一种域名解析方法、域名访问方法、域名解析服务器以及终端设备，所述域名解析方法在接收到域名解析请求后，根据域名解析请求携带的用户标识，在历史解析记录中查找是否存在对应的在先访问地址，如果查找到该用户标识对应的在先访问地址，则将该在先访问地址返回给用户终端，以使用户终端根据该在先访问地址进行数据访问。由于该用户标识对应的在先访问地址是使用该用户标识的用户终端进行在先访问时，服务端解析出的的距离发起请求的用户终端最近的服务器地址，因此当同一用户标识在多地区多设备上登录时，能够使在后访问的用户终端与在先访问的用户终端访问同一服务器以获取所需的数据，进而，在保障用户终端就近访问的同时，保证具有同一用户标识的各个设备所获取数据的一致性。
在一些实施例中，本申请实施例提供的域名解析方法可以应用于GSLB (Global Server Load Balance，全局负载均衡)集群，并为GSLB集群提供控制终端和redis。利用控制终端的UI面板导入前述第一映射关系数据和第二映射关系数据，并将第一映射关系数据、第二映射关系数据和历史解析记录保存在redis中。
根据图2所示的域名解析方法，本申请实施例还提供一种域名访问方法，应用于客户端，如图3所示，该方法可以包括：
步骤210，生成携带有用户标识的域名查询请求。
域名查询请求还包括客户端的出口IP地址和目标域名。
步骤220，发送所述域名查询请求至服务端。
步骤230，接收所述服务端返回的在先访问地址或者目标访问地址，所述在先访问地址为所述服务端在历史解析记录中查找到的与所述用户标识对应的在先访问地址，所述目标访问地址为所述服务端根据所述域名解析请求确定的距离用户终端最近的服务器的IP地址。
步骤240，根据所述在先访问地址或者目标访问地址进行数据访问。
根据图2所示实施例提供的域名解析方法，本申请实施例还提供一种域名解析服务器，如图4所示，该域名解析服务器可以包括：
接收模块410，用于接收用户终端发送的域名解析请求，所述域名解析请求携带有登录所述用户终端的用户标识；
第一解析模块420，用于根据所述用户标识，在历史解析记录中查找是否存在所述用户标识对应的在先访问地址，所述用户标识对应的在先访问地址为使用所述用户标识的用户终端进行在先访问时，根据域名解析请求得到的距离所述用户终端最近的服务器的IP地址；
发送模块430，用于如果在所述历史解析记录中查找到所述用户标识对应的在先访问地址，则将所述在先访问地址返回给所述用户终端，以使所述用户终端根据所述在先访问地址及进行数据访问。
在一些实施例中，该域名解析服务器还可以包括：第二解析模块，用于如果在所述历史解析记录中未查找到所述用户标识对应的在先访问地址，则根据所述域名解析请求确定距离所述用户终端最近的服务器的IP地址。
在一些实施例中，发送模块还用于将所述距离用户终端最近的服务器的IP地址作为目标访问地址，返回给所述用户终端，以使所述用户终端根据所述目标访问地址进行数据访问。
在一些实施例中，该域名解析服务器还可以包括：记录模块，用于将所述用户标识和所述目标访问地址对应保存在所述历史解析记录中。
在一些实施例中，第二解析模块，具体用于：获取所述目标域名对应的IP 地址列表，所述IP地址列表包括至少一个所述目标域名对应的服务器的IP地址；分别根据所述用户终端的IP地址和所述IP地址列表中服务器的IP地址，确定所述用户终端的地理位置和所述服务器的地理位置；根据所述用户终端的地理位置和所述IP地址列表中服务器的地理位置，从所述IP地址列表中选择距离所述用户终端最近的服务器的IP地址。
在一些实施例中，第二解析模块，具体用于：获取IP地址与地理位置间的映射关系；根据所述用户终端的IP地址，在所述映射关系中查找所述用户终端的地理位置。
在一些实施例中，基于本申请实施例提供的域名解析服务器搭建GSLB集群，并为GSLB集群提供控制终端和redis。利用控制终端的UI面板导入前述第一映射关系数据和第二映射关系数据，并将第一映射关系数据、第二映射关系数据和历史解析记录保存在redis中。
根据图3所示实施例提供的域名访问方法，本申请实施例还提供一种终端设备，该终端设备包括但不限于是显示设备、便携式智能用户设备以及头戴式智能设备等。如图5所示，本申请实施例提供的终端设备包括：
生成模块510，用于生成携带有用户标识的域名查询请求；
发送模块520，用于发送所述域名查询请求至服务端；
接收模块530，用于接收所述服务端返回的在先访问地址或者目标访问地址，所述在先访问地址为所述服务端在历史解析记录中查找到的与所述用户标识对应的在先访问地址，所述目标访问地址为所述服务端根据所述域名解析请求确定的距离用户终端最近的服务器的IP地址；
访问模块540，用于根据所述在先访问地址或者目标访问地址进行数据访问。
具体实现中，本申请还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时可包括本申请提供的域名解析方法或者域名访问方法的各实施例中的部分或全部步骤，当本申请提供的域名解析服务器或者终端设备的处理器运行所述计算机程序指令时，所述处理器执行本申请所述的域名解析方法或者域名访问方法的步骤。所述的存储介质可为磁碟、光盘、只读存储记忆体(英文：read-only memory，简称：ROM)或随机存储记忆体(英文：random access memory，简称：RAM)等。
本领域的技术人员可以清楚地了解到本申请实施例中的技术可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本申请实施例中的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器， 或者网络设备等)执行本申请各个实施例或者实施例的某些部分所述的方法。
本说明书中各个实施例之间相同相似的部分互相参见即可。尤其，对于域名解析服务器及终端设备实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例中的说明即可。
以上所述的本申请实施方式并不构成对本申请保护范围的限定。

Claims (10)

  1. 一种域名解析方法，其特征在于，包括：
    接收用户终端发送的域名解析请求，所述域名解析请求携带有登录所述用户终端的用户标识；
    根据所述用户标识，在历史解析记录中查找是否存在所述用户标识对应的在先访问地址，所述用户标识对应的在先访问地址为使用所述用户标识的用户终端进行在先访问时，根据域名解析请求得到的距离所述用户终端最近的服务器的IP地址；
    如果在所述历史解析记录中查找到所述用户标识对应的在先访问地址，则将所述在先访问地址返回给所述用户终端，以使所述用户终端根据所述在先访问地址及进行数据访问。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    如果在所述历史解析记录中未查找到所述用户标识对应的在先访问地址，则根据所述域名解析请求确定距离所述用户终端最近的服务器的IP地址；
    将所述距离用户终端最近的服务器的IP地址作为目标访问地址，返回给所述用户终端，以使所述用户终端根据所述目标访问地址进行数据访问。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    将所述用户标识和所述目标访问地址对应保存在所述历史解析记录中。
  4. 根据权利要求2所述的方法，其特征在于，所述域名解析请求包括所述用户终端的IP地址和目标域名，所述根据域名解析请求确定距离所述用户终端最近的服务器的IP地址，包括：
    获取所述目标域名对应的IP地址列表，所述IP地址列表包括至少一个所述目标域名对应的服务器的IP地址；
    分别根据所述用户终端的IP地址和所述IP地址列表中服务器的IP地址，确定所述用户终端的地理位置和所述服务器的地理位置；
    根据所述用户终端的地理位置和所述IP地址列表中服务器的地理位置，从所述IP地址列表中选择距离所述用户终端最近的服务器的IP地址。
  5. 根据权利要求4所述的方法，其特征在于，所述根据用户终端的IP地址确定所述用户终端的地理位置，包括：
    获取IP地址与地理位置间的映射关系；
    根据所述用户终端的IP地址，在所述映射关系中查找所述用户终端的地理位置。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述历史解析记录中所述在先访问地址的保存时长超过预设时长时， 将所述在先访问地址及对应的用户标识在所述历史解析记录中删除。
  7. 一种域名访问方法，其特征在于，所述方法包括：
    生成携带有用户标识的域名查询请求；
    发送所述域名查询请求至服务端；
    接收所述服务端返回的在先访问地址或者目标访问地址，所述在先访问地址为所述服务端在历史解析记录中查找到的与所述用户标识对应的在先访问地址，所述目标访问地址为所述服务端根据所述域名解析请求确定的距离用户终端最近的服务器的IP地址；
    根据所述在先访问地址或者目标访问地址进行数据访问。
  8. 根据权利要求7所述的方法，其特征在于，所述域名解析请求包括所述用户终端的IP地址和目标域名，所述服务端根据所述域名解析请求确定距离所述用户终端最近的服务器的IP地址，包括：
    获取所述目标域名对应的IP地址列表，所述IP地址列表包括至少一个所述目标域名对应的服务器的IP地址；
    分别根据所述用户终端的IP地址和所述IP地址列表中服务器的IP地址，确定所述用户终端的地理位置和所述服务器的地理位置；
    根据所述用户终端的地理位置和所述IP地址列表中服务器的地理位置，从所述IP地址列表中选择距离所述用户终端最近的服务器的IP地址。
  9. 一种域名解析服务器，其特征在于，包括：
    接收模块，用于接收用户终端发送的域名解析请求，所述域名解析请求携带有登录所述用户终端的用户标识；
    第一解析模块，用于根据所述用户标识，在历史解析记录中查找是否存在所述用户标识对应的在先访问地址，所述用户标识对应的在先访问地址为使用所述用户标识的用户终端进行在先访问时，根据域名解析请求得到的距离所述用户终端最近的服务器的IP地址；
    发送模块，用于如果在所述历史解析记录中查找到所述用户标识对应的在先访问地址，则将所述在先访问地址返回给所述用户终端，以使所述用户终端根据所述在先访问地址及进行数据访问。
  10. 一种终端设备，其特征在于，包括：
    生成模块，用于生成携带有用户标识的域名查询请求；
    发送模块，用于发送所述域名查询请求至服务端；
    接收模块，用于接收所述服务端返回的在先访问地址或者目标访问地址，所述在先访问地址为所述服务端在历史解析记录中查找到的与所述用户标识对应的在先访问地址，所述目标访问地址为所述服务端根据所述域名解析请求确定的距离用户终端最近的服务器的IP地址；
    访问模块，用于根据所述在先访问地址或者目标访问地址进行数据访问。
PCT/CN2020/129871 2020-02-21 2020-11-18 域名解析方法、域名解析服务器及终端设备 WO2021120969A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010108777.5A CN111314472B (zh) 2020-02-21 2020-02-21 域名解析方法、域名解析服务器及终端设备
CN202010108777.5 2020-02-21

Publications (1)

Publication Number Publication Date
WO2021120969A1 true WO2021120969A1 (zh) 2021-06-24

Family

ID=71147333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/129871 WO2021120969A1 (zh) 2020-02-21 2020-11-18 域名解析方法、域名解析服务器及终端设备

Country Status (2)

Country Link
CN (1) CN111314472B (zh)
WO (1) WO2021120969A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113472469A (zh) * 2021-07-27 2021-10-01 厦门亿联网络技术股份有限公司 一种数据同步方法、装置、设备及存储介质
CN113971181A (zh) * 2021-11-04 2022-01-25 京东科技信息技术有限公司 基于异地多活系统的数据同步方法及装置
CN114095567A (zh) * 2021-10-12 2022-02-25 鸬鹚科技(深圳)有限公司 数据访问请求的处理方法、装置、计算机设备及介质
CN114221933A (zh) * 2021-11-11 2022-03-22 中国建设银行股份有限公司 手机银行多中心多活的寻址方法、装置及系统
CN114285821A (zh) * 2021-11-17 2022-04-05 奇安信科技集团股份有限公司 一种域名解析方法、装置、电子设备、存储介质及产品
CN114785465A (zh) * 2022-04-26 2022-07-22 上海识装信息科技有限公司 一种异地多活的实现方法、服务器及存储介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111314472B (zh) * 2020-02-21 2022-03-11 聚好看科技股份有限公司 域名解析方法、域名解析服务器及终端设备
CN112087484B (zh) * 2020-07-28 2023-08-11 深圳拓邦股份有限公司 快速定位具体服务器的方法及系统
CN111953811B (zh) * 2020-08-07 2024-02-06 腾讯科技（深圳）有限公司 站点访问方法、站点注册方法、装置、设备及存储介质
CN112689027A (zh) * 2020-12-11 2021-04-20 北京北信源软件股份有限公司 App用户访问动态地址服务器的寻址方法及装置
CN113364873A (zh) * 2021-06-08 2021-09-07 中国联合网络通信集团有限公司 流量调度方法及设备
CN114039799B (zh) * 2021-12-10 2023-11-17 国网福建省电力有限公司 一种网络安全防护系统及方法
CN114363902A (zh) * 2022-01-05 2022-04-15 中国联合网络通信集团有限公司 5g专网业务安全保障方法、装置、设备及存储介质
CN115277566B (zh) * 2022-05-20 2024-03-22 鸬鹚科技(深圳)有限公司 数据访问的负载均衡方法、装置、计算机设备及介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160241508A1 (en) * 2013-08-26 2016-08-18 Jeong Hoan Seo Domain name system (dns) and domain name service method based on user information
CN106657132A (zh) * 2017-01-09 2017-05-10 北京小米移动软件有限公司 访问网站的方法和装置
CN108600412A (zh) * 2018-05-03 2018-09-28 深圳市茁壮网络股份有限公司 一种域名解析方法及系统
CN108881939A (zh) * 2018-07-05 2018-11-23 北京奇艺世纪科技有限公司 一种视频cdn处理方法及系统
CN110740191A (zh) * 2019-10-29 2020-01-31 成都超有爱科技有限公司 资源访问方法、装置、电子设备及存储介质
CN111314472A (zh) * 2020-02-21 2020-06-19 聚好看科技股份有限公司 域名解析方法、域名解析服务器及终端设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4375740B2 (ja) * 2004-10-08 2009-12-02 日本電信電話株式会社 ゲートウェイ装置および通信接続方法
US9723463B2 (en) * 2010-10-25 2017-08-01 Nokia Technologies Oy Method and apparatus for a device identifier based solution for user identification
US8990356B2 (en) * 2011-10-03 2015-03-24 Verisign, Inc. Adaptive name resolution
CN104519146A (zh) * 2013-09-29 2015-04-15 中国电信股份有限公司 基于用户位置进行域名解析服务的方法与系统
CN104301758A (zh) * 2014-10-10 2015-01-21 安徽华米信息科技有限公司 一种推送视频的方法、装置及系统
CN106161669A (zh) * 2015-04-28 2016-11-23 阿里巴巴集团控股有限公司 一种快速域名解析方法和系统、及其终端和服务器
CN106547800A (zh) * 2015-09-23 2017-03-29 北京国双科技有限公司 跨设备同步用户行为的方法及装置
CN109819066A (zh) * 2019-01-31 2019-05-28 平安科技（深圳）有限公司 一种基于地理位置的智能解析域名方法及装置
CN110674098B (zh) * 2019-09-19 2022-04-22 浪潮电子信息产业股份有限公司 一种分布式文件系统中的域名解析方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160241508A1 (en) * 2013-08-26 2016-08-18 Jeong Hoan Seo Domain name system (dns) and domain name service method based on user information
CN106657132A (zh) * 2017-01-09 2017-05-10 北京小米移动软件有限公司 访问网站的方法和装置
CN108600412A (zh) * 2018-05-03 2018-09-28 深圳市茁壮网络股份有限公司 一种域名解析方法及系统
CN108881939A (zh) * 2018-07-05 2018-11-23 北京奇艺世纪科技有限公司 一种视频cdn处理方法及系统
CN110740191A (zh) * 2019-10-29 2020-01-31 成都超有爱科技有限公司 资源访问方法、装置、电子设备及存储介质
CN111314472A (zh) * 2020-02-21 2020-06-19 聚好看科技股份有限公司 域名解析方法、域名解析服务器及终端设备

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113472469A (zh) * 2021-07-27 2021-10-01 厦门亿联网络技术股份有限公司 一种数据同步方法、装置、设备及存储介质
CN113472469B (zh) * 2021-07-27 2023-12-05 厦门亿联网络技术股份有限公司 一种数据同步方法、装置、设备及存储介质
CN114095567A (zh) * 2021-10-12 2022-02-25 鸬鹚科技(深圳)有限公司 数据访问请求的处理方法、装置、计算机设备及介质
CN114095567B (zh) * 2021-10-12 2023-12-29 鸬鹚科技(深圳)有限公司 数据访问请求的处理方法、装置、计算机设备及介质
CN113971181A (zh) * 2021-11-04 2022-01-25 京东科技信息技术有限公司 基于异地多活系统的数据同步方法及装置
CN114221933A (zh) * 2021-11-11 2022-03-22 中国建设银行股份有限公司 手机银行多中心多活的寻址方法、装置及系统
CN114221933B (zh) * 2021-11-11 2024-04-26 中国建设银行股份有限公司 手机银行多中心多活的寻址方法、装置及系统
CN114285821A (zh) * 2021-11-17 2022-04-05 奇安信科技集团股份有限公司 一种域名解析方法、装置、电子设备、存储介质及产品
CN114785465A (zh) * 2022-04-26 2022-07-22 上海识装信息科技有限公司 一种异地多活的实现方法、服务器及存储介质
CN114785465B (zh) * 2022-04-26 2024-04-12 上海识装信息科技有限公司 一种异地多活的实现方法、服务器及存储介质

Also Published As

Publication number Publication date
CN111314472B (zh) 2022-03-11
CN111314472A (zh) 2020-06-19

Similar Documents

Publication Publication Date Title
WO2021120969A1 (zh) 域名解析方法、域名解析服务器及终端设备
US10374955B2 (en) Managing network computing components utilizing request routing
US11811657B2 (en) Updating routing information based on client location
US10735267B2 (en) Determining an application delivery server based on geo-location information
US11632353B2 (en) Delegating DNS records to additional providers
US9800539B2 (en) Request routing management based on network components
US9444759B2 (en) Service provider registration by a content broker
US7707289B1 (en) Method and system for enabling persistent access to virtual servers by an LDNS server
JP5150769B2 (ja) 要求ルーティングおよびクライアントロケーション情報を利用したルーティング情報の更新
JP5974079B2 (ja) 変更ホストネームを使用するグローバル・トラフィック管理
US20070094361A1 (en) Multipath routing process
CN105959433A (zh) 一种域名解析方法及其域名解析系统
CN103780654A (zh) 业务请求处理方法、用户终端、业务路由器及网络系统
CN114205330B (zh) 域名解析方法、域名解析装置、服务器以及存储介质
JP2019506692A (ja) データを処理する方法、装置、及びコンピュータプログラム、並びに階層ドメインネームシステムのゾーンファイル
US20120191769A1 (en) Site-aware distributed file system access from outside enterprise network
WO2017096888A1 (zh) 域名解析系统的实现方法及装置
CN111447297A (zh) IPv4、IPv6的DNS统一接入的管理方法及系统
WO2016074148A1 (en) Method and system for domain name load balancing
CN118200286A (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: 20903675

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 1205 DATED 09/01/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20903675

Country of ref document: EP

Kind code of ref document: A1