CN116938872A - Domain name resolution request processing method, device, medium and electronic equipment - Google Patents
Domain name resolution request processing method, device, medium and electronic equipment Download PDFInfo
- Publication number
- CN116938872A CN116938872A CN202210358383.4A CN202210358383A CN116938872A CN 116938872 A CN116938872 A CN 116938872A CN 202210358383 A CN202210358383 A CN 202210358383A CN 116938872 A CN116938872 A CN 116938872A
- Authority
- CN
- China
- Prior art keywords
- domain name
- private network
- network domain
- address information
- resolution 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
- 238000003672 processing method Methods 0.000 title claims description 14
- 238000012545 processing Methods 0.000 claims description 33
- 238000000034 method Methods 0.000 claims description 26
- 230000004044 response Effects 0.000 claims description 23
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 238000007689 inspection Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The disclosure provides a domain name resolution request processing method, a domain name resolution request processing device, a domain name resolution request processing medium and electronic equipment, and relates to the technical field of communication. The domain name resolution request processing method comprises the following steps: receiving a first domain name resolution request message sent by a user terminal, wherein the first domain name resolution request message comprises a domain name to be resolved; if the domain name to be resolved is a private network domain name, determining the address information of a target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table; generating a second domain name resolution request message according to the domain name to be resolved and the address information of the target private network domain name server, and sending the second domain name resolution request message to the target private network domain name server. The method and the device improve the reliability of the private network domain name server for processing the domain name resolution request message.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a domain name resolution request processing method, a domain name resolution request processing device, a computer readable storage medium, and an electronic device.
Background
With the development of mobile communication technology, a 5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) network has been widely used, and in a ul cl (up link classifier ) offloading scenario of the 5G network, a UE (User Equipment) may generally establish a PDU (Protocol Data Unit Session ) connection with an edge UPF (User Plane Function ) to process a domain name resolution request packet sent by the User terminal.
Wherein the SMF (Session Management Function ) may cause the UE to obtain the IP address (Internet Protocol Address ) of the large network DNS (Domain Name Server, domain name server) when the UE establishes a PDU session connection with the edge UPF. When the domain name of the large network needs to be resolved, the UE can send a domain name resolution request message to a DNS server of the large network through an edge UPF; however, when the private network domain name needs to be resolved, the user terminal cannot acquire the IP address of the private network DNS server, and the domain name resolution request message is the IP address of the large network DNS; when the edge UPF determines that the private network domain name needs to be resolved by the user, a certain address rewriting rule is needed to convert the IP address of the large network DNS into the IP address of the private network DNS so as to shunt the domain name resolution request message to the private network DNS for resolution.
However, the existing address rewriting rule can only rewrite the IP address of one private network DNS, and when the private network DNS supported by the address rewriting rule fails, the domain name resolution request message cannot be shunted to the private network DNS, so that the private network domain name resolution result cannot be obtained.
Disclosure of Invention
The disclosure provides a domain name resolution request processing method, a domain name resolution request processing device, a computer readable storage medium and electronic equipment, so that reliability of processing a domain name resolution request message is improved.
According to a first aspect of the present disclosure, there is provided a domain name resolution request processing method, including:
receiving a first domain name resolution request message sent by a user terminal, wherein the first domain name resolution request message comprises a domain name to be resolved;
if the domain name to be resolved is a private network domain name, determining the address information of a target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table;
generating a second domain name resolution request message according to the domain name to be resolved and the address information of the target private network domain name server, and sending the second domain name resolution request message to the target private network domain name server.
According to a second aspect of the present disclosure, there is provided a domain name resolution request processing apparatus, including:
the receiving module is configured to receive a first domain name resolution request message sent by a user terminal, wherein the first domain name resolution request message comprises a domain name to be resolved;
the determining module is configured to determine the address information of the target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table if the domain name to be resolved is the private network domain name;
the sending module is configured to generate a second domain name resolution request message according to the domain name to be resolved and the address information of the target private network domain name server, and send the second domain name resolution request message to the target private network domain name server;
according to a third aspect of the present disclosure there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the method of the first aspect.
According to a fourth aspect of the present disclosure, there is provided an electronic device comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the method of the first aspect via execution of the executable instructions.
The technical scheme of the present disclosure has the following beneficial effects:
the method, the device, the medium and the electronic equipment for processing the domain name resolution request can receive a first domain name resolution request message sent by a user terminal, wherein the first domain name resolution request message comprises a domain name to be resolved; if the domain name to be resolved is a private network domain name, determining the address information of a target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table; generating a second domain name resolution request message according to the domain name to be resolved and the address information of the target private network domain name server, and sending the second domain name resolution request message to the target private network domain name server. The problem that the domain name processing request cannot be processed under the condition of failure of the private network domain name server in the process of processing the domain name request by utilizing the single private network domain name server can be prevented, and the reliability of processing the domain name resolution request message by the private network domain name server is further improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely some embodiments of the present disclosure and that other drawings may be derived from these drawings without undue effort.
Fig. 1 is a schematic diagram showing a structure of a domain name resolution request processing system in the present exemplary embodiment;
fig. 2 is a flowchart showing a domain name resolution request processing method in the present exemplary embodiment;
FIG. 3 is a schematic diagram of the splitting logic of a first domain name resolution request message in the present exemplary embodiment;
FIG. 4 is a schematic diagram of the splitting logic of another first domain name resolution request message in the present exemplary embodiment;
fig. 5 is an interactive flowchart showing a domain name resolution request processing method in the present exemplary embodiment;
fig. 6 is a schematic diagram showing a structure of a domain name resolution request processing apparatus in the present exemplary embodiment;
fig. 7 shows a schematic structural diagram of an electronic device in the present exemplary embodiment.
Detailed Description
Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. One skilled in the relevant art will recognize, however, that the aspects of the disclosure may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only and not necessarily all steps are included. For example, some steps may be decomposed, and some steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
The application scenario of the domain name resolution request processing method provided by the embodiment of the disclosure includes, but is not limited to, a 5G customized network neighbor mode, that is, a scenario in which a user terminal needs to resolve a large network domain name and a private network domain name when an edge UPF provides communication services for both a private network and a large network. The edge UPF can receive a first domain name resolution request message sent by the user terminal, wherein the first domain name resolution request message comprises a domain name to be resolved; if the domain name to be resolved is a private network domain name, determining the address information of a target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table; generating a second domain name resolution request message according to the domain name to be resolved and the address information of the target private network domain name server, and sending the second domain name resolution request message to the target private network domain name server. The private network domain name servers can provide services for the private network domain name resolution, and the reliability of the private network domain name servers for processing the domain name resolution request message is improved.
Fig. 1 is a schematic structural diagram of a domain name resolution request processing system according to an embodiment of the present disclosure. As shown in fig. 1, the domain name resolution request processing system includes: UE100, gNB (5G base station) 101, edge UPF 102, large network UPF 103, large network primary DNS server 104, large network backup DNS server 105, private network primary DNS server 106, private network backup DNS server 107 (backup). The UE100 is connected to the UPF 102 through the gNB 101, the UPF 102 is connected to the UE100 through the N3 interface, the UPF 102 is connected to the UPF 103 through the N9 interface, the UPF 103 is connected to the DNS server 104 and the DNS server 105 through the N6 interface, and the UPF 102 is connected to the DNS server 106 and the DNS server 107 through the N6 interface. Where the large network is the internet and the private network is a communication network of a specific institution, such as an enterprise or government communication network.
It should be noted that fig. 1 is only a schematic diagram, and in practical application, a large network may include an application server and at least one DNS server, for example, a large network may include one primary DNS server and three backup DNS servers; the private network may also include an application server and at least one DNS server, and in the context of the disclosed embodiments, is illustrated with a large network including two DNS servers and a private network including two DNS servers. Wherein the application servers in private and large networks are not shown in fig. 1.
In the embodiment of the present disclosure, the technical solution of the present disclosure is illustrated by using the edge UPF as the execution body.
Fig. 2 is a schematic diagram of a domain name resolution request processing method according to an embodiment of the present disclosure, where the domain name resolution request processing method may be applied to the edge UPF shown in fig. 1, and as shown in fig. 2, the method includes steps S201 to S203 described below, including:
step S201, a first domain name resolution request message sent by a user terminal is received.
In the embodiment of the present disclosure, the first domain name resolution request packet includes a domain name to be resolved.
Step S202, if the domain name to be resolved is a private network domain name, determining the address information of a target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table;
step S203, a second domain name resolution request message is generated according to the domain name to be resolved and the address information of the target private network domain name server, and the second domain name resolution request message is sent to the target private network domain name server.
In summary, in the domain name resolution request processing method provided in the embodiments of the present disclosure, after receiving a first domain name resolution request packet sent by a user terminal, when determining that a domain name to be resolved therein is a private network domain name, determining, at a plurality of private network domain servers, that a target private network domain server processes the domain name resolution request packet according to a pre-established splitting rule table; the realization scheme for shunting the domain name resolution request messages by a plurality of private network domain name servers can prevent the problem that the domain name resolution request cannot be processed under the condition of the failure of the private network domain name servers in the process of processing the domain name request by utilizing a single private network domain name server, and further improves the reliability of the private network domain name server in processing the domain name resolution request messages.
Each step in fig. 2 is described in detail below:
in step S201, the edge UPF receives a first domain name resolution request message sent by the user terminal.
In the embodiment of the present disclosure, the first domain name resolution request message sent by the user terminal may include a domain name to be resolved, where the domain name to be resolved may be a large network domain name or a private network domain name. It should be noted that, the first domain name resolution request message is used for requesting the large network domain name server to resolve the domain name to obtain the address of the large network application server, or requesting the private network domain name server to resolve the domain name to obtain the address of the private network application server, where the large network domain name server is used for resolving the large network domain name, and the private network domain name server is used for resolving the private network domain name; the address of the application server may be an IP address of the application server.
It should be noted that, in an embodiment, before executing the step S201, the ue may first establish a PDU session to the edge UPF through the SMF to obtain an address of a domain name server of the large network, and then the ue may send a domain first domain name resolution request message to the edge UPF.
In the embodiment of the present disclosure, the address of the domain name server may be an IP address, or may be another address that may be uniquely identified, which is not specifically limited in the embodiment of the present disclosure.
In an alternative embodiment, in the step S201, the edge UPF may receive a first domain name resolution request packet sent by the user terminal.
In an alternative embodiment, a DPI (Deep Packet Inspection, deep packet inspection technology) function module in the edge UPF may identify a request sent by the user terminal, and obtain a first domain name resolution request packet. Further, after the edge UPF receives the first domain name resolution request message sent by the user terminal, the first domain name resolution request message may be resolved to obtain a domain name to be resolved therein.
In step S202, if the edge UPF determines that the domain name to be resolved is a private network domain name, the address information of the target private network domain name server is determined from the address information of the plurality of private network domain name servers according to the pre-established splitting rule table.
In the embodiment of the disclosure, because the user terminal cannot acquire the address of the private network domain name server, when the user terminal needs to resolve the private network domain name, the edge UPF may select the target private network domain name server according to the splitting rule table after receiving the domain name resolution request message, and split the domain name resolution request message to the target private network domain name server for processing. The splitting rule table is used for recording the corresponding relation between a private network domain name server for resolving the private network domain name and a large network domain name server for resolving the private network domain name, so that after the edge UPF receives a first domain name resolving request message containing the private network domain name, a target private network domain name server is selected to resolve the private network domain name.
In an alternative embodiment, the edge UPF may also receive a shunting rule table configuration request before performing step S201 above; resolving the distribution rule table configuration request to obtain private network domain names, address information of a plurality of large network domain name servers associated with the private network domain names and address information of the private network domain name servers corresponding to the address information of each large network domain name server; generating a diversion rule table according to the private network domain name, the address information of a plurality of large network domain name servers and the address information of the private network domain name server corresponding to the address information of each large network domain name server; the address information may include an IP address and a port number, among others. The splitting rule table can be preconfigured in the edge UPF, so that after the first domain name resolution request message aiming at the private network domain name is received, the private network domain name resolution of the target private network domain name server can be rapidly determined according to the splitting rule table.
The splitting rule table may include a private network domain name field, an address field of a large network domain name server, a port number field of the large network domain name server, an address field of the private network domain name server, and a port number field of the private network domain name server. As shown in table 1, table 1 shows a branching rule table,
TABLE 1
The same row of the large network domain name servers and the private network domain name servers are a group of corresponding domain name servers, as shown in table 1, for the private network domain name 1, the address of the large network domain name server associated with the private network domain name 1 is IP1, the port number of the large network domain name server is 1, the address of the private network domain name server corresponding to the large network domain name server is IP3, and the port number of the private network domain name server corresponding to the large network domain name server is 3; when the address of the large network domain name server associated with the large network domain name 1 is IP2 and the port number 2 of the large network domain name server, the address of the special network domain name server corresponding to the large network domain name server is IP4 and the port number of the special network domain name server corresponding to the large network domain name server is 4.
It should be noted that, in the splitting rule table, the corresponding relationship between the large network domain name server and the private network domain name server associated with the private network domain name 2 and the private network domain name 3 … … private network domain name n may be further included, which is not limited in the embodiment of the present disclosure.
In an alternative embodiment, the process of determining whether the domain name to be resolved is a private network domain name by the edge UPF may include: comparing the domain name to be resolved with each private network domain name in the shunting rule table; if the private network domain name consistent with the domain name to be resolved exists, determining that the resolved domain name is the private network domain name; and if the private network domain name consistent with the domain name to be resolved does not exist, determining that the resolved domain name is a large network domain name. The splitting rule table can be utilized to rapidly determine whether the domain name to be resolved in the first domain name resolution request message is a private network domain name, so that the processing efficiency of the first domain name resolution request message is improved.
In an alternative embodiment, if the edge UPF determines that the domain name to be resolved is a private network domain name, the address information of the target private network domain name server may be determined from the address information of the plurality of private network domain name servers according to a pre-established splitting rule table.
The process of determining the address information of the target private network domain name server in the address information of the plurality of private network domain name servers by the edge UPF according to the pre-established splitting rule table may include: judging whether the first domain name resolution request message contains address information of a large network domain name server, if the first domain name resolution request message contains the address information of the large network domain name server, acquiring address information of a private network domain name server corresponding to the address information of the large network domain name server in a shunting rule table to acquire the address information of a target private network domain name server, and rapidly determining the target private network domain name server for resolving the private network domain name according to the private network domain name in the first domain name resolution request message and the address information of the large network domain name server in the shunting rule table; if the first domain name resolution request message does not contain the address information of the large-network domain name server, acquiring the address information of a private network main domain name server from the address information of a plurality of private network domain name servers in a shunting rule table to acquire the address information of a target private network domain name server; the method has the advantages that when the address information of the large-network domain name server in the domain name resolution request message is lost or the acquisition fails, a private network main domain name server is selected to be used for resolving the domain name to be resolved, so that the efficiency and the reliability of processing the domain name resolution request message are improved; or if the first domain name resolution request message does not contain the address information of the large-network domain name server, acquiring the address information of any private network domain name server from the address information of a plurality of private network domain name servers in the distribution rule table to acquire the address information of the target private network domain name server; any private network domain name server can be selected for analyzing the domain name to be analyzed under the condition that the address information of the large network domain name server in the domain name analysis request message is lost or the acquisition fails, so that the reliability of processing the domain name analysis request message is improved. In the embodiment of the present disclosure, in the splitting rule table, the identifier may be further configured to identify a main domain name server and a standby domain name server of the plurality of main domain name servers; and identifying the private network main domain name server and the private network standby domain name server in the plurality of private network domain name servers.
In step S203, the edge UPF may generate a second domain name resolution request packet according to the domain name to be resolved and the address information of the target private network domain name server, and send the second domain name resolution request packet to the target private network domain name server.
In an alternative embodiment, the process of generating the second domain name resolution request message by the edge UPF according to the domain name to be resolved and the address information of the target private network domain name server may include: and packaging the private network domain name and the address information of the target private network domain name server to obtain a second domain name resolution request message.
After the edge UPF sends the second domain name resolution request packet to the target private network domain name server, the target private network domain name server may resolve the private network domain name in the second domain name resolution request packet to obtain an address of the private network application server, where the address of the private network application server may be an IP address of the private network application server.
For example, assuming that the splitting rule table is shown in table 1, after the edge UPF receives the first domain name resolution request packet sent by the user terminal, the splitting logic of the first domain name resolution request packet may refer to fig. 3, where the address of the private network domain name server 301 is IP3, and the port number is 3; the address of the private network domain name server 302 is IP4, and the port number is 4; after the edge UPF receives the first domain name resolution request packet sent by the user terminal, it determines that the domain name to be resolved in the first domain name resolution request packet is a private network domain name 1, the address of the large network domain name server is IP2, the port number of the large network domain name server is 2, then it may determine that the address of the target private network domain name server is IP4 according to the splitting relation table shown in table 1, and the port number of the target private network domain name server is 4, then it may generate a second domain name resolution request packet according to the private network domain name 1, the address IP4 of the target private network domain name server, and the port number 4 of the target private network domain name server, and send the second domain name resolution request packet to the private network domain name server 302.
As another example, assuming that the splitting rule table is shown in table 1, after the edge UPF receives the first domain name resolution request packet sent by the user terminal, the splitting logic of the first domain name resolution request packet may refer to fig. 4, where the address of the private network domain name server 301 is IP3, and the port number is 3; the address of the private network domain name server 302 is IP4, and the port number is 4; after the edge UPF receives the first domain name resolution request packet sent by the user terminal, it determines that the domain name to be resolved in the first domain name resolution request packet is a private network domain name 1, then any private network domain name server may be selected according to the splitting relation table shown in table 1, for example, a private network domain name server with an address of IP3 and a port number of 4 is determined as a target private network domain name server, and a second domain name resolution request packet may be generated according to the private network domain name 1, the address IP3 of the target private network domain name server, and the port number 3 of the target private network domain name server, and the second domain name resolution request packet is sent to the private network domain name server 301.
In an alternative embodiment, after the edge UPF sends the second domain name resolution request packet to the target private network domain name server, the edge UPF may further: receiving a first domain name resolution response message sent by a target private network domain name server, wherein the first domain name resolution response message comprises an address of a private network application server and address information of the target private network domain name server; further, the edge UPF determines the address information of the large-network domain name server corresponding to the address information of the target private network domain name server according to the diversion rule table to obtain the address information of the target large-network domain name server; generating a second domain name resolution response message according to the address of the private network application server and the address information of the target large network domain name server, and sending the second domain name resolution response message to the user terminal so that the user terminal establishes connection with the private network application server according to the address of the private network application server. The edge UPF may send a domain name resolution response message carrying an address of the private network application server to the user terminal, where the target private network domain name server determines when the domain name resolution response message is received, and the target private network domain name server determines among the plurality of private network domain name servers after receiving the domain name resolution request message, so that reliability of the private network application server may be improved after the user terminal sends the domain name resolution request message.
For example, assuming that the splitting rule table is shown in table 1, the edge UPF receives a first domain name resolution response message sent by the target private network domain name server, where the first domain name resolution response message includes an address IP5 of the private network application server, an address IP3 of the target private network domain name server, and a port number 3, the edge UPF may determine, according to the splitting rule table, an address 1 and a port number 1 of the target large network domain name server, package the address IP5 of the private network application server, the address 1 and the port number 1 of the target large network domain name server, generate a second domain name resolution response message, and send the second domain name resolution response message to the user terminal.
As shown in fig. 5, fig. 5 shows an interactive flowchart of a domain name resolution request processing method according to an embodiment of the present disclosure, including the following steps S506 to S
Step S501, a user terminal sends a first domain name resolution request message to an edge UPF;
the first domain name resolution request message comprises a domain name to be resolved;
step S502, if the edge UPF determines that the domain name to be resolved is a private network domain name, determining the address information of a target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table;
in step S503, the edge UPF generates a second domain name resolution request message according to the domain name to be resolved and the address information of the target private network domain name server, and sends the second domain name resolution request message to the target private network domain name server.
Step S504, the target private network domain name server sends a first domain name resolution response message to the edge UPF;
the first domain name resolution response message comprises the address of the private network application server and the address information of the target private network domain name server;
step S505, the edge UPF determines the address information of the large-network domain name server corresponding to the address information of the target private network domain name server according to the diversion rule table to obtain the address information of the target large-network domain name server;
in step S506, the edge UPF generates a second domain name resolution response message according to the address of the private network application server and the address information of the target large network domain name server, and sends the second domain name resolution response message to the user terminal.
The embodiment of the present disclosure provides a domain name resolution request processing apparatus, as shown in fig. 6, a domain name resolution request processing apparatus 600 includes:
a receiving module 601, configured to receive a first domain name resolution request packet sent by a user terminal, where the first domain name resolution request packet includes a domain name to be resolved;
the determining module 602 is configured to determine, if the domain name to be resolved is a private network domain name, address information of a target private network domain name server from address information of a plurality of private network domain name servers according to a pre-established splitting rule table;
the sending module 603 is configured to generate a second domain name resolution request packet according to the domain name to be resolved and address information of the target private network domain name server, and send the second domain name resolution request packet to the target private network domain name server.
Optionally, the determining module 602 is configured to:
if the first domain name resolution request message contains the address information of the large network domain name server, the address information of the private network domain name server corresponding to the address information of the large network domain name server is obtained in the distribution rule table, and the address information of the target private network domain name server is obtained.
Optionally, the determining module 602 is configured to:
if the first domain name resolution request message does not contain the address information of the large network domain name server, the address information of the private network main domain name server is acquired from the address information of a plurality of private network domain name servers in the distribution rule table, and the address information of the target private network domain name server is acquired.
Optionally, the determining module 602 is configured to:
if the first domain name resolution request message does not contain the address information of the large-network domain name server, the address information of any private network domain name server is acquired from the address information of a plurality of private network domain name servers in the distribution rule table, and the address information of the target private network domain name server is obtained.
Optionally, as shown in fig. 5, the domain name resolution request processing apparatus 600 further includes a response processing module 604 configured to:
receiving a first domain name resolution response message sent by a target private network domain name server, wherein the first domain name resolution response message comprises the address of a private network application server and the address information of the target private network domain name server;
determining the address information of the large-network domain name server corresponding to the address information of the target private network domain name server according to the distribution rule table to obtain the address information of the target large-network domain name server;
and generating a second domain name resolution response message according to the address of the private network application server and the address information of the target large network domain name server, and sending the second domain name resolution response message to the user terminal.
Optionally, as shown in fig. 5, the domain name resolution request processing apparatus 600 further includes a configuration module 605 configured to:
receiving a shunting rule table configuration request;
resolving the distribution rule table configuration request to obtain private network domain names, address information of a plurality of large network domain name servers associated with the private network domain names and address information of the private network domain name servers corresponding to the address information of each large network domain name server;
and generating a diversion rule table according to the private network domain name, the address information of the plurality of large network domain name servers and the address information of the private network domain name server corresponding to the address information of each large network domain name server.
Optionally, the domain name resolution request processing apparatus 600 further includes a judging module 606 configured to:
comparing the domain name to be resolved with each private network domain name in the shunting rule table;
and if the private network domain name consistent with the domain name to be resolved exists, determining the resolved domain name as the private network domain name.
Exemplary embodiments of the present disclosure also provide a computer readable storage medium, which may be implemented in the form of a program product comprising program code for causing an electronic device to carry out the steps according to the various exemplary embodiments of the disclosure as described in the above section of the "exemplary method" when the program product is run on the electronic device. In one embodiment, the program product may be implemented as a portable compact disc read only memory (CD-ROM) and includes program code and may be run on an electronic device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's terminal, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
The exemplary embodiments of the present disclosure also provide an electronic device, which may be a server of an edge user plane function. The electronic device is described below with reference to fig. 7. It should be understood that the electronic device 700 shown in fig. 7 is merely an example and should not be construed to limit the functionality and scope of use of embodiments of the present disclosure in any way.
As shown in fig. 7, the electronic device 700 is embodied in the form of a general purpose computing device. Components of electronic device 700 may include, but are not limited to: at least one processing unit 710, at least one memory unit 720, a bus 730 connecting the different system components, including the memory unit 720 and the processing unit 710.
Wherein the storage unit stores program code that is executable by the processing unit 710 such that the processing unit 710 performs steps according to various exemplary embodiments of the present application described in the above-described "exemplary methods" section of the present specification. For example, the processing unit 710 may perform the method steps as shown in fig. 2, etc.
The memory unit 720 may include volatile memory units such as a random access memory unit (RAM) 721 and/or a cache memory unit 722, and may further include a read only memory unit (ROM) 723.
The storage unit 720 may also include a program/utility 724 having a set (at least one) of program modules 725, such program modules 725 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 730 may include a data bus, an address bus, and a control bus.
The electronic device 700 may also communicate with one or more external devices 800 (e.g., keyboard, pointing device, bluetooth device, etc.) via an input/output (I/O) interface 740. Electronic device 700 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the internet through network adapter 750. As shown, the network adapter 750 communicates with other modules of the electronic device 700 over the bus 730. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 700, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with exemplary embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system. Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method for processing a domain name resolution request, comprising:
receiving a first domain name resolution request message sent by a user terminal, wherein the first domain name resolution request message comprises a domain name to be resolved;
if the domain name to be resolved is a private network domain name, determining the address information of a target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table;
generating a second domain name resolution request message according to the domain name to be resolved and the address information of the target private network domain name server, and sending the second domain name resolution request message to the target private network domain name server.
2. The method according to claim 1, wherein determining the address information of the target private network domain name server from the address information of the plurality of private network domain name servers according to the pre-established splitting rule table comprises:
if the first domain name resolution request message contains address information of a large network domain name server, address information of a private network domain name server corresponding to the address information of the large network domain name server is obtained in the distribution rule table, and the address information of the target private network domain name server is obtained.
3. The method according to claim 1, wherein determining the address information of the target private network domain name server from the address information of the plurality of private network domain name servers according to the pre-established splitting rule table comprises:
if the first domain name resolution request message does not contain the address information of the large network domain name server, the address information of the private network main domain name server is acquired from the address information of the private network domain name servers in the shunting rule table, and the address information of the target private network domain name server is obtained.
4. The method according to claim 1, wherein determining the address information of the target private network domain name server from the address information of the plurality of private network domain name servers according to the pre-established splitting rule table comprises:
if the first domain name resolution request message does not contain the address information of the large network domain name server, the address information of any private network domain name server is acquired from the address information of a plurality of private network domain name servers in the shunting rule table, and the address information of the target private network domain name server is obtained.
5. The method of claim 1, wherein after sending the second domain name resolution request message to the target private network domain name server, the method further comprises:
receiving a first domain name resolution response message sent by the target private network domain name server, wherein the first domain name resolution response message comprises the address of a private network application server and the address information of the target private network domain name server;
determining the address information of the large-network domain name server corresponding to the address information of the target private network domain name server according to the shunting rule table to obtain the address information of the target large-network domain name server;
and generating a second domain name resolution response message according to the address of the private network application server and the address information of the target large network domain name server, and sending the second domain name resolution response message to the user terminal.
6. The method according to claim 1, wherein prior to receiving the first domain name resolution request message sent by the user terminal, the method further comprises:
receiving a shunting rule table configuration request;
resolving the distribution rule table configuration request to obtain private network domain names, address information of a plurality of large network domain name servers associated with the private network domain names and address information of the private network domain name servers corresponding to the address information of each large network domain name server;
and generating a shunting rule table according to the private network domain name, the address information of a plurality of the large network domain name servers and the address information of the private network domain name server corresponding to the address information of each large network domain name server.
7. The method according to any one of claims 1 to 6, wherein after receiving the first domain name resolution request message, determining whether the domain name to be resolved in the first domain name resolution request message is a private network domain name is performed by:
comparing the domain name to be resolved with each private network domain name in the shunting rule table;
and if the private network domain name consistent with the domain name to be resolved exists, determining that the resolved domain name is the private network domain name.
8. A domain name resolution request processing apparatus, comprising:
the receiving module is configured to receive a first domain name resolution request message sent by a user terminal, wherein the first domain name resolution request message comprises a domain name to be resolved;
the determining module is configured to determine the address information of the target private network domain name server from the address information of a plurality of private network domain name servers according to a pre-established distribution rule table if the domain name to be resolved is the private network domain name;
the sending module is configured to generate a second domain name resolution request message according to the domain name to be resolved and the address information of the target private network domain name server, and send the second domain name resolution request message to the target private network domain name server.
9. A readable storage medium having stored thereon a program or instructions which when executed by a processor implements a domain name resolution request processing method according to any one of claims 1 to 6.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the domain name resolution request processing method of the domain name query request according to any of claims 1 to 6 via execution of executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210358383.4A CN116938872A (en) | 2022-04-06 | 2022-04-06 | Domain name resolution request processing method, device, medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210358383.4A CN116938872A (en) | 2022-04-06 | 2022-04-06 | Domain name resolution request processing method, device, medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116938872A true CN116938872A (en) | 2023-10-24 |
Family
ID=88376213
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210358383.4A Pending CN116938872A (en) | 2022-04-06 | 2022-04-06 | Domain name resolution request processing method, device, medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116938872A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118200284A (en) * | 2024-03-11 | 2024-06-14 | 杭州迪普科技股份有限公司 | Domain name resolution method, device, computer equipment and storage medium |
-
2022
- 2022-04-06 CN CN202210358383.4A patent/CN116938872A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118200284A (en) * | 2024-03-11 | 2024-06-14 | 杭州迪普科技股份有限公司 | Domain name resolution method, device, computer equipment and storage medium |
| WO2025189644A1 (en) * | 2024-03-11 | 2025-09-18 | 杭州迪普科技股份有限公司 | Domain name resolution methods and apparatuses, computer device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110351283B (en) | Data transmission method, device, equipment and storage medium | |
| CN112114979A (en) | Remote procedure call method and device | |
| CN111460129B (en) | Method, device, electronic equipment and storage medium for generating identification | |
| CN113050987B (en) | Method and device for generating interface document, storage medium and electronic equipment | |
| CN107613005A (en) | Reverse proxy method and device, electronic equipment, storage medium | |
| CN109151033B (en) | Communication method and device based on distributed system, electronic equipment and storage medium | |
| US10044766B2 (en) | Managing mid-dialog session initiation protocol (SIP) messages | |
| CN111885190B (en) | Service request processing method and system | |
| CN114356925A (en) | Identification generation method and device, electronic equipment and storage medium | |
| CN104298675A (en) | Method and device for cache management | |
| CN117560396A (en) | Data processing method, device, equipment and medium | |
| US20170359440A1 (en) | Resource management system | |
| US11271875B2 (en) | System and method for contextually based fulfillment of communication requests via a telephony platform | |
| US7925788B2 (en) | Systems and methods for universal protocol for case management systems | |
| CN116938872A (en) | Domain name resolution request processing method, device, medium and electronic equipment | |
| CN114513552B (en) | Data processing method, device, equipment and storage medium | |
| CN113452778B (en) | Session holding method, device, equipment, system and storage medium | |
| CN117176688A (en) | Addressing method, addressing device, electronic equipment and computer readable storage medium | |
| CN113986995A (en) | Request distribution method and device, storage medium and electronic equipment | |
| CN115460000B (en) | Session processing method, network device, terminal device and medium | |
| CN118764429A (en) | A multi-level proxy dynamic routing method, device and system based on wildcard domain name | |
| CN108683586B (en) | Data processing method, device, medium and computing equipment in instant communication system | |
| CN114125732B (en) | Message processing method and device, storage medium and electronic equipment | |
| CN114168652B (en) | A smart contract interaction method, device, equipment and storage medium | |
| CN115484149A (en) | Network switching method, network switching device, electronic device and storage medium |
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 |