Domain name resolution method and device, equipment and storage medium

Abstract

The invention discloses a domain name resolution method and device, equipment and a storage medium, and relates to the technical field of communication, and the method comprises the steps: creating a subnet and a security group in a virtual private cloud on a preset cloud platform, and building a domain name resolution server based on the subnet and the security group; determining a domain name configuration file based on the predetermined domain name resolution software, and configuring the predetermined domain name resolution software by using the domain name configuration file so as to deploy the configured domain name resolution software to a domain name resolution server; and in the deployed domain name resolution server, determining a software service file based on a software starting command and a software restarting mechanism of the configured domain name resolution software, and driving the configured domain name resolution software to operate based on the software service file so as to analyze the domain name to be analyzed in the virtual private cloud. Therefore, the efficiency and the security of domain name resolution on the cloud platform are improved.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a domain name resolution method, device, equipment and storage medium. Background Art

[0002] As the number of Internet users is growing explosively, high concurrent access has become a severe challenge faced by many website applications. To ensure stable business operation, it has become a common response strategy to split the business into multiple servers to share the pressure, and use the same VPC (Virtual Private Cloud) to allow cloud servers to access each other through intranet IP (Internet Protocol) addresses. However, this solution has serious drawbacks. Once the cloud server is switched and the intranet IP address changes, the business code has to be modified and the changes re-published. This process is not only cumbersome and complicated, but also greatly increases the maintenance cost and difficulty, seriously affecting the continuity and stability of the business.

[0003] At the same time, the existing network settings still have many security and performance issues. If the intranet service is bound to a public IP address, malicious threats can easily penetrate the enterprise intranet through the Internet, causing the enterprise intranet domain name to be attacked and internal data to be leaked. If the DNS (Domain Name System) server associated with the VPC subnet is set to a public DNS, the cloud server must go through the public DNS resolution when accessing the cloud service. This process has a large access delay, which greatly reduces the user experience.

[0004] Therefore, how to improve the efficiency and security of domain name resolution on cloud platforms is a technical problem that needs to be solved urgently. Summary of the invention

[0005] In view of this, the purpose of the present invention is to provide a domain name resolution method, device, equipment and storage medium, which can improve the efficiency and security of domain name resolution on the cloud platform. The specific scheme is as follows:

[0006] In a first aspect, the present application provides a domain name resolution method, comprising:

[0007] In a virtual private cloud on a preset cloud platform, a subnet and a security group are created, and a domain name resolution server is built based on the subnet and the security group; wherein the inbound rule of the security group is to allow only traffic through a preset domain name resolution port of the server to enter the domain name resolution server;

[0008] Determining a domain name configuration file based on a predetermined domain name resolution software, and configuring the predetermined domain name resolution software using the domain name configuration file, so as to deploy the configured domain name resolution software to the domain name resolution server;

[0009] In the deployed domain name resolution server, a software service file is determined based on the software startup command and software restart mechanism of the configured domain name resolution software, and the configured domain name resolution software is driven to run based on the software service file to resolve the domain name to be resolved in the virtual private cloud.

[0010] Optionally, creating a subnet and a security group in a virtual private cloud on a preset cloud platform includes:

[0011] In a virtual private cloud on a preset cloud platform, determining a classless inter-domain routing scope of the virtual private cloud as a private cloud routing scope, and determining a target routing scope based on the private cloud routing scope to create a subnet using the target routing scope;

[0012] Determine inbound rules and outbound rules, and create a security group using the inbound rules and the outbound rules; wherein the outbound rule allows traffic through all ports of the server to flow out of the domain name resolution server.

[0013] Optionally, the building of a domain name resolution server based on the subnet and the security group includes:

[0014] A domain name resolution server is built based on preset computing and storage specifications, preset image versions, the subnet, and the security group.

[0015] Optionally, determining the domain name configuration file based on a predetermined domain name resolution software includes:

[0016] Creating an initial configuration file in an installation directory corresponding to a predetermined domain name resolution software, and determining the port number of the preset domain name resolution port and the IP address of the domain name resolution server as first configuration information;

[0017] Determine the domain name cache time, the domain name record file loading time and the file storage address of the domain name record file as the second configuration information;

[0018] The first configuration information and the second configuration information are added to the initial configuration file to obtain a domain name configuration file.

[0019] Optionally, the determining of the software service file based on the software startup command and software restart mechanism of the domain name resolution software after the configuration includes:

[0020] Based on the predetermined domain name resolution software, an initial service file, a software startup command and a software restart mechanism are determined, and the software startup command and the software restart mechanism are added to the initial service file to obtain a software service file.

[0021] Optionally, the step of driving the configured domain name resolution software to run based on the software service file includes:

[0022] The software service file is added to the daemon process, and the configured domain name resolution software is started using the software startup instruction in the software service file to drive the configured domain name resolution software to run.

[0023] Optionally, resolving the domain name to be resolved in the virtual private cloud includes:

[0024] Determine the domain name to be resolved in the virtual private cloud, and resolve the domain name to be resolved based on the domain name record file; wherein the domain name record file is a file that records the mapping relationship between the domain name and the IP address.

[0025] In a second aspect, the present application provides a domain name resolution device, including:

[0026] A server building module is used to create a subnet and a security group in a virtual private cloud on a preset cloud platform, and to build a domain name resolution server based on the subnet and the security group; wherein the inbound rule of the security group is to only allow traffic through a preset domain name resolution port of the server to enter the domain name resolution server;

[0027] A software configuration module, used to determine a domain name configuration file based on a predetermined domain name resolution software, and configure the predetermined domain name resolution software using the domain name configuration file, so as to deploy the configured domain name resolution software to the domain name resolution server;

[0028] The domain name resolution module is used to determine the software service file in the deployed domain name resolution server based on the software startup command and software restart mechanism of the configured domain name resolution software, and drive the configured domain name resolution software to run based on the software service file to resolve the domain name to be resolved in the virtual private cloud.

[0029] In a third aspect, the present application provides an electronic device, including:

[0030] Memory, used to store computer programs;

[0031] The processor is used to execute the computer program to implement the aforementioned domain name resolution method.

[0032] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned domain name resolution method is implemented.

[0033] In this application, in a virtual private cloud on a preset cloud platform, a subnet and a security group are created, and a domain name resolution server is built based on the subnet and the security group; wherein the inbound rule of the security group is to only allow traffic via the server preset domain name resolution port to enter the domain name resolution server; a domain name configuration file is determined based on a predetermined domain name resolution software, and the predetermined domain name resolution software is configured using the domain name configuration file to deploy the configured domain name resolution software to the domain name resolution server; in the deployed domain name resolution server, a software service file is determined based on the software startup command and software restart mechanism of the configured domain name resolution software, and the configured domain name resolution software is driven to run based on the software service file to resolve the domain name to be resolved in the virtual private cloud. As can be seen from the above, in the virtual private cloud of the preset cloud platform, the private cloud routing range is first determined and the subnet is divided. Set up a security group, the inbound rule only allows traffic from the server preset domain name resolution port to enter, and the outbound rule allows all port traffic to flow out. A domain name resolution server is built based on this subnet and security group. Select the domain name resolution software, create an initial configuration file in its installation directory, write the preset domain name resolution port number, server IP address, and key information such as domain name cache time, record file loading time and storage address as configuration parameters to form a complete domain name configuration file, so as to complete the configuration of the software and deploy it to the built server. Finally, according to the startup command and restart mechanism of the configured software, create a software service file and add it to the daemon process. Start the software through the service file and make it run. After the software is running, the domain name to be resolved in the virtual private cloud is resolved according to the domain name record file to realize the mapping conversion between domain name and IP address. In this way, this application can improve the efficiency and security of domain name resolution on the cloud platform, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0035] Figure 1 A flow chart of a domain name resolution method disclosed in this application;

[0036] Figure 2 A schematic diagram of a domain name resolution system deployment architecture disclosed in this application;

[0037] Figure 3 A flowchart of a specific domain name resolution method disclosed in this application;

[0038] Figure 4 A schematic diagram of the structure of a domain name resolution device disclosed in this application;

[0039] Figure 5 This is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION

[0040] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0041] At present, in order to ensure the stable operation of the business, it has become a common coping strategy to split the business into multiple servers to share the pressure, and use the same VPC to enable cloud servers to visit each other through the intranet IP. However, this solution has serious drawbacks. Once the cloud server is switched and the intranet IP changes, the business code has to be modified and the changes have to be republished. This process is not only cumbersome and complicated, but also greatly increases the maintenance cost and difficulty, seriously affecting the continuity and stability of the business. At the same time, there are many security and performance issues in the existing network setting method. If the intranet service is bound to the public network IP, malicious threats can easily penetrate into the enterprise intranet through the Internet, causing the enterprise intranet domain name to be attacked and internal data leaked. When the DNS server associated with the VPC subnet is set to a public DNS, the cloud server needs to be resolved by the public DNS when accessing the cloud service. This process has a large access delay, which greatly reduces the user experience. To this end, the present application provides a domain name resolution method, device, equipment and storage medium, which can improve the efficiency and security of domain name resolution on the cloud platform.

[0042] See also Figure 1 As shown, an embodiment of the present invention discloses a domain name resolution method, including:

[0043] Step S11: In the virtual private cloud on the preset cloud platform, create a subnet and a security group, and build a domain name resolution server based on the subnet and the security group; wherein the inbound rule of the security group is to only allow traffic through the server's preset domain name resolution port to enter the domain name resolution server.

[0044] In this embodiment, in the virtual private cloud on the preset cloud platform, the classless inter-domain routing scope of the virtual private cloud is determined as the private cloud routing scope, and the target routing scope is determined based on the private cloud routing scope, so as to create a subnet using the target routing scope. That is, the private cloud routing scope defines the address space of the virtual private cloud in the network, and then the target routing scope is further determined by the private cloud routing scope, and the subnet is created according to the target routing scope. In addition, the creation of the subnet can also comprehensively consider factors such as network scale, security requirements, and future scalability.

[0045] At the same time, determine the inbound rules and outbound rules, and use the inbound rules and outbound rules to create a security group. Among them, the inbound rule is set to only allow traffic through the server's preset domain name resolution port to enter the domain name resolution server. The setting of this rule is to enhance security and prevent illegal traffic from invading the domain name resolution server. Usually, the DNS protocol uses port number 53, so the preset domain name resolution port is generally port 53. The outbound rule is to allow traffic through all ports of the server to flow out of the domain name resolution server. In addition, because the security group restricts the domain name resolution server to only release port 53, security is guaranteed to a certain extent.

[0046] After the subnet and security group are created, an independent network address space is allocated to the domain name resolution server through the subnet, and the network security of the server is guaranteed with the help of the security group. Then, the domain name resolution server is built based on the preset computing and storage specifications, the preset image version, the subnet and the security group. Among them, the preset computing and storage specifications determine the processing power and storage capacity of the server, and the preset image version uses a stable and compatible operating system image to build the domain name resolution server. In addition, the domain name resolution server in the virtual private cloud can only be shared and used by cloud servers in the virtual private cloud, and is invisible to other virtual private clouds and cannot be accessed by the public network, ensuring the secure isolation of domain name data and preventing it from being hijacked.

[0047] Step S12: determining a domain name configuration file based on the predetermined domain name resolution software, and configuring the predetermined domain name resolution software using the domain name configuration file, so as to deploy the configured domain name resolution software to the domain name resolution server.

[0048] In this embodiment, first, it is necessary to clearly define the pre-determined domain name resolution software selected, and create an initial configuration file in the installation directory corresponding to the pre-determined domain name resolution software, wherein it should be noted that the initial configuration file is the basic framework for subsequent detailed configuration, which carries the various parameter settings necessary for the operation of the domain name resolution software. And the port number of the preset domain name resolution port and the IP address of the domain name resolution server are determined as the first configuration information. Determining these two key information as the first configuration information can ensure that the domain name resolution software accurately listens to the domain name resolution request on the specified port and responds through the corresponding IP address.

[0049] At the same time, the domain name cache time, the loading time of the domain name record file, and the file storage address of the domain name record file are determined as the second configuration information. Specifically, the setting of the domain name cache time is of great significance for improving the efficiency of domain name resolution. For example, setting the domain name cache time to 50S means that within these 50 seconds, if a resolution request for the same domain name is received again, the domain name resolution software does not need to re-query the domain name record file, but directly returns the result from the cache, thereby greatly shortening the resolution time. The loading time of the domain name record file determines the frequency with which the domain name resolution software checks and updates the domain name record file. For example, it can be set to 5S, which can ensure that the domain name resolution software can perceive the changes in the domain name record file in time, and ensure the accuracy and real-time nature of the resolution results. Regarding the file storage address of the domain name record file, it specifies the location where the domain name resolution software searches for the domain name record, which enables the domain name resolution software to efficiently locate and read the required domain name record information.

[0050] Finally, the first configuration information and the second configuration information are added to the initial configuration file to obtain a domain name configuration file. In this way, the domain name resolution software is fully configured so that it has various parameter settings that meet the intranet domain name resolution requirements of this embodiment. After the configuration is completed, the configured domain name resolution software is deployed to the established domain name resolution server, so that the domain name resolution server can accurately and efficiently provide domain name resolution services based on these configurations.

[0051] Step S13: In the deployed domain name resolution server, a software service file is determined based on the software startup command and software restart mechanism of the configured domain name resolution software, and the configured domain name resolution software is driven to run based on the software service file to resolve the domain name to be resolved in the virtual private cloud.

[0052] In this embodiment, after the domain name resolution software is configured and deployed to the domain name resolution server, in the deployed domain name resolution server, the initial service file, software startup command and software restart mechanism are determined based on the predetermined domain name resolution software, and the software startup instruction and the software restart mechanism are added to the initial service file to obtain the software service file. It should be explained that the software startup command is an instruction for triggering the domain name resolution software to start running, and the software restart mechanism ensures that when the domain name resolution software stops running unexpectedly due to various reasons, it can automatically resume running to ensure the continuity of domain name resolution.

[0053] Furthermore, the software service file is added to the daemon process, and the software startup instruction in the software service file is used to start the configured domain name resolution software to drive the configured domain name resolution software to run. During the startup process, the application will accurately execute the software startup command according to the configuration information in the software service file, load the required configuration files and dependencies, and put the domain name resolution software into operation. At this time, the domain name resolution software starts to listen to the preset domain name resolution port, ready to receive domain name resolution requests from the virtual private cloud at any time.

[0054] In addition, in this embodiment, the domain name to be resolved in the virtual private cloud is determined, and the domain name to be resolved is resolved based on the domain name record file. That is, when the domain name resolution software receives a request for a domain name to be resolved, it will search for the corresponding domain name record file, and then the domain name resolution software will search the domain name record file to see if there is a record matching the domain name. If so, the domain name resolution software will return the IP address corresponding to the domain name to be resolved to the requester, thereby completing the resolution process of the domain name. Among them, the domain name record file is a file that records the mapping relationship between domain names and IP addresses. It can be understood that the domain name to be resolved can be an internal domain name used by various cloud servers, applications, etc. in the virtual private cloud.

[0055] As can be seen from the above, in the virtual private cloud of the preset cloud platform, the private cloud routing range is first determined and the subnet is divided. Set up a security group, and the inbound rule only allows the traffic of the server's preset domain name resolution port to enter, and the outbound rule allows all port traffic to flow out. Build a domain name resolution server based on this subnet and security group. Select the domain name resolution software, create an initial configuration file in its installation directory, write the preset domain name resolution port number, server IP address, and key information such as domain name cache time, record file loading time and storage address as configuration parameters, and form a complete domain name configuration file to complete the configuration of the software and deploy it to the built server. Finally, according to the startup command and restart mechanism of the configured software, create a software service file and add it to the daemon process. Start the software through the service file and run it. After the software runs, the domain name to be resolved in the virtual private cloud is resolved according to the domain name record file to achieve the mapping conversion between the domain name and the IP address. In this way, this application can improve the efficiency and security of domain name resolution on the cloud platform, thereby improving the user experience.

[0056] Combine the following Figure 2 and Figure 3 The schematic diagram shown specifically illustrates the technical solution of the embodiment of the present application.

[0057] Specifically, on the preset cloud platform, firstly, the relevant parameters of the virtual private cloud need to be clarified. The CIDR (i.e., Classless Inter-Domain Routing) of the virtual private cloud is determined as the private cloud routing range, and the private cloud routing range defines the address space of the virtual private cloud in the network. For example, assuming that the CIDR of the VPC is 192.168.0.0 / 16, this means that the VPC has an address space from 192.168.0.0 to 192.168.255.255. Since the private cloud routing range is 192.168.0.0 / 16, in order to meet the specific subnet requirements, 192.168.3.0 / 24 can be divided from it as the target routing range to create a subnet. This subnet is exclusively used by the domain name resolution server. The advantage of this is that it can ensure that it is not affected by the entry and exit rules of other subnet ACLs (i.e., Access Control Lists), thereby providing a relatively independent and stable network environment for the domain name resolution server.

[0058] Next, create a security group. First, the inbound rule of the security group is to allow only port 53 (that is, the preset domain name resolution port), and the outbound rule is to allow all. In addition, use the specification of 1C1G40G (that is, the preset computing and storage specification), the image version of Ubuntu 18.04 (that is, the preset image version), the subnet and the security group to create a cloud server. This cloud server is called the intranet DNS server (that is, the domain name resolution server). Among them, the 1C1G40G specification means 1 CPU core, 1GB memory and 40GB storage space.

[0059] Furthermore, the open source CoreDNS software is used as the domain name resolution software. The software, with its high efficiency, flexibility and rich functional characteristics, can meet the various requirements of the present invention for intranet domain name resolution. After determining the domain name resolution software, create and configure the CoreDNS configuration file CoreFile (that is, the domain name configuration file). After creating the CoreFile file in the / etc / coredns / directory, configure it in detail. The configuration information includes the 53 port number for providing external services and the local IP of the intranet DNS server. At the same time, configure the domain name cache time to 50S, the domain name record file loading time to 5S, and the domain name record file storage configuration / etc / coredns / zones / (that is, the file storage address of the domain name record file).

[0060] Then, by creating the system coredns.service file and clearly defining the CoreDNS software startup command and restart mechanism, the domain name resolution service has higher reliability. Then, coredns.service is added to the daemon process and the service is started, ensuring that the domain name resolution service can be automatically restored when the server is restarted or unexpectedly interrupted, ensuring the continuity of the service.

[0061] Start the CoreDNS service, which means that the domain name resolution service is officially online. At this time, CoreDNS starts listening to port 53, ready to handle various domain name resolution requests.

[0062] Add domain name configuration files and domain name resolution records in the specified directory. This is the key to achieve personalized and customized DNS services. All domain name record files are stored in the / etc / coredns / zones / directory. According to different domain name requirements, create domain name configuration files such as db.dns.com to support A (Address Record), AAAA (IPv6 Address Record), CNAME (Canonical Name Record), MX (Mail Exchange Record), TXT (Text Record), SRV (Service Record), NS (Name Server Record), SOA (Start of Authority Record) and other types of domain name records. For PTR (Pointer Record) type domain name records, such as IPv4 PTR and IPv6 PTR, use db.in-addr.arpa and db.ip6.arpa for separate configuration to ensure the accuracy of reverse resolution. Once the configuration files are added, they are automatically loaded and take effect, allowing users to easily configure and update the mapping relationship between domain names and IP addresses within the VPC, providing efficient and accurate domain name resolution services for resources within the VPC.

[0063] Accordingly, see Figure 4 As shown, the embodiment of the present application provides a domain name resolution device, including:

[0064] The server building module 11 is used to create a subnet and a security group in a virtual private cloud on a preset cloud platform, and to build a domain name resolution server based on the subnet and the security group; wherein the inbound rule of the security group is to allow only traffic through a preset domain name resolution port of the server to enter the domain name resolution server;

[0065] The software configuration module 12 is used to determine a domain name configuration file based on the predetermined domain name resolution software, and configure the predetermined domain name resolution software using the domain name configuration file, so as to deploy the configured domain name resolution software to the domain name resolution server;

[0066] The domain name resolution module 13 is used to determine the software service file in the deployed domain name resolution server based on the software startup command and software restart mechanism of the configured domain name resolution software, and drive the configured domain name resolution software to run based on the software service file to resolve the domain name to be resolved in the virtual private cloud.

[0067] As can be seen from the above, in the virtual private cloud of the preset cloud platform, first determine the private cloud routing range and divide the subnet. Set up a security group, the inbound rule only allows the traffic of the server's preset domain name resolution port to enter, and the outbound rule allows all port traffic to flow out. Build a domain name resolution server based on this subnet and security group. Select the domain name resolution software, create an initial configuration file in its installation directory, write the preset domain name resolution port number, server IP address, and key information such as domain name cache time, record file loading time and storage address as configuration parameters, and form a complete domain name configuration file to complete the configuration of the software and deploy it to the built server. Finally, according to the startup command and restart mechanism of the configured software, create a software service file and add it to the daemon process. Start the software through the service file and run it. After the software runs, the domain name to be resolved in the virtual private cloud is resolved according to the domain name record file to achieve the mapping conversion between the domain name and the IP address. In this way, this application can improve the efficiency and security of domain name resolution on the cloud platform.

[0068] In a specific implementation, the server building module 11 specifically includes:

[0069] In a virtual private cloud on a preset cloud platform, determining a classless inter-domain routing scope of the virtual private cloud as a private cloud routing scope, and determining a target routing scope based on the private cloud routing scope to create a subnet using the target routing scope;

[0070] Determine inbound rules and outbound rules, and create a security group using the inbound rules and the outbound rules; wherein the outbound rule allows traffic through all ports of the server to flow out of the domain name resolution server.

[0071] In a specific implementation, the server building module 11 specifically includes:

[0072] A domain name resolution server is built based on preset computing and storage specifications, preset image versions, the subnet, and the security group.

[0073] In a specific implementation, the software configuration module 12 specifically includes:

[0074] Creating an initial configuration file in an installation directory corresponding to a predetermined domain name resolution software, and determining the port number of the preset domain name resolution port and the IP address of the domain name resolution server as first configuration information;

[0075] Determine the domain name cache time, the domain name record file loading time and the file storage address of the domain name record file as the second configuration information;

[0076] The first configuration information and the second configuration information are added to the initial configuration file to obtain a domain name configuration file.

[0077] In a specific implementation, the domain name resolution module 13 specifically includes:

[0078] Based on the predetermined domain name resolution software, an initial service file, a software startup command and a software restart mechanism are determined, and the software startup command and the software restart mechanism are added to the initial service file to obtain a software service file.

[0079] In a specific implementation, the domain name resolution module 13 specifically includes:

[0080] The software service file is added to the daemon process, and the configured domain name resolution software is started using the software startup instruction in the software service file to drive the configured domain name resolution software to run.

[0081] In a specific implementation, the domain name resolution module 13 specifically includes:

[0082] Determine the domain name to be resolved in the virtual private cloud, and resolve the domain name to be resolved based on the domain name record file; wherein the domain name record file is a file that records the mapping relationship between the domain name and the IP address.

[0083] Furthermore, the present application also discloses an electronic device. Figure 5 It is a structural diagram of an electronic device 20 according to an exemplary embodiment, and the content in the figure cannot be regarded as any limitation on the scope of use of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input and output interface 25 and a communication bus 26. Among them, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the domain name resolution method disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0084] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0085] In addition, the memory 22 as a carrier for resource storage may be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon may include an operating system 221, a computer program 222, etc., and the storage method may be temporary storage or permanent storage.

[0086] The operating system 221 is used to manage and control the hardware devices and computer program 222 on the electronic device 20, which can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program that can be used to complete the domain name resolution method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include a computer program that can be used to complete other specific tasks.

[0087] Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the aforementioned disclosed domain name resolution method. The specific steps of the method can refer to the corresponding contents disclosed in the aforementioned embodiments, and will not be repeated here.

[0088] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0089] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0090] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0091] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0092] The technical solution provided by the present application is introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technicians in this field, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A domain name resolution method, characterized in that: include: In a virtual private cloud on a preset cloud platform, a subnet and a security group are created, and a domain name resolution server is built based on the subnet and the security group; wherein the inbound rule of the security group is to allow only traffic through a preset domain name resolution port of the server to enter the domain name resolution server; Determining a domain name configuration file based on a predetermined domain name resolution software, and configuring the predetermined domain name resolution software using the domain name configuration file, so as to deploy the configured domain name resolution software to the domain name resolution server; In the deployed domain name resolution server, a software service file is determined based on the software startup command and software restart mechanism of the configured domain name resolution software, and the configured domain name resolution software is driven to run based on the software service file to resolve the domain name to be resolved in the virtual private cloud.

2. The domain name resolution method according to claim 1, characterized in that: The step of creating a subnet and a security group in a virtual private cloud on a preset cloud platform includes: In a virtual private cloud on a preset cloud platform, determining a classless inter-domain routing scope of the virtual private cloud as a private cloud routing scope, and determining a target routing scope based on the private cloud routing scope to create a subnet using the target routing scope; Determine inbound rules and outbound rules, and create a security group using the inbound rules and the outbound rules; wherein the outbound rule allows traffic through all ports of the server to flow out of the domain name resolution server.

3. The domain name resolution method according to claim 1, characterized in that: The step of building a domain name resolution server based on the subnet and the security group includes: A domain name resolution server is built based on preset computing and storage specifications, preset image versions, the subnet, and the security group.

4. The domain name resolution method according to claim 1, characterized in that: Determining the domain name configuration file based on the predetermined domain name resolution software includes: Creating an initial configuration file in an installation directory corresponding to a predetermined domain name resolution software, and determining the port number of the preset domain name resolution port and the IP address of the domain name resolution server as first configuration information; Determine the domain name cache time, the domain name record file loading time and the file storage address of the domain name record file as the second configuration information; The first configuration information and the second configuration information are added to the initial configuration file to obtain a domain name configuration file.

5. The domain name resolution method according to claim 1, characterized in that: The software service file is determined based on the software startup command and software restart mechanism of the domain name resolution software after the configuration, including: Based on the predetermined domain name resolution software, an initial service file, a software startup command and a software restart mechanism are determined, and the software startup command and the software restart mechanism are added to the initial service file to obtain a software service file.

6. The domain name resolution method according to claim 1, characterized in that: The step of driving the configured domain name resolution software to run based on the software service file includes: The software service file is added to the daemon process, and the configured domain name resolution software is started using the software startup instruction in the software service file to drive the configured domain name resolution software to run.

7. The domain name resolution method according to any one of claims 1 to 6, characterized in that: The resolving the domain name to be resolved in the virtual private cloud includes: Determine the domain name to be resolved in the virtual private cloud, and resolve the domain name to be resolved based on the domain name record file; wherein the domain name record file is a file that records the mapping relationship between the domain name and the IP address.

8. A domain name resolution device, characterized in that: include: A server building module is used to create a subnet and a security group in a virtual private cloud on a preset cloud platform, and to build a domain name resolution server based on the subnet and the security group; wherein the inbound rule of the security group is to only allow traffic through a preset domain name resolution port of the server to enter the domain name resolution server; A software configuration module, used to determine a domain name configuration file based on a predetermined domain name resolution software, and configure the predetermined domain name resolution software using the domain name configuration file, so as to deploy the configured domain name resolution software to the domain name resolution server; The domain name resolution module is used to determine the software service file in the deployed domain name resolution server based on the software startup command and software restart mechanism of the configured domain name resolution software, and drive the configured domain name resolution software to run based on the software service file to resolve the domain name to be resolved in the virtual private cloud.

9. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the domain name resolution method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Used to store a computer program; wherein, when the computer program is executed by a processor, the domain name resolution method according to any one of claims 1 to 7 is implemented.

Images