WO2013104172A1 - Procédé de réalisation d'équilibrage de charge, serveur dns et client - Google Patents

Procédé de réalisation d'équilibrage de charge, serveur dns et client Download PDF

Info

Publication number
WO2013104172A1
WO2013104172A1 PCT/CN2012/076812 CN2012076812W WO2013104172A1 WO 2013104172 A1 WO2013104172 A1 WO 2013104172A1 CN 2012076812 W CN2012076812 W CN 2012076812W WO 2013104172 A1 WO2013104172 A1 WO 2013104172A1
Authority
WO
WIPO (PCT)
Prior art keywords
load
application servers
address
dns
client
Prior art date
Application number
PCT/CN2012/076812
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 华为技术有限公司
Publication of WO2013104172A1 publication Critical patent/WO2013104172A1/fr

Links

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/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • 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]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method for implementing load balancing, a DNS server, and a client. Background technique
  • DNS Domain Name Resolution System
  • Load balancing technology is the earliest load balancing solution.
  • the DNS server configures multiple different IP addresses for the same domain name address. Therefore, when the client accesses the domain name address, it can obtain DNS.
  • the IP address list configured by the server according to the domain name address, and different clients can access different application servers according to different IP addresses in the IP address list, so as to achieve load balancing of accessing the application server.
  • DNS load balancing is a simple and effective way to implement load balancing.
  • the shortcoming of this solution is that it cannot distinguish the difference of application servers corresponding to different IP addresses, and does not consider the load capacity of these application servers.
  • the single application accesses different application servers according to different IP addresses, and the client does not implement balanced access to the application server according to the load of the application server, so it is not a true load balancing.
  • Embodiments of the present invention provide a method for implementing load balancing, a DNS server, and a client, which enable a client to balance access to an application server according to load conditions of an application server.
  • An embodiment of the present invention provides a method for implementing load balancing, including: receiving a client to send DNS request, the DNS request includes a domain name address; searching for a load and an IP address of the plurality of application servers corresponding to the domain name address; sending a DNS response to the client, where the DNS response includes the plurality of application servers And a load and an IP address, so that the client determines the accessed IP address according to the load of the multiple application servers.
  • Another embodiment of the present invention provides a method for implementing load balancing, including: sending a DNS request to a DNS server, where the DNS request includes a domain name address; receiving a DNS response sent by the DNS server, where the DNS response includes Determining the load and IP address of the plurality of application servers corresponding to the domain name address; determining the accessed IP address according to the load of the plurality of application servers.
  • An embodiment of the present invention provides a DNS server, including: a receiving unit, configured to receive a DNS request sent by a client, where the DNS request includes a domain name address, and a searching unit, configured to search for a DNS request received by the receiving unit a load and an IP address of the plurality of application servers corresponding to the domain name address; a sending unit, configured to send a DNS response to the client, where the DNS response includes a load and an IP address of the plurality of application servers found by the searching unit So that the client determines the accessed IP address according to the load of the multiple application servers.
  • An embodiment of the present invention provides a client, including: a sending unit, configured to send a DNS request to a DNS server, where the DNS request includes a domain name address, and a receiving unit, configured to receive, sent by the DNS server
  • the DNS response includes the load and the IP address of the plurality of servers corresponding to the domain name address
  • the access unit configured to determine the accessed IP address according to the load of the plurality of application servers.
  • the DNS server searches for the IP addresses of the corresponding multiple application servers according to the domain name address in the DNS request. And the load, so that the client can determine the appropriate application server as the access object according to the load condition of multiple application servers, and achieve the purpose of multiple clients to access multiple application servers in a balanced manner.
  • FIG. 1 is a flowchart of a method for implementing load balancing according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for implementing load balancing according to another embodiment of the present invention.
  • FIG. 3 is a signaling flowchart of a method for implementing load balancing according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a format of a DNS query packet according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a format of an extended DNS response packet according to an embodiment of the present invention.
  • FIG. 6 is a structural diagram of a DNS server according to an embodiment of the present invention.
  • FIG. 7 is a structural diagram of a client according to an embodiment of the present invention. detailed description
  • FIG. 1 is a flowchart of a method for implementing load balancing according to an embodiment of the present invention.
  • the embodiment includes:
  • the DNS server receives the DNS request sent by the client, where the DNS request carries the domain name address accessed by the client; wherein the DNS server is mainly used to resolve the domain name address accessed by the client, and convert the domain name address into a corresponding IP address. .
  • the DNS server Before receiving the DNS request sent by the client, the DNS server obtains the load of the multiple application servers corresponding to the domain name address, and the specific information includes: the DNS server sends a load request to the multiple application servers, and receives the load sent by the multiple application servers. a load response, the load response includes a load of the multiple application servers, and further, the load response may further include a status of the multiple application servers, including available or unavailable; alternatively, the DNS server receives the multiple application server active Reported load message, The load message includes the load of the multiple application servers. Further, the status of the multiple application servers may be included, including available or unavailable. Further, the multiple application servers may periodically report their own load messages.
  • the DNS server After receiving the DNS request sent by the client, the DNS server obtains the domain name address carried in the client, and searches for the IP address of the corresponding multiple application server and the plurality of application months according to the domain name address. Load of the device.
  • the application server includes a web server, a mail server, an FTP (File Transfer Protocol) server, etc.
  • the load of the application server reflects the carrying capacity of the application server, and the load is larger, indicating that the application server can still accept The less access, the smaller the load, indicating the more access the application server can accept.
  • the DNS server sends a DNS response message to the client, where the DNS response message carries the load and IP address of the plurality of application servers that are found, so that the client determines the accessed IP address according to the load of the multiple application servers. .
  • the DNS server searches for the load and IP address of the corresponding multiple servers according to the domain name address in the DNS request, so that the client can be based on multiple application servers.
  • the load situation determines the appropriate application server as the access object, and achieves the purpose of balanced access of multiple clients to multiple application servers.
  • FIG. 2 is a flowchart of a method for implementing load balancing according to another embodiment of the present invention.
  • the embodiment includes:
  • the client sends a DNS request to the DNS server, where the DNS request carries the domain name address requested by the client.
  • the client receives the DNS response sent by the DNS server, where the DNS response includes the load and the IP address of the multiple application servers corresponding to the domain name address, where the load and the IP address of the multiple application servers are determined by the DNS server.
  • the above domain name address lookup is obtained.
  • the client determines the accessed IP address according to the load of the multiple application servers, and accesses the related resource according to the IP address.
  • the client determines an IP address corresponding to the least loaded application server among the plurality of application servers as the accessed IP address.
  • the foregoing DNS response may further include a status of multiple application servers, including available or unavailable.
  • the client may determine the accessed IP address according to the load and status of multiple application servers, for example, the status is available.
  • the IP address corresponding to the application server with the lightest load is determined as the accessed IP address.
  • the DNS server searches for the load and IP address of the corresponding multiple servers according to the domain name address in the DNS request, so that the client can be based on multiple application servers.
  • the load situation determines the appropriate application server as the access object, and achieves the purpose of multiple clients to balance access to multiple application servers.
  • FIG. 3 illustrates a signaling flow of a method for implementing load balancing according to an embodiment of the present invention.
  • a DNS server interacts with multiple application servers, and an application server is marked in FIG. It cannot be understood as a limitation on the interaction of the DNS server with multiple application servers, so the application server in this embodiment can be understood as a plurality of application servers.
  • This embodiment includes:
  • the DNS server obtains the load of the application server. Specifically, the DNS server sends a load request to the application server.
  • the load request may be a User Datagram Protoco l (UDP) message, and the request application server is carried in the UDP message.
  • UDP User Datagram Protoco l
  • Load information For example, the structure of the UDP request message is defined as follows:
  • the data Data part includes: Field name type long description
  • the UDP request message may further include information requesting the status of the application server, where Mes sageType indicates that the UDP message is used to request the load and status of the application server. .
  • the application server After receiving the load request sent by the DNS server, the application server returns a load response to the DNS server.
  • the load response may be a UDP response message, where the UDP response message includes a load of the application server; further, when in S 31 When the UDP request message further includes status information requesting the application server, the UDP response message further includes the status of the application server, and the status includes available or unavailable.
  • the DNS server After obtaining the load response sent by the application server, the DNS server saves the correspondence between the IP address of the application server and its load according to the load of the application server carried in the load response. Further, if the load response further carries the application server The state also stores the correspondence between the IP address of the application server and its state.
  • the DNS server can obtain the load of the application server without using the S 31 and the S 32.
  • the application server actively sends its own load message to the DNS server, so that the DNS server obtains the load of the application server.
  • the application server may periodically send its own load message to the DNS server; wherein the load message includes a load of the application server, and further, the load message may further include a status of the application server, including available or unavailable.
  • the DNS server After obtaining the foregoing load message sent by the application server, the DNS server saves the correspondence between the IP address of the application server and its load according to the load of the application server carried in the load message; further, if the load response further carries the The state of the application server also stores the correspondence between the IP address of the application server and its state.
  • the client sends a DNS request to the DNS server, where the DNS request carries the domain name address requested by the client.
  • the DNS request uses a standard DNS query message format, as shown in FIG. 4 .
  • the problem 401 indicates the content of the DNS query message request query, which is composed of the domain name 402, the type 403, and the class 404.
  • the domain name 402 is the domain name address requested by the client, and the type 403 indicates the type of the DNS file request query, such as the domain name.
  • Querying an IP address or querying a domain name by an IP address, class 404 is typically 1 for Internet data.
  • the DNS server After receiving the DNS request sent by the client, the DNS server searches for the load and IP address of the corresponding multiple application servers according to the domain name address carried in the request.
  • the DNS server searches for the IP addresses of the corresponding multiple application servers according to the domain name address in the DNS request.
  • the IP address is saved in the DNS server The correspondence between the address and the load of the corresponding application server, so the DNS server can find the load and IP address of the corresponding multiple application servers according to the domain name address.
  • the DNS server can also store the correspondence between the IP address and the state of the corresponding application server, so the DNS server can also find the status of multiple application servers corresponding to the domain name address, and the DNS server is required to obtain more When the load of the application server is obtained, the status of the multiple application servers is acquired at the same time.
  • the DNS server After finding the load and IP address of the multiple application servers corresponding to the domain name address, the DNS server sends a DNS response to the client, where the DNS response includes the load and IP address of the multiple application servers.
  • the DNS response uses an extended DNS response message format, as shown in FIG. 5.
  • the answer 501 represents the content of the response of the DNS response message.
  • the answer 501 is composed of a pointer 502, a type 503, a class 504, a TTL 505, a length 506, and an IP address 507, wherein the pointer 502 indicates the domain name address requested by the client; type 503 is the same as type 403 in the DNS query message of FIG. 4; class 504 is usually 1 for Internet data; TTL 505 indicates lifetime of DNS response message; length 506 indicates resource data ( For example, the length of the IP address); the IP address 507 indicates the IP address corresponding to the domain name address requested by the client.
  • the extended field of the "answer" part of the extended DNS response message of the present invention includes a load 508, and may further include a state 509, where the load 508 refers to the load condition of the application server corresponding to the IP address, which may be reflected by a specific value.
  • the size of the load; Status 509 refers to the status of the application server corresponding to the IP address, including available or unavailable.
  • the client After obtaining the DNS response sent by the DNS server, the client determines the accessed IP address according to the load of the plurality of application servers carried in the DNS response, and initiates an access request to the determined IP address to obtain the corresponding resource. .
  • the client selects an IP address corresponding to the lightest load application server of the multiple application servers to initiate an access request.
  • the DNS response further includes the status of the multiple application servers, the client selects the available application as the available state. The application server with the lightest load in the server initiates access to obtain the resources of the application server.
  • the client accesses the appropriate application server according to the load condition of the application server, which can effectively prevent the load-bearing application server from continuing to accept access, and the lightly loaded application server is not accessed, thereby realizing reasonable access to the application.
  • the server balances the access load of multiple application servers.
  • the DNS server searches for the load and IP address of the corresponding multiple servers according to the domain name address in the DNS request, so that the client can be based on multiple application servers.
  • the load situation determines the appropriate application server as the access object, and achieves the purpose of multiple clients to balance access to multiple application servers.
  • FIG. 6 illustrates a structure of a DNS server according to an embodiment of the present invention, including: a receiving unit 608, configured to receive a DNS request sent by a client, where the DNS request includes a domain name address requested by the client.
  • the searching unit 609 is configured to find a load and an IP address of the corresponding multiple application servers according to the domain name address in the DNS request received by the receiving unit 608.
  • the sending unit 610 is configured to send a DNS response to the client, where the DNS response includes a load and an IP address of the plurality of application servers that are searched by the searching unit 609, so that the client determines the access according to the load of the multiple application servers. IP address.
  • the obtaining unit 611 is configured to obtain the load of the multiple application servers before receiving the DNS request sent by the client, and save the correspondence between the load and the IP address of the multiple application servers. Therefore, the search unit 609 searches for the load of the plurality of application servers corresponding to the domain name address according to the domain name address received by the receiving unit 608 and the load of the application server acquired by the obtaining unit 611.
  • the obtaining unit 611 may obtain a load condition of the multiple application servers by sending a load request to the multiple application servers, and then receiving a load response sent by the multiple application servers, where the process is related to S31 and S32 in FIG. The steps are the same. For details, see S 31 and S 32, which are not mentioned here.
  • the obtaining unit 611 may obtain the load of the multiple application servers by directly receiving the load message reported by the multiple application servers, and the multiple application servers are required to actively send their own load information to the DNS server. Further, the obtaining unit 611 can receive the load message sent by the application server at a certain time, that is, periodically send the load message to the DNS server. The process is the same as the step S311 in FIG. 3, which can be specifically referred to in S311. Narration.
  • FIG. 6 further illustrates the structure of a DNS server provided by an embodiment of the present invention.
  • the DNS server may include at least one processor 601, at least one network interface 604, a memory 605, and at least one communication bus 602. To achieve connection communication between these components.
  • the DNS server can also include a user interface 603 for enabling interaction with the user.
  • the memory 605 can include an operating system 606 for processing various underlying system services and performing hardware-based tasks.
  • the application unit 607 is configured to: according to the DNS request sent by the client, return a DNS response that carries the load and the IP address of the multiple application servers to the client. Specifically, the application unit 607 includes:
  • the receiving unit 608 is configured to receive a DNS request sent by the client, where the DNS request includes a domain name address requested by the client.
  • the searching unit 609 is configured to find a load and an IP address of the corresponding multiple application servers according to the domain name address in the DNS request received by the receiving unit 608.
  • the sending unit 610 is configured to send a DNS response to the client, where the DNS response includes a load and an IP address of the plurality of application servers that are searched by the searching unit 609, so that the client determines the access according to the load of the multiple application servers. IP address.
  • the obtaining unit 611 is configured to obtain, before the receiving unit 608 receives the DNS request sent by the client, The load of the plurality of application servers, and the correspondence between the load and the IP address of the plurality of application servers is saved. Therefore, the search unit 609 searches for the load of the plurality of application servers corresponding to the domain name address according to the domain name address received by the receiving unit 608 and the load of the application server acquired by the obtaining unit 611.
  • the obtaining unit 611 may obtain a load condition of the multiple application servers by sending a load request to the multiple application servers, and then receiving a load response sent by the multiple application servers, where the process is related to S31 and S32 in FIG. The steps are the same. For details, see S 31 and S 32, which are not mentioned here.
  • the obtaining unit 611 may obtain the load of the multiple application servers by directly receiving the load message reported by the multiple application servers, and the multiple application servers are required to actively send their own load information to the DNS server. Further, the obtaining unit 611 can receive the load message sent by the application server at a certain time, that is, periodically send the load message to the DNS server. The process is the same as the step S311 in FIG. 3, which can be specifically referred to in S311. Narration.
  • the foregoing DNS server performs the related method in the embodiment shown in FIG. 1 or FIG. 3.
  • the specific workflow is not described here.
  • the DNS server searches for the load and IP address of the corresponding multiple servers according to the domain name address in the DNS request, so that the client can be based on multiple application servers.
  • the load situation determines the appropriate application server as the access object, and achieves the purpose of balanced access of multiple clients to multiple application servers.
  • Figure 7 illustrates a client provided by an embodiment of the present invention.
  • the embodiment includes:
  • the sending unit 708 is configured to send a DNS request to the DNS server, where the DNS request includes a domain name address, that is, a domain name address requested by the client.
  • the receiving unit 709 is configured to receive a DNS response returned by the DNS server, where the DNS response includes a load and an IP address of multiple application servers corresponding to the domain name address. Further, the DNS response can also include the status of multiple application servers, including available or unavailable. Specifically, the DNS response received by the receiving unit 709 is the same as the DNS response in S35 in FIG. 3, and is not mentioned here.
  • the access unit 710 is configured to determine an accessed IP address according to the load of the multiple application servers received by the receiving unit 709, thereby accessing the corresponding application server. Preferably, the access unit 710 may initiate an access request to an IP address of the least loaded application server among the plurality of application servers, and then obtain an access request. Use the resources of the server. Optionally, if the DNS response received by the receiving unit 709 further includes the status of multiple application servers, the access unit 710 may initiate an access request to the IP address of the application server with the lightest load among the available application servers.
  • FIG. 7 further illustrates a structure of a client-loaded device according to an embodiment of the present invention.
  • the device may include at least one processor 701, at least one network interface 704, a memory 705, and at least one communication bus 702.
  • the communication bus 702 is used to implement connection communication between these components.
  • the device can also include a user interface 703 for enabling interaction with the user.
  • Memory 705 can include:
  • the operating system 706 is configured to process various basic system services and perform hardware-based tasks.
  • the client 707 is configured to determine an accessed IP address according to the load of the multiple application servers in the DNS response sent by the received DNS server. Specifically, the client 707 includes:
  • the sending unit 708 is configured to send a DNS request to the DNS server, where the DNS request includes a domain name address, that is, a domain name address requested by the client.
  • the receiving unit 709 is configured to receive a DNS response returned by the DNS server, where the DNS response includes a load and an IP address of multiple application servers corresponding to the domain name address. Further, the DNS response can also include the status of multiple application servers, including available or unavailable. Specifically, the DNS response received by the receiving unit 709 is the same as the DNS response in S35 in FIG. 3, and is not mentioned here.
  • the access unit 710 is configured to determine an accessed IP address according to the load of the multiple application servers received by the receiving unit 709, thereby accessing the corresponding application server. Preferably, the access unit 710 can initiate an access request to the IP address of the lightest loaded application server among the plurality of application servers, thereby acquiring resources of the application server. Optionally, if the DNS response received by the receiving unit 709 further includes the status of the multiple application servers, the access unit 710 may initiate an access request to the IP address of the application server with the lightest load among the available application servers.
  • the above-mentioned client performs the related method of the embodiment shown in FIG. 2 or FIG. 3, and the specific workflow is not described here.
  • the DNS server searches for the load and IP address of the corresponding multiple servers according to the domain name address in the DNS request, so that the client can be based on multiple application servers.
  • the load situation determines the appropriate application server as the access object, Achieve multiple clients to achieve balanced access to multiple application servers.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (RAM: Read-Only Memory), or a random access memory (RAM: Random Acces s Memory).
  • RAM Read-Only Memory
  • RAM Random Acces s Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne le domaine technique des communications et concerne particulièrement un procédé de réalisation d'équilibrage de charge, un serveur DSN et un client. Selon l'invention, le procédé de réalisation d'équilibrage de charge fait appel : à la réception d'une requête DNS envoyée par un client, la requête DNS comprenant une adresse de nom de domaine; à la recherche de charges et d'adresses IP de plusieurs serveurs d'applications correspondant à l'adresse de nom de domaine; et à l'envoi d'une réponse DNS à un client, la réponse DNS comprenant les charges et les adresses IP des plusieurs serveurs d'applications, de sorte que le client peut déterminer une adresse IP devant faire l'objet d'un accès en fonction des charges des plusieurs serveurs d'applications. Grâce à la présente invention, le client peut accéder à un serveur d'applications moins chargé en fonction des états de charge de plusieurs serveurs d'applications, de façon à atteindre l'objectif d'accès équilibrés à plusieurs serveurs d'applications par plusieurs clients.
PCT/CN2012/076812 2012-01-13 2012-06-13 Procédé de réalisation d'équilibrage de charge, serveur dns et client WO2013104172A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210011400.3 2012-01-13
CN2012100114003A CN102457440A (zh) 2012-01-13 2012-01-13 实现负载均衡的方法、dns服务器和客户端

Publications (1)

Publication Number Publication Date
WO2013104172A1 true WO2013104172A1 (fr) 2013-07-18

Family

ID=46040125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/076812 WO2013104172A1 (fr) 2012-01-13 2012-06-13 Procédé de réalisation d'équilibrage de charge, serveur dns et client

Country Status (2)

Country Link
CN (1) CN102457440A (fr)
WO (1) WO2013104172A1 (fr)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102457440A (zh) * 2012-01-13 2012-05-16 华为软件技术有限公司 实现负载均衡的方法、dns服务器和客户端
CN103491123A (zh) * 2012-06-14 2014-01-01 中国移动通信集团贵州有限公司 一种基于域名访问的负载均衡方法、系统及负载均衡器
CN102970391B (zh) * 2012-12-07 2016-09-28 华为技术有限公司 域名查询处理方法、服务器及系统
CN104144227B (zh) * 2013-05-10 2017-11-21 中国电信股份有限公司 Ip地址查询方法、系统与全网资源控制器
CN103237089A (zh) * 2013-05-16 2013-08-07 广东睿江科技有限公司 基于dns轮询方式网页的修复方法、装置和服务器
CN103905531A (zh) * 2014-03-14 2014-07-02 浪潮电子信息产业股份有限公司 一种集群存储系统中转换节点间负载均衡方法
CN104954401B (zh) * 2014-03-27 2018-06-08 阿里巴巴集团控股有限公司 流量调度方法和装置
CN103916332B (zh) * 2014-04-01 2017-02-08 珠海市君天电子科技有限公司 一种分配网络资源的方法及服务器
CN106936938B (zh) * 2015-12-29 2021-01-26 北界创想（北京）软件有限公司 域名解析方法及系统
CN107018159B (zh) * 2016-01-27 2020-09-11 五八同城信息技术有限公司 业务请求处理方法及装置、和业务请求方法及装置
CN107231446A (zh) * 2016-03-23 2017-10-03 北京京东尚科信息技术有限公司 同步ip配置方法和装置
CN105847462A (zh) * 2016-03-31 2016-08-10 乐视控股（北京）有限公司 域名解析方法及装置
CN107454209B (zh) * 2017-09-11 2020-05-19 深圳市茁壮网络股份有限公司 一种域名解析方法及装置
CN108040085A (zh) * 2017-11-20 2018-05-15 广州华多网络科技有限公司 网络接入方法、装置及服务器
CN111788809A (zh) * 2018-11-23 2020-10-16 华为技术有限公司 一种报文收发方法及装置
CN111696657A (zh) * 2019-03-12 2020-09-22 深圳迈瑞生物医疗电子股份有限公司 中间服务器、医疗监护设备及其连接方法和存储介质
CN111147556A (zh) * 2019-12-15 2020-05-12 浪潮电子信息产业股份有限公司 一种负载均衡方法、装置、设备及存储介质
CN111556126B (zh) * 2020-04-24 2023-04-18 杭州浮云网络科技有限公司 模型管理方法、系统、计算机设备和存储介质
CN112543150B (zh) * 2020-10-29 2022-11-04 贵州新致普惠信息技术有限公司 基于服务端控制的动态负载均衡方法
CN112333273B (zh) * 2020-11-06 2023-03-14 杭州迪普科技股份有限公司 一种访问请求的转发方法及系统
CN113268343A (zh) * 2021-05-10 2021-08-17 北京邮电大学 一种负载均衡系统及方法
CN113347037B (zh) * 2021-06-07 2022-07-12 中国建设银行股份有限公司 一种数据中心访问方法及装置
CN115834535A (zh) * 2022-10-17 2023-03-21 北京奇艺世纪科技有限公司 一种域名解析方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101102288A (zh) * 2006-07-06 2008-01-09 阿里巴巴公司 一种实现大型即时通信的方法及系统
US20100011120A1 (en) * 2002-08-07 2010-01-14 Foundry Networks, Inc. Canonical name (cname) handling for global server load balancing
CN102457440A (zh) * 2012-01-13 2012-05-16 华为软件技术有限公司 实现负载均衡的方法、dns服务器和客户端

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101677324B (zh) * 2008-09-17 2012-10-03 华为技术有限公司 业务管理方法、终端、网络系统及相关设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100011120A1 (en) * 2002-08-07 2010-01-14 Foundry Networks, Inc. Canonical name (cname) handling for global server load balancing
CN101102288A (zh) * 2006-07-06 2008-01-09 阿里巴巴公司 一种实现大型即时通信的方法及系统
CN102457440A (zh) * 2012-01-13 2012-05-16 华为软件技术有限公司 实现负载均衡的方法、dns服务器和客户端

Also Published As

Publication number Publication date
CN102457440A (zh) 2012-05-16

Similar Documents

Publication Publication Date Title
WO2013104172A1 (fr) Procédé de réalisation d'équilibrage de charge, serveur dns et client
US11811657B2 (en) Updating routing information based on client location
US11115500B2 (en) Request routing utilizing client location information
US10742593B1 (en) Hybrid content request routing system
US9794216B2 (en) Request routing in a networked environment
US9444759B2 (en) Service provider registration by a content broker
EP2294515B1 (fr) Routage de requête à l'aide de composants informatiques de réseau
EP3567881B1 (fr) Routage de requête et mise à jour d'informations de routage à l'aide d'informations de localisation de client
EP2266064B1 (fr) Routage de demandes
US20140330980A1 (en) Managing content delivery network service providers by a content broker
US20090222582A1 (en) Failover in an internet location coordinate enhanced domain name system
WO2021042673A1 (fr) Procédé de résolution dns, serveur dns d'autorité et système de résolution dns
US20120191769A1 (en) Site-aware distributed file system access from outside enterprise network

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: 12864990

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12864990

Country of ref document: EP

Kind code of ref document: A1