DNS (Domain Name Server) management system and method and electronic equipment

Abstract

The invention provides a DNS (Domain Name Server) management system and method and electronic equipment, and the system comprises a metadata definition module which is used for obtaining a hierarchical relationship configured by a user, and generating a domain name template; the domain name management module is used for receiving a to-be-analyzed domain name newly added by a user, and generating a domain name analysis record for the to-be-analyzed domain name based on a domain name template; the DNS equipment management module is used for maintaining a DNS server; the IP switching strategy module is used for generating an IP switching strategy and configuring a corresponding domain name according to the IP switching strategy; and the domain name authority management module is used for distributing authority to the user according to the domain name resolution record. Therefore, by adding the metadata definition module and the domain name management module, a large amount of domain name data can be simply and efficiently managed, a data basis is provided for subsequent addition of a domain name permission allocation mechanism, and each domain name is managed and controlled more finely according to different access requirements and security policies; the domain name management quality and security are improved, the operation complexity is reduced, and the security risk is reduced.

Description

Technical Field

[0001] This disclosure relates to the technical fields of infrastructure and IT production, and in particular to a DNS management system, method, and electronic device. Background Technology

[0002] The development of the internet is inseparable from domain name resolution, which is the process of pointing a domain name to the Internet Protocol (IP) space. This allows people to easily access websites through their registered domain names. An IP address is a numerical address that identifies a site on the network; for ease of remembering, domain names are used instead of IP addresses. Domain name resolution is the process of converting a domain name to an IP address. This domain name resolution is handled by Domain Name System (DNS) servers.

[0003] In continuous projects, the domain-based transformation of service calls generates a large number of domain name definition and resolution requirements, necessitating the synchronization of service-generated domain names to DNS servers. While current DNS servers can provide domain name resolution services, their use in actual production environments presents several problems: ambiguous domain name definitions, making it impossible to accurately search for domains with specific custom criteria; lack of an intuitive user interface, resulting in cumbersome and inefficient domain management and record changes; lack of access control and auditing mechanisms, potentially leading to unauthorized access and operations, increasing security risks, and resulting in low domain management security; and lack of policy-based domain name switching capabilities, making it impossible to mitigate failures through domain name switching. Summary of the Invention

[0004] This disclosure aims to at least partially address one of the technical problems in the related art.

[0005] Therefore, one objective of this disclosure is to propose a DNS management system.

[0006] The second objective of this disclosure is to propose a DNS management method.

[0007] The third objective of this disclosure is to propose an electronic device.

[0008] The fourth objective of this disclosure is to provide a non-transitory computer-readable storage medium.

[0009] The fifth objective of this disclosure is to provide a computer program product.

[0010] To achieve the above objectives, a first aspect of this disclosure proposes a DNS management system, comprising: a metadata definition module, a domain name management module, a DNS device management module, an IP switching policy module, and a domain name permission management module; wherein, the metadata definition module is used to obtain the hierarchical relationship configured by the user and generate a domain name template based on the hierarchical relationship; the domain name management module is used to receive a domain name to be resolved added by the user and generate a domain name analysis record for the domain name to be resolved based on the domain name template; the DNS device management module is used to maintain a DNS server; the IP switching policy module is used to generate an IP switching policy after receiving an IP switching request from the user and configure the corresponding domain name according to the IP switching policy; the domain name permission management module is used to assign permissions to the user according to the domain name resolution record.

[0011] According to one embodiment of this disclosure, the metadata definition module further includes: a metadata subunit, a domain name template configuration subunit, and a template compilation subunit; wherein, the metadata subunit is used to store metadata definition names and metadata value types; the domain name template configuration subunit is used to configure the hierarchical relationship of the metadata; and the template compilation subunit is used to convert the metadata into a domain name template according to the hierarchical relationship and store it.

[0012] According to one embodiment of this disclosure, the step of converting the metadata into a domain name template and storing it according to the hierarchical relationship includes: generating configurable items based on the hierarchical relationship and configuring them into an initial domain name template to generate the domain name template.

[0013] According to one embodiment of this disclosure, the domain name management module is further configured to: perform a normative verification on the received domain name based on the domain name template, and after the normative verification is passed, convert the domain name into a domain name attribute, wherein the domain name attribute is an attribute defined in the domain name template.

[0014] According to one embodiment of this disclosure, the domain name management module is further configured to: provide domain name attribute search function and domain name category search function.

[0015] According to one embodiment of this disclosure, the DNS device management module is also used to configure the interface of the DNS server.

[0016] According to one embodiment of this disclosure, the IP switching strategy module is further configured to: preview the effect of the configuration before configuring the corresponding domain name according to the IP switching strategy.

[0017] According to one embodiment of this disclosure, the IP switching strategy includes one of switching by node, switching by domain name, and switching by IP address.

[0018] To achieve the above objectives, a second aspect of this disclosure provides a DNS management method, comprising: after receiving a new domain name to be resolved from a user, analyzing the domain name to be resolved through a DNS management system to generate a domain name analysis record, wherein the DNS management system is the system described in the first aspect embodiment.

[0019] To achieve the above objectives, a third aspect of this disclosure provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor to implement the DNS management method as described in the second aspect of this disclosure.

[0020] To achieve the above objectives, a fourth aspect of this disclosure provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to implement the DNS management method as described in the second aspect of this disclosure.

[0021] To achieve the above objectives, a fifth aspect of this disclosure provides a computer program product including a computer program that, when executed by a processor, is used to implement the DNS management method as described in the second aspect of this disclosure.

[0022] Therefore, compared with the DNS management system in the current technology, the DNS management system in this disclosure can achieve simple and efficient management of a large amount of domain name data by adding a metadata definition module and a domain name management module. It provides a data foundation for the subsequent addition of a domain name permission allocation mechanism. According to different access needs and security policies, it can perform more refined management and control of each domain name, improve the management quality and security of domain names, reduce operational complexity, and reduce security risks. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of a DNS management system according to one embodiment of the present disclosure;

[0024] Figure 2 This is a schematic diagram of a metadata definition module according to one embodiment of this disclosure;

[0025] Figure 3 This is a schematic diagram of a domain name management module according to one embodiment of the present disclosure;

[0026] Figure 4 This is a schematic diagram of a custom attribute search according to one embodiment of this disclosure;

[0027] Figure 5 This is a schematic diagram of a DNS device management module according to one embodiment of the present disclosure;

[0028] Figure 6 This is a schematic diagram of an IP handover strategy module according to one embodiment of this disclosure;

[0029] Figure 7 This is a schematic flowchart of a preview process according to one embodiment of the present disclosure;

[0030] Figure 8 This is a schematic diagram of an IP switching process according to one embodiment of this disclosure;

[0031] Figure 9 This is a schematic diagram of a process for allocating permissions according to custom attributes and domain classification, as implemented in this disclosure.

[0032] Figure 10 This is a schematic diagram of the structure of an interface executor according to one embodiment of the present disclosure;

[0033] Figure 11 This is a schematic diagram of a DNS management method according to one embodiment of the present disclosure;

[0034] Figure 12 This is a flowchart illustrating a DNS management system according to one embodiment of the present disclosure, which analyzes newly added domain names based on newly added domain name information and preset domain name templates.

[0035] Figure 13 This is a schematic diagram of an electronic device according to one embodiment of the present disclosure. Detailed Implementation

[0036] Embodiments of this disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.

[0037] The acquisition, storage, use, and processing of data in this disclosed technical solution all comply with the relevant provisions of relevant laws and regulations.

[0038] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0039] In current technologies, the domain-based transformation of service calls in continuous projects generates a large number of domain name definitions and resolution requirements, necessitating the synchronization of service-generated domain names to a DNS server. To address these issues, this disclosure proposes a DNS management system.

[0040] Figure 1 This is a schematic diagram of a DNS management system according to one embodiment of this disclosure, as shown below. Figure 1 As shown, the DNS management system 100 includes: a metadata definition module 110, a domain name management module 120, a DNS device management module 130, an IP switching policy module 140, and a domain name permission management module 150.

[0041] The metadata definition module 110 is used to obtain the hierarchical relationship configured by the user and generate a domain name template based on the hierarchical relationship.

[0042] It should be noted that the configured hierarchical relationship can be entered by the user in advance, or it can be selected by the user from the preset hierarchical relationship in the DNS management system 100. There are no restrictions here.

[0043] The domain name management module 120 is used to receive newly added domain names to be resolved by users and generate domain name analysis records based on the domain name template.

[0044] The DNS device management module 130 is used to maintain the DNS server.

[0045] The IP switching policy module 140 is used to generate an IP switching policy after receiving a user's IP switching request, and to configure the corresponding domain name according to the IP switching policy.

[0046] The domain permission management module 150 is used to assign permissions to users based on domain name resolution records.

[0047] Therefore, compared with the DNS management system in the current technology, the DNS management system in this disclosure can achieve simple and efficient management of a large amount of domain name data by adding a metadata definition module and a domain name management module. It provides a data foundation for the subsequent addition of a domain name permission allocation mechanism. According to different access needs and security policies, it can perform more refined management and control of each domain name, improve the management quality and security of domain names, reduce operational complexity, and reduce security risks.

[0048] In the embodiments disclosed herein, such as Figure 2 As shown, the metadata definition module 110 also includes: a metadata subunit 210, a domain name template configuration subunit 220, and a template compilation subunit 230.

[0049] The metadata subunit 210 is used to store metadata definition names and metadata value types. It should be noted that the stored metadata can be of various types, without any limitations here. For example, metadata may include application name, channel, data center, network domain, service type, subdomain, root domain, etc.

[0050] Domain name template configuration subunit 220 is used to configure the hierarchical relationship of metadata.

[0051] In one possible implementation, the hierarchy of metadata can be: application name, channel, data center, network domain, service type, subdomain, root domain.

[0052] Template compilation subunit 230 is used to convert metadata into domain name templates according to hierarchical relationships and store them.

[0053] In this embodiment of the disclosure, configurable items can be generated based on hierarchical relationships and configured into the initial domain name template to generate a domain name template.

[0054] There are various domain name templates available, and no restrictions are imposed here. Taking domain name template A: ${appName}.${chAbbr}.${dataCenter}.${netArea}.${serviceType}.fmcc.com as an example, each ${...} represents a variable, and each variable has an attribute. These variables will be replaced with their actual values ​​when generating a specific domain name.

[0055] Here, ${appName} represents the application name. This variable typically represents the domain name portion you want to create for a specific application or service. For example, if the application is a "shopping cart," this variable might be replaced with "cart."

[0056] ${chAbbr}: Channel abbreviation. This variable may be used to represent different sales channels or business channels. For example, if it is a core channel, this variable might be "hx".

[0057] ${dataCenter}: Data center identifier. This is used to indicate the location or type of data center. For example, "sj" indicates the Shangjie Data Center or "bs" indicates the Beishu Data Center.

[0058] ${netArea}: Network area. This may represent a geographic area or network coverage area, such as the "bss-test" B-domain application test representation or the "bss-pro" B-domain application production.

[0059] ${serviceType}: Service type. This variable is used to distinguish different service or product types. For example, "app", "web", or "db".

[0060] fmcc.com: This is the basic part of the domain name, which usually represents the name of the company or organization.

[0061] By replacing these variables, the domain name corresponding to this domain name template can be generated, for example:

[0062] If appName is "rmc-infra-apigateway-gw", chAbbr is "iotht", dataCenter is "ns", netArea is "bss-hg", and serviceType is "app", then the generated domain name will be rmc-infra-apigateway-gw.iotht.ns.bss-hg.app.fmcc.com.

[0063] In the embodiments disclosed herein, such as Figure 3 As shown, the domain name management module 120 is used to generate domain name attributes and domain name classifications based on domain names and domain name templates through a domain name converter.

[0064] It should be noted that the domain name converter is a program or model pre-configured in the domain name management module 120, used to perform conversion based on domain names and domain name templates.

[0065] In this embodiment of the disclosure, the domain name management module 120 is further configured to: perform a normative verification on the received domain name based on the domain name template, and after the normative verification is passed, convert the domain name into domain name attributes, wherein the domain name attributes are the attributes defined in the domain name template.

[0066] In another possible implementation, the domain management module 120 also provides a custom attribute search function and a domain-based category search function. Domain attributes refer to the custom attributes that a domain has under the current domain template. After obtaining the custom attributes of each domain, custom searches can be performed using these attributes, thus flexibly adapting to different service needs and management requirements.

[0067] In one possible implementation, custom attribute search is as follows: Figure 4 As shown, the domain name management module 120 simultaneously initiates two custom searches. The search retrieves domain name resolution record A and domain name resolution record B by using attribute A=bss-pro, and retrieves domain name resolution record B by using attribute B=sj.

[0068] In another possible implementation, configurable items are generated based on hierarchical relationships and configured into the initial domain name template to generate a domain name template. For example, consider the following four metadata items: M1 (name: appName, value type: variable), M2 (name: serviceType, value type: variable), M3 (name: fmcc, value type: constant), and M4 (name: com, value type: constant). The hierarchical relationship is M4->M3->M2->M1, meaning M4 is the root node and M1 is the leaf node. In the template configuration, M2 is declared as the "service type" attribute and M1 as the "application name" attribute. The resulting domain name template B is ${appName}.${serviceType}.fmcc.com, and the domain name under this template has two custom attributes: "service type" and "application name".

[0069] For example, in the domain name esb.pdb.fmcc.com, the sub-defined attributes of this domain name include "service type" and "application name", where the value of the service type attribute is pdb and the value of the application name attribute is esb;

[0070] In the domain name smc.pdb.fmcc.com, the custom attributes of this domain name include "service type" and "application name". The value of the service type attribute is pdb, and the value of the application name attribute is smc.

[0071] To perform a domain search, you can limit the search by specifying the value of a custom attribute. For example, using the domains esb.pdb.fmcc.com and smc.pdb.fmcc.com, if a user searches for (custom attribute "Service Type" = "pdb"), it will return two domain records: smc.pdb.fmcc.com and esb.pdb.fmcc.com. If the user searches for (attribute "Application Name" = "smc"), it will return only one domain record: smc.pdb.fmcc.com.

[0072] In the embodiments disclosed herein, such as Figure 5 As shown, the DNS device management module 130 includes DNS service configuration and interface configuration.

[0073] The DNS server configuration is used to maintain the DNS server type, network address, authentication information, etc.

[0074] The interface configuration is used to configure the DNS server interface, such as query and add; configure the request method of the interface, such as POST, GET, PUT, etc.; configure the validation method of the interface, such as request header validation, Uniform Resource Locator (URL) parameter validation, request body validation, etc.

[0075] By differentiating DNS server types and configuring multiple server interfaces, the DNS management system has the ability to uniformly manage different DNS servers, reducing operational complexity.

[0076] In the embodiments disclosed herein, such as Figure 6 As shown, the IP switching policy module 140 includes policy configuration, IP switching preview executor, and IP switching executor.

[0077] Policy configuration responds to user actions and allows configuration of the domain name corresponding to the IP switching policy. This can be a single domain name, a single IP address, or a custom class of domain names; it also allows configuration of the target IP address for switching, such as a specific IP address or a custom class of IP addresses. Switching policies include switching by node, switching by domain name, and switching by IP address.

[0078] In response to user actions, the IP switching preview executor is used to display the effects of IP changes before and after the IP switching policy configuration takes effect or becomes invalid. Preview processing reference. Figure 7 The IP switching preview executor reads the domain names and their IP information included in the current policy of domain name management. Through the interface executor, it calls the DNS server interface to read the IP information of these domain names from the DNS server. It then displays the differences between the IP information in the platform's domain name management and the IP information in the DNS server, grouped by domain name. This allows users to easily compare the changes before and after, determine the switching effect, and improve the user experience.

[0079] The IP switching executor reads the IP switching policy configuration, DNS server configuration, and interface configuration, and calls the interface executor to perform the IP switching. (IP switching reference...) Figure 8 The IP switching executor reads the domain names and their IP information contained in the current policy of domain name management. It calls the DNS server interface through the interface executor to read the IP information of the domain names in the DNS server. Based on the difference between the domain name and the domain name in the DNS server, it calls the add, change, or delete interface to change the IP, and puts the interface call result into the database.

[0080] In this embodiment of the disclosure, the domain name permission management module 150 is used to provide domain name permission allocation functionality, which can allocate permissions according to custom attributes and domain name categories. For example, such as Figure 9 As shown, if there are two domain name resolution records that both belong to domain name category A,

[0081] A:ug-cmc-sac-jcgi.hx.bs.bss-pro.app.fmcc.com、

[0082] B:cmc-af-cgi.hx.sj.bss-pro.app.fmcc.com,

[0083] If a user is given the permission [domain category: A, custom attribute: (A like 'bss' or B = 'bs')], then that user can operate on two domains, A and B. If a user is given the permission [domain category: A, custom attribute: (B = 'bs')], then that user can operate on one domain, A.

[0084] If a user is assigned permission for [domain category: B, custom attribute: (B = 'bs')], the user will be unable to operate on domains A and B because records A and B do not belong to domain category A.

[0085] Figure 10 This is a schematic diagram of the interface actuator, such as... Figure 10 As shown, the interface executor is connected in this embodiment of the disclosure as follows: Figures 1-9 The DNS management system shown contains a parameter validation executor and an interface call record executor.

[0086] The parameter validation executor is used to read the parameter validation configuration stored locally and perform parameter validation.

[0087] The API call record executor is used to save API call records.

[0088] Figure 11 This is a schematic diagram of a DNS management method according to one embodiment of the present disclosure, as shown below. Figure 1 As shown, the method includes:

[0089] S1101, after receiving the new domain name to be resolved by the user, analyzes the domain name to be resolved through the DNS management system to generate a domain name analysis record.

[0090] It should be noted that the DNS management system in this embodiment is as follows: Figure 1-10 The DNS management system in this example.

[0091] In the embodiments disclosed herein, such as Figure 12 As shown, after a user adds a domain name record, the DNS management system analyzes the new domain name based on the new domain name information and the preset domain name template, obtains the custom attribute types in the new domain name and the corresponding values ​​of each custom attribute, and records and stores them in the database. The DNS management system then synchronizes the domain name record to the DNS root name server.

[0092] The calling service initiates a domain name resolution request. The resolver, acting as a client accessing the local name server, also initiates a request. The local name server checks if it has cached the domain name information. If so, it returns a response; otherwise, it queries the root name server for the domain name resolution record, caches the obtained record locally, and returns a response. The resolver parses the response and returns the domain name resolution information to the calling service. After obtaining the domain's IP address, the calling service initiates a service call.

[0093] To implement the above embodiments, this disclosure also proposes an electronic device 1300. Figure 13 This is a schematic diagram of an electronic device according to one embodiment of the present disclosure, such as... Figure 13 As shown, the electronic device 1300 includes: a processor 1301 and a memory 1302 communicatively connected to the processor. The memory 1302 stores instructions executable by at least one processor. The instructions are executed by at least one processor 1301 to implement the functions described in this disclosure. Figure 12 DNS management method of the example.

[0094] To implement the above embodiments, this disclosure also proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to implement the present disclosure. Figure 12 DNS management method of the example.

[0095] To implement the above embodiments, this disclosure also proposes a computer program product, including a computer program, which, when executed by a processor, implements the features of this disclosure. Figure 12 DNS management method of the example.

[0096] It should be noted that personal information collected from users should be used for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. Furthermore, such collection / sharing should only be conducted after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign an agreement / authorization that includes authorization of relevant user information before the user uses the function. In addition, any necessary steps must be taken to protect and safeguard access to such personal information data and ensure that others with access to personal information data comply with their privacy policies and procedures.

[0097] This application is intended to provide an implementation scheme for users to selectively prevent the use or access to their personal information data. Specifically, this disclosure is intended to provide hardware and / or software to prevent or block access to such personal information data. Once personal information data is no longer needed, risks can be minimized by restricting data collection and deleting data. Furthermore, where applicable, such personal information is de-identified to protect user privacy.

[0098] In the foregoing descriptions of the embodiments, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0099] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0100] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0101] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that contains, stores, communicates, propagates, or transmits programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0102] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0103] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it includes one or a combination of the steps of the method embodiments.

[0104] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0105] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A DNS management system, characterized in that, include: Metadata definition module, domain name management module, DNS device management module, IP switching policy module, and domain name permission management module; The metadata definition module is used to obtain the hierarchical relationship configured by the user and generate a domain name template based on the hierarchical relationship. The domain name management module is used to receive newly added domain names to be resolved by users, and to generate domain name analysis records for the domain names to be resolved based on the domain name template; The DNS device management module is used to maintain the DNS server; The IP switching strategy module is used to generate an IP switching strategy after receiving a user's IP switching request, and to configure the corresponding domain name according to the IP switching strategy. The domain name permission management module is used to assign permissions to users based on domain name resolution records.

2. The system according to claim 1, characterized in that, The metadata definition module also includes: Metadata subunit, domain name template configuration subunit, and template compilation subunit; The metadata subunit is used to store the metadata definition name and the metadata value type; The domain name template configuration subunit is used to configure the hierarchical relationship of the metadata; The template compilation subunit is used to convert the metadata into a domain name template according to the hierarchical relationship and store it.

3. The system according to claim 2, characterized in that, The step of converting the metadata into domain name templates according to the hierarchical relationship and storing them includes: Based on the hierarchical relationship, configurable items are generated and configured into the initial domain name template to generate the domain name template.

4. The system according to claim 1, characterized in that, The domain name management module is also used for: The received domain name is validated for compliance based on the domain name template. After the compliance validation is passed, the domain name is converted into domain name attributes, which are the attributes defined in the domain name template.

5. The system according to claim 4, characterized in that, The domain name management module is also used for: It provides domain attribute search function and domain category search function.

6. The system according to claim 1, characterized in that, The DNS device management module is also used to configure the DNS server interface.

7. The system according to claim 1, characterized in that, The IP switching strategy module is also used for: Before configuring the corresponding domain name according to the IP switching strategy, a preview of the configuration effect is displayed.

8. The system according to claim 1, characterized in that, The IP switching strategy includes one of the following: switching by node, switching by domain name, and switching by IP address.

9. A DNS management method, characterized in that, include: After receiving a new domain name to be resolved from a user, the DNS management system analyzes the domain name to be resolved to generate a domain name analysis record, wherein the DNS management system is the system as described in any one of claims 1-8.

10. An electronic device, characterized in that, Including memory and processor; The processor reads executable program code stored in the memory to run a program corresponding to the executable program code, so as to implement the method as described in claim 9.

Images