CN110674098A - Domain name resolution method in distributed file system - Google Patents
Domain name resolution method in distributed file system Download PDFInfo
- Publication number
- CN110674098A CN110674098A CN201910887762.0A CN201910887762A CN110674098A CN 110674098 A CN110674098 A CN 110674098A CN 201910887762 A CN201910887762 A CN 201910887762A CN 110674098 A CN110674098 A CN 110674098A
- Authority
- CN
- China
- Prior art keywords
- domain name
- virtual
- client
- condition
- name resolution
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 238000004590 computer program Methods 0.000 claims description 9
- 238000007616 round robin method Methods 0.000 claims description 2
- 230000006870 function Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/70—Virtual switches
-
- 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
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- 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]
Abstract
The application discloses a domain name resolution method, a domain name resolution device, a DNS server and a readable storage medium in a distributed file system, wherein the scheme comprises the following steps: acquiring a domain name resolution request sent by a client, and when the request continuously comes from the same client and aims at the same domain name, dividing the following two processing modes according to the service type and the time interval between two requests, wherein one processing mode is that virtual IP (Internet protocol) which is obtained by the previous resolution and corresponds to the client and a target domain name is sent to the client; and the other method is to recalculate the virtual IP according to the load balancing strategy and send the virtual IP to the client. Therefore, the scheme fully considers the service requirements of the client, enables the user to access the domain name according to the service type required by the user, and can improve the efficiency of the back-end server for processing the client request through the access of the service type.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for domain name resolution in a distributed file system, a DNS server, and a readable storage medium.
Background
The original load balancing strategy is mainly to distribute a back-end server by adopting a polling method, a minimum connection number method, a random method or a source address hashing method according to a domain name resolution request of a client so as to achieve the purpose of load balancing. However, the original load balancing policy does not consider the service requirement of the client, and for each domain name resolution request of the client, the domain name resolution is performed according to the policy corresponding to the domain name, and a virtual IP is returned to the client, so that the processing efficiency of the client request is low.
Disclosure of Invention
The application aims to provide a domain name resolution method, a domain name resolution device, a DNS server and a readable storage medium in a distributed file system, which are used for solving the problems that the original load balancing strategy does not consider the service requirement of a client, each time a domain name resolution request of the client is carried out, the domain name resolution is carried out according to a strategy corresponding to a domain name, a virtual IP is returned to the client, and the processing efficiency of the request of the client is low.
In order to solve the above technical problem, the present application provides a domain name resolution method in a distributed file system, which is applied to a DNS server, and includes:
acquiring a domain name resolution request sent by a current client, wherein the domain name access request comprises a target domain name;
when a first condition or a second condition is met, sending a virtual IP (Internet protocol) which is obtained by previous analysis and corresponds to the current client and the target domain name to the current client; the first condition is that file service or object service is opened locally, and domain name resolution requests for the same domain name from the same client are continuously received locally within a preset time period; the second condition is that a block service is locally started, and domain name resolution requests for the same domain name from the same client side are locally and continuously received;
and when the first condition and the second condition are not met, performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, and sending the virtual IP to the current client.
Preferably, the sending, to the current client, the virtual IP obtained through previous resolution and corresponding to the current client and the target domain name when the first condition or the second condition is satisfied includes:
when a first condition is met, sending a virtual IP (Internet protocol) which is obtained by last analysis and corresponds to the current client and the target domain name to the current client;
and when a second condition is met, sending the virtual IP which is obtained by the first analysis and corresponds to the current client and the target domain name to the current client.
Preferably, after performing domain name resolution according to the load balancing policy corresponding to the target domain name to obtain the virtual IP, the method further includes:
when file service or object service is opened locally, recording the IP of the current client, the virtual IP obtained by analysis and the current system time in the analysis process;
and when the block service is locally started, recording the virtual IP obtained by analysis in the analysis process.
Preferably, before the obtaining of the domain name resolution request sent by the current client, the method further includes:
and adding a timeswitch parameter in the local configuration file to indicate whether the block service is opened locally, wherein the default value of the timeswitch parameter is the unopened block service.
Preferably, before the sending, to the current client, the virtual IP corresponding to the current client and the target domain name obtained through past resolution, the method further includes:
and respectively judging whether a first condition and a second condition are met or not according to a timeswitch parameter newly added in the local configuration file, and a clienttype parameter and a clienttime parameter which originally exist, wherein the clienttype parameter is used for indicating whether two continuous domain name resolution requests come from the same client side or not, and the clienttime parameter is used for indicating whether a time interval between two continuous domain name resolution requests exceeds the preset time period or not.
Preferably, before the sending, to the current client, the virtual IP corresponding to the current client and the target domain name obtained through past resolution, the method further includes:
and determining the size of the preset time period according to user configuration.
Preferably, the performing domain name resolution according to the load balancing policy corresponding to the target domain name to obtain the virtual IP includes:
performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, wherein the load balancing strategy comprises any one or more of the following items: a weighted round robin method, a minimum connection number method, a random method, a source address hashing method.
The application also provides a domain name resolution device in the distributed file system, which is applied to a DNS server and comprises:
a request acquisition module: the domain name access request comprises a target domain name;
a first return module: the virtual IP server is used for sending the virtual IP which is obtained by the past analysis and corresponds to the current client and the target domain name to the current client when a first condition or a second condition is met; the first condition is that file service or object service is opened locally, and domain name resolution requests for the same domain name from the same client are continuously received locally within a preset time period; the second condition is that a block service is locally started, and domain name resolution requests for the same domain name from the same client side are locally and continuously received;
a second return module: and when the first condition and the second condition are not met, performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, and sending the virtual IP to the current client.
In addition, the present application also provides a DNS server, including:
a memory: for storing a computer program;
a processor: for executing the computer program for implementing the steps of a domain name resolution method in a distributed file system as described above.
Finally, the present application also provides a readable storage medium having stored thereon a computer program for implementing the steps of a domain name resolution method in a distributed file system as described above when being executed by a processor.
The scheme of the domain name resolution method, device, DNS server and readable storage medium in the distributed file system provided by the application includes: acquiring a domain name resolution request sent by a current client, wherein a domain name access request comprises a target domain name; when a first condition or a second condition is met, sending a virtual IP (Internet protocol) which is obtained by previous analysis and corresponds to a current client and a target domain name to the current client; otherwise, performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, and sending the virtual IP to the current client. The first condition is that a file service or an object service is locally started, and domain name resolution requests for the same domain name from the same client are locally and continuously received within a preset time period, and the second condition is that a block service is locally started, and domain name resolution requests for the same domain name from the same client are locally and continuously received. Therefore, the scheme fully considers the service requirements of the client, enables the user to access the domain name according to the service type required by the user, and can improve the efficiency of the back-end server for processing the client request, further strengthen the network data processing capacity and improve the flexibility and the usability of the network through the access of the service type.
Drawings
For a clearer explanation of the embodiments or technical solutions of the prior art of the present application, the drawings needed for the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart illustrating a first implementation of a domain name resolution method in a distributed file system according to an embodiment of the present disclosure;
fig. 2 is a flowchart illustrating an implementation of a second domain name resolution method in a distributed file system according to an embodiment of the present disclosure;
fig. 3 is a functional block diagram of an embodiment of a domain name resolution apparatus in a distributed file system according to the present application;
fig. 4 is a schematic structural diagram of an embodiment of a DNS server provided in the present application.
Detailed Description
The core of the application is to provide a domain name resolution method, a domain name resolution device, a DNS server and a readable storage medium in a distributed file system, and the purpose that the service type is determined according to the service requirement of a client is achieved, so that the request processing efficiency is improved.
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, a first embodiment of a domain name resolution method in a distributed file system provided in the present application is described below, where the first embodiment is applied to a DNS server, and includes:
s101, acquiring a domain name resolution request sent by a current client, wherein the domain name access request comprises a target domain name;
s102, when a first condition or a second condition is met, sending a virtual IP (Internet protocol) which is obtained by previous analysis and corresponds to the current client and the target domain name to the current client;
the first condition is that file service or object service is opened locally, and domain name resolution requests for the same domain name from the same client are continuously received locally within a preset time period; the second condition is that the block service is locally started, and domain name resolution requests for the same domain name from the same client are locally and continuously received.
S103, when the first condition and the second condition are not met, performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, and sending the virtual IP to the current client.
In the embodiment, based on DNS implementation, DNS is responsible for providing domain name resolution service, when a client accesses a certain site, it actually needs to obtain an IP address pointed by a domain name through a DNS server of the domain name of the site first, in this process, the DNS server completes mapping of the domain name to the IP address, and similarly, the mapping may also be one-to-many, and at this time, the DNS server serves as a load balancing scheduler, which, like an http redirection conversion policy, disperses a user's request to multiple servers, but its implementation mechanism is completely different.
In this embodiment, all backend servers may be regarded as cluster nodes, and are configured with the same service type switch, where the service types include: file service, object service, block service. As a specific implementation manner, if the DNS starts a file or object service and the same client continuously accesses the same domain name within a preset time period, the DNS returns a result of the last resolution, and if the preset time period is exceeded, the DNS recalculates a virtual IP according to a policy corresponding to the domain name; if the DNS starts block service and the same client continuously accesses the same domain name, the DNS returns the result of the first resolution every time.
Specifically, in this embodiment, a parameter is added in advance to the configuration file of the DNS, and the parameter is used to indicate the type of service opened by the DNS. As known to those skilled in the art, there are no such newly added parameters in the original DNS configuration file, and the DNS defaults to open file/object services. After the above parameters are added, when the DNS opens the file/object service, the value of the parameter is false, and when the DNS opens the block service, the value of the parameter is true.
In this embodiment, the load balancing policy corresponding to the target domain name includes a polling method, a weighted polling method, a minimum connection number method, a random method, a source address hash method, and the like, and the method is mainly to allocate a back-end server by using the polling method, the minimum connection number method, the random method, or the source address hash method according to the domain name resolution request of the client, so as to achieve the purpose of load balancing. In the traditional load balancing strategy, for each domain name resolution request of a client, domain name resolution is performed according to a strategy corresponding to a domain name, and a virtual IP is returned to the client, which can be called as a file service. If the client does not want to acquire a new virtual IP each time, the server is required to return a result analyzed when the client accesses the server for the first time.
The present embodiment is a supplement and improvement to a load balancing policy in a distributed file system, and to solve the above problems, the present embodiment provides a domain name resolution method in a distributed file system, which fully considers the service requirements of a client and enables a user to access a domain name according to the service type required by the user. Through the access of the service type, the efficiency of processing the client request by the back-end server can be improved, the network data processing capacity is further enhanced, and the flexibility and the usability of the network are improved.
The second embodiment of the domain name resolution method in the distributed file system provided by the present application is described in detail below, and the second embodiment is implemented based on the first embodiment and is expanded to a certain extent on the basis of the first embodiment.
Referring to fig. 2, the second embodiment is applied to a DNS server, and includes:
s201, acquiring a domain name resolution request sent by a current client, wherein the domain name access request comprises a target domain name;
s202, respectively judging whether a first condition and a second condition are met according to a newly added timeswitch parameter in a local configuration file, and a clienttype parameter and a clienttime parameter which originally exist;
the timeswitch parameter is used for indicating whether a block service is locally started, the clienttype parameter is used for indicating whether two consecutive domain name resolution requests come from the same client, and the clienttime parameter is used for indicating whether a time interval between two consecutive domain name resolution requests exceeds the preset time period. Specifically, < type clienttype ═ true > indicates that the domain name resolution is continued for the client; the < clienttime > 2' indicates that the time interval for analyzing the continuous domain name of the client is 2 seconds, and the parameter can be configured according to the needs of the client, such as 5 seconds, 10 seconds and the like; if the timer is true, the block service is started.
The block service function is newly added, the new configuration file of this embodiment has more than < timeswitch ═ false'/> to control the service type, the configuration file has no timeswitch parameter before upgrading, and is compatible with the version before upgrading, so the code needs to be perfected, the timeswitch is default to false in the code, that is, the block service is not started, and after upgrading, the original configuration file has no timeswitch parameter and does not affect the original function; adding < timeswitch to the configuration file, < true'/>, and then restarting the service, the block service function is turned on.
S203, when a first condition is met, sending the virtual IP corresponding to the current client and the target domain name obtained by the last analysis to the current client;
s204, when a second condition is met, sending the virtual IP which is obtained by first analysis and corresponds to the current client and the target domain name to the current client;
the first condition is that file service or object service is opened locally, and domain name resolution requests for the same domain name from the same client are continuously received locally within a preset time period; the second condition is that the block service is locally started, and domain name resolution requests for the same domain name from the same client are locally and continuously received.
Specifically, if the timeswitch is false, the file service is started, the clienttype ═ true "and the clienttime ═ 2" are effective values, that is, the client continuously requests domain name resolution twice within 2s, and the DNS returns the last resolution result; if the client side requests domain name resolution for more than 2s, the DNS needs to recalculate and return a new resolution result to the client side.
If the timeswitch is true, the block service is started, and the clienttype and the clienttime are invalid values, i.e. the same client continuously accesses the same domain name, and the DNS returns the result of the first resolution each time.
It should be noted that the same client accesses a plurality of domain names without affecting each other; different clients successively access the same domain name, and new resolution results need to be calculated according to the strategy corresponding to the domain name each time.
S205, when the first condition and the second condition are not met, performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, and sending the virtual IP to the current client;
s206, when the file service or the object service is opened locally, recording the IP of the current client, the virtual IP obtained by analysis and the current system time in the analysis process;
and S207, recording the virtual IP obtained by analysis in the analysis process when the block service is locally started.
Therefore, the domain name resolution method in the distributed file system provided by the embodiment fully considers the service requirements of the client, so that the user can access the domain name according to the required service type. Through the service type, the efficiency of processing the client request by the back-end server can be improved, the network data processing capacity is further enhanced, and the flexibility and the usability of the network are improved.
In the following, a domain name resolution device in a distributed file system provided in an embodiment of the present application is introduced, and a domain name resolution device in a distributed file system described below and a domain name resolution method in a distributed file system described above may be referred to correspondingly.
Referring to fig. 3, the apparatus includes:
the request acquisition module 301: the domain name access request comprises a target domain name;
the first return module 302: the virtual IP server is used for sending the virtual IP which is obtained by the past analysis and corresponds to the current client and the target domain name to the current client when a first condition or a second condition is met; the first condition is that file service or object service is opened locally, and domain name resolution requests for the same domain name from the same client are continuously received locally within a preset time period; the second condition is that a block service is locally started, and domain name resolution requests for the same domain name from the same client side are locally and continuously received;
the second return module 303: and when the first condition and the second condition are not met, performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, and sending the virtual IP to the current client.
The domain name resolution device in the distributed file system of this embodiment is used to implement the domain name resolution method in the distributed file system, and therefore a specific implementation manner of the device can be seen in the foregoing embodiment of the domain name resolution method in the distributed file system, for example, the request obtaining module 301, the first returning module 302, and the second returning module 303 are respectively used to implement steps S101, S102, and S103 in the domain name resolution method in the distributed file system. Therefore, specific embodiments thereof may be referred to in the description of the corresponding respective partial embodiments, and will not be described herein.
In addition, since the domain name resolution device in the distributed file system of this embodiment is used to implement the domain name resolution method in the distributed file system, the role of the domain name resolution device corresponds to that of the method described above, and details are not described here.
In addition, the present application also provides a DNS server, as shown in fig. 4, including:
the memory 100: for storing a computer program;
the processor 200: for executing the computer program for implementing the steps of a domain name resolution method in a distributed file system as described above.
Finally, the present application provides a readable storage medium having stored thereon a computer program for implementing the steps of a domain name resolution method in a distributed file system as described above when executed by a processor.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above detailed descriptions of the solutions provided in the present application, and the specific examples applied herein are set forth to explain the principles and implementations of the present application, and the above descriptions of the examples are only used to help understand the method and its core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A domain name resolution method in a distributed file system is applied to a DNS server and comprises the following steps:
acquiring a domain name resolution request sent by a current client, wherein the domain name access request comprises a target domain name;
when a first condition or a second condition is met, sending a virtual IP (Internet protocol) which is obtained by previous analysis and corresponds to the current client and the target domain name to the current client; the first condition is that file service or object service is opened locally, and domain name resolution requests for the same domain name from the same client are continuously received locally within a preset time period; the second condition is that a block service is locally started, and domain name resolution requests for the same domain name from the same client side are locally and continuously received;
and when the first condition and the second condition are not met, performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, and sending the virtual IP to the current client.
2. The method according to claim 1, wherein the sending the previously-resolved virtual IP corresponding to the current client and the target domain name to the current client when a first condition or a second condition is satisfied comprises:
when a first condition is met, sending a virtual IP (Internet protocol) which is obtained by last analysis and corresponds to the current client and the target domain name to the current client;
and when a second condition is met, sending the virtual IP which is obtained by the first analysis and corresponds to the current client and the target domain name to the current client.
3. The method according to claim 2, wherein after performing domain name resolution according to the load balancing policy corresponding to the target domain name to obtain the virtual IP, the method further comprises:
when file service or object service is opened locally, recording the IP of the current client, the virtual IP obtained by analysis and the current system time in the analysis process;
and when the block service is locally started, recording the virtual IP obtained by analysis in the analysis process.
4. The method of claim 1, wherein before the obtaining the domain name resolution request sent by the current client, further comprising:
and adding a timeswitch parameter in the local configuration file to indicate whether the block service is opened locally, wherein the default value of the timeswitch parameter is the unopened block service.
5. The method of claim 4, wherein prior to said sending the previously resolved virtual IP corresponding to the current client and the target domain name to the current client, further comprising:
and respectively judging whether a first condition and a second condition are met or not according to a timeswitch parameter newly added in the local configuration file, and a clienttype parameter and a clienttime parameter which originally exist, wherein the clienttype parameter is used for indicating whether two continuous domain name resolution requests come from the same client side or not, and the clienttime parameter is used for indicating whether a time interval between two continuous domain name resolution requests exceeds the preset time period or not.
6. The method of claim 5, wherein prior to said sending the previously resolved virtual IP corresponding to the current client and the target domain name to the current client, further comprising:
and determining the size of the preset time period according to user configuration.
7. The method according to any one of claims 1 to 6, wherein the performing domain name resolution according to the load balancing policy corresponding to the target domain name to obtain the virtual IP comprises:
performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, wherein the load balancing strategy comprises any one or more of the following items: a weighted round robin method, a minimum connection number method, a random method, a source address hashing method.
8. A domain name resolution device in a distributed file system is applied to a DNS server and comprises:
a request acquisition module: the domain name access request comprises a target domain name;
a first return module: the virtual IP server is used for sending the virtual IP which is obtained by the past analysis and corresponds to the current client and the target domain name to the current client when a first condition or a second condition is met; the first condition is that file service or object service is opened locally, and domain name resolution requests for the same domain name from the same client are continuously received locally within a preset time period; the second condition is that a block service is locally started, and domain name resolution requests for the same domain name from the same client side are locally and continuously received;
a second return module: and when the first condition and the second condition are not met, performing domain name resolution according to a load balancing strategy corresponding to the target domain name to obtain a virtual IP, and sending the virtual IP to the current client.
9. A DNS server, comprising:
a memory: for storing a computer program;
a processor: for executing the computer program for implementing the steps of a domain name resolution method in a distributed file system as claimed in any of the claims 1-7.
10. A readable storage medium, having stored thereon a computer program for implementing the steps of a domain name resolution method in a distributed file system according to any of claims 1-7 when being executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910887762.0A CN110674098B (en) | 2019-09-19 | 2019-09-19 | Domain name resolution method in distributed file system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910887762.0A CN110674098B (en) | 2019-09-19 | 2019-09-19 | Domain name resolution method in distributed file system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110674098A true CN110674098A (en) | 2020-01-10 |
| CN110674098B CN110674098B (en) | 2022-04-22 |
Family
ID=69078263
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910887762.0A Active CN110674098B (en) | 2019-09-19 | 2019-09-19 | Domain name resolution method in distributed file system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110674098B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111314472A (en) * | 2020-02-21 | 2020-06-19 | 聚好看科技股份有限公司 | Domain name resolution method, domain name resolution server and terminal equipment |
| CN112596911A (en) * | 2020-12-29 | 2021-04-02 | 恩亿科(北京)数据科技有限公司 | Automatic operation and maintenance method and system for high-availability distributed system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6701329B1 (en) * | 2000-09-14 | 2004-03-02 | Microsoft Corporation | Aging and scavenging of DNS resource records |
| CN102055650A (en) * | 2009-10-29 | 2011-05-11 | 华为技术有限公司 | Load balance method and system and management server |
| CN102577303A (en) * | 2009-04-20 | 2012-07-11 | 思杰系统有限公司 | Systems and methods for generating a dns query to improve resistance against a dns attack |
| KR20160039882A (en) * | 2014-10-02 | 2016-04-12 | 삼성전자주식회사 | A DNS resolution method in a terminal of a wireless communication system, and an apparatus therefor |
| CN107547653A (en) * | 2017-09-11 | 2018-01-05 | 华北水利水电大学 | A kind of distributed file storage system |
| CN108449283A (en) * | 2018-06-22 | 2018-08-24 | 郑州云海信息技术有限公司 | Domain name analytic method, system, equipment based on load balancing and storage medium |
| CN108886540A (en) * | 2018-06-13 | 2018-11-23 | 深圳前海达闼云端智能科技有限公司 | Domain name resolution method, device and computer readable storage medium |
| CN108965154A (en) * | 2018-06-29 | 2018-12-07 | 华为技术有限公司 | Job flow control method and device in object storage system |
-
2019
- 2019-09-19 CN CN201910887762.0A patent/CN110674098B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6701329B1 (en) * | 2000-09-14 | 2004-03-02 | Microsoft Corporation | Aging and scavenging of DNS resource records |
| CN102577303A (en) * | 2009-04-20 | 2012-07-11 | 思杰系统有限公司 | Systems and methods for generating a dns query to improve resistance against a dns attack |
| CN102055650A (en) * | 2009-10-29 | 2011-05-11 | 华为技术有限公司 | Load balance method and system and management server |
| KR20160039882A (en) * | 2014-10-02 | 2016-04-12 | 삼성전자주식회사 | A DNS resolution method in a terminal of a wireless communication system, and an apparatus therefor |
| CN107547653A (en) * | 2017-09-11 | 2018-01-05 | 华北水利水电大学 | A kind of distributed file storage system |
| CN108886540A (en) * | 2018-06-13 | 2018-11-23 | 深圳前海达闼云端智能科技有限公司 | Domain name resolution method, device and computer readable storage medium |
| CN108449283A (en) * | 2018-06-22 | 2018-08-24 | 郑州云海信息技术有限公司 | Domain name analytic method, system, equipment based on load balancing and storage medium |
| CN108965154A (en) * | 2018-06-29 | 2018-12-07 | 华为技术有限公司 | Job flow control method and device in object storage system |
Non-Patent Citations (1)
| Title |
|---|
| 刘衍森: ""基于Hadoop的全分布式存储架构研究"", 《中国优秀硕士学位论文全文数据库（电子期刊）信息科技辑》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111314472A (en) * | 2020-02-21 | 2020-06-19 | 聚好看科技股份有限公司 | Domain name resolution method, domain name resolution server and terminal equipment |
| CN111314472B (en) * | 2020-02-21 | 2022-03-11 | 聚好看科技股份有限公司 | Domain name resolution method, domain name resolution server and terminal equipment |
| CN112596911A (en) * | 2020-12-29 | 2021-04-02 | 恩亿科(北京)数据科技有限公司 | Automatic operation and maintenance method and system for high-availability distributed system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110674098B (en) | 2022-04-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11115500B2 (en) | Request routing utilizing client location information | |
| CN103716251B (en) | For the load-balancing method and equipment of content distributing network | |
| US9450912B2 (en) | Method and device for accessing application server | |
| US20100169442A1 (en) | Apparatus and method for providing peer-to-peer proxy service with temporary storage management and traffic load balancing in peer-to-peer communications | |
| WO2013104172A1 (en) | Method for realizing load balancing, dns server, and client | |
| CN108259603B (en) | Load balancing method and device | |
| CN111711716B (en) | Domain name resolution method, device and equipment and readable storage medium | |
| US20230025679A1 (en) | Security aware load balancing for a global server load balancing system | |
| JP2012509623A (en) | Updating routing information using request routing and client location information | |
| CN110674098B (en) | Domain name resolution method in distributed file system | |
| US20230024475A1 (en) | Security aware load balancing for a global server load balancing system | |
| US11075987B1 (en) | Load estimating content delivery network | |
| CN110933136A (en) | Service node selection method, device, equipment and readable storage medium | |
| CN110557464A (en) | DNS (Domain name Server) resolution method, authoritative DNS server and DNS resolution system | |
| CN112583952A (en) | Redirection scheduling processing method, device and system, related equipment and storage medium | |
| US20180159941A1 (en) | Method for connecting a client to a server in a communication system | |
| CN112417404B (en) | User identity recognition method, computing device and computer storage medium | |
| EP2887620B1 (en) | Session Initiation Protocol Messaging | |
| CN108124021B (en) | Method, device and system for obtaining Internet Protocol (IP) address and accessing website | |
| US11095605B1 (en) | Request routing utilizing encoded DNS-based messaging parameters | |
| US10819775B2 (en) | Systems and methods for server failover and load balancing | |
| JP6001512B2 (en) | Communication control system and communication control method | |
| CN111163142B (en) | Domain name resolution method and related device | |
| CN109618014B (en) | Message forwarding method and device | |
| CN114500459A (en) | Data scheduling method and device based on DNS protocol and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |