CN114401247A - High-concurrency service request processing system based on bind service - Google Patents
High-concurrency service request processing system based on bind service Download PDFInfo
- Publication number
- CN114401247A CN114401247A CN202210042512.9A CN202210042512A CN114401247A CN 114401247 A CN114401247 A CN 114401247A CN 202210042512 A CN202210042512 A CN 202210042512A CN 114401247 A CN114401247 A CN 114401247A
- Authority
- CN
- China
- Prior art keywords
- dns
- service
- bind
- result
- service request
- 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.)
- Pending
Links
- 238000001514 detection method Methods 0.000 claims description 11
- 230000002159 abnormal effect Effects 0.000 claims description 10
- 230000007246 mechanism Effects 0.000 claims description 10
- 238000000034 method Methods 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 7
- 238000002360 preparation method Methods 0.000 claims 1
- 230000004044 response Effects 0.000 abstract description 14
- 238000011144 upstream manufacturing Methods 0.000 description 9
- 230000000977 initiatory effect Effects 0.000 description 3
- 230000036541 health Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
Abstract
The invention provides a high-concurrency service request processing system based on bind service, wherein a service machine inquires whether a corresponding DNS result is cached locally or not according to a service request; if yes, connecting a service server according to a DNS result; if not, sending the service request to the bind cluster; the bind cluster queries whether a corresponding DNS result is cached according to the service request; if yes, returning the DNS result to the service machine; if not, sending the service request to an authoritative DNS system; and the authoritative DNS system is configured to obtain a corresponding DNS result and return the DNS result to the bind cluster when the service request is received. The system greatly reduces the pressure of the bind server and improves the response speed of the service query DNS.
Description
Technical Field
The invention belongs to the technical field of internet, and particularly relates to a high-concurrency service request processing system based on bind service.
Background
In an IDC (Internet Data Center) room, the default mechanism of a service program on most service machines is that each service request needs to access a bind (berkeley Internet Name domain) server for domain Name resolution. When the peak value of the request of the service program to the bind server reaches 100w QPS, the limit of the bind server is seriously exceeded, so that the domain name resolution fails and the normal use cannot be realized.
The existing business machines mostly use a Linux system, and a/etc/resolv.conf (DNS client configuration file) mechanism of the Linux system cannot monitor and detect a bind server. When a bind server is abnormal, the service machine will wait until the resolution is overtime, and then poll to the next bind server, so that the domain name resolution time will be increased, and finally the service is overtime and cannot be used normally.
Most of the existing bind servers adopt a forward mechanism, and when an upstream authoritative dns (computer domain name system) server fails, domain name resolution is overtime, services are abnormal, and the server cannot be normally used.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a high-concurrency service request processing system based on bind service, which greatly reduces the pressure of a bind server.
A high-concurrency service request processing system based on bind service comprises a service machine, a bind cluster and an authoritative DNS system; the service machine is configured to initiate a service request;
the service machine is configured to inquire whether a corresponding DNS result is cached locally or not according to the service request; if yes, connecting a service server according to a DNS result; if not, sending the service request to the bind cluster; the service machine is configured to connect with the service server according to the DNS result returned by the bind cluster;
the bind cluster is configured to query whether a corresponding DNS result is cached according to the service request; if yes, returning the DNS result to the service machine; if not, sending the service request to an authoritative DNS system; the bind cluster is configured to send a DNS result returned by the authoritative DNS system to the service machine;
and the authoritative DNS system is configured to obtain a corresponding DNS result and return the DNS result to the bind cluster when the service request is received.
Preferably, the business machine comprises:
a service unit: configured to initiate a service request to a DNS cache unit; the service unit is configured to connect with the service server according to the DNS result;
a DNS cache unit: configured to determine whether a corresponding DNS result is cached when a service request is received; if yes, returning a DNS result to the service unit; if not, transmitting the service request to a first DNS forwarding unit, and caching a DNS result returned by the first DNS forwarding unit;
a first DNS forwarding unit: configured to determine whether a corresponding DNS result is cached when a service request is received; if yes, returning a DNS result to the DNS cache unit and the service unit; if not, the service request is transmitted to the bind cluster, the DNS result returned by the bind cluster is cached, and the DNS result is sent to the DNS cache unit and the service unit.
Preferably, the DNS cache unit is an NSCD module; and the business machine configures the caching parameters of the NSCD module through the configuration file of the domain name service caching process of the business machine.
Preferably, the first DNS forwarding unit is a DNSmasq module; and the service machine configures the cache parameter of the first DNS forwarding unit through the domain name service cache process configuration file of the service machine, and the first DNS forwarding unit points to the bind cluster.
Preferably, the bind cluster is deployed with a plurality of bind servers and a plurality of second DNS forwarding units;
the bind server is configured to determine whether a corresponding DNS result is cached when the service request is received; if yes, returning a DNS result to the first DNS forwarding unit; if not, transmitting the service request to a second DNS forwarding unit, caching a DNS result returned by the second DNS forwarding unit, and transmitting the DNS result to the first DNS forwarding unit;
the second DNS forwarding unit is configured to judge whether a corresponding DNS result is cached when the service request is received; if yes, returning a DNS result to the bind server; if not, the service request is transmitted to the authoritative DNS system, and the DNS result returned by the authoritative DNS system is cached and sent to the bind server.
Preferably, the second DNS forwarding unit is a DNSmasq module; and the bind cluster configures the cache parameter of the second DNS forwarding unit through the mechanism of the bind cluster, and the second DNS forwarding unit points to the authoritative DNS system.
Preferably, the first DNS forwarding unit is configured to detect a bind server in the bind cluster, and mark the bind server according to a detection result, where the marking information includes normal or abnormal.
Preferably, the first DNS forwarding unit is configured to:
and when the DNS result is not cached, transmitting the service request to the bind server with normal marking information.
Preferably, the authoritative DNS system comprises a plurality of authoritative DNS servers;
the second DNS forwarding unit is configured to detect an authoritative DNS server in the authoritative DNS system and mark the authoritative DNS server according to a detection result, wherein the marking information includes normal or abnormal information.
Preferably, the second DNS forwarding unit is configured to:
and when the DNS result is not cached, transmitting the service request to an authoritative DNS server with normal marking information.
According to the technical scheme, the high-concurrency service request processing system based on the bind service, provided by the invention, caches DNS results corresponding to part of service requests in the service machine, the service machine does not need to access the bind cluster every time the service request is carried out, and only when the corresponding DNS result does not exist locally, the bind cluster is accessed, so that the pressure of a bind server is greatly reduced, and the response speed of service query DNS is improved.
Drawings
In order to more clearly illustrate the detailed description of the invention or the technical solutions in the prior art, the drawings that are needed in the detailed description of the invention or the prior art will be briefly described below. Throughout the drawings, like elements or portions are generally identified by like reference numerals. In the drawings, elements or portions are not necessarily drawn to scale.
Fig. 1 is a flowchart illustrating an architecture of a high concurrency service request processing system according to this embodiment.
Fig. 2 is a block flow diagram of a high concurrency service request processing system according to this embodiment.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The following examples are only for illustrating the technical solutions of the present invention more clearly, and therefore are only examples, and the protection scope of the present invention is not limited thereby. It is to be noted that, unless otherwise specified, technical or scientific terms used herein shall have the ordinary meaning as understood by those skilled in the art to which the invention pertains.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Example (b):
a high-concurrency service request processing system based on bind service, see FIG. 1, includes a service machine, a bind cluster and an authoritative DNS system; the service machine is configured to initiate a service request;
the service machine is configured to inquire whether a corresponding DNS result is cached locally or not according to the service request; if yes, connecting a service server according to a DNS result; if not, sending the service request to the bind cluster; the service machine is configured to connect with the service server according to the DNS result returned by the bind cluster;
the bind cluster is configured to query whether a corresponding DNS result is cached according to the service request; if yes, returning the DNS result to the service machine; if not, sending the service request to an authoritative DNS system; the bind cluster is configured to send a DNS result returned by the authoritative DNS system to the service machine;
and the authoritative DNS system is configured to obtain a corresponding DNS result and return the DNS result to the bind cluster when the service request is received.
In this embodiment, most of the service processing flows require the service machine to access the service server to complete the corresponding service processing. The service machine can only be connected with the service server corresponding to the domain name after obtaining the domain name of the service server to be connected, so that the service machine needs to generate different service requests according to different service requirements, the service requests are used for requesting to analyze the domain name, for example, the service machine can generate the service requests according to a website to be accessed, and the service requests include the website api. The service request may be generated by a service machine, or may receive a service request from an external device, for example, the service machine may receive a service request from an external terminal.
In this embodiment, after receiving the service request, the service machine does not need to immediately send the service request to the bind cluster for domain name resolution, and needs to query whether the DNS result corresponding to the service request is cached locally. For example, the service machine may locally cache a domain name corresponding to each website, and after receiving a website to be accessed, the service machine queries the domain name according to the website and generates a DNS result according to the domain name. If the local service machine inquires that the local cache has the corresponding DNS result, the service server is connected according to the DNS result, for example, if the domain name corresponding to the website api, push, applet and com is cached in the service machine, the service server is directly connected according to the domain name, and the service processing is completed. The domain name may include the IP address of the website.
In this embodiment, if the service machine does not locally cache the corresponding DNS result, domain name resolution is requested from the bind cluster, and the corresponding domain name is resolved by the bind cluster. If the bind cluster caches the corresponding DNS result, the DNS result is returned to the service machine layer by layer downwards; and if the corresponding DNS result is not cached, requesting domain name resolution from an authoritative DNS system, resolving the corresponding domain name through the DNS system, and returning the obtained domain name to the service machine layer by layer.
According to the high-concurrency service request processing system based on the bind service, DNS results corresponding to part of service requests are cached in the service machine, the service machine does not need to access the bind cluster every time the service request is carried out, and only when the corresponding DNS result does not exist locally, the bind cluster is accessed, so that the pressure of a bind server is greatly reduced, and the response speed of a service query DNS is improved.
Further, in some embodiments, referring to fig. 2, a business machine comprises:
a service unit: configured to initiate a service request to a DNS cache unit; the service unit is configured to connect with the service server according to the DNS result;
a DNS cache unit: configured to determine whether a corresponding DNS result is cached when a service request is received; if yes, returning a DNS result to the service unit; if not, transmitting the service request to a first DNS forwarding unit, and caching a DNS result returned by the first DNS forwarding unit;
a first DNS forwarding unit: configured to determine whether a corresponding DNS result is cached when a service request is received; if yes, returning a DNS result to the DNS cache unit and the service unit; if not, the service request is transmitted to the bind cluster, the DNS result returned by the bind cluster is cached, and the DNS result is sent to the DNS cache unit and the service unit.
In this embodiment, the service unit is mainly responsible for performing specific service processing, including initiating a service request, connecting with a service server, and the like. The DNS cache unit mainly realizes the caching or storage of DNS results, and mainly comprises the following functions in 3 aspects: 1) when the cached DNS result exists, returning the DNS result to the service unit; 2) when the cached DNS result does not exist, a domain name resolution request (namely a service request or request data which is substantially the same as the service request) is initiated to the first DNS forwarding unit; 3) the DNS results from the first DNS forwarding unit are cached.
In this embodiment, the first DNS forwarding unit mainly implements forwarding of a DNS result, and mainly includes the following functions in 3 aspects: 1) when the cached DNS result exists, returning the DNS result to the DNS cache unit and the service unit; 2) when the cached DNS result does not exist, a domain name resolution request (namely a service request or request data which is substantially the same as the service request) is initiated to the bind cluster; 3) and caching the DNS result from the bind cluster and sending the DNS result to the DNS caching unit and the service unit.
Further, in some embodiments, the DNS cache unit is an NSCD module; and the business machine configures the caching parameters of the NSCD module through the configuration file of the domain name service caching process of the business machine.
In this embodiment, the NSCD module may be a memory-type DNS local cache component, and the service machine may install the NSCD module in advance and configure the NSCD module. The domain name service cache process configuration file of the business machine can be a/etc/nscd. The caching parameter may be a caching duration, etc., so that the number of requests to the bind cluster may be reduced.
Further, in some embodiments, the first DNS forwarding unit is a DNSmasq module; and the service machine configures the cache parameter of the first DNS forwarding unit through the domain name service cache process configuration file of the service machine, and the first DNS forwarding unit points to the bind cluster.
In this embodiment, the service machine may install a DNSmasq module in advance and configure the DNSmasq module. For example, the service machine may configure bind-interfaces and listen-addresses of the DNSmasq module through the/etc/nscd. The service machine can also configure the DNSmasq module to point to the bind cluster, and is used for initiating a domain name resolution request to the bind cluster under the condition of no cache.
Further, in some embodiments, referring to fig. 2, a bind cluster is deployed with a plurality of bind servers and a plurality of second DNS forwarding units;
the bind server is configured to determine whether a corresponding DNS result is cached when the service request is received; if yes, returning a DNS result to the first DNS forwarding unit; if not, transmitting the service request to a second DNS forwarding unit, caching a DNS result returned by the second DNS forwarding unit, and transmitting the DNS result to the first DNS forwarding unit;
the second DNS forwarding unit is configured to judge whether a corresponding DNS result is cached when the service request is received; if yes, returning a DNS result to the bind server; if not, the service request is transmitted to the authoritative DNS system, and the DNS result returned by the authoritative DNS system is cached and sent to the bind server.
In this embodiment, the bind server mainly includes the following functions in 3 aspects: 1) when the cached DNS result exists, returning the DNS result to the first DNS forwarding unit; 2) when the cached DNS result does not exist, a domain name resolution request (namely a service request or request data which is substantially the same as the service request) is initiated to a second DNS forwarding unit; 3) and caching the DNS result from the second DNS forwarding unit and sending the DNS result to the first DNS forwarding unit.
The second DNS forwarding unit mainly implements forwarding of DNS results, and mainly includes the following functions in 3 aspects: 1) when the cached DNS result exists, returning the DNS result to the bind server; 2) when the cached DNS result does not exist, initiating a domain name resolution request (namely a service request or request data which is substantially the same as the service request) to an authoritative DNS system; 3) and caching the DNS result from the authoritative DNS system and sending the DNS result to the bind server.
Further, in some embodiments, the second DNS forwarding unit is a DNSmasq module; and the bind cluster configures the cache parameter of the second DNS forwarding unit through the mechanism of the bind cluster, and the second DNS forwarding unit points to the authoritative DNS system.
In this embodiment, a bind cluster deploys a plurality of bind servers and a plurality of second DNS forwarding units, and the mechanism of the bind cluster may be a bind forward mechanism. The bind cluster can configure the bind server to point to the second DNS forwarding unit through the bind forward mechanism, and the bind cluster can configure the bind-interfaces and the listen-addresses of the second DNS forwarding unit through the bind forward mechanism, so as to monitor the service machine ip and realize the functions of local forwarding and caching. The bind cluster may configure the second DNS forwarding unit to point to the authoritative DNS system, and initiate a domain name resolution request to the authoritative DNS system without caching.
Further, in some embodiments, the first DNS forwarding unit is configured to detect a bind server in the bind cluster, and mark the bind server according to a detection result, where the marking information includes normal or abnormal.
In this embodiment, the service machine may set/etc/resolv.conf DNS domain name resolution configuration file to point to the first DNS forwarding unit, so that the service machine may implement health detection on the bind cluster through the first DNS forwarding unit, detect whether each bind server in the upstream bind cluster is normal, and implement a high-availability architecture for DNS automatic switching and unlimited capacity expansion of the bind cluster. The service machine can also configure resolv-file in the/etc/dnssmasq. conf configuration file, which is convenient for the ip of the upstream bind server needing to be accessed in real time and realizes dynamic update.
In this embodiment, the first DNS forwarding unit may send the detection information to all the bind servers in the bind cluster at the same time, and determine whether the bind server is normal according to the time when the bind server returns the response information. For example, the first N bind servers with the shortest tag response time are normal, and the first M bind servers with the longest tag response time are abnormal, where N, M may be an integer greater than or equal to 1.
The system can acquire the state of each bind server in the bind cluster in real time by detecting the bind cluster through the service machine, so that when the service machine sends a domain name resolution request to the bind cluster, the service machine can only send the request to the normal bind server, and the overtime of the request caused by the fault of the bind server is avoided.
Further, in some embodiments, the first DNS forwarding unit is configured to:
and when the DNS result is not cached, transmitting the service request to the bind server with normal marking information.
In this embodiment, when the first DNS forwarding unit needs to initiate a domain name resolution request to an upstream bind server, it only needs to send a service request to a normal bind server, and it is not necessary to search through all bind servers in a bind cluster, thereby avoiding a request timeout caused by a fault of a bind server.
Further, in some embodiments, the authoritative DNS system includes a plurality of authoritative DNS servers;
the second DNS forwarding unit is configured to detect an authoritative DNS server in the authoritative DNS system and mark the authoritative DNS server according to a detection result, wherein the marking information includes normal or abnormal information.
In this embodiment, the bind cluster may implement health detection on the authoritative DNS system through the second DNS forwarding unit, and detect whether the authoritative DNS server in the upstream authoritative DNS system is normal, thereby solving the problem that the system cannot be used when the upstream authoritative DNS server has a single point of failure in the prior art.
In this embodiment, the second DNS forwarding unit may send the detection information to the ownership DNS server in the authoritative DNS system at the same time, and determine whether the authoritative DNS server is normal according to the time when the authoritative DNS server returns the response information. For example, the first N authoritative DNS servers with the shortest tag response time are normal, the first M authoritative DNS servers with the longest tag response time are abnormal, or the tag response time is out of order, where N, M may be an integer greater than or equal to 1.
The system detects the authoritative DNS through the bind cluster, and can acquire the state of each authoritative DNS in the authoritative DNS in real time, so that when the bind cluster sends a domain name resolution request to the authoritative DNS, the bind cluster can only send the request to the normal authoritative DNS, and the problem that the system cannot be used when the upstream authoritative DNS has a single point fault in the prior art is solved.
Further, in some embodiments, the second DNS forwarding unit is configured to:
and when the DNS result is not cached, transmitting the service request to an authoritative DNS server with normal marking information.
In this embodiment, when the second DNS forwarding unit needs to initiate a domain name resolution request to an upstream authoritative DNS system, it is only necessary to send the service request to a normal authoritative DNS server, and it is not necessary to search all authoritative DNS servers in the authoritative DNS system, which solves the problem in the prior art that the system cannot be used when the upstream authoritative DNS server has a single point of failure.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.
Claims (10)
1. A high-concurrency service request processing system based on bind service comprises a service machine, a bind cluster and an authoritative DNS system; the service machine is configured to initiate a service request; it is characterized in that the preparation method is characterized in that,
the service machine is configured to inquire whether a corresponding DNS result is cached locally or not according to the service request; if yes, connecting a service server according to the DNS result; if not, sending the service request to the bind cluster; the business machine is configured to connect a business server according to the DNS result returned by the bind cluster;
the bind cluster is configured to query whether a corresponding DNS result is cached according to the service request; if yes, the DNS result is returned to the service machine; if not, sending the service request to the authoritative DNS system; the bind cluster is configured to send a DNS result returned by the authoritative DNS system to the business machine;
and the authoritative DNS system is configured to obtain a corresponding DNS result when the service request is received, and return the DNS result to the bind cluster.
2. The bind service based high-concurrency service request processing system as claimed in claim 1, wherein said service machine comprises:
a service unit: configured to initiate the service request to a DNS cache unit; the service unit is configured to connect to the service server according to the DNS result;
a DNS cache unit: configured to determine whether a corresponding DNS result is cached when the service request is received; if yes, returning the DNS result to the service unit; if not, transmitting the service request to a first DNS forwarding unit, and caching the DNS result returned by the first DNS forwarding unit;
a first DNS forwarding unit: configured to determine whether a corresponding DNS result is cached when the service request is received; if yes, returning the DNS result to the DNS cache unit and the service unit; if not, the service request is transmitted to the bind cluster, the DNS result returned by the bind cluster is cached, and the DNS result is sent to the DNS cache unit and the service unit.
3. The bind service based high-concurrency service request processing system as recited in claim 2,
the DNS cache unit is an NSCD module; and the business machine configures the cache parameters of the NSCD module through the domain name service cache process configuration file.
4. The bind service based high-concurrency service request processing system as recited in claim 2,
the first DNS forwarding unit is a DNSmasq module; and the service machine configures the cache parameter of the first DNS forwarding unit through a domain name service cache process configuration file of the service machine, and the first DNS forwarding unit points to the bind cluster.
5. The bind service-based high-concurrency traffic request processing system according to claim 2, wherein said bind cluster is deployed with a plurality of bind servers and a plurality of second DNS forwarding units;
the bind server is configured to determine whether a corresponding DNS result is cached when the service request is received; if yes, returning the DNS result to the first DNS forwarding unit; if not, transmitting the service request to the second DNS forwarding unit, caching the DNS result returned by the second DNS forwarding unit, and sending the DNS result to the first DNS forwarding unit;
the second DNS forwarding unit is configured to judge whether a corresponding DNS result is cached when the service request is received; if yes, returning the DNS result to the bind server; if not, the service request is transmitted to an authoritative DNS system, the DNS result returned by the authoritative DNS system is cached, and the result is sent to the bind server.
6. The bind service based high-concurrency service request processing system as recited in claim 5,
the second DNS forwarding unit is a DNSmasq module; and the bind cluster configures the cache parameter of the second DNS forwarding unit through the mechanism of the bind cluster, and the second DNS forwarding unit points to the authoritative DNS system.
7. The bind service based high-concurrency service request processing system as recited in claim 5,
the first DNS forwarding unit is configured to detect the bind server in the bind cluster and mark the bind server according to a detection result, wherein the marking information includes normal or abnormal information.
8. The bind service based high concurrent traffic request processing system according to claim 7, wherein the first DNS forwarding unit is configured to:
and when the DNS result is not cached, transmitting the service request to the bind server with normal marking information.
9. The bind service based high-concurrency service request processing system as recited in claim 5,
the authoritative DNS system comprises a plurality of authoritative DNS servers;
the second DNS forwarding unit is configured to detect the authoritative DNS server in the authoritative DNS system and mark the authoritative DNS server according to a detection result, wherein the marking information includes normal or abnormal information.
10. The bind service based high concurrent traffic request processing system according to claim 9, wherein the second DNS forwarding unit is configured to:
and when the DNS result is not cached, transmitting the service request to the authoritative DNS server with normal marking information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210042512.9A CN114401247A (en) | 2022-01-14 | 2022-01-14 | High-concurrency service request processing system based on bind service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210042512.9A CN114401247A (en) | 2022-01-14 | 2022-01-14 | High-concurrency service request processing system based on bind service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114401247A true CN114401247A (en) | 2022-04-26 |
Family
ID=81230108
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210042512.9A Pending CN114401247A (en) | 2022-01-14 | 2022-01-14 | High-concurrency service request processing system based on bind service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114401247A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103281409A (en) * | 2013-06-24 | 2013-09-04 | 广州菁英信息技术有限公司 | Domain name resolution method of mobile internet and DNS server based on TCP protocol |
| CN105357212A (en) * | 2015-11-23 | 2016-02-24 | 北京天地互连信息技术有限公司 | DNS end-to-end analysis method capable of ensuring safety and privacy |
| CN108650211A (en) * | 2018-03-14 | 2018-10-12 | 北京奇艺世纪科技有限公司 | A kind of detection method and device of DNS abduction |
| CN109151092A (en) * | 2018-10-11 | 2019-01-04 | 深圳互联先锋科技有限公司 | A kind of domain name analytic method |
| CN110855636A (en) * | 2019-10-25 | 2020-02-28 | 武汉绿色网络信息服务有限责任公司 | DNS hijacking detection method and device |
-
2022
- 2022-01-14 CN CN202210042512.9A patent/CN114401247A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103281409A (en) * | 2013-06-24 | 2013-09-04 | 广州菁英信息技术有限公司 | Domain name resolution method of mobile internet and DNS server based on TCP protocol |
| CN105357212A (en) * | 2015-11-23 | 2016-02-24 | 北京天地互连信息技术有限公司 | DNS end-to-end analysis method capable of ensuring safety and privacy |
| CN108650211A (en) * | 2018-03-14 | 2018-10-12 | 北京奇艺世纪科技有限公司 | A kind of detection method and device of DNS abduction |
| CN109151092A (en) * | 2018-10-11 | 2019-01-04 | 深圳互联先锋科技有限公司 | A kind of domain name analytic method |
| CN110855636A (en) * | 2019-10-25 | 2020-02-28 | 武汉绿色网络信息服务有限责任公司 | DNS hijacking detection method and device |
Non-Patent Citations (5)
| Title |
|---|
| （美）H.FRANK CERVONE著，盛敬刚等译: "《Solaris性能管理》", 30 November 2000, 机械工业出版社, pages: 149 * |
| 宋海瑞: "面向映射系统的关键技术研究", 中国优秀硕士学位论文全文数据库, no. 11 * |
| 山金孝等: "《OpenShift云原生架构原理与实践》", 30 April 2020, 机械工业出版社, pages: 78 - 79 * |
| 徐建: "《计算机组网及WIRESHARK实验教程》", 31 December 2018, 西安电子科技大学出版社, pages: 140 - 141 * |
| 李晓宾;李淑珍;: "校园网中Bind域名服务器的实现", 软件导刊, no. 12, pages 144 - 146 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11909639B2 (en) | Request routing based on class | |
| US11108729B2 (en) | Managing request routing information utilizing client identifiers | |
| US20050240574A1 (en) | Pre-fetching resources based on a resource lookup query | |
| US6775743B2 (en) | Content caching with special handling of multiple identical requests for content | |
| EP2266064B1 (en) | Request routing | |
| US6795434B1 (en) | Replicated server discovery in client-proxy servers | |
| US10958501B1 (en) | Request routing information based on client IP groupings | |
| EP2263163B1 (en) | Content management | |
| US8166197B2 (en) | Multipath routing process | |
| US8478903B2 (en) | Shared content delivery infrastructure | |
| CA2574416C (en) | Accessing distributed services in a network | |
| CN101164321A (en) | Process for managing resource address requests and associated gateway device | |
| CN110809070A (en) | Website domain name resolution record processing method and device, electronic equipment and storage medium | |
| CN110730250A (en) | Information processing method and device, service system and storage medium | |
| CN113315852B (en) | Domain name resolution method, device and system | |
| CN108494870B (en) | CDN-based dynamic data loading method and device | |
| US20050005027A1 (en) | Method and system for obtaining data through an IP transmission network by using an optimized domain name server | |
| CN113938464B (en) | Access request method and terminal | |
| JP2002368781A (en) | User location management domain name conversion system | |
| CN114401247A (en) | High-concurrency service request processing system based on bind service | |
| CN115103008B (en) | Service request forwarding system | |
| CN115022399A (en) | Proxy service processing method and system | |
| CN111935329B (en) | Domain name resolution method and device | |
| US20030125909A1 (en) | System and method for monitoring server host operation | |
| WO2010054554A1 (en) | Method, system and server for centralized management of network service |
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 |