CN116708366A - DNS domain name management method and device - Google Patents

DNS domain name management method and device Download PDF

Info

Publication number
CN116708366A
CN116708366A CN202310701394.2A CN202310701394A CN116708366A CN 116708366 A CN116708366 A CN 116708366A CN 202310701394 A CN202310701394 A CN 202310701394A CN 116708366 A CN116708366 A CN 116708366A
Authority
CN
China
Prior art keywords
domain name
name resolution
dns
target
cloud resource
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310701394.2A
Other languages
Chinese (zh)
Inventor
叶圣安
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN202310701394.2A priority Critical patent/CN116708366A/en
Publication of CN116708366A publication Critical patent/CN116708366A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]

Abstract

One or more embodiments of the present disclosure provide a DNS domain name management method and apparatus. The method comprises the following steps: acquiring a domain name resolution rule corresponding to a domain name of a target cloud resource; in response to receiving a domain name resolution request for a domain name of the target cloud resource, sending the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource, so that the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource; the domain name resolution result is received from the DNS resolver.

Description

DNS domain name management method and device
Technical Field
One or more embodiments of the present disclosure relate to the field of network data, and in particular, to a DNS domain name management method and apparatus.
Background
With the development of cloud on enterprise services, a part of large enterprises still keep private cloud networks off-line, such as network data centers (Internet Data Center, IDC) off-line, and build corresponding privately owned domain name systems (Domain Name System, DNS). If the privately owned DNS migrates to the public cloud network, the security requirement of the private cloud network cannot be guaranteed.
The related art introduces a DNS resolver corresponding to the private cloud network, and the DNS resolver achieves the purpose of DNS fusion between the public cloud network and the private cloud network. The DNS resolver may process DNS resolution requests for a private cloud network. In order to obtain an accurate DNS resolution result, the DNS resolver needs to sense information such as migration of service addresses of cloud resources in the private cloud network side, tenant isolation, and the like in real time. For this reason, the DNS resolver needs to acquire, in real time, domain name resolution rules related to the private cloud network from the cloud management end of the public cloud network.
In practical application, a DNS resolver is used as a far distance between an edge node and a cloud management end, the management capability of the cloud management end to the edge node is relatively weak, the link stability between the cloud management end and the edge node cannot be ensured, so that a domain name resolution rule cannot be updated in time, and domain name resolution errors are easily caused.
Disclosure of Invention
In view of this, one or more embodiments of the present disclosure provide a DNS domain name management method and apparatus to solve the problems in the related art.
In order to achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:
According to a first aspect of one or more embodiments of the present disclosure, a DNS domain name management method is provided, which is applied to a DNS server, and includes:
acquiring a domain name resolution rule corresponding to a domain name of a target cloud resource;
in response to receiving a domain name resolution request for a domain name of the target cloud resource, sending the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource, so that the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
the domain name resolution result is received from the DNS resolver.
Optionally, the domain name resolution rule includes address information of a target DNS server; the target DNS server is a DNS server for maintaining a domain name resolution result corresponding to a domain name of the target cloud resource;
correspondingly, the domain name resolution result corresponding to the domain name of the target cloud resource is obtained from the target DNS server based on the address information.
Optionally, the sending the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource includes:
Sending a request message based on a target data format to a DNS resolver corresponding to the target cloud resource, wherein the request message comprises the domain name resolution request and the domain name resolution rule; the target data format is a data format expanded according to an expansion mechanism of a DNS protocol.
Optionally, the DNS protocol-based extension mechanism is an end 0 extension mechanism.
Optionally, the target cloud resource is a cloud resource in a private cloud network created in the public cloud network by a tenant of the public cloud network; the DNS resolvers corresponding to the target cloud resources are DNS resolvers corresponding to private cloud networks where the target cloud resources are located; a cloud management end corresponding to the public cloud network maintains domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are uploaded by the tenant; the DNS server is a cloud server deployed on a public cloud network;
the obtaining a domain name resolution rule corresponding to the domain name of the target cloud resource includes:
and acquiring domain name resolution rules corresponding to domain names of target cloud resources in the private cloud network, which are maintained on a cloud management end corresponding to the public cloud network.
According to a second aspect of one or more embodiments of the present specification, there is provided a DNS domain name management method applied to a DNS resolver, including:
receiving a domain name resolution request aiming at a domain name of a target cloud resource corresponding to the DNS resolver from a DNS server, and a domain name resolution rule corresponding to the domain name of the target cloud resource;
performing domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
and sending the domain name resolution result to the DNS server.
Optionally, the domain name resolution rule includes address information of a target DNS server; the target DNS server is a DNS server for maintaining a domain name resolution result corresponding to a domain name of the target cloud resource;
the performing domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource, including:
according to the address information of the target DNS server, a domain name resolution request aiming at the domain name of the target cloud resource is sent to the target DNS server;
and acquiring a domain name resolution result corresponding to the domain name of the target cloud resource from the target DNS server.
Optionally, the receiving, from a DNS server, a domain name resolution request for a domain name of a target cloud resource corresponding to the DNS resolver, and a domain name resolution rule corresponding to the domain name of the target cloud resource, includes:
receiving a request message based on a target data format from a DNS server, wherein the request message comprises a domain name resolution request for a domain name of a target cloud resource corresponding to the DNS resolver and a domain name resolution rule corresponding to the domain name of the target cloud resource; the target data format is a data format expanded according to an expansion mechanism of a DNS protocol.
Optionally, the DNS protocol-based extension mechanism is an end 0 extension mechanism.
Optionally, the target cloud resource is a cloud resource in a private cloud network created in the public cloud network by a tenant of the public cloud network; the DNS resolvers corresponding to the target cloud resources are DNS resolvers corresponding to private cloud networks where the target cloud resources are located; a cloud management end corresponding to the public cloud network maintains domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are uploaded by the tenant; the DNS server is a cloud server deployed on a public cloud network.
According to a third aspect of one or more embodiments of the present specification, there is provided a DNS namemanagement device, including:
the rule receiving module is used for acquiring domain name resolution rules corresponding to the domain names of the target cloud resources;
a request forwarding module, configured to send, in response to receiving a domain name resolution request for a domain name of the target cloud resource, the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource, so that the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule, to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
and the result receiving module is used for receiving the domain name resolution result from the DNS resolver.
According to a fourth aspect of one or more embodiments of the present specification, there is provided a DNS namemanagement device, including:
the request receiving module is used for receiving a domain name resolution request aiming at a domain name of a target cloud resource corresponding to the DNS resolver from the DNS server and a domain name resolution rule corresponding to the target cloud resource;
the domain name resolution module is used for performing domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule so as to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
And the result sending module is used for sending the domain name resolution result to the DNS server.
According to a fifth aspect of one or more embodiments of the present specification, there is provided an electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of the first aspect by executing the executable instructions.
According to a sixth aspect of one or more embodiments of the present description, a computer-readable storage medium is presented, having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to the first aspect.
According to the embodiment of the application, when the DNS server side sends the domain name resolution request to the DNS resolver, the domain name resolution rule is sent to the DNS resolver, so that the DNS resolver can be ensured to perform domain name resolution based on the latest domain name resolution rule, the domain name resolution error caused by the fact that the update message of the domain name resolution rule of the cloud management side is not received is avoided, and the possibility of domain name resolution error is reduced.
Drawings
FIG. 1 is a flow chart of a DNS domain name management method provided in an exemplary embodiment;
FIG. 2 is a flowchart of a DNS domain name management method provided in an exemplary embodiment;
FIG. 3 is a schematic diagram of a target data format extended based on an EDNS0 extension mechanism provided by an exemplary embodiment;
FIG. 4 is a flowchart of another DNS domain name management method provided in an exemplary embodiment;
FIG. 5 is a flowchart of another DNS domain name management method provided in an exemplary embodiment;
fig. 6 is a schematic structural diagram of a DNS namemanagement device according to an exemplary embodiment;
fig. 7 is a schematic structural diagram of another DNS namemanagement device provided in an exemplary embodiment;
fig. 8 is a schematic structural diagram of an electronic device according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with aspects of one or more embodiments of the present description as detailed in the accompanying claims.
It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.
With the development of cloud on enterprise services, part of large enterprises still keep private cloud networks off-line, for example, off-line network data centers, and build corresponding privately owned domain name systems. If the privately owned DNS migrates to the public cloud network, the security requirement of the private cloud network cannot be guaranteed.
The related art introduces a DNS resolver corresponding to the private cloud network, and the DNS resolver achieves the purpose of DNS fusion between the public cloud network and the private cloud network. The DNS resolver corresponding to the private cloud network may provide DNS resolution services for the private cloud network, for processing a domain name resolution request in the private cloud network, and may also process a DNS resolution request in the private cloud network acquired from the public cloud network. The access problem between the private cloud network and the public cloud network can be solved through the DNS resolver, and a prerequisite is provided for the migration of the upper layer service to the public cloud network or the private cloud network. In order to obtain an accurate DNS resolution result, the DNS resolver needs to sense information such as migration of service addresses of cloud resources in the private cloud network, tenant isolation, and the like in real time. For this reason, the DNS resolver needs to acquire, in real time, domain name resolution rules related to the private cloud network from the cloud management end of the public cloud network.
As shown in fig. 1, each private cloud network is respectively deployed with a corresponding DNS resolver, where the DNS resolvers may receive a DNS resolution request for the private cloud network sent by a DNS server deployed on the public cloud network, and the DNS resolvers may perform domain name resolution based on the maintained domain name resolution rule, and return the obtained domain name resolution result to the DNS server. The DNS resolver can acquire the latest domain name resolution rule from the cloud management end deployed in the public cloud network, and update the domain name resolution rule maintained by the DNS resolver based on the update message for the domain name resolution rule received from the cloud management end.
In practical application, because a long distance may exist between the DNS resolver serving as an edge node and the cloud management end, the management capability of the cloud management end on the edge node is relatively weak, and the link stability between the cloud management end and the edge node cannot be ensured, so that the domain name resolution rule cannot be updated in time, and domain name resolution errors are easily caused.
In view of this, the present specification proposes a DNS domain name management method. The cloud management end does not directly send the update message of the domain name resolution rule to the DNS resolver any more, and when the DNS server end sends the domain name resolution request to the DNS resolver, the domain name resolution rule is sent to the DNS resolver, so that the DNS resolver carries out domain name resolution according to the received domain name resolution rule, and a domain name resolution result is obtained.
When the method is realized, domain name resolution rules corresponding to the domain name of the target cloud resource are obtained; in response to receiving a domain name resolution request for a domain name of the target cloud resource, sending the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource, so that the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource; the domain name resolution result is received from the DNS resolver.
In the technical scheme, when the DNS server side sends the domain name resolution request to the DNS resolver, the domain name resolution rule is sent to the DNS resolver, so that the DNS resolver can be ensured to perform domain name resolution based on the latest domain name resolution rule, domain name resolution errors caused by the fact that update information of the domain name resolution rule of the cloud management side is not received are avoided, and the possibility of domain name resolution errors is reduced.
In order to enable those skilled in the art to better understand the technical solutions of the present application, the technical solutions in the present specification will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.
Referring to fig. 2, fig. 2 is a schematic diagram of a DNS domain name management method according to an exemplary embodiment. The method can be applied to a DNS server.
It should be noted that, the DNS server may be a cloud server deployed in a public cloud network, and may be configured to process a domain name resolution request for a private cloud network corresponding to the DNS server. The public cloud network may deploy one or more DNS servers in each place, where the DNS servers in this specification may be DNS servers in the same area as the private cloud network in the DNS servers deployed by the public cloud network, and may be referred to as Local DNS servers, or central DNS servers. The DNS server may correspond to one or more private cloud networks located in the same area.
The private cloud network corresponding to the DNS server can be a cloud environment built or managed by an enterprise or a person, and can be in butt joint with a public cloud network; alternatively, a private cloud network created in the public cloud network may be created for a tenant (user) of the public cloud network. And a user can build a privately-owned DNS in the privately-owned cloud network so as to facilitate the management of cloud resources in the privately-owned network by the user.
It should be noted that the public cloud network may be a cloud environment provided by a professional cloud service provider, and an enterprise or individual may rent its services to host applications, data, and services.
The DNS domain name management method may include the following steps.
S210, acquiring a domain name resolution rule corresponding to the domain name of the target cloud resource.
The DNS server may obtain, in advance, a domain name resolution rule corresponding to the private cloud network, and specifically may include a domain name resolution rule corresponding to a domain name of each cloud resource in the private cloud network.
It should be noted that, the cloud resource may refer to a resource available for computing and storing in a cloud network, and may include a virtual machine, a container, a storage space, a database, an application program, and so on. The target cloud resource is a cloud resource in a private cloud network. And a user can build a privately owned DNS in the private cloud network, and allocate corresponding domain names for each cloud resource and domain name resolution rules corresponding to each domain name.
The DNS server may acquire the domain name resolution rule corresponding to the domain name of the target cloud resource in various manners, for example, the user may upload the domain name resolution rule corresponding to the domain name of the target cloud resource to the DNS server, or the DNS server may acquire the domain name resolution rule corresponding to the domain name of the target cloud resource in the private cloud network, which is maintained from the cloud management end corresponding to the public cloud network.
For example, in one embodiment, domain name resolution rules corresponding to domain names of respective cloud resources in respective private cloud networks may be maintained at cloud management ends corresponding to public cloud networks. If the domain name resolution rule corresponding to the domain name needs to be updated, the user can upload the updated information of the domain name resolution rule or the updated domain name resolution rule to the cloud management end, so that the cloud management end updates the maintained domain name resolution rule. The cloud management end can periodically send domain name resolution rules corresponding to domain names of all cloud resources of the private cloud network corresponding to the DNS server end; or, the cloud management end can send the updated domain name resolution rule to the DNS server after updating the domain name resolution rule; or, the DNS server may request, from the cloud management end, to obtain a domain name resolution rule corresponding to the domain name of the target cloud resource in the private cloud network according to an actual requirement.
S220, responding to the received domain name resolution request for the domain name of the target cloud resource, and sending the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource, so that the DNS resolver carries out domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource.
The DNS resolver corresponding to the target cloud resource may be a DNS resolver corresponding to a private cloud network where the target cloud resource is located. The DNS resolver may be a server in the private cloud network for processing a domain name resolution request for a domain name of a cloud resource in the private cloud network initiated by the public cloud network side.
The DNS resolver may maintain domain name resolution rules corresponding to domain names of respective cloud resources in the private cloud network.
If cloud resources in the public cloud network want to access target cloud resources in the private cloud network, a domain name resolution request for domain names of the target cloud resources can be initiated to a DNS server corresponding to the private cloud network in the public cloud network. The cloud resources in the public cloud network may be resources available for computation and storage, and the services purchased for the users of the private cloud network may correspond to the cloud resources.
After receiving the domain name resolution request, the DNS server may first determine whether the domain name targeted by the domain name resolution request is a domain name of a cloud resource in the private cloud network; if not, performing domain name resolution by adopting a conventional domain name resolution mode, for example, performing domain name resolution by adopting a recursion mode to obtain a domain name resolution result corresponding to the domain name aimed at by the domain name resolution request; if so, it may be determined that the received domain name resolution request is a domain name resolution request for a domain name of a target cloud resource in a private cloud network, in which case the domain name resolution request and a domain name resolution rule corresponding to the domain name of the target cloud resource may be sent to a DNS resolver corresponding to the private network.
The manner in which the DNS server sends the domain name resolution request and the domain name resolution rule to the DNS resolver corresponding to the target cloud resource may be various, for example, the domain name resolution request and the domain name resolution rule may be carried by the same request message and sent to the DNS resolver corresponding to the target cloud resource, or the domain name resolution request and the domain name resolution rule may be respectively sent to the DNS resolver corresponding to the target cloud resource.
For example, in one embodiment, in response to receiving a domain name resolution request for a domain name of the target cloud resource, the DNS server may send a request message based on a target data format to a DNS resolver corresponding to the target cloud resource, where the request message includes the domain name resolution request and the domain name resolution rule.
It should be noted that, the target data format of the request message may be a data format that is extended from an extension mechanism according to the DNS protocol. The DNS protocol expansion mechanism may be varied and may include, for example, DNS security expansion (DNSSEC), DNS expansion mechanism (Extension Mechanisms for DNS, EDNS), and the like. Among these, EDNS adds some fields to the DNS message format.
For example, in one embodiment, the DNS protocol expansion mechanism is an EDNS0 expansion mechanism. Referring to fig. 3, fig. 3 shows a target data format extended based on the EDNS0 extension mechanism, where the target data format includes an OPTION-CODE field for representing a data type, an OPTION length field for representing a data length, a field containing a domain name resolution rule, and so on. Wherein the domain name resolution rule may include ADDRESS information for indicating a target DNS server, the target DNS server being a DNS server that maintains a domain name resolution result corresponding to a domain name of the target cloud resource in the cloud network, and a DNSSERVER-NUM field for indicating a server identification of the target DNS server, an ADDRESS field and a PORT field for indicating an IP ADDRESS and a PORT number of the target DNS server are included in the target data format.
For example, in one embodiment, in response to receiving a domain name resolution request for a domain name of the target cloud resource, the DNS server may check whether the DNS server stores a domain name resolution rule corresponding to the domain name of the target cloud resource, and if the DNS server does not store a domain name resolution rule corresponding to the domain name of the target cloud resource, may send a rule request for the domain name of the target cloud resource or a rule request for a private cloud network where the target cloud resource is located to the cloud management end, so as to obtain, from the cloud management end, a domain name resolution rule corresponding to the domain name of the target cloud resource or a domain name resolution rule corresponding to a domain name of each cloud resource of the private cloud network, and store the received domain name resolution rule.
It should be noted that, the DNS server may maintain the survival time length corresponding to each domain name resolution rule, and if the survival time length of any domain name resolution rule reaches a preset time length threshold, the DNS server may discard the domain name resolution rule, or request to update the domain name resolution rule to the cloud management end.
After acquiring a domain name resolution request and a domain name resolution rule corresponding to the domain name of the target cloud resource from the DNS server, the DNS resolver may perform domain name resolution on the domain name of the target cloud resource based on the received domain name resolution rule, so as to obtain a domain name resolution result corresponding to the domain name of the target cloud resource. The domain name resolution result may include obtaining address information, such as an IP address, corresponding to the domain name of the target cloud resource.
The DNS resolver may perform domain name resolution on the domain name of the target cloud resource according to the received domain name resolution rule, and if the DNS resolver maintains a domain name resolution result corresponding to the domain name of the target cloud resource, the DNS resolver may query from data maintained by the DNS resolver to obtain a domain name resolution result corresponding to the domain name of the target cloud resource; alternatively, if the DNS resolver does not maintain a domain name resolution result corresponding to the domain name of the target cloud resource, and the domain name resolution rule includes address information of a target DNS server, for example, as shown in fig. 3, the domain name resolution rule in the request message may include a server identifier of the target DNS server and address information (IP address and port number) of the target DNS server, the DNS resolver may send a domain name resolution request for the domain name of the target cloud resource to the target DNS server according to the address information of the target DNS server; and acquiring a domain name resolution result corresponding to the domain name of the target cloud resource from the target DNS server.
S230, receiving the domain name resolution result from the DNS resolver.
And the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule, and can send the domain name resolution result to the DNS server after obtaining the domain name resolution result corresponding to the domain name of the target cloud resource.
After receiving the domain name resolution result, the DNS server may return the domain name resolution result to cloud resources of a public cloud network that initiates the domain name resolution request, so that the cloud resources of the public cloud network may access target cloud resources in the private cloud network based on the domain name resolution result.
Referring to fig. 4, fig. 4 shows a DNS domain name management method, which includes:
the cloud management end can periodically send domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are uploaded by a user, to a DNS server corresponding to the private cloud network so as to update the domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are maintained by the DNS server;
the DNS server side responds to receiving a domain name resolution request for a domain name of a target cloud resource of the private cloud network, and sends a request message to a DNS resolver corresponding to the private cloud network, wherein the request message comprises the domain name resolution request for the domain name of the target cloud resource of the private cloud network and a domain name resolution rule corresponding to the domain name of the target cloud resource; the domain name resolution rule comprises address information of a target DNS server corresponding to the target cloud resource, and the target DNS server is a DNS server for maintaining a domain name resolution result corresponding to a domain name of the target cloud resource in the private cloud network;
After receiving the domain name resolution request and the domain name resolution rule, the DNS resolver can send the domain name resolution request to a target DNS server according to the address information of the target DNS server in the received domain name resolution rule;
the target DNS server performs domain name resolution on the domain name of the target cloud resource according to the received domain name resolution request for the domain name of the target cloud resource so as to obtain a domain name resolution result corresponding to the domain name of the target cloud resource, and returns the obtained domain name resolution result to the DNS resolver;
the DNS resolver returns the obtained domain name resolution result to the DNS server;
and the DNS server returns a domain name resolution result to the initiating terminal of the domain name resolution request, so that the initiating terminal can access target cloud resources in the private cloud network according to the domain name resolution result.
It should be noted that, the domain name resolution result may be resolution success or resolution failure, and if resolution is successful, the domain name resolution result may further include an IP address corresponding to the domain name of the target cloud resource; if the resolution fails, the domain name resolution result may further include a reason for the resolution failure.
In one embodiment, if the DNS server receives the domain name resolution result from the DNS resolver as resolution is successful, the DNS server may return the domain name resolution result to the cloud resource of the public cloud network that initiates the domain name resolution request, so that the cloud resource of the public cloud network may access the target cloud resource in the private cloud network based on the domain name resolution result; if the domain name resolution result is that the resolution fails, the DNS server may request to the cloud management end again to obtain a new domain name resolution rule corresponding to the domain name of the target cloud resource in the cloud network, and after receiving the new domain name resolution rule, send the domain name resolution request and the new domain name resolution rule to the DNS resolver corresponding to the private cloud network again, so that the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the new domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource.
Because sending the domain name resolution rule at the same time increases network load when sending the domain name resolution request to the DNS resolver corresponding to the cloud network, the DNS server may not send the domain name resolution rule to the DNS resolver first, and send the domain name resolution rule to the DNS resolver when receiving the domain name resolution result as resolution failure.
For example, in one implementation, in response to receiving a domain name resolution request for a domain name of a target cloud resource of the private cloud network, a DNS server sends the domain name resolution request to a DNS resolver corresponding to the private cloud network;
after receiving a domain name resolution request for a domain name of a target cloud resource, a DNS resolver can send the domain name resolution request to the target DNS server based on address information of the target DNS server in a currently maintained domain name resolution rule so as to acquire a domain name resolution result corresponding to the domain name of the target cloud resource from the target DNS server;
if the address of the target DNS server corresponding to the domain name of the target cloud resource is migrated, the obtained domain name resolution result may be resolution failure;
the DNS resolver returns the domain name resolution result to the DNS server, and when the DNS server determines that the obtained domain name resolution result is resolution failure, the DNS server can request the cloud management end to acquire a new domain name resolution rule for the domain name of the target cloud resource of the private cloud network, wherein the new domain name resolution rule can comprise address information of the new target DNS server;
After acquiring a new domain name resolution rule, sending a request message to the DNS resolver, wherein the request message comprises a request for domain name resolution and the new domain name resolution rule;
after receiving the domain name resolution request and the new domain name resolution rule, the DNS resolver can send the domain name resolution request to the new target DNS server according to the address information of the new target DNS server in the new domain name resolution rule, so as to obtain a new domain name resolution result corresponding to the domain name of the target cloud resource from the new target DNS server;
and the DNS server returns the new domain name resolution result to the DNS server, and returns the new domain name resolution result to the initiating terminal of the domain name resolution request under the condition that the DNS server determines that the new domain name resolution result is successfully resolved, so that the initiating terminal can access the target cloud resources in the private cloud network according to the domain name resolution result.
According to the technical scheme of the embodiment, when the DNS server side sends the domain name resolution request to the DNS resolver, the domain name resolution rule is sent to the DNS resolver, so that the DNS resolver can be ensured to resolve the domain name based on the latest domain name resolution rule, domain name resolution errors caused by the fact that the updating message of the domain name resolution rule of the cloud management side is not received are avoided, and the possibility of the domain name resolution errors is reduced.
Referring to fig. 5, fig. 5 illustrates a DNS domain name management method applied to a DNS resolver corresponding to a cloud network, the method including the steps of.
S510, receiving a domain name resolution request aiming at a domain name of a target cloud resource corresponding to the DNS resolver from a DNS server, and a domain name resolution rule corresponding to the domain name of the target cloud resource;
s530, performing domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
s530, sending the domain name resolution result to the DNS server.
Optionally, the domain name resolution rule includes address information of a target DNS server; the target DNS server is a DNS server which maintains a domain name resolution result corresponding to the domain name of the target cloud resource;
the performing domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource, including:
according to the address information of the target DNS server, a domain name resolution request aiming at the domain name of the target cloud resource is sent to the target DNS server;
And acquiring a domain name resolution result corresponding to the domain name of the target cloud resource from the target DNS server.
Optionally, the receiving, from a DNS server, a domain name resolution request for a domain name of a target cloud resource corresponding to the DNS resolver, and a domain name resolution rule corresponding to the domain name of the target cloud resource, includes:
receiving a request message based on a target data format from a DNS server, wherein the request message comprises a domain name resolution request for a domain name of a target cloud resource corresponding to the DNS resolver and a domain name resolution rule corresponding to the domain name of the target cloud resource; the target data format is a data format expanded according to an expansion mechanism of a DNS protocol.
Optionally, the DNS protocol-based extension mechanism is an end 0 extension mechanism.
Optionally, the target cloud resource is a cloud resource in a private cloud network created in the public cloud network by a tenant of the public cloud network; the DNS resolvers corresponding to the target cloud resources are DNS resolvers corresponding to private cloud networks where the target cloud resources are located; a cloud management end corresponding to the public cloud network maintains domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are uploaded by the tenant; the DNS server is a cloud server deployed on a public cloud network
According to the embodiment of the application, when the DNS server side sends the domain name resolution request to the DNS resolver, the domain name resolution rule is sent to the DNS resolver, so that the DNS resolver can be ensured to perform domain name resolution based on the latest domain name resolution rule, the domain name resolution error caused by the fact that the update message of the domain name resolution rule of the cloud management side is not received is avoided, and the possibility of domain name resolution error is reduced.
The application also provides an embodiment of the DNS domain name management device corresponding to the embodiment of the DNS domain name management method.
As shown in fig. 6, the DNS namemanagement device includes: rule receiving module 601, request forwarding module 602, and result receiving module 603.
The rule receiving module 601 is configured to obtain a domain name resolution rule corresponding to a domain name of a target cloud resource;
the request forwarding module 602 is configured to send, in response to receiving a domain name resolution request for a domain name of the target cloud resource, the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource, so that the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule, to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
The result receiving module 603 is configured to receive the domain name resolution result from the DNS resolver.
The domain name resolution rule comprises address information of a target DNS server; the target DNS server is a DNS server for maintaining a domain name resolution result corresponding to a domain name of the target cloud resource;
correspondingly, the domain name resolution result corresponding to the domain name of the target cloud resource is obtained from the target DNS server based on the address information.
Optionally, the request forwarding module 602 is configured to send a request message based on a target data format to a DNS resolver corresponding to the target cloud resource, where the request message includes the domain name resolution request and the domain name resolution rule; the target data format is a data format expanded according to an expansion mechanism of a DNS protocol.
Optionally, the DNS protocol-based extension mechanism is an end 0 extension mechanism.
Optionally, the target cloud resource is a cloud resource in a private cloud network created in the public cloud network by a tenant of the public cloud network; the DNS resolvers corresponding to the target cloud resources are DNS resolvers corresponding to private cloud networks where the target cloud resources are located; a cloud management end corresponding to the public cloud network maintains domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are uploaded by the tenant; the DNS server is a cloud server deployed on a public cloud network;
The rule receiving module 601 is configured to obtain a domain name resolution rule corresponding to a domain name of a target cloud resource in the private cloud network, where the domain name resolution rule corresponds to a domain name of a target cloud resource in the private cloud network, and the domain name resolution rule is maintained on a cloud management end corresponding to the public cloud network.
In the technical scheme, when the DNS server side sends the domain name resolution request to the DNS resolver, the domain name resolution rule is sent to the DNS resolver, so that the DNS resolver can be ensured to perform domain name resolution based on the latest domain name resolution rule, domain name resolution errors caused by the fact that update information of the domain name resolution rule of the cloud management side is not received are avoided, and the possibility of domain name resolution errors is reduced.
The application also provides an embodiment of the DNS domain name management device corresponding to the embodiment of the DNS domain name management method.
As shown in fig. 7, the DNS namemanagement device includes: a request receiving module 701, a domain name resolution module 702 and a result sending module 703.
The request receiving module 701 is configured to receive, from a DNS server, a domain name resolution request for a domain name of a target cloud resource corresponding to the DNS resolver, and a domain name resolution rule corresponding to the domain name of the target cloud resource;
The domain name resolution module 702 is configured to perform domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule, so as to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
the result sending module 703 is configured to send the domain name resolution result to the DNS server.
Optionally, the domain name resolution rule includes address information of a target DNS server; the target DNS server is a DNS server for maintaining a domain name resolution result corresponding to a domain name of the target cloud resource;
the domain name resolution module 702 is configured to:
according to the address information of the target DNS server, a domain name resolution request aiming at the domain name of the target cloud resource is sent to the target DNS server;
and acquiring a domain name resolution result corresponding to the domain name of the target cloud resource from the target DNS server.
Optionally, the request receiving module 701 is configured to receive, from a DNS server, a request message based on a target data format, where the request message includes a domain name resolution request for a domain name of a target cloud resource corresponding to the DNS resolver and a domain name resolution rule corresponding to the domain name of the target cloud resource; the target data format is a data format expanded according to an expansion mechanism of a DNS protocol.
Optionally, the DNS protocol-based extension mechanism is an end 0 extension mechanism.
Optionally, the target cloud resource is a cloud resource in a private cloud network created in the public cloud network by a tenant of the public cloud network; the DNS resolvers corresponding to the target cloud resources are DNS resolvers corresponding to private cloud networks where the target cloud resources are located; a cloud management end corresponding to the public cloud network maintains domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are uploaded by the tenant; the DNS server is a cloud server deployed on a public cloud network.
In the technical scheme, when the DNS server side sends the domain name resolution request to the DNS resolver, the domain name resolution rule is sent to the DNS resolver, so that the DNS resolver can be ensured to perform domain name resolution based on the latest domain name resolution rule, domain name resolution errors caused by the fact that update information of the domain name resolution rule of the cloud management side is not received are avoided, and the possibility of domain name resolution errors is reduced.
Fig. 8 is a schematic block diagram of an apparatus according to an exemplary embodiment. Referring to fig. 8, at the hardware level, the device includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile storage 810, although other hardware is possible. One or more embodiments of the present description may be implemented in a software-based manner, such as by the processor 802 reading a corresponding computer program from the non-volatile memory 810 into the memory 808 and then running. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region, and provide corresponding operation entries for the user to select authorization or rejection.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.

Claims (14)

1. The DNS domain name management method is characterized by being applied to a DNS server and comprising the following steps:
acquiring a domain name resolution rule corresponding to a domain name of a target cloud resource;
in response to receiving a domain name resolution request for a domain name of the target cloud resource, sending the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource, so that the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
the domain name resolution result is received from the DNS resolver.
2. The method of claim 1, wherein the domain name resolution rule includes address information of a target DNS server; the target DNS server is a DNS server for maintaining a domain name resolution result corresponding to a domain name of the target cloud resource;
Correspondingly, the domain name resolution result corresponding to the domain name of the target cloud resource is obtained from the target DNS server based on the address information.
3. The method of claim 1, wherein the sending the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource comprises:
sending a request message based on a target data format to a DNS resolver corresponding to the target cloud resource, wherein the request message comprises the domain name resolution request and the domain name resolution rule; the target data format is a data format expanded according to an expansion mechanism of a DNS protocol.
4. A method according to claim 3, wherein the DNS protocol based expansion mechanism is an end 0 expansion mechanism.
5. The method according to any of claims 1-4, wherein the target cloud resource is a cloud resource in a private cloud network created in a public cloud network by a tenant of the public cloud network; the DNS resolvers corresponding to the target cloud resources are DNS resolvers corresponding to private cloud networks where the target cloud resources are located; a cloud management end corresponding to the public cloud network maintains domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are uploaded by the tenant; the DNS server is a cloud server deployed on a public cloud network;
The obtaining a domain name resolution rule corresponding to the domain name of the target cloud resource includes:
and acquiring domain name resolution rules corresponding to domain names of target cloud resources in the private cloud network, which are maintained on a cloud management end corresponding to the public cloud network.
6. A DNS nameplate method, applied to a DNS resolver, comprising:
receiving a domain name resolution request aiming at a domain name of a target cloud resource corresponding to the DNS resolver from a DNS server, and a domain name resolution rule corresponding to the domain name of the target cloud resource;
performing domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
and sending the domain name resolution result to the DNS server.
7. The method of claim 6, wherein the domain name resolution rule includes address information of a target DNS server; the target DNS server is a DNS server for maintaining a domain name resolution result corresponding to a domain name of the target cloud resource;
the performing domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule to obtain a domain name resolution result corresponding to the domain name of the target cloud resource, including:
According to the address information of the target DNS server, a domain name resolution request aiming at the domain name of the target cloud resource is sent to the target DNS server;
and acquiring a domain name resolution result corresponding to the domain name of the target cloud resource from the target DNS server.
8. The method of claim 6, wherein the receiving, from a DNS server, a domain name resolution request for a domain name of a target cloud resource corresponding to the DNS resolver, and a domain name resolution rule corresponding to the domain name of the target cloud resource, comprises:
receiving a request message based on a target data format from a DNS server, wherein the request message comprises a domain name resolution request for a domain name of a target cloud resource corresponding to the DNS resolver and a domain name resolution rule corresponding to the domain name of the target cloud resource; the target data format is a data format expanded according to an expansion mechanism of a DNS protocol.
9. The method of claim 8, wherein the DNS protocol-based expansion mechanism is an end 0 expansion mechanism.
10. The method according to any of claims 6-9, wherein the target cloud resource is a cloud resource in a private cloud network created in a public cloud network by a tenant of the public cloud network; the DNS resolvers corresponding to the target cloud resources are DNS resolvers corresponding to private cloud networks where the target cloud resources are located; a cloud management end corresponding to the public cloud network maintains domain name resolution rules corresponding to domain names of all cloud resources in the private cloud network, which are uploaded by the tenant; the DNS server is a cloud server deployed on a public cloud network.
11. A DNS nameplate managing apparatus, comprising:
the rule receiving module is used for acquiring domain name resolution rules corresponding to the domain names of the target cloud resources;
a request forwarding module, configured to send, in response to receiving a domain name resolution request for a domain name of the target cloud resource, the domain name resolution request and the domain name resolution rule to a DNS resolver corresponding to the target cloud resource, so that the DNS resolver performs domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule, to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
and the result receiving module is used for receiving the domain name resolution result from the DNS resolver.
12. A DNS nameplate managing apparatus, comprising:
the request receiving module is used for receiving a domain name resolution request aiming at a domain name of a target cloud resource corresponding to the DNS resolver from the DNS server and a domain name resolution rule corresponding to the target cloud resource;
the domain name resolution module is used for performing domain name resolution on the domain name of the target cloud resource based on the domain name resolution rule so as to obtain a domain name resolution result corresponding to the domain name of the target cloud resource;
And the result sending module is used for sending the domain name resolution result to the DNS server.
13. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement the method of any of claims 1-10 by executing the executable instructions.
14. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method of any of claims 1-10.
CN202310701394.2A 2023-06-13 2023-06-13 DNS domain name management method and device Pending CN116708366A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310701394.2A CN116708366A (en) 2023-06-13 2023-06-13 DNS domain name management method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310701394.2A CN116708366A (en) 2023-06-13 2023-06-13 DNS domain name management method and device

Publications (1)

Publication Number Publication Date
CN116708366A true CN116708366A (en) 2023-09-05

Family

ID=87828887

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310701394.2A Pending CN116708366A (en) 2023-06-13 2023-06-13 DNS domain name management method and device

Country Status (1)

Country Link
CN (1) CN116708366A (en)

Similar Documents

Publication Publication Date Title
CN107948135B (en) Data processing method and device supporting multiple API protocols
CN111314472B (en) Domain name resolution method, domain name resolution server and terminal equipment
CN111800458B (en) Dynamic load balancing method and system for Kubernetes container cloud platform
CN113452592B (en) Cross-cloud data access method and device under hybrid cloud architecture
WO2017054526A1 (en) Arp entry generation method and device
CN106933548B (en) Global information obtaining, processing and updating method, device and system
CN107153644B (en) Data synchronization method and device
CN110677492B (en) Access request processing method and device, electronic equipment and storage medium
CN109327559B (en) Domain name resolution method and device based on hybrid cloud platform
CN104378452A (en) Method, device and system for domain name resolution
CN107172214B (en) Service node discovery method and device with load balancing function
CN107135242B (en) Mongodb cluster access method, device and system
CN111786984B (en) Pod communication connection method and device, electronic equipment and storage medium
CN111752681A (en) Request processing method, device, server and computer readable storage medium
CN113438307A (en) Domain name resolution method, server, system and storage medium
CN115002228B (en) Service cascade calling method and device, electronic equipment and storage medium
CN113315848A (en) Access control method, device and equipment
US10986065B1 (en) Cell-based distributed service architecture with dynamic cell assignment
CN113301005B (en) Data acquisition method and device
US8972604B1 (en) Network address retention and assignment
CN110830492B (en) Method and system for mutually scheduling edge applications based on CoreDNS registration service
US11303606B1 (en) Hashing name resolution requests according to an identified routing policy
CN113301173A (en) Domain name updating system and method, message forwarding method and server
CN116708366A (en) DNS domain name management method and device
CN112532666A (en) Reverse proxy method, apparatus, storage medium, 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