CN114422477A - Domain name resolution method and device based on edge cloud architecture and storage medium - Google Patents
Domain name resolution method and device based on edge cloud architecture and storage medium Download PDFInfo
- Publication number
- CN114422477A CN114422477A CN202111648808.7A CN202111648808A CN114422477A CN 114422477 A CN114422477 A CN 114422477A CN 202111648808 A CN202111648808 A CN 202111648808A CN 114422477 A CN114422477 A CN 114422477A
- 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.)
- Granted
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
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 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, but is not limited to, a domain name resolution method, a domain name resolution device and a storage medium based on an edge cloud architecture.
Background
Multi-access Edge Computing (MEC) provides cloud Computing functionality for application developers and content providers, as well as IT service environments at the Edge of the network. The MEC has the characteristics of ultra-low delay and high bandwidth, and becomes a key technology for supporting a 5G network to meet the development requirements of technologies such as high-definition video, VR/AR, industrial internet, car networking and the like.
In the related art, when a user makes a request for a service through Domain Name Server (DNS), there is a problem that the user cannot accurately schedule the resource corresponding to an optimal target service, so that access delay is increased.
Disclosure of Invention
In view of this, an embodiment of the present application provides a domain name resolution method, an apparatus, 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, and 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 according to the first domain name query request and a target identifier includes:
and adding the target identifier to a first query domain name of the first domain name query request, so that the server side obtains the target identifier by analyzing the first query domain name.
In some embodiments, before the adding the target identity 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 according to the first domain name query request and a target identifier 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, and 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 according to the first domain name query response and the target identity includes:
obtaining alias record information from the first domain name query response;
generating a second query domain name according to the alias recording 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 a server corresponding to the second domain name query request includes:
and sending the 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 comprises:
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, the target identifier is generated according to the network address of the first domain name server and a preset rule.
The embodiment of the application provides a domain name resolution device, the device includes:
the first acquisition module is used for acquiring a first domain name query request of a 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 generating 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 so that the server returns a target network address from the first network address according to the target identifier.
An embodiment of the present 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 described above.
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 process of domain name resolution, 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 the 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. Therefore, the second domain name query request contains the target identifier corresponding to the position of the first domain name server, and the server side can return the network address of the target node based on the target identifier in the domain name resolution process, so that the accurate scheduling of the target node is realized, the access delay of user equipment is reduced, and the 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 first schematic flowchart of a domain name resolution method based on an MEC architecture according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of an edge cloud architecture according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a second domain name resolution method based on the MEC architecture according to an embodiment of the present disclosure;
fig. 5 is a schematic flowchart third of a domain name resolution method based on the MEC architecture according to an embodiment of the present application;
fig. 6 is a fourth schematic flowchart of a domain name resolution method based on the MEC architecture according to the embodiment of the present application;
fig. 7 is a fifth flowchart illustrating a domain name resolution method based on the MEC architecture according to an embodiment of the present disclosure;
fig. 8 is a schematic structural diagram of a domain name resolution apparatus according to an embodiment of the present application.
Detailed Description
Exemplary embodiments disclosed in the present application 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. It will be apparent, however, to one skilled in the art, that the present application may be practiced without one or more of these specific details. In other instances, well-known features have not been described in order to avoid obscuring the present application; that is, not all features of an actual embodiment are described herein, and well-known functions and structures are not described in detail.
Fig. 1a is a schematic diagram 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). MEC host 104 is composed of a corresponding MEC platform 1041, a virtualization infrastructure 1042, and a MEC application 1043(MEC APP), where 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 used to respond to requests initiated by a user through a device application.
The MEC provides capabilities of Infrastructure as a Service (IaaS), Platform as a Service (PaaS) and Software as a Service (SaaS) of cloud computing, and simultaneously provides network connection capability through a mobile communication technology because the deployment position of the MEC is close to a data source, which is the best mode for realizing 5G low delay. Referring to fig. 1a, although the application service 1043 on the MEC edge cloud is deployed in a position close to the user terminal 101, in the MEC architecture, as the authoritative DNS server 121 located at the server is communicatively connected to a plurality of edge cloud zones, for example, an edge cloud zone a, an edge cloud zone B, and an edge cloud zone C, through the UPF122, referring to fig. 1B. Meanwhile, due to the complexity of Network Address Translation (NAT) and a real network, the user equipment a in the edge cloud a region may not be able to access the application service on the MEC host a in the region, or access the application service on the MEC host B in the edge cloud region B, so that the access delay and cost are high. Therefore, how to discover and use the application service on the local edge cloud becomes a primary problem.
When a user terminal wants to use a service on an MEC in a region, a Domain Name Server (DNS) query request is initiated firstly, a MEC platform forwards the DNS query request to a Server, and the Server carries out Domain Name resolution according to the DNS query request initiated by the user so as to return to a target service node.
Fig. 1c is a schematic flowchart of a domain name resolution method provided in the related art, where a terminal 131 located in an edge cloud area a and a target service node expected to be accessed are MEC APPs 132 located in the edge cloud area a and closest in physical distance. When the terminal wants to access MEC APP 132 of the area A, the terminal 131 sends the DNS request to the local DNS server 133, the local DNS server 133 serves as a DNS recursive query server, a server corresponding to the DNS request is recursively queried, the DNS request is sent to an authoritative DNS server 134 of the server, and the authoritative DNS server 134 searches for a target service node. However, in the MEC architecture, the authoritative DNS server is connected to services of a plurality of edge cloud areas, and therefore, in response to a DNS request sent by a user terminal, the authoritative DNS server may obtain a network address of the MEC APP 135 located in the edge cloud B area and return the network address to the terminal 131, so that since the physical distance between the service node located in the edge cloud B area and the user terminal located in the edge cloud a area is long, the access delay of the terminal 131 is increased, and thus the problem that the service node cannot be accurately scheduled to the target service node is caused.
Another domain name resolution method provided by the related art, please continue to refer to fig. 1a, is to configure a DNS rule 1042a on the MEC platform, and the MEC platform returns a network address of a suitable service node by hijacking the DNS request and responding to the DNS query request according to the configured DNS rule. However, this domain name resolution method has the following problems: first, since the edge cloud service provider and the edge service operator are often not the same market entity, the edge service operator cannot easily add, modify, and delete DNS rules. Second, DNS rules are difficult to integrate with existing DNS scheduling facilities, such as current service load and service availability monitoring facilities. Finally, each service program needs to interface with MECs of different providers, with high overall costs.
Based on the above problem existing in performing domain name resolution in the MEC architecture, an embodiment of the present application provides a domain name resolution method based on the MEC architecture, as shown in fig. 1d, which is applied to a first domain name server deployed in an edge cloud architecture, a first domain name server 1442a is deployed on an MEC platform 1442, the MEC platform 1442, an MEC APP 1443 and a virtualization infrastructure 1441 jointly form an MEC host 144, and a 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 embodiment of the application, the first domain name server is introduced into the MEC framework, can be used as a DNS proxy service for edge calculation, achieves flexible DNS scheduling rule processing, further achieves integration with DNS traffic scheduling facilities of original application service programs, is transparently compatible with client application and established application service clusters, and does not need adaptation and new development.
Fig. 2 is a first schematic view illustrating a flow implementation of a domain name resolution method provided in an embodiment of the present application, as shown in fig. 2, the method includes:
step S201: the method comprises the steps of obtaining a first domain name query request of a client.
Fig. 3 is a schematic view of an edge cloud architecture provided in an embodiment of the present application, and 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 the embodiment of the present application, the method may be applied to the first domain name server 302. When a client 301 wants to access data of a target service node in a server 303, the client 301 first initiates a first domain name query request to a first domain name server 302, where the client may be any application installed on a terminal device such as a mobile phone, a computer, a smart watch, a smart band, smart glasses, and the like, and provides a local service for the terminal.
In this embodiment of the application, the first domain name query request may be generated based on a user operating the client, or may be generated by the client based on an application triggering the client, and a specific manner is not limited herein. The first domain name query request is used for requesting a target service node of a corresponding server closest to the client in physical distance.
Step S202: and acquiring a target identifier, wherein the target identifier is an identifier corresponding to the position of the first domain name server.
In this embodiment of the application, when the first domain name server 302 is in 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 a.
Step S203: and generating a second domain name query request according to the first domain name query request and the target identifier.
And the first domain name server adds the position identification information in the acquired target identification to a first domain name query request initiated by the client to generate 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, the 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 the server corresponding to the second domain name query request. For example, 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, and then determines that the server corresponding to the first domain name query request is 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 the server corresponding to the second domain name query request is determined, 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. And after receiving the second domain name query request, the server analyzes the second domain name query request to obtain a target identifier, and selects a target network address corresponding to the target identifier from the first network address 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, the second domain name query request hosta.a.com is sent to the corresponding search server, the search server searches for a target network address matched with hosta in the first network address based on the unique identification information hosta of the location of the area where the first domain name server is located in the second domain name query request, assuming 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 at the search service returns the IP address of the search service instance to the first domain name server. The first domain name server returns the resolution address 2.2.2.2 of the first domain name request a.com to the client initiating the first query request, so that the client 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 a target network address corresponding to the target identifier from the first network address according to the location identifier information included in the target identifier obtained through resolution. Here, the service end may sequence the service nodes corresponding to the first network address according to a physical distance between the service node corresponding to the first network address and the target identifier in an order from small to large to form a first service node sequence, and when selecting the target network address, may select, in the first service node sequence, a network address corresponding to a service node located at a head of the first service node sequence as the target network address, or select, in the first service node sequence, a network address corresponding to a service node whose load information is 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 numerical value preset by a technician, and is not limited in this embodiment.
According to the domain name resolution method based on the edge cloud architecture, in the process of domain name resolution, a target identifier corresponding to the position of a first domain name server is added in a first domain name query request initiated by a client to generate a second domain name query request; and sending the 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. Therefore, the second domain name query request comprises 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 the network address of the target node based on the target identifier, so that the accurate scheduling of the target node is realized, the access delay of the user equipment is reduced, and the user experience is improved.
Fig. 4 is a schematic view illustrating a second implementation process of the domain name resolution method based on the edge cloud architecture according to the embodiment of the present application, where as shown in fig. 4, the method includes:
step S401: the method comprises the steps of obtaining a first domain name query request of a client.
Step S402: and acquiring 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 steps S201 to S202, and are not described herein again.
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, a 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, performs rule matching on the first query domain name, and judges whether the first query domain name meets a first preset condition. The first preset condition is that a first query domain name of the first domain name query request includes first target information, where the first target information may be target field information, and when the first query domain name includes the target field information, it is determined that the first query domain name satisfies the first preset condition. The first preset condition may be a condition that is manually preset.
For example, the first query domain name is a.com, the first target information may be whether a target field a.com is included in the first query domain name, and if so, it is determined that the first domain name query request satisfies the first preset condition.
Step S404: and adding the target identifier to a first query domain name of the first domain name query request, so that the target server side obtains the target identifier by analyzing the first query domain name.
When it is determined through step S403 that the first domain name query request satisfies the first preset condition, adding the target identifier of the first domain name server to the first domain name query request to generate a second domain name query request including the location information identifier of the first domain name server, so that the target server obtains the target identifier by analyzing the second query domain name. For example, when it is determined that the first domain name query request meets the first preset condition, that is, the first query domain name contains the first target information a.com, the target identifier hosta of the first domain name server is added to the first domain name query request, and the 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 that the first domain name query request does not satisfy the first preset condition through step S403, the first domain name query request may be directly sent to the server, the server parses the first domain name query request to obtain a first query domain name a.com, and 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 a 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 framework, 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 adaptation and new development are not needed.
According to the method and the device, 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 view of a third implementation process of the domain name resolution method provided in the embodiment of the present application, and as shown in fig. 5, the domain name resolution method provided in the embodiment of the present application includes:
step S501: the method comprises the steps of obtaining a first domain name query request of a client.
Step S502: and acquiring 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.
The method comprises the steps that after a first domain name query request initiated by a client side is received by a first domain name server, the first domain name query request is analyzed to obtain a first query domain name corresponding to the first domain name query request, a server side corresponding to the first query domain name is determined, and the first domain name query request is sent to the server side. And the server side responds to the first domain name inquiry request and sends a first domain name inquiry response to the first domain name server. For example, the first domain name query may be a.com, and the server obtains a.com CNAME a.mec.a.com response in response to the a.com in the first domain name query request, and returns the first domain name query to the first domain name server.
In some embodiments, when the MEC architecture is not deployed with the first domain name server, 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 to the client, so that the client may perform data access based on the conventional domain name query response, and ensure compatibility with an 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, a first domain name server judges whether the first domain name query response meets a second preset condition, wherein the second preset condition is that alias records of the first domain name query response contain second target information. The alias record may be a CNAME record and the second preset condition may be a condition that is 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 is a.com CNAME a.mec.a.com, and the alias is recorded as com CNAME a. At this time, the second preset condition may be whether a suffix is included in the a.com CNAME a.mec.a.com. And when the alias record is judged to contain the second target information, namely the suffix, mec.a.com, determining that the first domain name query response meets 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 obtaining alias record information from the first domain name query response.
And when the first domain name query response is determined to meet the second preset condition, obtaining alias record information from the first domain name query response, wherein the alias record information may be information corresponding to the 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, and the second query domain name may be generated. For example, the alias record information com CNAME a in the first query response a.com CNAME a.mec.a.com is replaced by the target identifier hosta, and the second query domain name is obtained as: a.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 are not described herein again.
According to the embodiment of the application, a first domain name server is introduced in a domain name resolution process based on an MEC framework, 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 into the first domain name query response to generate a second domain name query request, 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 output accurate scheduling capability through the MEC platform, accurate scheduling can be achieved, the advantage that the MEC platform is close to the user is combined, access delay of user equipment can be reduced, flow scheduling is optimized, and user experience is improved. And each edge service program operator does not need to develop and invest aiming at the MEC platform, the method is compatible with the existing flow dispatching facilities of each edge service, and the use cost of the MEC platform user is reduced.
In some embodiments, step 506: determining a server corresponding to the second domain name query request may be implemented by the following method: and sending the 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 any one of the following two methods:
the first method is as follows: 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 be used as the target identification. In the embodiment of the application, a preset data table is stored in the first domain name server, and the data table includes location information of a 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.
The second method comprises the following steps: and generating the target identifier according to the network address of the first domain name server and a preset rule. Here, the preset rule may be that field information indicating a location in the network address is acquired, and the field information is parsed to generate the target identifier.
Next, an exemplary application of the embodiment of the present application in a practical application scenario will be described.
An embodiment of the present application provides a method for domain name resolution based on an MEC architecture, and fig. 6 is a fourth flowchart of the method for domain name resolution based on an MEC architecture provided in the embodiment of the present application, as shown in fig. 6, the method includes:
step S601: the user device sends a DNS query request to the DNS engine.
In the embodiment of the present application, a user equipment (i.e., a client) initiates a DNS query request (i.e., a first domain name query request), as shown in fig. 6, assuming that a query domain name is a.com, the MEC platform forwards the DNS query request to a DNS engine (i.e., a first domain name server).
Step S602: and the DNS engine carries out rule matching on the DNS query request and determines 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 matching, directly forwards to the recursive DNS server (i.e., a domain name proxy server).
Step S603: if the DNS query request is determined to meet the first preset condition, the target identifier corresponding to the position of the DNS engine is obtained, the DNS query request is modified, the target identifier is added into the DNS query domain name to generate a modified DNS query request, and the modified DNS query request is sent to a DNS recursive query server.
In the embodiment of the application, if the DNS query request matches a rule, the first domain name server obtains the location information hosta of the area where the edge cloud A is located, modifies the first query domain name according to the rule, and modifies a.com to hosta.a.com; the modified generated domain name query request (i.e., the second domain name query request) is then forwarded to the recursive DNS server. In some embodiments, when forwarding the modified domain name query request, 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 returned to the UE device.
Step S604: and the DNS recursive query server performs recursive query according to a 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 performs query to 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 the optimal service instance IP on the edge cloud hostA in the area where the UE device is located according to the specific regional information contained in the DNS request domain name, the load in the service cluster, the 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 an 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 connection to the server based on the target network address.
In the embodiment of the present application, the user equipment initiates a connection to a service instance on the MEC host a in the area a based on the resolved address.
In the embodiment of the application, a second domain name query request is generated by adding a first target identifier to a first domain name query request meeting a first preset condition, so that accurate scheduling in a domain name resolution process is realized. Firstly, the first domain name server outputs accurate scheduling capability to the outside in a unified manner through the MEC platform, so that 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, the first domain name server enables each edge service program operator not to develop and dock aiming at a single MEC platform, can be compatible with the established flow scheduling facilities of each edge service, and reduces the use cost of the MEC platform user. Finally, due to the introduction of the first domain name server, even if an application service operator adds a new instance on the edge cloud platform, the application service operator can be easily integrated into the existing service cluster without completely building a new service cluster.
Next, still another exemplary application of the embodiment of the present application in a practical application scenario will be described.
Fig. 7 is a schematic flowchart of a fifth process of a domain name resolution method based on an MEC architecture according to an embodiment of the present application, and as shown in fig. 7, the method includes:
step S701: the user device sends a DNS query request to the DNS engine.
In the embodiment of the present application, a user equipment (i.e. a client) initiates a DNS query request (i.e. a first domain name query request), as shown in fig. 7, assuming that a query domain name is a.com, the MEC platform forwards the DNS query to a DNS engine.
Step S702: and the DNS engine sends the DNS query request to a DNS recursive query server.
In the embodiment of the present application, the DNS engine (i.e. the first domain name server) acts as a DNS proxy and forwards 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 recursive query server recursively 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 present application, a recursive DNS server of an operator performs DNS recursive query, and finally queries an authoritative DNS server of a domain name (i.e., a server), where the authoritative DNS returns a query response (i.e., a first domain name query response) according to a DNS request, assuming that there are two response records as follows: com CNAME a.mec.a.com; a.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 traditional scheduling node, a.mec.a.com CNAME 1.1.1.1, may be directly accessed, ensuring compatibility with the originally built service node network.
Step S704: the DNS recursive query server sends a query response to the DNS engine.
In an embodiment of the present application, the recursive DNS server of the operator returns a response of the authoritative DNS 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 alias records of the query response contain second target information; and if the query response is determined to meet a 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 recursive 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 if the configured rule matching condition is that whether a CNAME RR record (i.e., an alias record) in the response packet contains a suffix, mec.a.com (i.e., second target information), and if the configured rule matching condition is hit, the configured suffix is replaced, so as to initiate the DNS query request again, where, for example, the suffix is replaced with hosta.mec.com, where hosta is a unique identifier of a region where the MEC is located.
Step S706: and sending the modified DNS 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.
In the embodiment of the application, the DNS authoritative server of the server returns an optimal service node IP according to various indexes such as MEC regional information, server loads and availability 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 serving 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 present application, the user equipment initiates connection to the service instance located on the MEC host a based on the target network address to perform data access.
In the embodiment of the application, the first domain name server is introduced at first, the first domain name server outputs the accurate scheduling capability to the outside in a unified manner through the edge computing platform, the accurate scheduling can be realized, the access delay of user equipment can be reduced by combining the advantage that the MEC platform is close to a user, the flow scheduling is optimized, and the user experience is improved. And secondly, development investment of each edge service program operator for the MEC platform is not needed, the existing flow scheduling facilities of each edge service are compatible, and the use cost of the MEC platform user is reduced. And finally, the edge service program operator can realize the adjustment strategy by modifying the authoritative DNS response message without operating and controlling the scheduling strategy through an edge cloud service provider, and the adjustment control is flexible.
An embodiment of the present application provides a domain name resolution apparatus, fig. 8 is a schematic structural diagram of the domain name resolution apparatus, and as shown in fig. 8, the domain name resolution apparatus 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.
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 generation module is further to:
and adding the target identifier to a first query domain name of the first domain name query request, so that the server side 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:
a third sending module, configured to send 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 generation module is further 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:
a second determining module, configured to determine that the first domain name query response meets a second preset condition, where the second preset condition is that an alias record of the first domain name query response includes second target information.
In some embodiments, the apparatus further comprises:
a third obtaining module, configured to obtain alias record information from the first domain name query response;
the generation module is further to: generating a second query domain name according to the alias recording 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 the 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 obtaining module is further configured 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, the target identifier is generated according to the network address of the first domain name server and a preset rule.
It should be noted that: in the domain name resolution device provided in the above embodiment, only the division of the program modules is illustrated when domain name resolution is performed, and in practical applications, the processing allocation may be completed by different program modules according to needs, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the domain name resolution device and the domain name resolution method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.
An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program 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 to a first query domain name of the first domain name query request, so that the server side 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: obtaining alias record information from the first domain name query response; generating a second query domain name according to the alias recording 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 the 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, the target identifier is generated according to the network address of the first domain name server and a preset rule.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The methods disclosed in the several method embodiments provided in the present application may be combined arbitrarily without conflict to obtain new method embodiments.
Features disclosed in several of the product embodiments provided in the present application may be combined in any combination to yield new product embodiments without conflict.
The features disclosed in the several method or apparatus embodiments provided in the present application may be combined arbitrarily, without conflict, to arrive at new method embodiments or apparatus embodiments.
The above description is only for the 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 conceive of the changes or substitutions within the technical scope of the present application, and shall 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 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.
2. The method of claim 1, wherein generating a second domain name query request according to the first domain name query request and a target identity comprises:
and adding the target identifier to a first query domain name of the first domain name query request, so that the server side obtains the target identifier by analyzing the first query domain name.
3. The method of claim 2, prior to the adding the target identity to the first query domain name of the first domain name query request, the method further comprising:
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, wherein generating a second domain name query request according to the first domain name query request and a target identity comprises:
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 receiving a first domain name query response returned by the target server and before generating the second domain name query request according to the first domain name query response and the target identifier, the method further comprising:
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:
obtaining alias record information from the first domain name query response;
generating a second query domain name according to the alias recording information and the target identifier;
and generating the second domain name query request according to the second query domain name.
7. The method according to claim 1, wherein the determining a server corresponding to the second domain name query request includes:
and sending the 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, the target identifier is generated according to the network address of the first domain name server and a preset rule.
9. A domain name resolution apparatus, the apparatus comprising:
the first acquisition module is used for acquiring a first domain name query request of a 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 generating 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 so that the server 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 implement 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 true CN114422477A (en) | 2022-04-29 |
| CN114422477B 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 (10)
| 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 |
| CN109640319A (en) * | 2019-01-16 | 2019-04-16 | 腾讯科技（深圳）有限公司 | Dispatching method, device and electronic equipment based on access information |
| CN110098947A (en) * | 2018-01-31 | 2019-08-06 | 华为技术有限公司 | A kind of dispositions method of application, equipment and system |
| CN110381131A (en) * | 2019-07-15 | 2019-10-25 | 北京奇艺世纪科技有限公司 | Implementation method, mobile terminal, server and the storage medium of MEC node identification |
| CN110572377A (en) * | 2019-08-22 | 2019-12-13 | 网宿科技股份有限公司 | Data forwarding method, plug-in and domain name server |
| 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 |
| CN113259260A (en) * | 2020-02-11 | 2021-08-13 | 华为技术有限公司 | Method and device for deploying application instance and scheduling application instance |
| US20210273987A1 (en) * | 2019-05-10 | 2021-09-02 | Tencent Technology (Shenzhen) Company Limited | Method, apparatus, and system for selecting mec node |
| CN113489772A (en) * | 2019-08-08 | 2021-10-08 | 腾讯科技（深圳）有限公司 | Network request processing method and device and electronic equipment |
-
2021
- 2021-12-30 CN CN202111648808.7A patent/CN114422477B/en active Active
Patent Citations (10)
| 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 |
| CN110098947A (en) * | 2018-01-31 | 2019-08-06 | 华为技术有限公司 | A kind of dispositions method of application, equipment and system |
| CN109640319A (en) * | 2019-01-16 | 2019-04-16 | 腾讯科技（深圳）有限公司 | Dispatching method, device and electronic equipment based on access information |
| US20210273987A1 (en) * | 2019-05-10 | 2021-09-02 | Tencent Technology (Shenzhen) Company Limited | Method, apparatus, and system for selecting mec node |
| CN110381131A (en) * | 2019-07-15 | 2019-10-25 | 北京奇艺世纪科技有限公司 | Implementation method, mobile terminal, server and the storage medium of MEC node identification |
| CN113489772A (en) * | 2019-08-08 | 2021-10-08 | 腾讯科技（深圳）有限公司 | Network request processing method and device and electronic equipment |
| CN112422701A (en) * | 2019-08-20 | 2021-02-26 | 华为技术有限公司 | Domain name system query method and communication device |
| CN110572377A (en) * | 2019-08-22 | 2019-12-13 | 网宿科技股份有限公司 | Data forwarding method, plug-in and domain name server |
| CN113067909A (en) * | 2020-01-02 | 2021-07-02 | ***通信有限公司研究院 | Edge node addressing method, device, equipment and storage medium |
| CN113259260A (en) * | 2020-02-11 | 2021-08-13 | 华为技术有限公司 | Method and device for deploying application instance and scheduling application instance |
Non-Patent Citations (2)
| Title |
|---|
| 姜昊，欧阳峰，汤新坤: "基于边缘云的CDN部署方案研究", 《有线网络》 * |
| 姜昊，欧阳峰，汤新坤: "基于边缘云的CDN部署方案研究", 《有线网络》, 15 June 2021 (2021-06-15) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114422477B (en) | 2023-07-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3993347A1 (en) | Method and device for application migration | |
| US11563713B2 (en) | Domain name server allocation method and apparatus | |
| EP3657765B1 (en) | Multi-access edge network service system and network service method | |
| US10715482B2 (en) | Wide area service discovery for internet of things | |
| US20230171618A1 (en) | Communication method and apparatus | |
| CN106937362B (en) | Network slice management device and network slice management method | |
| US20220103990A1 (en) | Communication Method, Apparatus, and System | |
| WO2021004528A1 (en) | Method, device and apparatus for address acquisition of application example and storage medium | |
| US10834202B2 (en) | Network service system and network service method | |
| CN110635933A (en) | Device for managing network of SDN, control method, and recording medium | |
| CN112104640B (en) | Data processing method, device and equipment of gateway and readable storage medium | |
| CN111885216A (en) | DNS query method, device, equipment and storage medium | |
| WO2015085573A1 (en) | Method and device for communication using white spectrum | |
| US20220263759A1 (en) | Addressing method, addressing system, and addressing apparatus | |
| CN109962834B (en) | Information processing method, system, terminal and computer storage medium | |
| CN114422477B (en) | Domain name resolution method, device and storage medium based on edge cloud architecture | |
| US20230216825A1 (en) | Gateway based ip address translation in communication networks | |
| JP2017118248A (en) | Device, method and program for name resolution | |
| EP3422674A1 (en) | A method of resolving a domain name by a dns server to a plurality of ip addresses based on location information of the user equipment | |
| CN113169936B (en) | Service chaining mechanism for data stream processing | |
| US11929979B1 (en) | Systems and methods for edge-aware domain name resolution | |
| KR20190053336A (en) | Device authentication method and system in the Internet of Things Network | |
| US11652781B2 (en) | Data processing method based on MEC platform, device, and storage medium | |
| US20220350748A1 (en) | Consistent hashing for communication devices | |
| EP4311280A1 (en) | Communication method and device |
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 |