CN114422477B - Domain name resolution method, device and storage medium based on edge cloud architecture - Google Patents
Domain name resolution method, device and storage medium based on edge cloud architecture Download PDFInfo
- Publication number
- CN114422477B CN114422477B CN202111648808.7A CN202111648808A CN114422477B CN 114422477 B CN114422477 B CN 114422477B CN 202111648808 A CN202111648808 A CN 202111648808A CN 114422477 B CN114422477 B CN 114422477B
- Authority
- CN
- China
- Prior art keywords
- domain name
- server
- query request
- target
- name query
- 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.)
- Active
Links
Abstract
The embodiment of the application provides a domain name resolution method, a device and a storage medium based on an edge cloud architecture, wherein the edge cloud architecture comprises a client, a first domain name server and a server, the server is deployed in a plurality of edge clouds, the server is provided with a first network address matched with each edge cloud, the method is applied to the first domain name server, and the method comprises the following steps: acquiring a first domain name query request of a client; acquiring a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server; generating a second domain name query request according to the first domain name query request and the target identifier; determining a server corresponding to the second domain name query request; and sending the second domain name query request to the server so that the server returns a target network address from the first network address according to the target identifier.
Description
Technical Field
The application relates to the technical field of internet, and relates to a domain name resolution method, a domain name resolution device and a storage medium based on an edge cloud architecture.
Background
Multiple access edge computing (Mobile Edge Computing, MEC) provides cloud computing functionality for application developers and content providers, as well as IT service environments at the network edge. MEC has the characteristics of ultra-low delay and high bandwidth, and becomes a key technology for supporting a 5G network, so as to meet the development requirements of high-definition video, VR/AR, industrial Internet, internet of vehicles and other technologies.
In the related art, when a user initiates a request for a service by domain name resolution (Domain Name Server, DNS), there is a problem that resources corresponding to an optimal target service cannot be precisely scheduled, and thus access delay is increased.
Disclosure of Invention
In view of this, an embodiment of the present application provides a domain name resolution method, a device and a storage medium based on an edge cloud architecture, where the edge cloud architecture includes a client, a first domain name server and a server, the server is deployed in a plurality of edge clouds, the server is provided with a first network address matched with each edge cloud, the method is applied to the first domain name server, and the method includes:
acquiring a first domain name query request of a client;
acquiring a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server;
Generating a second domain name query request according to the first domain name query request and the target identifier;
determining a server corresponding to the second domain name query request;
and sending the second domain name query request to the server so that the server returns a target network address from the first network address according to the target identifier.
In some embodiments, the generating a second domain name query request from the first domain name query request and the target identification includes:
and adding the target identifier into a first query domain name of the first domain name query request, so that the server obtains the target identifier by analyzing the first query domain name.
In some embodiments, before the adding the target identifier to the first query domain name of the first domain name query request, the method further comprises:
determining that the first domain name query request meets a first preset condition, wherein the first preset condition is that a first query domain name of the first domain name query request contains first target information.
In some embodiments, the generating a second domain name query request from the first domain name query request and the target identification includes:
Sending the first domain name query request to the server;
receiving a first domain name query response returned by the server;
and generating the second domain name query request according to the first domain name query response and the target identifier.
In some embodiments, after receiving the first domain name query response returned by the target server, before generating the second domain name query request according to the first domain name query response and the target identifier, the method further includes:
and determining that the first domain name query response meets a second preset condition, wherein the second preset condition is that the alias record of the first domain name query response contains second target information.
In some embodiments, the generating the second domain name query request from the first domain name query response and the target identity includes:
acquiring alias record information from the first domain name query response;
generating a second query domain name according to the alias record information and the target identifier;
and generating the second domain name query request according to the second query domain name.
In some embodiments, the determining the server corresponding to the second domain name query request includes:
And sending a second query domain name in the second domain name query request to a domain name proxy server, wherein the domain name proxy server is used for recursively querying the server according to the second query domain name.
In some embodiments, the obtaining the target identification includes:
determining the position of the client according to the network address of the first domain name server, and inquiring identification information corresponding to the position of the client from a preset data table to serve as the target identification;
or generating the target identifier according to a preset rule according to the network address of the first domain name server.
The embodiment of the application provides a domain name resolution device, which comprises:
the first acquisition module is used for acquiring a first domain name query request of the client;
the second acquisition module is used for acquiring a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server;
the generation module is used for generating a second domain name query request according to the first domain name query request and the target identifier;
the determining module is used for determining a server corresponding to the second domain name query request;
and the sending module is used for sending the second domain name query request to the server side so that the server side returns a target network address from the first network address according to the target identifier.
The embodiment of the application provides a computer readable storage medium, which stores executable instructions for causing a processor to execute the executable instructions to implement the domain name resolution method.
The embodiment of the application provides a domain name resolution method, a domain name resolution device and a storage medium based on an edge cloud architecture, wherein in the domain name resolution process, a second domain name query request is generated by adding a target identifier corresponding to the position of a first domain name server in a first domain name query request initiated by a client; and sending a second domain name query request to a corresponding server so that the server returns the network address of the target node from the first network address according to the target identifier. In this way, the second domain name query request includes the target identifier corresponding to the position of the first domain name server, and in the domain name resolution process, the server side can return to the network address of the target node based on the target identifier, so that accurate scheduling of the target node is realized, access delay of the user equipment is reduced, and user experience is improved.
Drawings
FIGS. 1 a-1 c are schematic diagrams of an edge cloud architecture in the related art;
fig. 1d is a schematic diagram of an edge cloud architecture provided in an embodiment of the present application;
Fig. 2 is a flowchart of a domain name resolution method based on MEC architecture according to an embodiment of the present application;
fig. 3 is a schematic diagram of an edge cloud architecture according to an embodiment of the present application;
fig. 4 is a second flow chart of a domain name resolution method based on MEC architecture according to the embodiment of the present application;
fig. 5 is a flowchart of a domain name resolution method based on MEC architecture according to an embodiment of the present application;
fig. 6 is a flow chart diagram of a domain name resolution method based on MEC architecture according to an embodiment of the present application;
fig. 7 is a flowchart of a domain name resolution method based on MEC architecture according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a domain name resolution device according to an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the specific embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In the following description, numerous specific details are set forth in order to provide a more thorough understanding of the present application. However, it will be apparent to one skilled in the art that the present application may be practiced without one or more of these details. In other instances, well-known features have not been described in detail so as not to obscure the application; that is, not all features of an actual implementation are described in detail herein, and well-known functions and constructions are not described in detail.
Fig. 1a is a schematic view of an MEC architecture, as shown in fig. 1a, in which a user equipment 101 interacts with a MEC host 104 through a radio access network base station 102 (RAN) and a user plane function 103 (UPF). The MEC host 104 consists of a belonging MEC platform 1041, a virtualization infrastructure 1042, a MEC application 1043 (MEC APP), wherein the MEC platform is used to run the MEC APP on a specific virtualization infrastructure; the virtualization infrastructure is used for providing computing, storage and network resources for the MEC APP; the MEC APP is configured to respond to requests initiated by a user through the device application.
MECs provide the capability of cloud computing Infrastructure-as-a-Service (IaaS), platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS), while providing network connectivity through mobile communication technology is the best way to achieve 5G low latency because MECs are deployed close to data sources. Referring to fig. 1a, although the application service 1043 on the MEC edge cloud is deployed closer to the user terminal 101, referring to fig. 1B, in the MEC architecture, since the authoritative DNS server 121 located at the server side is communicatively connected to a plurality of edge cloud areas, such as an edge cloud area a, an edge cloud area B, and an edge cloud area C, through the UPF 122. Meanwhile, due to the complexity of Network Address Translation (NAT) and a real network, the user equipment A in the edge cloud A area can not access the application service on the MEC host A in the area or access the application service on the MEC host B in the edge cloud B, so that the access delay is high in cost. Thus, how to discover and use application services on a local edge cloud is a primary issue.
When the user terminal wants to use the service on the local area MEC, a domain name resolution (Domain Name Server, DNS) query request is first initiated, the MEC platform forwards the DNS query request to the server, and the server performs domain name resolution according to the DNS query request initiated by the user, so as to return to the target service node.
Fig. 1c is a flow chart of a domain name resolution method provided by the related art, where the terminal 131 located in the edge cloud area a desires to access a target service node that is the MEC APP 132 located in the edge cloud area a that is closest in physical distance. When the terminal wants to access the MEC APP 132 of the area a, the terminal 131 sends a DNS request to the local DNS server 133, and the local DNS server 133 serves as a DNS recursive query server, recursively queries a server corresponding to the DNS request, sends the DNS request to the authoritative DNS server 134 of the server, and searches for the target service node by the authoritative DNS server 134. However, in the MEC architecture, the authoritative DNS server is connected to the services of multiple edge cloud areas, so that in response to the DNS request sent by the user terminal, the authoritative DNS server may obtain the network address of the MEC APP 135 located in the edge cloud B area and return to the terminal 131, so that the service node located in the edge cloud B area is further away from the user terminal located in the edge cloud a area, which increases the access delay of the terminal 131, and thus causes a problem that the network address cannot be accurately scheduled to the target service node.
In another domain name resolution method provided by the related art, please continue to refer to fig. 1a, a DNS rule 1042a is configured on the MEC platform, and the MEC platform responds to the DNS query request by hijacking the DNS request and according to the configured DNS rule, thereby returning the network address of the appropriate service node. However, this domain name resolution method has the following problems: first, since edge cloud service providers are often not the same market body as edge service operators, edge service operators cannot easily add, modify, and delete DNS rules. Second, DNS rules are difficult to integrate with existing DNS dispatch facilities, such as with current service load and service availability monitoring facilities. Finally, each service program needs to interface with MECs of different providers, and the overall cost is high.
Based on the above problems in performing domain name resolution in the MEC architecture, the embodiment of the present application provides a domain name resolution method based on the MEC architecture, as shown in fig. 1d, applied to a first domain name server deployed in an edge cloud architecture, where a first domain name server 1442a is deployed on a MEC platform 1442, and the MEC platform 1442, MEC APP 1443 and virtualization infrastructure 1441 together form a MEC host 144, and the user equipment 141 interacts with the MEC host 144 through a wireless access base station 142 and a user plane function 143. According to the method and the device, the first domain name server is introduced into the MEC architecture, the first domain name server can serve as a DNS proxy service for edge calculation, flexible DNS scheduling rule processing is achieved, integration with DNS traffic scheduling facilities of original application service programs is achieved, client application and established application service clusters are compatible transparently, and adaptation and new development are not needed.
Fig. 2 is a schematic diagram of a flow implementation of a domain name resolution method according to an embodiment of the present application, as shown in fig. 2, where the method includes:
step S201: and acquiring a first domain name query request of the client.
Fig. 3 is a schematic diagram of an edge cloud architecture provided in the embodiment of the present application, as shown in fig. 3, the edge cloud architecture includes a client 301, a first domain name server 302, and a server 303, where the server 303 is deployed in a plurality of edge cloud areas a and B, and the server is provided with a first network address matched with each edge cloud area.
Referring to fig. 3, in an embodiment of the present application, the method may be applied to a first domain name server 302. When the client 301 wants to access the data of the target service node in the server 303, the client 301 first initiates a first domain name query request to the first domain name server 302, where the client may be any application program installed on a terminal device such as a mobile phone, a computer, a smart watch, a smart bracelet, and a smart glasses, and provides a local service for the terminal.
In this embodiment of the present application, the first domain name query request may be generated based on the operation of the client by the user, or may be generated by the client triggering the client based on the application, and the specific manner is not limited herein. The first domain name query request is for requesting a target service node of a corresponding server that is physically closest to the client.
Step S202: and obtaining a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server.
In this embodiment, when the first domain name server 302 is within the range of the edge cloud area a, the target identifier of the first domain name server 302 includes the location identifier information of the edge cloud area a.
Step S203: and generating a second domain name query request according to the first domain name query request and the target identifier.
The first domain name server adds the position identification information in the obtained target identification to a first domain name query request initiated by the client, and generates a second domain name query request. For example, if the first query domain name corresponding to the first domain name query request is a.com and the obtained target identifier is hosta, hosta may be added to the first domain name query request to generate a second domain name query request hosta.a.com.
Step S204: and determining a server corresponding to the second domain name query request.
The first domain name server analyzes the received first domain name query request to obtain a first query domain name corresponding to the first domain name query request, determines a server corresponding to the first domain name query request according to information in the first query domain name, and determines the server as a server corresponding to the second domain name query request. For example, if the first domain name server determines that the server corresponding to the first query domain name is the search server according to the information in the first query domain name, the server corresponding to the first domain name query request is determined to be the search server.
Step S205: and sending the second domain name query request to the server so that the server returns a target network address from the first network address according to the target identifier.
And after determining the server corresponding to the second domain name query request, sending the second domain name query request to the server. Here, the server is deployed in a plurality of edge clouds, and the server is provided with a first network address matched with each edge cloud area. After the server receives the second domain name query request, the second domain name query request is analyzed to obtain a target identifier, and a target network address corresponding to the target identifier is selected from the first network addresses according to the position identifier information contained in the target identifier. The target network address here is a network address corresponding to an edge cloud that is closest in physical distance to the client.
For example, a second domain name query request hosta.com is sent to a corresponding search server, and the search server searches a target network address matched with hosta in the first network address based on unique identification information hosta of the area location where the first domain name server is located in the second domain name query request, and presumes that the target network address is a search service instance on the edge cloud a, and the IP address is: 2.2.2.2 the server of the search server returns the IP address of the search service instance to the first domain name server. The first domain name server returns the resolved address 2.2.2.2 of the first domain name request a.com to the client side initiating the first query request, so that the client side initiates connection to the search service instance on the edge cloud based on the target network address 2.2.2.2 and performs data access.
In some embodiments, after receiving the second domain name query request, the server may select, from the first network addresses, the target network address corresponding to the target identifier according to the location identifier information included in the resolved target identifier. Here, the server may sort the service nodes corresponding to the first network address according to the physical distance between the service node corresponding to the first network address and the target identifier, and form a first service node sequence according to the order from the small distance to the large distance, when selecting the target network address, may select, in the first service node sequence, a network address corresponding to the service node located at the first position of the first service node sequence as the target network address, or select, in the first service node sequence, a network address corresponding to the service node with load information not greater than a preset threshold as the target network address, where the load information may include, but is not limited to, at least one of: the preset threshold may be a value preset by a technician, which is not limited in this embodiment.
In the domain name resolution method based on the edge cloud architecture, in the domain name resolution process, a second domain name query request is generated by adding a target identifier corresponding to the position of a first domain name server in a first domain name query request initiated by a client; and sending a second domain name query request to a corresponding server so that the server returns the network address of the target node from the first network address according to the target identifier. In this way, the second domain name query request includes the target identifier corresponding to the position of the first domain name server, and in the domain name resolution process, the server side can return to the network address of the target node based on the target identifier, so that accurate scheduling of the target node is realized, access delay of the user equipment is reduced, and user experience is improved.
Fig. 4 is a second schematic flowchart of a flow implementation of a domain name resolution method based on an edge cloud architecture according to an embodiment of the present application, as shown in fig. 4, where the method includes:
step S401: and acquiring a first domain name query request of the client.
Step S402: and obtaining a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server.
Steps S401 to S402 are similar to those in steps S201 to S202, and will not be described here.
Step S403: determining that the first domain name query request meets a first preset condition, wherein the first preset condition is that a first query domain name of the first domain name query request contains first target information.
After receiving a first domain name query request sent by a client, the first domain name server analyzes the first domain name query request to obtain a first query domain name of the first domain name query request, and carries out rule matching on the first query domain name to judge whether the first query domain name meets a first preset condition. The first preset condition is that the first query domain name of the first domain name query request contains first target information, the first target information can be target field information, and when the first query domain name contains the target field information, it is determined that the first query domain name meets the first preset condition. The first preset condition may be a condition manually preset.
For example, the first query domain name is a.com, and the first target information may be whether the first query domain name includes the target field a.com, and if so, it is determined that the first domain name query request satisfies a first preset condition.
Step S404: and adding the target identifier into a first query domain name of the first domain name query request, so that the target server obtains the target identifier by analyzing the first query domain name.
When it is determined in step S403 that the first domain name query request meets a first preset condition, adding a target identifier of a first domain name server to the first domain name query request, so as to generate a second domain name query request including a location information identifier of the first domain name server, so that the target server obtains the target identifier by resolving the second query domain name. For example, when it is determined that the first domain name query request meets a first preset condition, that is, the first query domain name includes first target information a.com, a target identifier hosta of the first domain name server is added to the first domain name query request, and a second domain name query request hosta.a.com is generated, where hosta is unique identifier information indicating an area where the first domain name server is located.
Step S405: and determining a server corresponding to the second domain name query request.
Step S406: and sending the second domain name query request to the server so that the server returns a target network address from the first network address according to the target identifier.
In some embodiments, when it is determined in step S403 that the first domain name query request does not meet the first preset condition, the first domain name query request may be directly sent to the server, where the server parses the first domain name query request to obtain a first query domain name a.com, returns a first query response based on the first query domain name a.com, where the first query response includes a target network address, and the first domain name server returns the first query response to the client, so that the client initiates connection to a service instance on an edge cloud corresponding to the network address and performs data access based on the network address included in the first query response. Therefore, when the first domain name server is not arranged in the MEC architecture, the network address accessed by the client can still be obtained based on the first domain name query request, the integration with the domain name resolution facilities of the original application service programs is realized, the client and the established application service clusters are transparently compatible, and no adaptation and new development are needed.
According to the method and the device for obtaining the target identifier, the target identifier is added to the first query domain name of the first domain name query request meeting the first preset condition, so that the target server can obtain the target identifier by analyzing the first query domain name, and the target network address is returned based on the target identifier. In the domain name resolution process, resolution scheduling is accurately performed according to the region information, so that the client accesses the optimal service node.
Fig. 5 is a schematic diagram III of a flow implementation of a domain name resolution method provided in an embodiment of the present application, as shown in fig. 5, where the domain name resolution method provided in the embodiment of the present application includes:
step S501: and acquiring a first domain name query request of the client.
Step S502: and obtaining a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server.
Step S503: sending the first domain name query request to the server; and receiving a first domain name query response returned by the server.
After receiving a first domain name query request initiated by a client, the first domain name server analyzes the first domain name query request to obtain a first query domain name corresponding to the first domain name query request, determines a server corresponding to the first query domain name, and sends the first domain name query request to the server. The server responds to the first domain name query request and sends a first domain name query response to the first domain name server. For example, the first query domain name may be a.com, and the server side obtains a first domain name query response a.com CNAME a.mec.a.com in response to the a.com in the first domain name query request, and returns to the first domain name server.
In some embodiments, when the first domain name server is not deployed in the MEC architecture, the server may further obtain a conventional domain name query response a.mec.a.com CNAME 1.1.1.1 in response to a.com in the first domain name query request and return the conventional domain name query response a.mec.a.com CNAME 1.1.1 to the client, so that the client may perform data access based on the conventional domain name query response, and ensure compatibility with the original service node network.
Step S504: and determining that the first domain name query response meets a second preset condition, wherein the second preset condition is that the alias record of the first domain name query response contains second target information.
After receiving a first domain name query response of a server side, the first domain name server judges whether the first domain name query response meets a second preset condition, wherein the second preset condition is that an alias record of the first domain name query response contains second target information. The alias record may be a CNAME record, and the second preset condition may be a condition manually preset.
For example, the first query domain name corresponding to the first domain name query request is a.com, the first query response returned by the server side is a.com CNAME a.mec.a.com, and then the alias record is com CNAME a. At this time, the second preset condition may be whether the suffix. Mec.a.com is included in a.com CNAME a.mec.a.com. When the alias record is judged to contain second target information, namely suffix, mec.a.com, the first domain name query response is determined to meet a second preset condition.
Step S505: and generating the second domain name query request according to the first domain name query response and the target identifier.
In some embodiments, step S505 may be accomplished by:
step S5051: and acquiring alias record information from the first domain name query response.
When the first domain name query response meets the second preset condition, alias record information is obtained from the first domain name query response, wherein the alias record information can be information corresponding to CNAME. For example, the alias record information is obtained from the first domain name query response as a.com CNAME a.mec.a.com.
Step S5052: and generating a second query domain name according to the alias record information and the target identifier.
Here, the alias record information in the first query response may be replaced with the target identifier, to generate the second query domain name. For example, the alias record information com CNAME a in the first query response a.com CNAME a.mec.com is replaced by the target identifier hosta, so as to obtain a second query domain name: hosta. Mec. A.com.
Step S5053: and generating the second domain name query request according to the second query domain name.
For example, the second domain name query request may be generated from the second query domain name a.hosta.mec.a.com.
Step S506: and determining a server corresponding to the second domain name query request.
Step S507: and sending the second domain name query request to the server so that the server returns a target network address from the first network address according to the target identifier.
It should be noted that, steps S506 to S507 are similar to steps S204 to S205, and will not be repeated here.
In the embodiment of the application, a first domain name server is introduced in a domain name resolution process based on MEC architecture, the first domain name server resolves a first domain name query response returned by a server in response to a first domain name query request, a target identifier is added to the first domain name query response, a second domain name query request is generated, and the server acquires a target network address based on the target identifier in the second domain name query request. The first domain name server can uniformly output the capability of accurate scheduling through the MEC platform, can realize accurate scheduling, combines the advantage that the MEC platform is close to a user, can not only reduce the access delay of user equipment, optimize flow scheduling, and improve user experience. And each edge service program operator does not need to carry out development investment on the MEC platform, is compatible with the existing flow scheduling facilities of each edge service, and reduces the use cost of MEC platform users.
In some embodiments, step 506: the determining the server corresponding to the second domain name query request may be implemented by the following method: and sending a second query domain name in the second domain name query request to a domain name proxy server, wherein the domain name proxy server is used for recursively querying the server according to the second query domain name.
In some embodiments, obtaining the target identifier may be achieved by either of two methods:
mode one: and determining the position of the client according to the network address of the first domain name server, and inquiring identification information corresponding to the position of the client from a preset data table to serve as the target identification. In this embodiment of the present application, a preset data table is stored in the first domain name server, where the data table includes location information of the client, identification information corresponding to the location information of the client, and a mapping relationship between the location information of the client and the identification information. And inquiring the identification information of the position of the client as a target identification according to the data table.
Mode two: and generating the target identifier according to a preset rule according to the network address of the first domain name server. Here, the preset rule may be to acquire field information representing a location in the network address, and parse the field information to generate the target identifier.
In the following, an exemplary application of the embodiments of the present application in a practical application scenario will be described.
An embodiment of the present application provides a domain name resolution method based on an MEC architecture, and fig. 6 is a flow chart diagram of the domain name resolution method based on the MEC architecture provided in the embodiment of the present application, as shown in fig. 6, where the method includes:
step S601: the user device sends a DNS query request to the DNS engine.
In the embodiment of the present application, the user equipment (i.e. the client) initiates a DNS query request (i.e. the first domain name query request), as shown in fig. 6, assuming that the query domain name is a.com, the MEC platform forwards the DNS query request to the DNS engine (i.e. to be the first domain name server).
Step S602: and the DNS engine performs rule matching on the DNS query request to determine that the DNS query request meets a first preset condition.
Here, the DNS engine performs rule matching (i.e., a first preset condition) according to the domain name of the DNS query request, and if there is no match, directly forwards to the recursive DNS server (i.e., the domain name proxy server).
Step S603: if the DNS query request is determined to meet the first preset condition, acquiring a target identifier corresponding to the position of the DNS engine, modifying the DNS query request, adding the target identifier in the DNS query domain name to generate a modified DNS query request, and sending the modified DNS query request to a DNS recursion query server.
In the embodiment of the application, if the DNS query request matches the rule, the first domain name server obtains the location information hosta of the area where the edge cloud a is located, and modifies the first query domain name according to the rule, to modify a.com to hosta.a.com; the domain name query request (i.e., the second domain name query request) generated after the modification is then forwarded to the recursive DNS server. In some embodiments, when forwarding the domain name query request generated after modification, the first domain name server may also forward the DNS request of the original a.com at the same time according to the configuration, and when the modified domain name query request hosta.a.com does not obtain a valid resolution result, the resolution result of the a.com may be used to return to the UE device.
Step S604: and the DNS recursion query server carries out recursion query according to the second query domain name in the modified DNS query request, determines a server corresponding to the second domain name query request, and sends the modified query request to the server so that the server returns a target network address from the first network address according to the target identifier.
In the embodiment of the application, the recursive DNS server performs recursive query, and finally queries an authoritative DNS server of the domain name, the authoritative DNS determines a server corresponding to the DNS request according to the DNS request domain name, and the server returns a service instance IP on an edge cloud hostA where the UE device is located in an optimal area according to specific area information contained in the DNS request domain name, a load in a service cluster, service availability, and the like: 2.2.2.2.
Step S605: and the DNS engine sends the target network address corresponding to the modified DNS query request to the user equipment.
In the embodiment of the application, the DNS engine returns the resolved address 2.2.2.2 of a.com to the user equipment.
Step S606: the user equipment initiates a connection to the server based on the target network address.
In the embodiment of the application, the user equipment initiates connection to the service instance on the MEC host a in the area a based on the resolved address.
In the embodiment of the application, the first target identifier is added to the first domain name query request meeting the first preset condition to generate the second domain name query request, so that accurate scheduling in the domain name resolution process is realized. First, the first domain name server uniformly outputs the capability of accurate scheduling through the MEC platform, so that the accurate scheduling can be realized, the access delay of user equipment can be reduced, the traffic scheduling is optimized, and the user experience is improved by combining the advantage that the MEC platform is close to a user. And secondly, the first domain name server enables each edge service program operator not to develop and butt joint aiming at a single MEC platform, can be compatible with established traffic scheduling facilities of each edge service, and reduces the use cost of MEC platform users. Finally, because the first domain name server is introduced, even if an application service operator adds an instance on the edge cloud platform, the application service operator can be easily integrated into the existing service cluster without completely building a service cluster.
Next, still another exemplary application of the embodiment of the present application in one practical application scenario will be described.
Fig. 7 is a flowchart fifth of a domain name resolution method based on MEC architecture according to an embodiment of the present application, as shown in fig. 7, where the method includes:
step S701: the user device sends a DNS query request to the DNS engine.
In the embodiment of the present application, the user equipment (i.e., the client) initiates a DNS query request (i.e., the first domain name query request), as shown in fig. 7, assuming that the query domain name is a.com, the MEC platform forwards the DNS query to the DNS engine.
Step S702: the DNS engine sends the DNS query request to a DNS recursive query server.
In the embodiment of the application, the DNS engine (i.e., the first domain name server) acts as a DNS proxy, forwarding the DNS query request to the DNS recursive query server (i.e., the domain name proxy server) of the operator.
Step S703: and the DNS recursion query server recursion queries the query domain name in the DNS query request to determine a corresponding server, and sends the DNS query request to the server, and the server returns a query response in response to the DNS query request.
In the embodiment of the application, the recursive DNS server of the operator performs DNS recursive query, and finally queries the authoritative DNS server of the domain name (i.e., the server), and the authoritative DNS returns a query response (i.e., a first domain name query response) according to the DNS request, assuming that there are two response records: com CNAME a.mec.a.com; mec.a.com CNAME 1.1.1.1. In some embodiments, if the area where the user equipment is located does not have a DNS engine, the conventional scheduling node a.mec.a.com CNAME 1.1.1.1 can be directly accessed, so as to ensure compatibility with the originally constructed service node network.
Step S704: the DNS recursive query server sends a query response to the DNS engine.
In the present embodiment, the operator's recursive DNS server returns the authoritative DNS response to the DNS engine on the MEC.
Step S705: the DNS engine carries out rule matching on the query response, and determines that the query response meets a second preset condition, wherein the second preset condition is that the alias record of the query response contains second target information; if the query response meets the second preset condition, acquiring a target identifier corresponding to the position of the DNS engine, adding the target identifier into the DNS query request to obtain a modified DNS query request, and sending the modified DNS query request to a DNS recursion query server.
In this embodiment of the present application, the DNS engine performs rule matching (i.e., a second preset condition) on the response packet, and it is assumed that the configured rule matching condition is whether the CNAME RR record (i.e., the alias record) in the response packet contains a suffix, mec.a.com (i.e., the second target information), and if hit, replaces the specified suffix to initiate the DNS query request again, e.g., replaces the suffix, mec.a.com with a. Hosta.a.com, where hosta is the unique identifier of the region where the MEC is located.
Step S706: and sending the modified DNS query request to the server so that the server returns a target network address from the first network address according to the target identifier.
In the embodiment of the application, the DNS authority server of the server returns an optimal service node IP according to various indexes such as MEC region information, loads of servers, availability and the like contained in the modified DNS request.
Step S707: and the DNS engine sends the target network address corresponding to the modified DNS query request to the user equipment.
In the embodiment of the application, the DNS engine returns the best service node IP obtained by the query to the user equipment.
Step S708: the user equipment initiates a connection to a service instance located on MEC host a based on the target network address.
In the embodiment of the application, the user equipment initiates connection to a service instance located on the MEC host a based on the target network address, and performs data access.
In the embodiment of the application, the first domain name server is introduced first, and the first domain name server uniformly outputs the capability of accurate scheduling outwards through the edge computing platform, so that the accurate scheduling can be realized, the advantage that the MEC platform is close to a user is combined, the access delay of user equipment can be reduced, the flow scheduling is optimized, and the user experience is improved. And secondly, development investment is not required for MEC platforms by each edge service program operator, the existing flow scheduling facilities of each edge service are compatible, and the use cost of MEC platform users is reduced. Finally, the edge service program operator can realize adjustment strategy by modifying the authoritative DNS response message, and does not need to operate and control the scheduling strategy through the edge cloud service provider, so that the adjustment control is flexible.
An embodiment of the present application provides a domain name resolution device, fig. 8 is a schematic structural diagram of the domain name resolution device, as shown in fig. 8, where the domain name resolution device 800 includes:
a first obtaining module 801, configured to obtain a first domain name query request of a client;
a second obtaining module 802, configured to obtain a target identifier, where the target identifier is an identifier corresponding to a location where the first domain name server is located;
a generating module 803, configured to generate a second domain name query request according to the first domain name query request and the target identifier;
a determining module 804, configured to determine a server corresponding to the second domain name query request.
And a sending module 805, configured to send the second domain name query request to the server, so that the server returns a target network address from the first network address according to the target identifier.
In some embodiments, the generating module is further configured to:
and adding the target identifier into a first query domain name of the first domain name query request, so that the server obtains the target identifier by analyzing the first query domain name.
In some embodiments, the apparatus further comprises:
the first determining module is configured to determine that the first domain name query request meets a first preset condition, where the first preset condition is that a first query domain name of the first domain name query request includes first target information.
In some embodiments, the apparatus further comprises:
the third sending module is used for sending the first domain name query request to the server;
the first receiving module is used for receiving a first domain name query response returned by the server;
the generating module is further configured to: and generating the second domain name query request according to the first domain name query response and the target identifier.
In some embodiments, the apparatus further comprises:
and the second determining module is used for determining that the first domain name query response meets a second preset condition, wherein the second preset condition is that the alias record of the first domain name query response contains second target information.
In some embodiments, the apparatus further comprises:
the third acquisition module is used for acquiring alias record information from the first domain name query response;
the generating module is further configured to: generating a second query domain name according to the alias record information and the target identifier; and generating the second domain name query request according to the second query domain name.
In some embodiments, the sending module is further configured to:
and sending a second query domain name in the second domain name query request to a domain name proxy server, wherein the domain name proxy server is used for recursively querying the server according to the second query domain name.
In some embodiments, the second acquisition module is further to:
determining the position of the client according to the network address of the first domain name server, and inquiring identification information corresponding to the position of the client from a preset data table to serve as the target identification;
or generating the target identifier according to a preset rule according to the network address of the first domain name server.
It should be noted that: in the domain name resolution device provided in the above embodiment, only the division of each program module is used for illustration, and in practical application, the process allocation may be performed by different program modules according to needs, that is, the internal structure of the device is divided into different program modules, so as to complete all or part of the processes described above. In addition, the domain name resolution device and the domain name resolution method provided in the above embodiments belong to the same concept, and detailed implementation processes of the domain name resolution device and the domain name resolution method are detailed in the method embodiments, which are not repeated here.
The present embodiments provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs: acquiring a first domain name query request of a client; acquiring a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server; generating a second domain name query request according to the first domain name query request and the target identifier; determining a server corresponding to the second domain name query request; and sending the second domain name query request to the server so that the server returns a target network address from the first network address according to the target identifier.
The computer program, when executed by the processor, further performs: and adding the target identifier into a first query domain name of the first domain name query request, so that the server obtains the target identifier by analyzing the first query domain name.
The computer program, when executed by the processor, further performs: determining that the first domain name query request meets a first preset condition, wherein the first preset condition is that a first query domain name of the first domain name query request contains first target information.
The computer program, when executed by the processor, further performs: sending the first domain name query request to the server; receiving a first domain name query response returned by the server; generating the second domain name query request according to the first domain name query response and the target identifier; determining a server corresponding to the second domain name query request; and sending the second domain name query request to the server so that the server returns a target network address from the first network address according to the target identifier. .
The computer program, when executed by the processor, further performs: and determining that the first domain name query response meets a second preset condition, wherein the second preset condition is that the alias record of the first domain name query response contains second target information.
The computer program, when executed by the processor, further performs: acquiring alias record information from the first domain name query response; generating a second query domain name according to the alias record information and the target identifier; and generating the second domain name query request according to the second query domain name.
The computer program, when executed by the processor, further performs: and sending a second query domain name in the second domain name query request to a domain name proxy server, wherein the domain name proxy server is used for recursively querying the server according to the second query domain name.
The computer program, when executed by the processor, further performs: determining the position of the client according to the network address of the first domain name server, and inquiring identification information corresponding to the position of the client from a preset data table to serve as the target identification; or generating the target identifier according to a preset rule according to the network address of the first domain name server.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.
The units described as separate units may or may not be physically separate, and units displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
The methods disclosed in the several method embodiments provided in the present application may be arbitrarily combined without collision to obtain a new method embodiment.
The features disclosed in the several product embodiments provided in the present application may be combined arbitrarily without conflict to obtain new product embodiments.
The features disclosed in the several method or apparatus embodiments provided in the present application may be arbitrarily combined without conflict to obtain new method embodiments or apparatus embodiments.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A domain name resolution method based on an edge cloud architecture, wherein the edge cloud architecture comprises a client, a first domain name server and a server, the server is deployed in a plurality of edge clouds, the server is provided with a first network address matched with each edge cloud, the method is applied to the first domain name server, and the method comprises:
acquiring a first domain name query request of a client;
acquiring a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server;
generating a second domain name query request according to the first domain name query request and the target identifier;
determining a server corresponding to the second domain name query request;
and sending the second domain name query request to the server so that the server returns a target network address from the first network address according to the target identifier.
2. The method of claim 1, the generating a second domain name query request from the first domain name query request and a target identity comprising:
and adding the target identifier into a first query domain name of the first domain name query request, so that the server obtains the target identifier by analyzing the first query domain name.
3. The method of claim 2, the method further comprising, prior to the adding the target identification to the first query domain name of the first domain name query request:
determining that the first domain name query request meets a first preset condition, wherein the first preset condition is that a first query domain name of the first domain name query request contains first target information.
4. The method of claim 1, the generating a second domain name query request from the first domain name query request and a target identity comprising:
sending the first domain name query request to the server;
receiving a first domain name query response returned by the server;
and generating the second domain name query request according to the first domain name query response and the target identifier.
5. The method according to claim 4, after the receiving the first domain name query response returned by the server, before the generating the second domain name query request according to the first domain name query response and the target identifier, the method further comprises:
and determining that the first domain name query response meets a second preset condition, wherein the second preset condition is that the alias record of the first domain name query response contains second target information.
6. The method of claim 4, the generating the second domain name query request from the first domain name query response and the target identity, comprising:
acquiring alias record information from the first domain name query response;
generating a second query domain name according to the alias record information and the target identifier;
and generating the second domain name query request according to the second query domain name.
7. The method of claim 1, the determining the server corresponding to the second domain name query request, includes:
and sending a second query domain name in the second domain name query request to a domain name proxy server, wherein the domain name proxy server is used for recursively querying the server according to the second query domain name.
8. The method of claim 1, the obtaining a target identification comprising:
determining the position of the client according to the network address of the first domain name server, and inquiring identification information corresponding to the position of the client from a preset data table to serve as the target identification;
or generating the target identifier according to a preset rule according to the network address of the first domain name server.
9. A domain name resolution device based on an edge cloud architecture, the edge cloud architecture including a client, a first domain name server, and a server, the server being deployed in a plurality of edge clouds, the server being provided with a first network address matching each of the edge clouds, the device comprising:
the first acquisition module is used for acquiring a first domain name query request of the client;
the second acquisition module is used for acquiring a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server;
the generation module is used for generating a second domain name query request according to the first domain name query request and the target identifier;
the determining module is used for determining a server corresponding to the second domain name query request;
and the sending module is used for sending the second domain name query request to the server side so that the server side returns a target network address from the first network address according to the target identifier.
10. A computer readable storage medium storing executable instructions for causing a processor to perform the domain name resolution method of any one of claims 1 to 8 when the executable instructions are executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111648808.7A CN114422477B (en) | 2021-12-30 | 2021-12-30 | Domain name resolution method, device and storage medium based on edge cloud architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111648808.7A CN114422477B (en) | 2021-12-30 | 2021-12-30 | Domain name resolution method, device and storage medium based on edge cloud architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114422477A CN114422477A (en) | 2022-04-29 |
| CN114422477B true CN114422477B (en) | 2023-07-21 |
Family
ID=81268593
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111648808.7A Active CN114422477B (en) | 2021-12-30 | 2021-12-30 | Domain name resolution method, device and storage medium based on edge cloud architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114422477B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109640319A (en) * | 2019-01-16 | 2019-04-16 | 腾讯科技（深圳）有限公司 | Dispatching method, device and electronic equipment based on access information |
| CN112422701A (en) * | 2019-08-20 | 2021-02-26 | 华为技术有限公司 | Domain name system query method and communication device |
| CN113067909A (en) * | 2020-01-02 | 2021-07-02 | ***通信有限公司研究院 | Edge node addressing method, device, equipment and storage medium |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101640684A (en) * | 2009-08-21 | 2010-02-03 | 中国电信股份有限公司 | Content delivering method, network system, GSLB device and domain name server |
| CN110098947B (en) * | 2018-01-31 | 2021-01-29 | 华为技术有限公司 | Application deployment method, device and system |
| CN110198307B (en) * | 2019-05-10 | 2021-05-18 | 深圳市腾讯计算机***有限公司 | Method, device and system for selecting mobile edge computing node |
| CN110381131B (en) * | 2019-07-15 | 2022-01-28 | 北京奇艺世纪科技有限公司 | Method for realizing MEC node identification, mobile terminal, server and storage medium |
| CN113489772B (en) * | 2019-08-08 | 2022-09-09 | 腾讯科技（深圳）有限公司 | Network request processing method and device and electronic equipment |
| CN110572377B (en) * | 2019-08-22 | 2022-02-22 | 网宿科技股份有限公司 | Data forwarding method, plug-in and domain name server |
| CN113259260A (en) * | 2020-02-11 | 2021-08-13 | 华为技术有限公司 | Method and device for deploying application instance and scheduling application instance |
-
2021
- 2021-12-30 CN CN202111648808.7A patent/CN114422477B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109640319A (en) * | 2019-01-16 | 2019-04-16 | 腾讯科技（深圳）有限公司 | Dispatching method, device and electronic equipment based on access information |
| CN112422701A (en) * | 2019-08-20 | 2021-02-26 | 华为技术有限公司 | Domain name system query method and communication device |
| CN113067909A (en) * | 2020-01-02 | 2021-07-02 | ***通信有限公司研究院 | Edge node addressing method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114422477A (en) | 2022-04-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11811657B2 (en) | Updating routing information based on client location | |
| CN109040343B (en) | Domain name resolution method and device, computer readable storage medium and electronic equipment | |
| EP2356577B1 (en) | Request routing and updating routing information utilizing client location information | |
| EP3657765B1 (en) | Multi-access edge network service system and network service method | |
| CN109587290B (en) | Domain name resolution method and related device | |
| CN112217856A (en) | Address acquisition method, device, equipment and storage medium of application example | |
| CN109729183B (en) | Request processing method, device, equipment and storage medium | |
| US10834202B2 (en) | Network service system and network service method | |
| JP2012161078A (en) | Method and apparatus for determining server which should respond to service request | |
| CN111885216B (en) | DNS query method, device, equipment and storage medium | |
| CN112291384B (en) | Information processing method for domain name resolution and electronic equipment | |
| CN114301990A (en) | Node scheduling method, device and storage medium based on content distribution network | |
| CN115297088A (en) | Domain name resolution system and method in cloud computing environment | |
| CN114422477B (en) | Domain name resolution method, device and storage medium based on edge cloud architecture | |
| CN110677512B (en) | Address resolution method and device | |
| CN114006915B (en) | Resource request method, device, equipment and computer readable storage medium | |
| CN115225606A (en) | Domain name access method and system of cross-network protocol of container cloud platform | |
| CN115004657B (en) | Addressing method, addressing system and addressing device | |
| CN112714078A (en) | Network traffic identification method and device, storage medium and server | |
| CN114363287B (en) | Domain name recursive query method and device, recursive server and DNS system | |
| US11652781B2 (en) | Data processing method based on MEC platform, device, and storage medium | |
| US20220350748A1 (en) | Consistent hashing for communication devices | |
| US11381503B2 (en) | Data packet routing method and data packet routing device | |
| CN111147618B (en) | Communication method, communication device, electronic equipment and storage medium | |
| CN117729214A (en) | Proxy method, proxy device, electronic equipment 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |