CN118200286A - Domain name resolution method, device, electronic equipment and storage medium - Google Patents
Domain name resolution method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN118200286A CN118200286A CN202410301855.1A CN202410301855A CN118200286A CN 118200286 A CN118200286 A CN 118200286A CN 202410301855 A CN202410301855 A CN 202410301855A CN 118200286 A CN118200286 A CN 118200286A
- Authority
- CN
- China
- Prior art keywords
- domain name
- address
- recorded
- virtual service
- source
- 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
- 238000000034 method Methods 0.000 title claims abstract description 59
- 230000004044 response Effects 0.000 claims abstract description 77
- 238000012423 maintenance Methods 0.000 claims description 42
- 230000032683 aging Effects 0.000 claims description 16
- 238000012544 monitoring process Methods 0.000 claims description 8
- 238000004891 communication Methods 0.000 claims description 6
- 238000001514 detection method Methods 0.000 claims description 6
- 238000010276 construction Methods 0.000 claims description 5
- 230000003862 health status Effects 0.000 claims description 5
- 230000008569 process Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 8
- 230000008859 change Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000002431 foraging effect Effects 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 239000000523 sample Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000004083 survival effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- 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/14—Session management
- H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The specification provides a domain name resolution method, a domain name resolution device, an electronic device and a storage medium, wherein the domain name resolution method comprises the following steps: receiving a domain name resolution request which is sent by a client and comprises a source IP address and a domain name to be accessed; searching a session maintaining table item of which the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name; if the session maintaining list item is searched, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded by the searched session maintaining list item, and sending the response message to the client; the information of the virtual service includes the IP addresses of a plurality of virtual services obtained by first requesting the resolution of the domain name by the client belonging to the same network segment as the source IP address. According to the scheme, the number of virtual service resources obtained after the client sends the domain name resolution request is increased, the client can select conveniently, single-point faults are avoided, and high service availability is guaranteed.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of session maintenance, and in particular, to a domain name resolution method, a domain name resolution device, an electronic device, and a storage medium.
Background
In the current network technology field, DNS (Domain NAME SYSTEM) service is tightly combined with session maintenance technology, and supports efficient service access and resource scheduling in a complex network environment. Specifically, when the DNS server receives a domain name resolution request sent by the client, the DNS server not only resolves the domain name to a corresponding IP address, but also performs session maintenance processing according to the source IP address carried in the request.
Session maintenance processing is a mechanism that combines DNS services with load balancing policies in network technology. When a DNS server receives a domain name resolution request, not only does the domain name to IP address translation proceed, but a session hold table entry is created or looked up based on the request source IP address, associating the request to a particular virtual service resource.
Disclosure of Invention
The present disclosure provides a domain name resolution method, the method comprising:
Receiving a domain name resolution request sent by a client, wherein the domain name resolution request comprises a source IP address and a domain name to be accessed;
searching a session maintaining table item of which the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name;
If the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded in the searched session maintenance table, and sending the response message to the client;
The information of the virtual service includes IP addresses of a plurality of virtual services obtained by analyzing the domain name, wherein the client side belonging to the same network segment as the source IP address first requests the client side to analyze the domain name.
Optionally, the method further comprises:
If the recorded IP address and the source IP address belong to the same network segment and the recorded session maintaining list item of the requested domain name and the domain name are the same, selecting virtual service according to a load balancing algorithm, constructing a response message corresponding to the domain name resolution request based on the information of the selected virtual service, and sending the response message to the client.
Optionally, the method further comprises:
if the virtual services recorded in the session maintaining list item pass the health status check, and the IP address currently used by the virtual services recorded in the session maintaining list item is matched with the IP address recorded in the session maintaining list item, the session maintaining list item is valid;
The IP address of the virtual service currently used recorded in the session maintaining table entry is obtained through service state monitoring or configuration information query.
Optionally, if the session maintaining table item that the recorded IP address belongs to the same network segment as the source IP address and the recorded requested domain name is the same as the domain name is found, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded in the found session maintaining table item, including:
If the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name, and the session maintaining list item is determined to be effective, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded by the searched session maintaining list item.
Optionally, the virtual service is located in a virtual service group, and the selecting the virtual service according to the load balancing algorithm includes:
Selecting a virtual service group from a virtual service list according to a load balancing algorithm configured by the domain name, wherein the virtual service group comprises at least one virtual service;
and selecting a specified number of virtual services from the at least one virtual service according to a load balancing algorithm configured by the virtual service group.
Optionally, the method further comprises:
Aging detection is carried out on the session maintaining table item in the effective state;
And deleting the session maintaining table entries meeting the aging condition.
The present disclosure also provides a domain name resolution apparatus, the apparatus comprising:
The receiving unit is used for receiving a domain name resolution request sent by the client, wherein the domain name resolution request comprises a source IP address and a domain name to be accessed;
A searching unit, configured to search a session maintenance table entry in which the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name;
A first construction unit, configured to construct a response message corresponding to the domain name resolution request based on information of a virtual service recorded in the searched session maintenance table if the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name; the information of the virtual service comprises IP addresses of a plurality of virtual services obtained by first requesting to analyze the domain name by a client which belongs to the same network segment as the source IP address;
And the return unit is used for sending the response message to the client.
The disclosure also provides an electronic device, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;
The memory stores machine readable instructions and the processor performs the method by invoking the machine readable instructions.
The present disclosure also provides a machine-readable storage medium storing machine-readable instructions that, when invoked and executed by a processor, implement the above-described methods.
By the above way, through recording a plurality of virtual service IP address resources which are firstly distributed for the client in a certain network segment in the table entry, when the domain name resolution request which is from the same network segment and aims at the same domain name is received, if the session maintaining table entry which belongs to the same network segment with the source IP address and has the same domain name as the domain name is searched, a response message is constructed based on the IP addresses of a plurality of virtual services which are recorded in the searched session maintaining table entry and are obtained by the client which belongs to the same network segment with the source IP address and firstly requests to resolve the domain name, and the response message is sent to the client. Accordingly, the client can obtain a plurality of virtual service resources corresponding to the first domain name resolution request of the same network segment client aiming at the same domain name in each domain name resolution request. Compared with the implementation mode that only the first virtual service resource is sent to the client under the session maintaining function, on one hand, the method and the device increase the number of the virtual service resources obtained after the client sends the domain name resolution request, enlarge the selection range of the client to the virtual service, and enhance the service experience flexibility; on the other hand, when part of virtual service resources (such as the IP address of the first virtual service) are unavailable, the client can select other available virtual service resources from the obtained virtual service resources, so that single-point faults are effectively avoided, disaster recovery capacity and resource utilization efficiency of the whole network service are improved, and high availability of the service is ensured.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a domain name resolution method according to an exemplary embodiment;
FIG. 2 is a schematic diagram of a domain name resolution process shown in an exemplary embodiment;
FIG. 3 is a hardware block diagram of an electronic device in which a domain name resolution device is located, as shown in an exemplary embodiment;
fig. 4 is a block diagram of a domain name resolution device, as shown in an exemplary embodiment.
Detailed Description
In order to make the technical solutions in the present specification better understood by those skilled in the art, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.
It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.
In the current network technology field, domain name resolution (Domain NAME SYSTEM, DNS) service is tightly combined with session maintenance technology, and supports efficient service access and resource scheduling in complex network environments. Specifically, when the DNS server receives a domain name resolution request sent by the client, the DNS server not only resolves the domain name to a corresponding IP address, but also performs session maintenance processing according to the source IP address carried in the request. Session maintenance processing is a mechanism that combines DNS services with load balancing policies in network technology. When a DNS server receives a domain name resolution request, not only does the domain name to IP address translation proceed, but a session hold table entry is created or looked up based on the request source IP address, associating the request to a particular virtual service resource. This process is intended to ensure that clients from the same network subnet or IP segment can obtain a consistent and continuous service experience when subsequently accessing the same domain name.
For example, when a client whose IP address belongs to 192.168.1.0/24 segments initiates a domain name resolution request to the DNS server for the first time, the DNS server selects a set of back-end server IP addresses, e.g., 10.0.0.1, 10.0.0.2, and 10.0.0.3, according to a preset load balancing policy, and returns the set of IP addresses to the client as response contents. Meanwhile, the DNS server records association information between this network segment (192.168.1.0/24) and the selected plurality of virtual services (e.g., 10.0.0.1, 10.0.0.2, and 10.0.0.3) in a session maintenance table maintained therein.
Subsequently, if other clients from the same network segment (192.168.1.0/24) initiate domain name resolution requests for the same domain name (inter.app.service.com), after the DNS server retrieves the corresponding session maintenance table entry, the DNS server uses the first IP address resource (10.0.0.1) in the IP address group allocated before to construct a DNS response packet, so as to achieve the purpose of session maintenance, and ensure that clients in the same network area enjoy consistent service resource allocation.
It can be seen that, in the above embodiment, the first server resource (such as an IP address) allocated when providing the first query to the domain name resolution request from the same network segment to the same domain name is generally based on the first DNS query result, this may cause that, in the subsequent domain name resolution request from the same network segment to the same domain name, even if the state of the back-end server resource changes (such as the server is down or the load is too high), the client cannot switch to other available servers in time, thereby affecting the continuity and stability of the service.
In view of this, the present specification aims to propose a technical solution for obtaining a resource resolution result consistent with a first request by a domain name resolution request under a session maintenance function.
When the method is realized, firstly, a domain name resolution request sent by a client is received, the domain name resolution request comprises a source IP address and a domain name needing to be accessed, and then, a session maintaining table item which is that the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name is searched; further, if the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the session maintenance table item of the domain name, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded in the searched session maintenance table item, and sending the response message to the client; the information of the virtual service includes IP addresses of a plurality of virtual services obtained by analyzing the domain name, wherein the client side belonging to the same network segment as the source IP address first requests the client side to analyze the domain name.
For example, a domain name resolution request sent by the client to an internal application server (e.g., intranet. App. Server. Com) of the enterprise is received, where the domain name resolution request includes a source IP address 192.168.1.1 of the client itself and a domain name intranet. App. Server. Com that needs to be accessed. 192.168.1.1 is located in the network segment 192.168.1.1 to 192.168.1.254, and searches the session maintaining list item which belongs to the same network segment as the source IP address 192.168.1.1 and has the same requested domain name as the requested domain name of the present time. If the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded in the searched session maintenance table (including the IP addresses of a plurality of virtual services obtained by the client side, i.e. 10.0.0.1, 10.0.0.2 and 10.0.0.3, of which the source IP address 192.168.1.1 belongs to the same network segment, for the first time) and sending the response message to the client side.
In one possible implementation manner, the technical solution of the present disclosure may be applied to a domain name resolution function on a network service system, such as a DNS server or a load balancing device, and the disclosure is not limited to this regarding the object of applying the solution.
By the above way, through recording a plurality of virtual service IP address resources which are firstly distributed for the client in a certain network segment in the table entry, when the domain name resolution request which is from the same network segment and aims at the same domain name is received, if the session maintaining table entry which belongs to the same network segment with the source IP address and has the same domain name as the domain name is searched, a response message is constructed based on the IP addresses of a plurality of virtual services which are recorded in the searched session maintaining table entry and are obtained by the client which belongs to the same network segment with the source IP address and firstly requests to resolve the domain name, and the response message is sent to the client. Accordingly, the client can obtain a plurality of virtual service resources corresponding to the first domain name resolution request of the same network segment client aiming at the same domain name in each domain name resolution request. Compared with the implementation mode that only the first virtual service resource is sent to the client under the session maintaining function, on one hand, the method and the device increase the number of the virtual service resources obtained after the client sends the domain name resolution request, enlarge the selection range of the client to the virtual service, and enhance the service experience flexibility; on the other hand, when part of virtual service resources (such as the IP address of the first virtual service) are unavailable, the client can select other available virtual service resources from the obtained virtual service resources, so that single-point faults are effectively avoided, disaster recovery capacity and resource utilization efficiency of the whole network service are improved, and high availability of the service is ensured.
The present disclosure is described below with reference to specific embodiments and specific application scenarios.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating a domain name resolution method according to an exemplary embodiment. The method may perform the steps of:
step 102: and receiving a domain name resolution request sent by the client, wherein the domain name resolution request comprises a source IP address and a domain name to be accessed.
For example, a domain name resolution request sent by the client for the intranet app. Server. Com is received, where the domain name resolution request includes the source IP address 192.168.1.1 of the client itself and the domain name intranet app. Server.
In some embodiments, the domain name resolution request may include DNS query instructions, and the client initiates the domain name resolution request to translate the human-readable domain name that is easy to remember into a machine-recognizable internet protocol address (Internet Protocol Address, IP address for short). The domain name that needs to be accessed is the name of the website or service that the user wishes to access through a web browser or other application, such as "www.123456.com". The domain name is a logical addressing mode on the Internet, so that people can conveniently memorize and access Internet resources. In actual network communications, the client device must translate the domain name to a specific IP address to establish an active connection.
In some embodiments, the domain name that needs to be accessed may also be described as a domain name that needs DNS domain name resolution.
Step 104: and searching a session maintaining table item of which the recorded IP address belongs to the same network segment as the source IP address and the recorded requested domain name is the same as the domain name.
For example, the domain name resolution request includes the network segments 192.168.1.1, 192.168.1.1 and 192.168.1.254 of the source IP address of the client, and searches the session maintaining table item which is the same as the requested domain name and the requested domain name, i.e. the internet protocol, app.server.com, in the same network segment as the source IP address 192.168.1.1.
Before searching the session maintaining table entry, it is generally required to query whether the domain name requested to be resolved in the domain name resolution request is a resolvable domain name preconfigured by the domain name resolution system, if not, the request is submitted to other services for processing, and if so, the searching is continued. The source IP address reflects the location information from which the request originated, and in TCP/IP network communications, the source IP address is sent as part of the header of the data with each request so that the domain name resolution system can identify and respond to the source of the request. In CIDR (CLASSLESS INTER-Domain Routing), segments 192.168.1.1 through 192.168.1.254 may also be denoted as 192.168.1.0/24, with "/24" representing the network prefix length of the IP address, i.e., the IP address is 32 bits total, with 24 bits identifying the network portion and the remaining 8 bits identifying the host portion. The present specification does not limit the method of representing the network segment.
The session maintaining table entry is a data structure maintained by a network service system (such as a DNS server or a load balancing device) for implementing a session maintaining function, and is used for recording interaction history information of a client and a server, including an IP address of the client, a domain name of a request, an allocated service resource (such as an IP address and a port number of a virtual service), a validity period of the session, and the like. By maintaining the session hold table entry, the network service system can ensure that clients continue to communicate with the same server during one session to implement the session hold function.
Step 106: if the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded in the searched session maintenance table (including the IP addresses of a plurality of virtual services obtained by the client side, i.e. 10.0.0.1, 10.0.0.2 and 10.0.0.3, of which the source IP address 192.168.1.1 belongs to the same network segment, for the first time) and sending the response message to the client side.
For example, the domain name resolution request includes a session maintenance table entry in which the source IP addresses of the clients are 192.168.1.1, 192.168.1.1 and 192.168.1.254, and if the client with the IP address of 192.168.1.2 is found to request domain name resolution for the domain name intranet.app.server.com, the client with the IP address of 192.168.1.2 recorded in the session maintenance table entry first requests to resolve the domain name intranet.app.server.com, and then constructs a response message, and sends the constructed response message to the client.
The process of constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded in the searched session maintaining table entry and sending the response message to the client is approximately as follows: firstly, according to the source IP address in the domain name resolution request and the domain name to be resolved, searching whether a matching record exists in the session maintaining list item. If there is a record which belongs to the same network segment as the source IP address and is the same as the domain name requested to be resolved, the information of the recorded virtual service is extracted from the searched session maintaining table entry, and the record generally comprises the IP address and port number of one or more groups of virtual services. The number of virtual services may be one or more, and the present specification does not limit the number of virtual services. The IP addresses are available server resources allocated according to a load balancing strategy when the client side of the same network segment first requests to resolve the same domain name. These IP addresses are then encapsulated in DNS response messages as a result of domain name resolution. The DNS response message typically includes additional content, such as a resource record type and a TTL (Time to Live), where the resource record type is used to indicate whether the IP address in the response message is an IPv4 address or an IPv6 address, and the Time to Live defines the Time that the DNS record survives in the DNS cache. The present specification does not limit the content of the DNS response message. And finally, sending the constructed response message back to the client side initiating the domain name resolution request through the network. After receiving the response, the client establishes connection with the server according to the IP address provided in the DNS response message, thereby realizing subsequent service request and data exchange.
In one embodiment shown, the method further comprises: if the recorded IP address and the source IP address belong to the same network segment and the recorded session maintaining list item of the requested domain name and the domain name are the same, selecting virtual service according to a load balancing algorithm, constructing a response message corresponding to the domain name resolution request based on the information of the selected virtual service, and sending the response message to the client.
For example, the domain name resolution request includes the source IP addresses 192.168.1.1, 192.168.1.1 of the client, and the network segments 192.168.1.1 to 192.168.1.254, if no session maintenance list item recorded that the client with the IP address being the range of the network segment has requested domain name resolution for the domain name intranet.app.server.com is found, a virtual service is selected according to the load balancing algorithm, for example, the IP addresses of the selected virtual service are 10.0.0.4, 10.0.0.5 and 10.0.0.6, a response message is constructed based on the IP addresses 10.0.0.4, 10.0.0.5 and 10.0.0.6 of the selected virtual service, and the constructed response message is sent to the client.
In the above embodiment, when the system does not find the session maintenance table entry matching the source IP address and domain name of the client request, a set of virtual service resources (for example, virtual services with IP addresses of 10.0.0.4, 10.0.0.5 and 10.0.0.6) are selected according to the load balancing algorithm, and then DNS response messages are constructed according to the information of these virtual services, and the response messages are sent to the client. The purpose of this is to ensure that even if no session maintenance record exists, the client can be provided with services in a dynamic allocation manner, and to ensure efficient utilization of service resources and high availability of the system.
The load balancing algorithm is a network service technology, and distributes client requests to a plurality of virtual services or back-end servers through a preset strategy so as to balance loads among the servers and improve availability and response speed of the system. The load balancing algorithm includes a polling algorithm, a weighted polling algorithm, a minimum connection algorithm, a weighted minimum connection algorithm, and the like. The source IP address refers to the IP address of the client device in the network that originated the domain name resolution request. The network segment represents all available IP addresses within the same subnet. Virtual services are a logical abstraction of the actual backend server, which is not a real physical server, but rather a virtualized service entity created by the load balancing system for purposes of traffic distribution and management. In this specification, a virtual service is a resource record contained in a load balancing device, and mainly consists of an IP address and a port, and these information are returned to a client as a value of the resource record in a DNS response message. The response message refers to a data packet which is generated and returned after the DNS server receives the domain name resolution request of the client and contains the IP address corresponding to the request domain name and other resource records.
In one embodiment shown, the method further comprises: creating a session maintaining table item corresponding to the source IP address, wherein the session maintaining table item records the source IP address, a domain name to be accessed and information of a virtual service selected for the source IP address; wherein the information of the virtual service includes an IP address of the virtual service.
For example, when the DNS server receives a client initiated domain name resolution request from IP address 192.168.1.1, requesting resolution of the domain name "inter.app.server.com", if a session hold table entry for the domain name within the network segment (192.168.1.0/24) does not already exist, the DNS server will select a set of virtual service IP addresses, such as 10.0.0.4, 10.0.0.5 and 10.0.0.6, from available back-end server resources according to a preset load balancing algorithm (e.g., a polling algorithm). The DNS server then creates a new session hold table entry that records the source IP address 192.168.1.1, the domain name "inter-net.app.service.com" that needs to be accessed, and the information of the virtual service selected for the source IP address, i.e., IP addresses 10.0.0.4, 10.0.0.5, and 10.0.0.6.
In the above embodiment, the DNS server constructs a DNS response message based on the IP address of the virtual service, and sends the response message to the client (e.g., the client). Therefore, the subsequent domain name resolution request from the same source IP address can quickly respond according to the established session maintenance list item, and a load balancing algorithm is not required to be executed each time to select a new virtual service, so that the domain name resolution speed and the stability of network services are improved. Meanwhile, the mechanism also ensures that the same client can continuously access the same back-end service resource within a period of time, thereby being beneficial to realizing session persistence and keeping service consistency.
Stored in the session hold table entry is an index of the virtual service configuration, through which the technician can find virtual service related information, such as the IP address of the virtual service. The information of the virtual service typically includes the IP address and port number of the virtual service because the core content of the DNS response message is to map the requested domain name to one or more IP addresses. The DNS response message can theoretically be constructed from only the IP address, but this can lead to inaccuracy in the connection of the service unless the standard port for the service is used by default. In certain situations, the specific service needs to be specified precisely through a port number, and in such situations, when constructing a DNS response message, it is likely that both the IP address of the virtual service and the port number of the virtual service will be used, so that it is ensured that the client can accurately establish a connection with the background service. In addition, record priorities, weights, survival durations, etc. may also be required to construct DNS response messages. In addition to the IP address of the virtual service, the present specification does not limit what is needed to construct DNS response messages.
In one embodiment shown, the method further comprises: if the virtual services recorded in the session maintaining list item pass the health status check, and the IP address currently used by the virtual services recorded in the session maintaining list item is matched with the IP address recorded in the session maintaining list item, the session maintaining list item is valid; the IP address of the virtual service currently used recorded in the session maintaining table entry is obtained through service state monitoring or configuration information query.
For example, there is a session maintenance table in the DNS server, which records information of virtual services allocated when the client with the source IP address of 192.168.1.1 has requested resolution of the domain name "intranet.app.service.com", including the IP address of 10.0.0.1. Upon receiving the new domain name resolution request, the DNS server first checks the session hold table entry, confirming that the virtual service (IP address 10.0.0.1) recorded in the session hold table entry passes the health check, i.e., the virtual service is still currently online and can normally respond to the client request. The DNS server then verifies that the IP address currently actually used by the virtual service is still 10.0.0.1. If the above conditions are satisfied, the session hold table entry is determined to be still valid.
Wherein, if the virtual service recorded in the session maintaining table entry is divided into virtual service groups, it is necessary to perform health status check on the virtual service group in which the virtual service is located. Because the individual services within a virtual service group may be redundant configurations, any one or more of the services may present problems, and the entire service group may continue to maintain continuity and availability of services as long as there are healthy service instances within the group.
The IP address actually used by the virtual service can be obtained through a real-time service state monitoring system or can be obtained by inquiring from a service configuration information center. The following three approaches are mainly obtained from a real-time service state monitoring system: the first is heartbeat detection, i.e. the load balancer or management system periodically sends heartbeat probe messages to the virtual service, indicating that it is also providing service using the IP address if the virtual service can respond correctly. Second is network traffic monitoring, i.e., collecting traffic data into and out of the virtual service IP address by a network monitoring tool or device, if persistent network traffic is observed, it can be inferred that the virtual service is still using the IP address. Third is log analysis, i.e. by analyzing the log file of the virtual service, to see if there is a request and response record associated with the IP address, to confirm if the service is using the IP address normally. The following two approaches are mainly used for querying from the service configuration information center: the first is that the virtual service is acquired by the service registry, and the service information including the IP address and the port is actively registered in the service registry when the virtual service is started. When a service configuration change (e.g., an IP address change) occurs, the service updates registration information. The load balancer may acquire the latest service configuration information from the service registry to thereby verify whether the virtual service is still using the IP address recorded in the session hold table entry. Second, read system configuration files, system administrators change the configuration files of virtual services, such as changing the IP address of the service binding, either manually or through automation tools. Subsequently, it is possible to verify whether the IP address currently used by the virtual service is consistent with the record in the session maintenance table entry by reading the latest configuration file.
In one embodiment shown, the method further comprises: if the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the session maintaining table item of the domain name, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded by the searched session maintaining table item, including: if the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name, and the session maintaining list item is determined to be effective, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded by the searched session maintaining list item.
For example, there is a session maintenance table in the DNS server, which records information of virtual services allocated when the client with the source IP address of 192.168.1.1 has requested resolution of the domain name "intranet.app.service.com", including the IP address of 10.0.0.1. When receiving that the new domain name resolution request matches the session maintenance table entry, the DNS server first checks the session maintenance table entry, and after confirming that the session maintenance table entry is still valid, can directly construct a DNS response message based on the information (IP address 10.0.0.1) of the virtual service in the table entry, and send the message to the client 192.168.1.1.
Wherein if the session hold table entry is not confirmed to be valid, the system performs at least one of the following operations according to a preset policy: first, the load balancing algorithm is re-executed: the DNS server does not rely on the session maintenance table entry any more, and instead reselects one or more virtual services according to the current load balancing policy, and constructs a DNS response message based on the information of the newly selected virtual service. Second, update session hold table entry: and the DNS server updates the session maintaining table entry according to the latest virtual service resource configuration, and constructs a response message based on the updated information. Thirdly, querying a DNS authoritative server: if the session maintaining list item is invalid and the virtual service cannot be redistributed locally, the DNS server can initiate a query request to the DNS authoritative server, obtain the latest domain name resolution result and construct a response message according to the information returned by the authoritative server. Fourth, notify the client to retry or use the standby resource: the DNS server informs the client that the current session remains inactive and recommends that the client reinitiate a domain name resolution request or attempt to connect to other known available virtual service resources. Through the operation modes, even if the session keeping list item is invalid, the session keeping list item can timely react, reliable service response is provided for the client, and meanwhile, the continuity of service and the effective allocation of resources are considered.
In one embodiment shown, the virtual services are located in a virtual service group, the selecting the virtual services according to a load balancing algorithm comprising: selecting a virtual service group from a virtual service list according to a load balancing algorithm configured by the domain name, wherein the virtual service group comprises at least one virtual service; and selecting a specified number of virtual services from the at least one virtual service according to a load balancing algorithm configured by the virtual service group.
For example, a load balancing policy is configured in the DNS server, which maps its requests to predefined virtual service groups a according to the characteristics of the domain name "intranet.app.service.com". The virtual service group a includes a plurality of virtual service resources, such as three virtual servers with IP addresses of 10.0.0.1, 10.0.0.2 and 10.0.0.3, respectively. When receiving a domain name resolution request of a client to a domain name of 'intranet.app.server.com', the DNS server first retrieves and locks the virtual service group a from the virtual service list according to a load balancing algorithm configured by the domain name. Then, according to the configuration of the virtual service group A, such as a polled load balancing algorithm, virtual service resources with a designated number of one are selected from the virtual service group A when the request is first requested, such as selecting an IP address of 10.0.0.1 as the content of a response message, and selecting an IP address of 10.0.0.2 when the request is second requested, and so on, the balanced distribution of service requests in the virtual service group is ensured, and the service availability and response speed are effectively improved.
Wherein a virtual service group typically represents a set of server resources that provide the same service or function, the virtual service group contains one or more virtual services that provide services externally as a whole and can be uniformly managed and scheduled by a load balancing policy. The load balancer typically performs traffic distribution according to the overall situation of the virtual service group (such as the load, health, etc. of each service instance). Load balancing policies are an important means in network services for distributing network traffic to achieve server resource optimization and high availability. Common load balancing strategies include, but are not limited to, the following: polling, weighted polling, minimum number of connections, weighted minimum number of connections. The present description does not limit this to the choice of load balancing strategy.
In one embodiment shown, the method further comprises: aging detection is carried out on the session maintaining table item in the effective state; and deleting the session maintaining table entries meeting the aging condition.
For example, in a DNS server system, all active session hold entries are checked for aging periodically or each time a new domain name resolution request is processed. The aging condition may be based on a time interval, e.g., a session hold table entry records information of virtual services assigned when a client with a source IP address of 192.168.1.1 requests resolution of the domain name "inter.app.service.com". If an hour has passed since the last update of the entry (assuming a preset aging period of 1 hour), the system automatically detects this aging and deletes the session hold entry.
The aging condition includes, but is not limited to, the following four cases, and when any one of them is satisfied, the session maintenance table entry is considered to satisfy the aging condition and needs to be deleted. The aging conditions include four cases: firstly, the difference between the current time and the last updated time recorded by the table item exceeds the aging time, wherein the last updated time recorded by the table item is used for representing the time when the table item is created or the time when the table item is updated after being searched last time; second, the session hold table entry is marked as an entry that needs to be deleted; thirdly, deleting the configuration information of the domain name recorded in the session maintaining table item; fourth, the domain name recorded in the session hold table entry is disabled from the session hold function. The meaning of deleting the aging session maintaining list item is that the system resource is released, the long-term unused session is prevented from occupying excessive storage space, the follow-up domain name resolution request can be ensured to carry out load balancing and domain name resolution again according to the latest service resource allocation strategy and server state, and further the effective utilization of the service resource and the overall system performance are ensured.
In this embodiment, please refer to fig. 2, fig. 2 is a schematic diagram of a domain name resolution process shown in an exemplary embodiment, and the technical solution in this specification can be intuitively shown by the following process schematic diagram.
When the technical scheme disclosed by the disclosure starts, firstly, a domain name resolution request sent by a client is received, whether a session maintaining table item which has requested the same domain name exists in the session maintaining table item belonging to the same network segment with the client is searched, if so, a response message corresponding to the domain name resolution request is constructed based on the information of the virtual service recorded in the searched session maintaining table item, and the response message is sent to the client. If not, selecting a virtual service group according to a load balancing algorithm configured by a domain name, selecting virtual service according to the load balancing algorithm configured by the virtual service group, creating a session maintaining list item according to the selected virtual service, and recording information including an IP address (namely a source IP address) of a client, a domain name to be accessed and an IP address of the virtual service selected for the source IP address; and finally, constructing a response message according to the information of the selected virtual service and returning the response message to the client.
Corresponding to the embodiment of the domain name resolution method, the present specification also provides an embodiment of a domain name resolution device.
Referring to fig. 3, fig. 3 is a hardware configuration diagram of an electronic device where a domain name resolution device is shown in an exemplary embodiment. At the hardware level, the device includes a processor 302, an internal bus 304, a network interface 306, memory 308, and non-volatile storage 310, although other hardware requirements are possible. One or more embodiments of the present description may be implemented in a software-based manner, such as by the processor 302 reading a corresponding computer program from the non-volatile storage 310 into the memory 308 and then running. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.
Referring to fig. 4, fig. 4 is a block diagram illustrating a domain name resolution device according to an exemplary embodiment. The domain name resolution device can be applied to the electronic equipment shown in fig. 3 to realize the technical scheme of the specification. The apparatus may include:
a receiving unit 402, configured to receive a domain name resolution request sent by a client, where the domain name resolution request includes a source IP address and a domain name that needs to be accessed;
A searching unit 404, configured to search a session maintenance table entry in which the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name;
a first construction unit 406, configured to, if a session maintenance table entry in which the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name is found, construct a response message corresponding to the domain name resolution request based on information of a virtual service recorded in the found session maintenance table entry; the information of the virtual service comprises IP addresses of a plurality of virtual services obtained by first requesting to analyze the domain name by a client which belongs to the same network segment as the source IP address;
and a return unit 408, configured to send the response message to the client.
In this embodiment, the apparatus further includes:
And the second construction unit is used for selecting virtual service according to a load balancing algorithm if the recorded IP address and the source IP address belong to the same network segment and the recorded session maintaining table item with the same requested domain name and the domain name are not found, constructing a response message corresponding to the domain name resolution request based on the information of the selected virtual service, and sending the response message to the client.
In this embodiment, the apparatus further includes:
A creating unit, configured to create a session maintenance table entry corresponding to the source IP address, where the session maintenance table entry records the source IP address, a domain name to be accessed, and information of a virtual service selected for the source IP address; wherein the information of the virtual service includes an IP address of the virtual service.
In this embodiment, the apparatus further includes:
A determining unit, configured to, if all virtual services recorded in the session keeping table entry pass the health status check, and an IP address currently used by the virtual service recorded in the session keeping table entry matches an IP address recorded in the session keeping table entry, enable the session keeping table entry to be valid; the IP address of the virtual service currently used recorded in the session maintaining table entry is obtained through service state monitoring or configuration information query.
In this embodiment, the first building unit includes:
And the first construction subunit is used for constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded by the searched session holding table item if the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name and the session holding table item is determined to be valid.
In this embodiment, the second building unit includes:
the first selecting subunit is used for selecting a virtual service group from a virtual service list according to the load balancing algorithm configured by the domain name, wherein the virtual service group comprises at least one virtual service;
and the second selecting subunit is used for selecting a specified number of virtual services from the at least one virtual service according to a load balancing algorithm configured by the virtual service group.
In this embodiment, the apparatus further includes:
the detection unit is used for performing aging detection on the session maintaining table item in the effective state;
And the deleting unit is used for deleting the session maintaining table items meeting the aging condition.
The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are illustrative only, in that the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. The computer readable medium, as defined herein, does not include a transient client readable medium (transition medium), such as a modulated data signal and carrier wave.
User information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in this disclosure are both user-authorized or fully authorized information and data by parties, and the collection, use and processing of relevant data requires compliance with relevant laws and regulations and standards of relevant countries and regions, and is provided with corresponding operation portals for user selection of authorization or denial.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments 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. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" depending on the context.
The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.
Claims (10)
1. A method of domain name resolution, the method comprising:
Receiving a domain name resolution request sent by a client, wherein the domain name resolution request comprises a source IP address and a domain name to be accessed;
searching a session maintaining table item of which the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name;
If the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded in the searched session maintenance table, and sending the response message to the client;
The information of the virtual service includes IP addresses of a plurality of virtual services obtained by analyzing the domain name, wherein the client side belonging to the same network segment as the source IP address first requests the client side to analyze the domain name.
2. The method according to claim 1, wherein the method further comprises:
If the recorded IP address and the source IP address belong to the same network segment and the recorded session maintaining list item of the requested domain name and the domain name are the same, selecting virtual service according to a load balancing algorithm, constructing a response message corresponding to the domain name resolution request based on the information of the selected virtual service, and sending the response message to the client.
3. The method according to claim 2, wherein the method further comprises:
Creating a session maintaining table item corresponding to the source IP address, wherein the session maintaining table item records the source IP address, a domain name to be accessed and information of a virtual service selected for the source IP address; wherein the information of the virtual service includes an IP address of the virtual service.
4. A method according to claim 3, characterized in that the method further comprises:
if the virtual services recorded in the session maintaining list item pass the health status check, and the IP address currently used by the virtual services recorded in the session maintaining list item is matched with the IP address recorded in the session maintaining list item, the session maintaining list item is valid;
The IP address of the virtual service currently used recorded in the session maintaining table entry is obtained through service state monitoring or configuration information query.
5. The method according to claim 4, wherein if the session maintenance table item in which the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name is found, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded in the found session maintenance table item includes:
If the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name, and the session maintaining list item is determined to be effective, constructing a response message corresponding to the domain name resolution request based on the information of the virtual service recorded by the searched session maintaining list item.
6. A method according to claim 3, wherein the virtual services are located in a virtual service group, the selecting the virtual services according to a load balancing algorithm comprising:
Selecting a virtual service group from a virtual service list according to a load balancing algorithm configured by the domain name, wherein the virtual service group comprises at least one virtual service;
and selecting a specified number of virtual services from the at least one virtual service according to a load balancing algorithm configured by the virtual service group.
7. The method according to claim 1, wherein the method further comprises:
Aging detection is carried out on the session maintaining table item in the effective state;
And deleting the session maintaining table entries meeting the aging condition.
8. A domain name resolution device, the device comprising:
The receiving unit is used for receiving a domain name resolution request sent by the client, wherein the domain name resolution request comprises a source IP address and a domain name to be accessed;
A searching unit, configured to search a session maintenance table entry in which the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name;
A first construction unit, configured to construct a response message corresponding to the domain name resolution request based on information of a virtual service recorded in the searched session maintenance table if the recorded IP address and the source IP address belong to the same network segment and the recorded requested domain name is the same as the domain name; the information of the virtual service comprises IP addresses of a plurality of virtual services obtained by first requesting to analyze the domain name by a client which belongs to the same network segment as the source IP address;
And the return unit is used for sending the response message to the client.
9. An electronic device, comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;
The memory stores machine readable instructions, the processor executing the method of any of claims 1 to 7 by invoking the machine readable instructions.
10. A machine-readable storage medium storing machine-readable instructions which, when invoked and executed by a processor, implement the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410301855.1A CN118200286A (en) | 2024-03-15 | 2024-03-15 | Domain name resolution method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410301855.1A CN118200286A (en) | 2024-03-15 | 2024-03-15 | Domain name resolution method, device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118200286A true CN118200286A (en) | 2024-06-14 |
Family
ID=91404683
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410301855.1A Pending CN118200286A (en) | 2024-03-15 | 2024-03-15 | Domain name resolution method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118200286A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118869696A (en) * | 2024-07-08 | 2024-10-29 | 山石网科通信技术股份有限公司 | Network traffic processing method, device and electronic equipment |
-
2024
- 2024-03-15 CN CN202410301855.1A patent/CN118200286A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118869696A (en) * | 2024-07-08 | 2024-10-29 | 山石网科通信技术股份有限公司 | Network traffic processing method, device and electronic equipment |
| CN118869696B (en) * | 2024-07-08 | 2025-09-23 | 山石网科通信技术股份有限公司 | Network traffic processing method, device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11283715B2 (en) | Updating routing information based on client location | |
| EP2356577B1 (en) | Request routing and updating routing information utilizing client location information | |
| EP3391627B1 (en) | Shared multi-tenant domain name system (dns) server for virtual networks and corresponding method | |
| CN109302498B (en) | Network resource access method and device | |
| US9686158B1 (en) | Point to node in a multi-tiered middleware environment | |
| WO2013104172A1 (en) | Method for realizing load balancing, dns server, and client | |
| US10944714B1 (en) | Multi-factor domain name resolution | |
| CN111064804B (en) | Network access method and device | |
| CN110213365B (en) | User access request processing method based on user partition and electronic equipment | |
| CN111711716A (en) | A method, apparatus, device and readable storage medium for domain name resolution | |
| WO2017096888A1 (en) | Method and device for implementing domain name system | |
| US20070112812A1 (en) | System and method for writing data to a directory | |
| US8972604B1 (en) | Network address retention and assignment | |
| CN118200286A (en) | Domain name resolution method, device, electronic equipment and storage medium | |
| CN112532666A (en) | Reverse proxy method, apparatus, storage medium, and device | |
| CN108494870A (en) | Dynamic data loading method based on CDN and device | |
| CN114844670B (en) | IP address hiding method based on named network | |
| JP2000112908A (en) | Load balancing DNS system | |
| RU2427032C2 (en) | Next site for distributed service connections | |
| CN109302505B (en) | Data transmission method, system, device and storage medium | |
| CN116708366B (en) | DNS Domain Name Management Method and Device | |
| WO2016074150A1 (en) | Streamlining location-dependent dns configuration | |
| CN118301127A (en) | IP address resolution method, device, electronic equipment and readable storage medium | |
| WO2025008970A1 (en) | System and method of caching dns responses for application detection | |
| CN121441997A (en) | Microservice request methods, systems, microservice gateway devices, and electronic devices |
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 |