CN113596187B - Domain name configuration management system - Google Patents
Domain name configuration management system Download PDFInfo
- Publication number
- CN113596187B CN113596187B CN202110713434.6A CN202110713434A CN113596187B CN 113596187 B CN113596187 B CN 113596187B CN 202110713434 A CN202110713434 A CN 202110713434A CN 113596187 B CN113596187 B CN 113596187B
- Authority
- CN
- China
- Prior art keywords
- agent
- configuration
- management
- information
- dns
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a domain name configuration management system, which comprises: a management server, an Agent management cluster and an Agent plug-in are configured; the configuration management server and the Agent management cluster are arranged at the server, the Agent plug-in is arranged at the DNS client of the domain name system, and the Agent plug-in can be compatible with multiple types of DNS software; the configuration management server provides an application program interface for the DNS client and issues configuration information stored by the server to the DNS client through the application program interface; the Agent management cluster comprises a plurality of Agent management nodes, each Agent management node receives and processes Agent state information in the DNS server, and the Agent state information comprises heartbeat information uploaded by an Agent plug-in, a configuration loading state of the Agent plug-in and a lock state set by a configuration management server. The system can be compatible with various types of DNS software by arranging the Agent plug-in at the DNS server, and the server is provided with a corresponding Agent management cluster to receive heartbeat information and configuration loading state uploaded by the Agent plug-in.
Description
Technical Field
The invention relates to the technical field of domain name management, in particular to a domain name configuration management system.
Background
The domain name system (Domain Name System, DNS) is a service of the internet. The method is used as a distributed database for mapping the domain name and the IP address with each other, so that people can access the Internet more conveniently. Because of the problems of domain name infringement, domain name robbery and the like in different degrees in all countries of the world, the domain name needs to be configured and managed.
In some embodiments, a daemon process, such as a timer driver or waiting for a user request, is started to perform a configuration update task, and the transmission of a configuration file is generally performed by means of a file synchronization tool, such as rsync, and when the configuration file is updated, the DNS service is restarted by a script or tool, so as to achieve a certain level of configuration management. However, because DNS data in a production environment is sensitive, the system is compatible with other DNS software, and the cost is high, so that the design cannot meet the actual application scenario.
Disclosure of Invention
The embodiment of the invention provides a domain name configuration management system, which aims to solve the problem that the prior design cannot meet the actual application scene because the system is compatible with other DNS software due to relatively sensitive DNS data in the production environment and relatively high cost in the prior art.
In order to solve the technical problems, the invention is realized as follows:
in a first aspect, a domain name configuration management system is provided, including: a management server, an Agent management cluster and an Agent plug-in are configured; the configuration management server and the Agent management cluster are arranged at the server, the Agent plug-in is arranged at a Domain Name System (DNS) client, and the Agent plug-in can be compatible with multiple types of DNS software;
the configuration management server provides an application program interface for the DNS client and issues configuration information stored by the server to the DNS client through the application program interface, wherein the configuration information is used for updating configuration in the DNS client and comprises equipment group configuration data, IP address configuration data and area configuration data;
the Agent management cluster comprises a plurality of Agent management nodes, and each Agent management node receives and processes heartbeat information uploaded by an Agent plug-in the DNS client, a configuration loading state of the Agent plug-in and a lock state set by the configuration management server.
In the embodiment of the invention, the domain name configuration management system comprises a configuration management server side, an Agent management cluster and an Agent plug-in unit, wherein the configuration management server side is arranged at a server side, the Agent plug-in unit is compatible with multiple types of DNS software, the configuration management server side provides an application program interface for the DNS client side, and issues configuration information stored at the server side to the DNS client side through the application program interface, the configuration information is used for updating configuration in the DNS client side, the configuration information comprises equipment group configuration data, IP address configuration data and area configuration data, the Agent management cluster comprises a plurality of Agent management nodes, and each Agent management node receives and processes heartbeat information uploaded by the Agent plug-in unit in the DNS client side, configuration loading state of the Agent plug-in unit and lock state set by the configuration management server. According to the embodiment of the invention, the system can be compatible with various types of DNS software by arranging the Agent plug-in on the DNS client, and the corresponding Agent management cluster is arranged on the server to receive the heartbeat information and the configuration loading state uploaded by the Agent plug-in.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a schematic diagram of a domain name configuration management system according to an embodiment of the present invention;
FIG. 2 is a detailed schematic diagram of a domain name configuration management system according to an embodiment of the present invention;
FIG. 3 is a Jackson diagram of device group configuration data provided by one embodiment of the present invention;
FIG. 4 is a Jackson diagram of IP library configuration data provided by one embodiment of the present invention;
FIG. 5 is a Jackson diagram of Zone configuration data provided by one embodiment of the present invention;
FIG. 6 is a flowchart of processing logic after an Agent plug-in receives configuration information issued by an ETCD cluster according to an embodiment of the present invention;
FIG. 7 is a flow chart of the processing logic of an Agent management node provided by one embodiment of the invention;
FIG. 8 is a flowchart illustrating the execution of a system for processing a domain name configuration update once according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The embodiment of the application provides a domain name configuration management system. The system is a work order system, and can allow a user to operate a plurality of domain names in batches. In implementation the system is divided into three parts: firstly, providing an application program interface (RESTful API) for the configuration management server, wherein the RESTful API comprises an access right control (RBAC) module, a domain name management module and a plurality of business logic modules; secondly, an Agent (Agent) deployed on each domain name system (Domain Name System, DNS) client is responsible for acquiring configuration information and validating the configuration, and is compatible with multiple types of DNS software through a plug-in method; the last part is an Agent management cluster, and each node in the cluster is responsible for receiving and processing Agent state information, wherein the Agent state information comprises Agent heartbeat information, agent configuration loading state and a lock state set by a server.
Wherein REST is representational state transfer, API is application program interface, RESTful API is REST style application program interface; DNS is a distributed database that maps domain names and internet protocol (Internet Protocol, IP) addresses to each other; an Agent is a daemon deployed on a DNS client for configuration updates.
Fig. 1 is a schematic structural diagram of a domain name configuration management system according to an embodiment of the present application. As shown in fig. 1, the domain name configuration management system may include: the Agent management system comprises a configuration management server, an Agent management cluster and an Agent plug-in.
The configuration management server and the Agent management cluster are arranged at the server, the Agent plug-in is arranged at the DNS client of the domain name system, and the Agent plug-in can be compatible with multiple types of DNS software. The configuration management server provides an application program interface for the DNS client, and issues configuration information stored by the server to the DNS client through the application program interface, wherein the configuration information is used for updating the configuration in the DNS client, and the configuration information comprises equipment group configuration data, IP address configuration data and area configuration data; the Agent management cluster comprises a plurality of Agent management nodes, and each Agent management node receives and processes Agent state information in the DNS client, wherein the Agent state information comprises heartbeat information uploaded by an Agent plug-in, a configuration loading state of the Agent plug-in and a lock state set by a configuration management server.
The lock state may include a released state, a locked state, among others.
In the embodiment of the application, the domain name configuration management system comprises a configuration management server side, an Agent management cluster and an Agent plug-in unit, wherein the configuration management server side is arranged at a server side, the Agent plug-in unit is compatible with multiple types of DNS software, the configuration management server side provides an application program interface for the DNS client side, and issues configuration information stored by the server side to the DNS client side through the application program interface, the configuration information is used for updating configuration of the DNS client side, the configuration information comprises equipment group configuration data, IP address configuration data and area configuration data, the Agent management cluster comprises a plurality of Agent management nodes, each Agent management node receives and processes Agent state information in the DNS client side, and the Agent state information comprises heartbeat information uploaded by the Agent plug-in unit, configuration loading state of the Agent plug-in unit and lock state set by the configuration management server. According to the embodiment of the invention, the system can be compatible with various types of DNS software by arranging the Agent plug-in on the DNS client, and the corresponding Agent management cluster is arranged on the server to receive the heartbeat information and the configuration loading state uploaded by the Agent plug-in.
The system realizes role-based authority control by means of the user list, the product line list, the role list, the user group list and the request white list. In the system, a combination of a user and a product line corresponds to an application program interface (Application Programming Interface, API) user, the API user self-maintains an IP white list for requesting the system API, and the system controls the operation authority of the API user on domain name resources by modifying the role of the API user.
As shown in fig. 2, in one possible implementation manner of the present application, the configuration management server includes an access right control module, a domain name management module, and a service logic module.
The access right control module is used for determining the device access right in the issued configuration according to the data acquired from the database. And the domain name management module is used for determining the domain name of each device according to the data acquired from the database. The business logic module includes a number of business logics.
In one possible implementation of the present application, multiple DNS clients are divided into different device groups according to service categories, each device group using one type of DNS software.
In the embodiment of the application, in order to realize compatibility of multiple DNS software, the system classifies multiple DNS clients into different device groups according to service categories for management, and each device group uses one DNS software.
The service class refers to a class of providing services by a domain name system. For example, a first device group provides a hostname resolution service, a second device group provides a service for business-related domain names, and such information is recorded in a device group role table. The system can manage the Zone (Zone) through the equipment group, and then manage the domain name through the Zone.
As shown in fig. 2, device group 1 corresponds to PowerDNS software, device group 2 corresponds to Bind9 software, and device group 3 corresponds to other DNS software.
To implement the dynamic scheduling function of domain names, the system introduces the concept of domain name partitioning, and in one possible implementation of the present application, the device group includes a plurality of areas, each area includes a plurality of domain names, and each domain name is associated with an IP address one by one.
In the embodiment of the application, the domain names are associated with the records through the partitions, each domain name can have a default partition, and when the domain names do not need dynamic scheduling, the system can search the record information of the domain names through the default partition. The system stores complete IP library information through the IP library and the IP address, and realizes domain name dynamic scheduling by associating domain name partitions with the IP address. For example, when a user a in a certain province of a certain country accesses a domain name B, DNS software may obtain the geographic location of the user through an IP library, and further select a partition of the domain name to resolve the domain name record.
In one possible implementation manner of the present application, the server further includes: the system comprises a database, a configuration management server side, an application program interface and a DNS client side, wherein the database stores configuration information and Agent state information, and the configuration management server side acquires the configuration information and the Agent state information from the database and transmits the configuration information to the DNS client side through the application program interface according to the Agent state information.
In the embodiment of the application, the server may include a database, where configuration information, for example, device group configuration data, IP library configuration data, zone configuration data, and the like, is stored in the database.
Specifically, a Jackson graph of the device group configuration data is shown in fig. 3, a Jackson graph of the IP library configuration data is shown in fig. 4, and a Jackson graph of the Zone configuration data is shown in fig. 5, where the Jackson graph is formed by at least one occurrence of one data element.
The order of the device group configuration data is: ETCD Value) - > MD5 check Value- > json format configuration information- > device role id- > device group id- > device management IP- > device id- > … - > device id (input completion) - > device group name- > device group id- > … - > device group id (input completion) - > device role name- > device role id- > … - > device role id (input completion).
The order of the IP library configuration data is: ETCD Value- > MD5 check Value- > json format configuration information- > IP segment- > start IP (integer) - > end IP (integer) - > IP location id- > parent location id- > location number- > country number- > province number- > city number- > operator number- > data center (Internet Data Center, abbreviated IDC) number- > IP segment- > … - > IP segment (input complete).
The sequence of Zone configuration data is: ETCD Value- > MD5 check Value- > json format configuration information- > zone configuration- > zone- > version number- > domain name configuration- > domain name- > enable- > partition- > default- > policy- > record- > type- > enable- > Time To Live Value (Time To Live, TTL) - > weight- > all records- > … - > all records (input done) - > all partition- > … - > all partitions (input done) - > domain name configuration- > … - > domain name configuration (input done) - > refresh rate (refresh) - > retry- > expiration) Time To Live Value (Time To Live, TTL).
In one possible embodiment of the present application, the database may be updated according to Agent status information received by the Agent management cluster.
That is, each node in the Agent management cluster is responsible for receiving and processing Agent heartbeat information, synchronizing the configuration loading state of the Agent, clearing the lock set by the server, and then sending the information to the database, wherein the database updates the information so that the configuration management server can issue configuration according to the information when issuing data next time.
In one possible implementation manner of the present application, the server further includes: the ETCD cluster and the configuration management server may send the configuration information to the DNS client through the application according to the Agent status information, which may specifically include: and the configuration management server synchronizes the configuration information to the ETCD cluster according to the Agent state information, and the ETCD cluster transmits the configuration information to the DNS client through the application program interface.
That is, the configuration management server acquires the configuration information and the Agent status information from the database, synchronizes the configuration information to the ETCD cluster according to the Agent status information, and the ETCD cluster issues the configuration information to the DNS client through the application program interface.
Specifically, the ETCD cluster includes a plurality of ETCD nodes, each ETCD node corresponds to one device group of the DNS client, and the ETCD nodes issue configuration information to the device group corresponding to the application program interface.
In the embodiment of the application, after the configuration management server acquires the configuration information from the database, the configuration management server synchronizes to different ETCD nodes in the ETCD cluster, and then issues the configuration information to a corresponding device group in the DNS client through the ETCD nodes.
In one possible embodiment of the present application, configuration information in the ETCD cluster is stored in units of areas, each including a device group role ID, a device group ID, and an area ID.
In this embodiment, domain name configuration information is stored in the ETCD in units of Zone, and its key is composed of a device group role id, a device group id, and a Zone id. For example: cfg/device-group-role-1-part/device-group-3-part/zone-12-part. In this way, the configuration synchronization efficiency can be improved when domain names are operated in batches, but the configuration data of one Zone is often more and possibly exceeds the maximum number of bytes allowed when the ETCD is requested, so that the data can be compressed when the ETCD cluster is synchronized. That is, the configuration management server synchronizes the configuration information after compressing the configuration information to the ETCD cluster.
Further, as shown in fig. 6, processing logic after the Agent plug-in receives the configuration information issued by the ETCD cluster is as follows.
The starting protocol is used for monitoring internal operation errors, setting a timer, scanning an Agent error log, judging whether a system error occurs, sending an alarm if the system error occurs, setting a timer cycle, and setting the timer cycle if the system error does not occur.
And starting a coroutine for timing heartbeat information synchronization, setting a timer, sending heartbeats to the Agent management cluster, retrying if the heartbeat is failed, and then setting a timer cycle.
Acquiring information of all equipment groups through an ETCD, judging whether an Agent is added into the equipment groups, if not, acquiring all zone configuration information managed by the equipment through the ETCD, decompressing the equipment, judging whether the data version number is equal to a cache version number, if not, caching and updating the version number of the zone configuration, returning a state (retrying if failure), starting a protocol for monitoring the change of the zone configuration, if not, directly starting the protocol for monitoring the change of the zone configuration, then monitoring the change of the zone configuration, judging whether the monitoring (Watch) is interrupted, if yes, returning all zone configuration information managed by the equipment through the ETCD, decompressing the equipment, if not, judging whether the change occurs, if not, continuing to monitor the change of the zone configuration, caching and updating the version number of the zone configuration if the change occurs, returning the state (retrying if failure), and continuing to monitor the change of the zone configuration. When judging that the equipment where the Agent is located joins the equipment group, starting a protocol for monitoring the change of the equipment group configuration, monitoring the equipment group configuration change, judging whether a Watch is interrupted, restarting the protocol for monitoring the equipment group configuration change if the Watch is interrupted, judging whether the equipment is moved to other equipment groups if the equipment is not interrupted, acquiring all zone configuration information managed by the equipment through an ETCD if the equipment is moved to the other equipment groups, judging whether the equipment is removed if the equipment is not moved to the other equipment groups, ending if the equipment is removed, and continuing to monitor the equipment group configuration change if the equipment is not removed. When judging that the equipment where the Agent is located joins the equipment group, starting a protocol for monitoring the configuration change of the ip library, judging whether the Watch is interrupted, restarting the protocol for monitoring the configuration change of the ip library if the Watch is interrupted, judging whether the configuration is changed if the ip library is not interrupted, continuing to monitor the configuration change of the ip library if the configuration is not changed, reloading the configuration file if the configuration is changed, returning the state (retrying if the configuration is failed), and continuing to monitor the configuration change of the ip library. After the version number of the cache update zone configuration and reloading the configuration file, a data processing plug-in may also be performed: generating a configuration file, then DNS software configuration file, configuration loading and verification: and loading the configuration and verifying.
In the embodiment of the application, the Agent periodically sends heartbeat information to the Agent management node in the running process, and meanwhile, an ETCD monitoring mechanism is utilized to monitor internal running errors, timing heartbeat information synchronization and information change of the equipment group. The Agent judges whether the program needs to finish running or not by monitoring the equipment group configuration, updates the IP library data on the DNS client by monitoring the IP library configuration, and executes the updating of the DNS configuration by monitoring the Zone configuration. In implementation, the Agent can tolerate monitoring interruption caused by network problems and has abnormal self-monitoring capability.
Agents have good compatibility with a variety of DNS software, depending on their plug-in design. Different DNS software have different configuration files, configuration loading modes and verification methods, and related logic is stripped and compiled into a plug-in, so that the compatibility of the DNS software can be improved at minimum cost.
In one possible implementation of the present application, the Agent management node communicates with the Agent plugin through a remote procedure call RPC; when synchronizing heartbeat information, an Agent plug-in sends an equipment management IP to an Agent management node; when the loading state is synchronously configured, the Agent plugin sends the work order ID, the equipment management IP, the area and the state code to the Agent management node.
Specifically, as shown in fig. 7, the processing logic of the Agent management node is as follows.
The starting protocol is used for monitoring internal operation errors, setting a timer, scanning an Agent management node error log, judging whether a system error occurs, sending an alarm if the system error occurs, setting a timer cycle, and setting the timer cycle if the system error does not occur.
Starting a plurality of coprocesses for processing Agent heartbeat information, starting a plurality of coprocesses for synchronizing Agent configuration change states, waiting for an RPC call request, storing RPC request data, responding to the Agent request, judging whether the heartbeat information or state synchronous data is the heartbeat information or not, if so, performing heartbeat data processing, updating a database device table, and continuing to wait for the RPC call request; if not, setting a lock (preventing data conflict in the cluster in the processing process), updating a database configuration change state/updating a Redis cache to judge whether all the agents related to the change task are successfully executed, if yes, updating the database configuration change state/releasing the distributed lock, notifying mail, synchronizing information and the like, releasing the lock (preventing data conflict in the cluster in the mode processing process), continuing to wait for the RPC call request, if not, releasing the lock (preventing data conflict in the cluster in the mode processing process), and continuing to wait for the RPC call request.
In the embodiment of the application, the Agent management node and the Agent communicate by using Remote Procedure Call (RPC), and the communication information of the Agent management node and the Agent is simpler. The Agent transmits the device management IP when synchronizing the heartbeat, and transmits the work order id, the device management IP, the Zone, and the status code when synchronizing the configuration loading status. In order to improve the information processing efficiency, after receiving the RPC request, the Agent management node only responds to one random id, and then processes heartbeat information and configuration change states asynchronously through a plurality of procedures. Similar to agents, agent management nodes also have the ability to self-monitor anomalies.
The system has higher compatibility to various DNS software, meanwhile, due to the plug-in design of the Agent, the system is very simple in the deployment and maintenance processes, the system supports the dynamic scheduling function of domain names, a user can decide whether to start the system or not, the system responds to the user request in real time, only the Zone to be updated is configured and updated, and configuration data is transmitted in an encryption mode, so that the efficiency and the safety of configuration and updating are higher, the deployment of multiple machine rooms and multiple nodes are supported, and each component of the system also supports transverse expansion. Therefore, the system has higher usability and expandability.
As shown in fig. 8, a timing diagram of the execution flow of the system processing a domain name configuration update once is shown.
The method comprises the steps that a user submits work order data to a configuration management server, the configuration management server caches work order state/equipment distributed locks to Redis, then receives a Redis response, the configuration management server sends the processed work order data to a database, receives configuration data returned by the database, sends the configuration data to an ETCD, then receives ETCD response data, and returns a work order id to the user, at the moment, an Agent acquires the configuration data from the ETCD, receives the configuration data returned by the ETCD, then sends a task state to an Agent management cluster, the Agent management cluster sets task locks to the Redis, receives the Redis response, then sends response information to the Agent, then the Agent management cluster updates the database and receives a database response, the Agent management cluster updates the distributed locks to the Redis, and receives the Redis response.
When a user inquires the work order state from the configuration management server, the configuration management server acquires the work order cache from the Redis, acquires the work order cache information returned by the Redis, and sends the work order execution state to the user.
It should be noted that, in this document, 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.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.
Claims (10)
1. A domain name configuration management system, comprising: a management server, an Agent management cluster and an Agent plug-in are configured; the configuration management server and the Agent management cluster are arranged at the server, the Agent plug-in is arranged at a Domain Name System (DNS) client, and the Agent plug-in can be compatible with multiple types of DNS software;
the configuration management server provides an application program interface for the DNS client and issues configuration information stored by the server to the DNS client through the application program interface, wherein the configuration information is used for updating configuration in the DNS client and comprises equipment group configuration data, IP address configuration data and area configuration data;
the Agent management cluster comprises a plurality of Agent management nodes, each Agent management node receives and processes Agent state information in the DNS client, and the Agent state information comprises heartbeat information uploaded by an Agent plug-in, a configuration loading state of the Agent plug-in and a lock state set by the configuration management server.
2. The system of claim 1, wherein a plurality of said DNS clients are divided into different device groups by service class, each of said device groups using a DNS software.
3. The system of claim 2, wherein the set of devices comprises a plurality of zones, each zone comprising a plurality of domain names, each domain name being associated with an IP address.
4. The system of claim 3, wherein the server further comprises: the system comprises a database, wherein configuration information and Agent state information are stored in the database, and the configuration management server side acquires the configuration information and the Agent state information from the database and issues the configuration information to the DNS client side through the application program interface according to the Agent state information.
5. The system of claim 4, wherein the database is updated based on the Agent status information received by the Agent management cluster.
6. The system of claim 5, wherein the server further comprises: ETCD cluster
The configuration management server side issues the configuration information to the DNS client side through the application program interface according to the Agent state information, and specifically comprises the following steps:
and the configuration management server synchronizes the configuration information to the ETCD cluster according to the Agent state information, and the ETCD cluster transmits the configuration information to the DNS client through the application program interface.
7. The system of claim 6, wherein the ETCD cluster includes a plurality of ETCD nodes, each of the ETCD nodes corresponding to one of the device groups of the DNS client, the ETCD nodes issuing the configuration information to the device group corresponding to the application program interface.
8. The system of claim 6, wherein configuration information in the ETCD cluster is stored in units of zones, each zone including a device group role ID, a device group ID, and a zone ID.
9. The system of claim 8, wherein the configuration management server compresses the configuration information and synchronizes the compressed configuration information to the ETCD cluster.
10. The system of claim 1, wherein each of the Agent management nodes communicates with the Agent plugin via a remote procedure call RPC;
when synchronizing the heartbeat information, the Agent plugin sends an equipment management IP to each Agent management node; and when the configuration loading state is synchronized, the Agent plugin sends a work order ID, an equipment management IP, an area and a state code to each Agent management node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110713434.6A CN113596187B (en) | 2021-06-25 | 2021-06-25 | Domain name configuration management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110713434.6A CN113596187B (en) | 2021-06-25 | 2021-06-25 | Domain name configuration management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113596187A CN113596187A (en) | 2021-11-02 |
| CN113596187B true CN113596187B (en) | 2023-05-05 |
Family
ID=78244648
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110713434.6A Active CN113596187B (en) | 2021-06-25 | 2021-06-25 | Domain name configuration management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113596187B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114143321B (en) * | 2021-11-26 | 2023-08-25 | 中电信数智科技有限公司 | Multi-tenant application configuration distribution system based on cross-IDC environment |
| CN114401273A (en) * | 2022-01-18 | 2022-04-26 | 中国建设银行股份有限公司 | Equipment control method and system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112099918A (en) * | 2019-09-13 | 2020-12-18 | 谷歌有限责任公司 | Live migration of clusters in containerized environments |
| CN112491606A (en) * | 2020-11-20 | 2021-03-12 | 湖南麒麟信安科技股份有限公司 | Method for automatically deploying high-availability cluster of service system based on infrastructure |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002039699A1 (en) * | 2000-11-09 | 2002-05-16 | Cacheflow, Inc. | Domain name system extensions to support reverse proxy operations and layer-7 redirection |
| KR20030065064A (en) * | 2002-01-29 | 2003-08-06 | 삼성전자주식회사 | Method for managing domain name |
| US10140140B2 (en) * | 2015-06-30 | 2018-11-27 | Microsoft Technology Licensing, Llc | Cloud virtual machine customization using extension framework |
| CN108092936A (en) * | 2016-11-22 | 2018-05-29 | 北京计算机技术及应用研究所 | A kind of Host Supervision System based on plug-in architecture |
| CN110912966A (en) * | 2019-10-29 | 2020-03-24 | 东南大学 | Expressway portal system based on containerization of packaging and isolation mechanism |
| CN112769634B (en) * | 2020-12-09 | 2023-11-07 | 航天信息股份有限公司 | Zookeeper-based laterally-expandable distributed system and development method |
-
2021
- 2021-06-25 CN CN202110713434.6A patent/CN113596187B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112099918A (en) * | 2019-09-13 | 2020-12-18 | 谷歌有限责任公司 | Live migration of clusters in containerized environments |
| CN112491606A (en) * | 2020-11-20 | 2021-03-12 | 湖南麒麟信安科技股份有限公司 | Method for automatically deploying high-availability cluster of service system based on infrastructure |
Non-Patent Citations (1)
| Title |
|---|
| 刘春 ; 景建强 ; 邵国强 ; 孙涛 ; 张丽华 ; .CentOS 7中Squid代理服务器的配置与实现.现代信息科技.2020,(03),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113596187A (en) | 2021-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5727020B2 (en) | Cloud computing system and data synchronization method thereof | |
| US10951623B2 (en) | Smart remote control system | |
| CN113596187B (en) | Domain name configuration management system | |
| KR101389101B1 (en) | Method and apparatus for tracking device management data changes | |
| KR20080068110A (en) | A method for processing data synchronization and client terminal, server and data synchronization system thereof | |
| CN110555041A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN111901705B (en) | OMCI function virtualization system of OLT equipment | |
| US8326913B2 (en) | Method and system for service contract discovery | |
| CN112632029B (en) | Data management method, device and equipment of distributed storage system | |
| CN114448686B (en) | Cross-network communication device and method based on micro-service | |
| CN111526185A (en) | Data downloading method, device, system and storage medium | |
| CN110163003B (en) | Password management method and device | |
| CN111371615A (en) | Online server, updating method and system of operation and maintenance tool and readable storage medium | |
| CN113259476B (en) | Message pushing method and system | |
| CN116346834A (en) | Session synchronization method, device, computing equipment and computer storage medium | |
| CN112039910B (en) | Method, system, equipment and medium for unified management of authentication and authority | |
| CN115086347A (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN111586438A (en) | Method, device and system for processing service data | |
| CN115297129B (en) | Method and device for establishing data communication network | |
| WO2024093328A1 (en) | Virtual desktop connection method and apparatus | |
| CN117955991A (en) | Service processing method, device, equipment and storage medium | |
| CN116627925A (en) | Service log data processing method and device based on K8S environment | |
| CN114301930A (en) | Distributed data synchronization method, system and storage medium | |
| CN118092780A (en) | Recording information synchronization method, recording information synchronization device, blockchain node and storage medium | |
| CN113760843A (en) | Site deployment method and terminal |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230322 Address after: Room 501-502, 5/F, Sina Headquarters Scientific Research Building, Block N-1 and N-2, Zhongguancun Software Park, Dongbei Wangxi Road, Haidian District, Beijing, 100193 Applicant after: Sina Technology (China) Co.,Ltd. Address before: 100080 7th floor, Sina headquarters scientific research building, plot n-1 and n-2, Zhongguancun Software Park Phase II (West Expansion), Dongbeiwang West Road, Haidian District, Beijing Applicant before: Sina.com Technology (China) Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |