CN116192800A - A DNS service deployment method and related device - Google Patents

Abstract

The present application discloses a DNS service deployment method, including: using container technology to run the DNS service in the containers of multiple nodes; using virtual address technology to bind the IP addresses of the DNS services of the multiple nodes to the target virtual IP address; when a DNS request is received through the target virtual IP address, the DNS request is processed. By running the DNS service in the container of multiple nodes in the form of a container, and then binding the IP addresses of the DNS services of multiple nodes to a separate virtual IP address, and finally performing the DNS request received through the virtual IP address For processing, use containers to maintain the reliability of node services and further improve the reliability of DNS services. The present application also discloses a DNS service deployment device, a computing device, and a computer-readable storage medium, which have the above beneficial effects.

Description

A DNS service deployment method and related device

technical field

The present application relates to the field of computer technology, and in particular to a DNS service deployment method, deployment device, computing equipment and computer-readable storage medium.

Background technique

DNS is the abbreviation of Domain Name System. It is a distributed database on the Internet that maps domain names and IP addresses to each other, enabling users to access the Internet more conveniently without having to remember the IP number string that can be directly read by the machine. The process of finally obtaining the IP address corresponding to the host through the host name is called domain name resolution (or host name resolution).

In related technologies, a DNS program is run in a server to provide DNS service. When the service fails or the server fails, the user can no longer use the DNS server. Moreover, due to the DNS access mechanism, it is necessary to wait for a timeout when switching access to the DNS server, which will greatly prolong the waiting time when the user accesses the DNS server to obtain translation results, and this is the case for every client, greatly reducing the user experience. When there is a problem with the DNS server, it needs to be repaired and started manually, and the DNS service will also be suspended during the maintenance period, causing users to be troubled.

Therefore, how to improve the reliability of the DNS service and avoid the inability to provide the DNS service due to unstable nodes is a key issue concerned by those skilled in the art.

Contents of the invention

The purpose of this application is to provide a DNS service deployment method, deployment device, computing equipment, and computer-readable storage medium, and improve the reliability of the DNS service through container technology.

In order to solve the above technical problems, this application provides a DNS service deployment method, including:

Run the DNS service in containers of multiple nodes through container technology;

Binding the IP addresses of the DNS services of the plurality of nodes to the target virtual IP address through a virtual address technology;

When a DNS request is received through the target virtual IP address, the DNS request is processed.

Optionally, use container technology to run the DNS service in containers on multiple nodes, including:

Obtain a mirror image of the DNS service;

The mirror image of the DNS service is deployed in the containers of the plurality of nodes, and the DNS service is run through a command line.

Optionally, after running the DNS service, it also includes:

Connect the DNS service to the Designate service;

The DNS service performs DNS information synchronization through the Designate service.

Optionally, binding the IP addresses of the DNS services of the plurality of nodes to the target virtual IP address through virtual address technology, including:

Bind the IP addresses of the DNS services of the plurality of nodes to the target virtual IP address through Keepalived technology.

Optionally, also include:

When a certain node fails, the target virtual IP address is transferred to other normally available nodes.

Optionally, also include:

Selecting high availability nodes from the plurality of nodes based on high availability parameter information;

Bind an additional virtual IP address to the high availability node.

Optionally, when a DNS request is received through the target virtual IP address, processing the DNS request includes:

When a DNS request is received through the target virtual IP address, the DNS request is distributed to a corresponding node of the DNS server, so that the node can process the DNS request.

The present application also provides a DNS service deployment device, including:

The containerized deployment module is used to run the DNS service in containers of multiple nodes through container technology;

A virtual address binding module, configured to bind the IP addresses of the DNS services of the plurality of nodes to a target virtual IP address through a virtual address technology;

A service providing module, configured to process the DNS request when the DNS request is received through the target virtual IP address.

The present application also provides a computing device, comprising:

memory for storing computer programs;

A processor, configured to implement the steps of the above deployment method when executing the computer program.

The present application also provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above deployment method are implemented.

A DNS service deployment method provided by the present application includes: using container technology to run the DNS service in the containers of multiple nodes; using virtual address technology to bind the IP addresses of the DNS services of the multiple nodes to the target A virtual IP address; when a DNS request is received through the target virtual IP address, the DNS request is processed.

By running the DNS service in the container of multiple nodes in the form of a container, and then binding the IP addresses of the DNS services of multiple nodes in a separate virtual IP address, and finally performing the DNS request received through the virtual IP address For processing, use containers to maintain the reliability of node services and further improve the reliability of DNS services.

The present application also provides a DNS service deployment device, a computing device, and a computer-readable storage medium, which have the above beneficial effects and will not be repeated here.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present application, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

FIG. 1 is a flowchart of a DNS service deployment method provided by an embodiment of the present application;

FIG. 2 is a schematic structural diagram of a DNS service deployment method provided by an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a DNS service deployment device provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a computing device provided by an embodiment of the present application.

Detailed ways

The core of the present application is to provide a DNS service deployment method, deployment device, computing equipment, and computer-readable storage medium, and improve the reliability of the DNS service through container technology.

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments It is a part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

In related technologies, a DNS program is run in a server to provide DNS service. When the service fails or the server fails, the user can no longer use the DNS server. Moreover, due to the DNS access mechanism, it is necessary to wait for a timeout when switching access to the DNS server, which will greatly prolong the waiting time when the user accesses the DNS server to obtain translation results, and this is the case for every client, greatly reducing the user experience. When there is a problem with the DNS server, it needs to be repaired and started manually, and the DNS service will also be suspended during the maintenance period, causing users to be troubled.

Therefore, this application provides a DNS service deployment method, by running the DNS service in the container of multiple nodes in the form of a container, and then binding the IP addresses of the DNS services of multiple nodes to a separate virtual IP address Finally, the received DNS request is processed through the virtual IP address, and the reliability of the node service is maintained by using the container to further improve the reliability of the DNS service.

The following describes a method for deploying a DNS service provided by this application through an embodiment.

Please refer to FIG. 1 , which is a flow chart of a DNS service deployment method provided by an embodiment of the present application.

In this embodiment, the method may include:

S101, running the DNS service in containers of multiple nodes through container technology;

This step aims to run the DNS service in containers on multiple nodes through container technology. That is, the DNS service originally set directly in the server is deployed in a cloud computing container composed of multiple nodes. Among them, a DNS service is run in the container of each node, so that multiple DNS services are deployed in multiple nodes.

Among them, container technology is literally translated from Linux Container, and the word container can be translated as container. The feature of container is that its format is uniform and can be overlapped layer by layer. Our container is like a service program and the operations it runs The system and the dependent environment are packaged into the container container, and can be transported like a container, and the program and environment will not be damaged during the transportation process. After unloading (installation and running) on another server, the program inside can be It still runs normally without caring about the operating system and environment of the server itself.

Container technology: It is a lightweight operating system-level virtualization technology for the kernel. It is essentially a special process that uses namespaces, control groups, and chroot technologies to organize resources, Files, devices, status and configuration are divided into a separate space.

k8s: The full name of k8s is kubernetes. It is a portable container orchestration management tool for container services. Its main features include: service discovery and scheduling, load balancing, service self-healing, service elastic expansion, horizontal expansion, storage volume Mounting, etc., k8s can make the deployment and operation of applications used by users more convenient.

DNS: DNS is the abbreviation of Domain Name System. It is a distributed database on the Internet that maps domain names and IP addresses to each other. It enables users to access the Internet more conveniently without remembering the IP numbers that can be directly read by machines. string. The process of finally obtaining the IP address corresponding to the host through the host name is called domain name resolution (or host name resolution). The DNS protocol runs on top of the UDP protocol, using port number 53.

Further, this step can be to use k8s to deploy DNS servers in each control node to provide DNS services, so that DNS services can be containerized instead of directly deployed in servers, so that DNS services can enjoy the advantages of containers, not only can DNS services It is saved as a container image for batch deployment, and it can also be linked with the service self-healing feature of k8s to provide a certain degree of self-healing for containerized DNS services and reduce the operation and maintenance costs of DNS services.

Further, this step may include:

Step 1, obtain the mirror image of the DNS service;

Step 2. Deploy the mirror image of the DNS service in containers on multiple nodes, and run the DNS service through the command line.

It can be seen that this optional solution mainly explains how to run the DNS service based on the container. In this optional solution, obtain the image of the DNS service; deploy the image of the DNS service in containers on multiple nodes, and run the DNS service through the command line. Realized running the DNS service in the container, improving the reliability and security of the DNS service.

Further, after running the DNS service in this embodiment, it may also include:

Step 1, connect the DNS service to the Designate service;

Step 2, the DNS service performs DNS information synchronization through the Designate service.

It can be seen that this optional scheme mainly shows that information synchronization can also be performed. In this optional solution, the DNS service is connected to the Designate service; the DNS service performs DNS information synchronization through the Designate service. It can be seen that by connecting to the Designate service, the rapid management of DNS information can be realized, the efficiency of DNS information management can be improved, and the cost can be reduced.

Among them, Designate is an open source DNS as a service facility, which is part of the OpenStack service ecosystem for running the cloud. Designate is a multi-tenant DNSaaS service for OpenStack. It provides a REST API with integrated Keystone authentication. It can be configured to automatically generate records based on Nova and Neutron operations. Designate supports a variety of DNS servers, including Bind9 and PowerDNS 4.

S102. Bind the IP addresses of the DNS services of multiple nodes to the target virtual IP address through virtual address technology;

On the basis of S101, this step aims to bind the IP addresses of the DNS services of multiple nodes to the target virtual IP address through the virtual address technology. Because a DNS service is provided by providing a unified IP address to the outside world. Therefore, in this step, the mapping to multiple IP addresses is realized through the target virtual IP address.

Further, this step may include:

Bind the IP addresses of the DNS services of multiple nodes to the target virtual IP address through Keepalived technology.

It can be seen that this optional solution mainly describes how to bind a virtual IP address. In this optional solution, the IP addresses of the DNS services of multiple nodes are bound to the target virtual IP address through Keepalived technology.

Among them, Keepalived technology is a lightweight high-availability solution under Linux. The function of this technology is to detect the status of the server. If there is a web server down or the work fails, Keepalived will detect it and send the faulty The server is removed from the system, and other servers are used to replace the work of the server. When the server works normally, Keepalived automatically adds the server to the server group. All these tasks are automatically completed without manual intervention. What needs to be done manually is to repair the fault. server.

Therefore, this option can be to use Keepalived technology to combine multiple physical nodes together to improve the robustness and fault tolerance of DNS services. Keepalived technology will assign an additional VIP (virtual IP address) to highly available nodes. Users can pass The VIP can access a certain server in the cluster. When the node where the VIP is located fails, the VIP will automatically jump to other nodes that can be used normally.

Further, this embodiment may also include:

When a node fails, the target virtual IP address is redirected to other normally available nodes.

It can be seen that how to perform access jump is also described in this optional solution. In this optional solution, when a node fails, the target virtual IP address is redirected to other normally available nodes.

Further, this embodiment may also include:

Step 1, based on high-availability parameter information, select high-availability nodes from multiple nodes;

Step 2, bind an additional virtual IP address to the highly available node.

It can be seen that this optional solution mainly indicates that an additional virtual IP address is bound to the high-availability node. In this optional solution, high-availability nodes are selected from multiple nodes based on high-availability parameter information; additional virtual IP addresses are bound to high-availability nodes. That is, to achieve more highly available deployment operations, so as to export the performance of highly available nodes to the outside, and improve the overall availability and robustness of the DNS service.

S103, when a DNS request is received through the target virtual IP address, process the DNS request.

On the basis of S102, this step aims at processing the DNS request when the DNS request is received through the target virtual IP address.

It can be seen that on the basis of the target virtual IP address, the DNS service is bound to the VIP, and the user can directly access the DNS service of the node where the VIP is located through the VIP, so that the user is not aware of the underlying DNS service and does not need to pay attention For the status and quantity of the underlying DNS service, you only need to configure the VIP in the nameserver, which can also avoid the problem of waiting for the timeout period when the DNS service fails and cannot be accessed when the IP address of the DNS service is individually configured. , improve user experience and efficiency.

Further, this step may include:

When a DNS request is received through the target virtual IP address, the DNS request is distributed to the corresponding DNS server node, so that the node can process the DNS request.

It can be seen that this optional solution mainly describes how to process the DNS request through the target virtual IP address. In this optional solution, when a DNS request is received through the target virtual IP address, the DNS request is distributed to a corresponding node of the DNS server, so that the node can process the DNS request.

To sum up, in this embodiment, the DNS service is run in the container of multiple nodes in the form of a container, and then the IP addresses of the DNS service of multiple nodes are bound to a separate virtual IP address, and finally through the virtual IP address Process the received DNS requests, and use containers to maintain the reliability of node services, further improving the reliability of DNS services.

A method for deploying a DNS service provided by the present application will be further described below through another specific embodiment.

Please refer to FIG. 2 . FIG. 2 is a schematic structural diagram of a DNS service deployment method provided by an embodiment of the present application.

In this embodiment, k8s-based deployment of BindDNS server, way for users to access the DNS server connected to Designate in the cluster, and keepalive high-availability deployment of k8s cluster.

Among them, the k8s-based deployment of the BindDNS server provides DNS services with certain self-healing properties and improves the service robustness of the cluster; When the server fails, the access method no longer waits for the timeout; the keepalive high-availability deployment of the k8s cluster provides theoretical support for the access method.

The k8s-based deployment of the BindDNS server allows the DNS service to enjoy the advantages of k8s. You only need to install the DNS service and related dependent services in the container, configure the configuration file of the DNS service, and then write the command line startup method of the DNS service to the container. In this way, a general-purpose DNS service container is completed. Save it as an image and export it, and then deploy and install it on any server that supports container services. You only need to modify the listening IP in the configuration file With k8s technology, when the DNS service container fails, k8s will automatically restart it to realize the automatic recovery function of the DNS service, endow the DNS service with a certain degree of self-healing, and reduce maintenance costs and time.

The keepalived high-availability deployment of the k8s cluster provides a VIP. When accessing this VIP, it will be automatically brought to the high-availability node in the keepalive cluster, and connected to the control node of openstack. When the node where the VIP is located fails and shuts down, This VIP will automatically jump to other control nodes, because as long as all control nodes are not shut down, this VIP can be accessed to provide service robustness.

The way for users to access the DNS server connected to Designate in the cluster is to provide a way to avoid waiting for the timeout period when the configured DNS server cannot be accessed. It needs to be combined with the VIP provided by keepalived. Just configure the nameserver as a VIP in the client. Yes, in this way, when accessing the DNS service, first access the VIP, and then the VIP will bring it to the specific DNS service. This function works best when combined with Designate, because when creating a DNS resource in Designate, all DNS services in the cluster ( It needs to be configured in Designate’s DNS server docking configuration file) and the creation command is issued. The DNS servers in the cluster are all MasterDNS servers, and the resources in each are consistent.

That is to say, using k8s to deploy DNS servers in each control node to provide DNS services, containerizing DNS services instead of directly deploying them in servers can make DNS services enjoy the advantages of containers, not only saving DNS services as A container image is used for batch deployment, and it can also be linked with the service self-healing feature of k8s to provide a certain degree of self-healing for containerized DNS services and reduce the operation and maintenance costs of DNS services

Combined with the VIP configuration provided by the keepalived high-availability service to the nameserver of the client, the IP addresses of many DNS servers in the cluster can be integrated into one VIP. When the node where the VIP is located fails, the VIP will automatically jump to other nodes that can be used normally, so that the actual access to the underlying DNS server has also changed to access the normal DNS server node. However, when the Designate service creates resources, it will automatically issue creation commands to all DNS servers connected to it (additions, deletions, and modifications are the same, and all are issued to all DNS servers), and Designate has a synchronization mechanism. The resources in the server are consistent, so even if the actual accessed DNS server is redirected, there is no perception, and the resources that need to be accessed still exist.

A schematic diagram of a high-availability method for docking Designate based on a k8s containerized bind server is shown in Figure 1. The specific implementation process is as follows:

Step 1, run the DNS service in containers of multiple nodes through container technology;

Using the k8s container technology to convert the DNS service from the traditional direct deployment mode to running in the k8s container can not only endow it with the characteristics of batch deployment, strong portability, and low environmental dependence, but also has the self-healing of the k8s container To use the command line to start the DNS service, the container will automatically restart when there is a problem with the service, and due to the characteristics of connecting to Designate, after the DNS service is started, it will automatically initiate synchronization with Designate to avoid problems such as lack of information.

Step 2, binding the IP addresses of the DNS services of multiple nodes to the target virtual IP address through the virtual address technology;

Use Keepalived technology to combine multiple physical nodes together to improve the robustness and fault tolerance of DNS services. Keepalived technology will assign an additional VIP to high-availability nodes, and users can access a certain server in the cluster through the VIP. When the node where the VIP is located fails, the VIP will automatically jump to other nodes that can be used normally.

Step 3, when a DNS request is received through the target virtual IP address, the DNS request is processed.

Bind the DNS service with the VIP, and the user can directly access the DNS service of the node where the VIP is located through the VIP, so that the user is not aware of the underlying DNS service, and does not need to pay attention to the status and quantity of the underlying DNS service. It is enough to configure the VIP in the nameserver, which can also avoid the problem of waiting for the timeout period when the DNS service fails and cannot be accessed when the IP address of the DNS service is configured individually, improving the user experience and efficiency.

It can be seen that in this embodiment, the DNS service is run in the container of multiple nodes in the form of a container, and then the IP addresses of the DNS service of multiple nodes are bound to a separate virtual IP address, and finally the virtual IP address pairs The DNS request is received and processed, and the reliability of the node service is maintained by using the container, which further improves the reliability of the DNS service.

The following is an introduction to the device for deploying the DNS service provided by the embodiment of the present application. The device for deploying the DNS service described below and the method for deploying the DNS service described above can be referred to in correspondence.

Please refer to FIG. 3 , which is a schematic structural diagram of an apparatus for deploying a DNS service provided by an embodiment of the present application.

In this embodiment, the device may include:

The containerized deployment module 100 is used to run the DNS service in containers of multiple nodes through container technology;

The virtual address binding module 200 is used to bind the IP addresses of the DNS services of multiple nodes to the target virtual IP address through the virtual address technology;

The service providing module 300 is configured to process the DNS request when the DNS request is received through the target virtual IP address.

Optionally, the containerized deployment module 100 is specifically configured to acquire a mirror image of the DNS service; deploy the mirror image of the DNS service in containers of multiple nodes, and run the DNS service through a command line.

Optionally, after running the DNS service, include:

Connect the DNS service to the Designate service;

The DNS service uses the Designate service to synchronize DNS information.

Optionally, the virtual address binding module 200 is specifically configured to bind the IP addresses of DNS services of multiple nodes to the target virtual IP address through Keepalived technology.

Optionally, the device may also include:

The fault jumping module is used for jumping the target virtual IP address to other normally available nodes when a certain node fails.

Optionally, the device may also include:

The high-availability processing module is used to select high-availability nodes from multiple nodes based on high-availability parameter information; bind additional virtual IP addresses to high-availability nodes.

Optionally, the service providing module 300 is specifically configured to distribute the DNS request to the corresponding DNS server node when receiving the DNS request through the target virtual IP address, so that the node can process the DNS request.

It can be seen that in this embodiment, the DNS service is run in the container of multiple nodes in the form of a container, and then the IP addresses of the DNS service of multiple nodes are bound to a separate virtual IP address, and finally the virtual IP address pairs The DNS request is received and processed, and the reliability of the node service is maintained by using the container, which further improves the reliability of the DNS service.

The present application also provides a computing device. Please refer to FIG. 4. FIG. 4 is a schematic structural diagram of a computing device provided by an embodiment of the present application. The computing device may include:

memory for storing computer programs;

The processor is configured to implement the steps of any one of the above DNS service deployment methods when executing the computer program.

As shown in FIG. 4 , which is a schematic structural diagram of a computing device, the computing device may include: a processor 10 , a memory 11 , a communication interface 12 and a communication bus 13 . The processor 10 , the memory 11 , and the communication interface 12 all communicate with each other through the communication bus 13 .

In the embodiment of the present application, the processor 10 may be a central processing unit (Central Processing Unit, CPU), an application-specific integrated circuit, a digital signal processor, a field programmable gate array, or other programmable logic devices.

The processor 10 can call the program stored in the memory 11, specifically, the processor 10 can execute the operations in the embodiment of the abnormal IP identification method.

The memory 11 is used to store one or more programs. The programs may include program codes, and the program codes include computer operation instructions. In the embodiment of the present application, the memory 11 stores at least programs for realizing the following functions:

Run the DNS service in containers of multiple nodes through container technology;

Bind the IP addresses of the DNS services of multiple nodes to the target virtual IP address through virtual address technology;

When a DNS request is received through the target virtual IP address, the DNS request is processed.

In a possible implementation, the memory 11 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application program required by a function; the data storage area may store The data created.

In addition, the memory 11 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device or other volatile solid-state storage devices.

The communication interface 12 may be an interface of a communication module, and is used for connecting with other devices or systems.

Of course, it should be noted that the structure shown in FIG. 4 does not constitute a limitation on the computing device in the embodiment of the present application. In practical applications, the computing device may include more or less components than those shown in FIG. 4, or combine certain parts.

It can be seen that in this embodiment, the DNS service is run in the container of multiple nodes in the form of a container, and then the IP addresses of the DNS service of multiple nodes are bound to a separate virtual IP address, and finally the virtual IP address pairs The DNS request is received and processed, and the reliability of the node service is maintained by using the container, which further improves the reliability of the DNS service.

The present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the above-mentioned DNS service deployment methods can be implemented.

The computer-readable storage medium may include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc., which can store program codes. medium.

For the introduction of the computer-readable storage medium provided by the present application, please refer to the foregoing method embodiments, and the present application does not repeat it here.

It can be seen that in this embodiment, the DNS service is run in the container of multiple nodes in the form of a container, and then the IP addresses of the DNS service of multiple nodes are bound to a separate virtual IP address, and finally the virtual IP address pairs The DNS request is received and processed, and the reliability of the node service is maintained by using the container, which further improves the reliability of the DNS service.

Each embodiment in the description is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for relevant details, please refer to the description of the method part.

Professionals can further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of the two. In order to clearly illustrate the possible For interchangeability, in the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be directly implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

A DNS service deployment method, deployment device, computing device, and computer-readable storage medium provided by the present application have been introduced in detail above. In this paper, specific examples are used to illustrate the principles and implementation methods of the present application, and the descriptions of the above embodiments are only used to help understand the methods and core ideas of the present application. It should be pointed out that those skilled in the art can make some improvements and modifications to the application without departing from the principles of the application, and these improvements and modifications also fall within the protection scope of the claims of the application.

Claims (10)

1. A deployment method of DNS service, characterized in that, comprising: Run the DNS service in containers of multiple nodes through container technology; Binding the IP addresses of the DNS services of the plurality of nodes to the target virtual IP address through a virtual address technology; When a DNS request is received through the target virtual IP address, the DNS request is processed. 2. The deployment method according to claim 1, wherein the DNS service is run in containers of multiple nodes through container technology, including: Obtain a mirror image of the DNS service; The mirror image of the DNS service is deployed in the containers of the plurality of nodes, and the DNS service is run through a command line. 3. The deployment method according to claim 2, further comprising: after running the DNS service: Connect the DNS service to the Designate service; The DNS service performs DNS information synchronization through the Designate service. 4. The deployment method according to claim 1, wherein binding the IP addresses of the DNS services of the plurality of nodes to the target virtual IP address through a virtual address technology includes: Bind the IP addresses of the DNS services of the plurality of nodes to the target virtual IP address through Keepalived technology. 5. The deployment method according to claim 1, further comprising: When a certain node fails, the target virtual IP address is transferred to other normally available nodes. 6. The deployment method according to claim 1, further comprising: Selecting high availability nodes from the plurality of nodes based on high availability parameter information; Bind an additional virtual IP address to the high availability node. 7. The deployment method according to claim 1, wherein when a DNS request is received through the target virtual IP address, processing the DNS request includes: When a DNS request is received through the target virtual IP address, the DNS request is distributed to a corresponding node of the DNS server, so that the node can process the DNS request. 8. A device for deploying DNS services, comprising: The containerized deployment module is used to run the DNS service in containers of multiple nodes through container technology; A virtual address binding module, configured to bind the IP addresses of the DNS services of the plurality of nodes to a target virtual IP address through a virtual address technology; A service providing module, configured to process the DNS request when the DNS request is received through the target virtual IP address. 9. A computing device, comprising: memory for storing computer programs; A processor configured to implement the steps of the deployment method according to any one of claims 1 to 7 when executing the computer program. 10. A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the deployment according to any one of claims 1 to 7 is realized method steps.

Images