Domain name management method and device and computer equipment

Abstract

The invention relates to a domain name management method and device and computer equipment. The method comprises the following steps: pulling a plurality of sub-domain names and an address list corresponding to each sub-domain name from a data center; in response to the triggered domain name management instruction, obtaining a domain name management type corresponding to the domain name management instruction; determining a to-be-deployed sub-domain name and a corresponding address list according to the domain name management type, the plurality of sub-domain names and the address list corresponding to each sub-domain name; sending a deployment instruction generated based on the to-be-deployed sub-domain name and the corresponding address list to a deployment device, and updating a local domain name database; the deployment instruction is used for indicating the deployment device to perform deployment in the authoritative domain name database. By adopting the method, the domain name management efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of domain name management, and in particular to a domain name management method, apparatus, and computer equipment. Background Art

[0002] With the rapid development of Internet technology, the Domain Name System (DNS), as one of the core infrastructures of the Internet, is crucial to the operation of the entire Internet in terms of stability and efficiency.

[0003] In related technologies, the management of domain name resolution data still relies on manual operations. Operation and maintenance personnel need to manually log in to the management interface to complete addition, modification and deletion operations based on dynamic information such as domain name registration changes and server migration.

[0004] However, the related art methods have the problem of poor management efficiency. Summary of the Invention

[0005] Based on this, it is necessary to provide a domain name management method, device and computer equipment to improve the efficiency of domain name management in response to the above technical problems.

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

[0007] Pull multiple subdomains and a list of addresses corresponding to each subdomain from the data center;

[0008] In response to the triggered domain name management instruction, obtaining a domain name management type corresponding to the domain name management instruction;

[0009] Determine the subdomains to be deployed and the corresponding address list based on the domain name management type, multiple subdomains, and the address list corresponding to each subdomain;

[0010] Send a deployment instruction generated based on the subdomain to be deployed and the corresponding address list to the deployment device, and update the local domain name database; the deployment instruction is used to instruct the deployment device to deploy in the authoritative domain name database.

[0011] In one embodiment, obtaining the domain name management type corresponding to the domain name management instruction includes:

[0012] In the case where the domain name management instruction is a domain name update instruction triggered by a user, determining that the domain name management type corresponding to the domain name management instruction is update management;

[0013] In the case that the domain name management instruction is an instruction triggered by reaching a preset condition, it is determined that the domain name management type corresponding to the domain name management instruction is fault management.

[0014] In one embodiment, the update management includes adding a new primary domain name;

[0015] Determine the subdomains to be deployed and the corresponding address list based on the domain name management type, multiple subdomains, and the address list corresponding to each subdomain, including:

[0016] Performing a validity check on the target subdomain selected from multiple subdomains and the corresponding parameter information carried in the domain name management instruction;

[0017] If the validity check passes, the duplication check is performed on the main domain name composed of each target subdomain name carried in the domain name management instruction;

[0018] If there is no duplication, the target subdomain is used as the subdomain to be deployed, and the address list of the target subdomain is used as the address list corresponding to the reference domain to be deployed.

[0019] In one embodiment, update management includes modifying a domain name;

[0020] Determine the subdomains to be deployed and the corresponding address list based on the domain name management type, multiple subdomains, and the address list corresponding to each subdomain, including:

[0021] Verify the validity of modification parameter information carried in domain name management instructions;

[0022] If the validity check passes, determine whether the modified parameter information, the subdomain name corresponding to the modified parameter information, and the address corresponding to the modified parameter information have changed;

[0023] If a change occurs, the subdomain corresponding to the modified parameter information is used as the subdomain to be deployed, and the address corresponding to the modified parameter information is used as the address list corresponding to the subdomain to be deployed.

[0024] In one embodiment, determining the subdomain to be deployed and the corresponding address list according to the domain name management type, multiple subdomains, and the address list corresponding to each subdomain includes:

[0025] When the domain name management type is fault management, obtain the final coverage information formed by the address list under all subdomains;

[0026] Determine whether the final coverage information is consistent with the coverage information in the local domain name database;

[0027] If they are inconsistent, the subdomain to be deployed is filtered from all subdomains, and the address list corresponding to the subdomain to be deployed is filtered from the addresses of all subdomains.

[0028] In one embodiment, the method further comprises:

[0029] Find the newly added address from the address list under all subdomains;

[0030] Determine whether the newly added address can operate normally in the authoritative domain name database;

[0031] If so, the subdomain corresponding to the newly added address is used as the reference domain name to be deployed, and the newly added address is used as the address list corresponding to the reference domain name to be deployed; if not, the first alarm information is output; the first alarm information is used to prompt that there is an abnormality in the newly added address.

[0032] In one embodiment, before determining whether the final coverage information is consistent with the coverage information in the local domain name database, the method further includes:

[0033] Determine whether the final coverage information formed by the address list under all subdomains is empty;

[0034] If yes, then output the second warning information; the second warning information is used to prompt that there is an abnormality in the final coverage information;

[0035] If not, perform the step of searching for the newly added address from the address list under all subdomains.

[0036] In one embodiment, the method further comprises:

[0037] Send multiple address requests corresponding to the test domain name to the deployment device;

[0038] Compare the test address corresponding to each received test domain name with the address in the local domain name database;

[0039] If the comparison results are different for multiple times, it is determined that the deployment process in the authoritative domain name database has failed.

[0040] In a second aspect, the present application further provides a domain name management device, comprising:

[0041] The pull module is used to pull multiple subdomains and the address list corresponding to each subdomain from the data center;

[0042] An acquisition module, configured to, in response to a triggered domain name management instruction, acquire a domain name management type corresponding to the domain name management instruction;

[0043] A determination module is used to determine the subdomain to be deployed and the corresponding address list according to the domain name management type, multiple subdomains and the address list corresponding to each subdomain;

[0044] The processing module is used to send a deployment instruction generated based on the subdomain to be deployed and the corresponding address list to the deployment device, and to update the local domain name database; the deployment instruction is used to instruct the deployment device to deploy in the authoritative domain name database.

[0045] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the content of any one embodiment of the domain name management method in the first aspect above is implemented.

[0046] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the content of any one embodiment of the domain name management method in the first aspect above.

[0047] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the content of any one embodiment of the domain name management method in the first aspect above.

[0048] The above-mentioned domain name management method, apparatus, and computer device pull multiple subdomains and an address list corresponding to each subdomain from a data center; in response to a triggered domain name management instruction, obtain the domain name management type corresponding to the domain name management instruction; determine the subdomain to be deployed and the corresponding address list based on the domain name management type, multiple subdomains, and the address list corresponding to each subdomain; send a deployment instruction generated based on the subdomain to be deployed and the corresponding address list to a deployment device, and update the local domain name database; the deployment instruction is used to instruct the deployment device to deploy in the authoritative domain name database. This method can automatically pull multiple subdomains and an address list corresponding to each subdomain from a data center, and according to the domain name management instruction, can quickly filter out the subdomain to be deployed from the multiple subdomains, and filter out the address list corresponding to the subdomain to be deployed from the address list corresponding to each subdomain, and then complete the deployment through the deployment device. The entire process is fully automated, reducing the time required for domain name management and improving domain name management efficiency. In addition, for different domain name management types, the subdomain to be deployed and the corresponding address list corresponding to the domain name management type can be flexibly determined, making the domain name management process applicable to more scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments of the present application or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0050] Figure 1 A diagram illustrating an application environment of a domain name management method according to an embodiment;

[0051] Figure 2 1 is a flowchart of a domain name management method according to an embodiment;

[0052] Figure 3 1 is a flowchart of a domain name management method according to an embodiment;

[0053] Figure 4 This is a schematic diagram of the process of adding a new primary domain name in one embodiment;

[0054] Figure 5 1 is a flowchart of a domain name management method according to an embodiment;

[0055] Figure 6 A schematic diagram of a process for modifying a domain name in one embodiment;

[0056] Figure 7 1 is a flowchart of a domain name management method according to an embodiment;

[0057] Figure 8 1 is a flowchart of a domain name management method according to an embodiment;

[0058] Figure 9 1 is a flowchart of a domain name management method according to an embodiment;

[0059] Figure 10 is a schematic diagram of a fault management process in one embodiment;

[0060] Figure 11 1 is a flowchart of a domain name management method according to an embodiment;

[0061] Figure 12 is a structural block diagram of a domain name management device in one embodiment;

[0062] Figure 13 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0064] Before introducing the technical solution of the present application in detail, a brief introduction to the background technology of the present application is first given.

[0065] With the rapid development of Internet technology, DNS, as one of the core infrastructures of the Internet, is crucial to the operation of the entire Internet in terms of stability and efficiency.

[0066] In related technologies, the management of domain name resolution data still relies on manual operations. Operation and maintenance personnel need to manually log in to the management interface to complete addition, modification and deletion operations based on dynamic information such as domain name registration changes and server migration.

[0067] However, with the increasing number of domain names, the workload of manual domain name management has increased dramatically. This not only consumes a large amount of human resources, but also makes it difficult to ensure accurate and timely management. Faced with complex network environments and ever-changing business needs, manual domain name management lacks automation and intelligent support, making it difficult to quickly respond and adapt to various changes. Furthermore, in high-traffic and high-concurrency scenarios, manual domain name management cannot ensure high service availability and fast response, which directly affects the user experience.

[0068] To address the above issues, this application provides a domain name management method, apparatus, and computer device. By automatically obtaining domain name-related information from a data center and then automatically managing it, manual intervention is reduced and management efficiency is improved. The technical solution of this application is described in detail below.

[0069] The domain name management method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. The application environment includes a data center 101, a computer device 102 and a deployment device 103, wherein the local domain name database is deployed in the computer device 102, and the authoritative domain name database is deployed in the deployment device 103. The data center 101 and the deployment device 103 are both connected to the computer device 102, and the data center 101 is used to provide the latest subdomain names and the address list under each subdomain name. The computer device 102 is used to respond to the triggered domain name management instruction, obtain the domain name management type corresponding to the domain name management instruction; determine the subdomain name to be deployed and the corresponding address list according to the domain name management type, multiple subdomain names and the address list corresponding to each subdomain name; send the deployment instruction generated based on the subdomain name to be deployed and the corresponding address list to the deployment device, and update the local domain name database. After receiving the deployment instruction, the deployment device 103 deploys the subdomain name to be deployed and the corresponding address list in the authoritative domain name database.

[0070] In an exemplary embodiment, Figure 2 As shown, a domain name management method is provided, which is applied to Figure 1 The computer device in the embodiment is used as an example to illustrate the method, including the following steps 101 to 104. Among them:

[0071] S101: Pull multiple subdomains and an address list corresponding to each subdomain from the data center.

[0072] A subdomain refers to a domain name (NS), or NS record value, a type of resource record in the DNS that specifies an authoritative DNS server, the server that resolves the domain name. Each subdomain includes at least one address, which is a list of addresses, known as an address list. An address is an Internet Protocol (IP) address, used to convert a domain name into a specific IP address during DNS resolution.

[0073] In an embodiment of the present application, the computer device may trigger a pull instruction based on a user operation and send the pull instruction to the data center. After receiving the pull instruction, the data center sends the latest multiple subdomains and the address list corresponding to each subdomain to the computer device. Alternatively, the data center may send the latest multiple subdomains and the address list corresponding to each subdomain to the computer device when a preset condition (e.g., a preset time interval) is met.

[0074] S102: In response to the triggered domain name management instruction, obtain a domain name management type corresponding to the domain name management instruction.

[0075] Among them, domain name management types include adding a new primary domain name, modifying a domain name, and fault management.

[0076] In an embodiment of the present application, when a user clicks the "Add Subdomain" button on the domain name management interface provided by the computer device, the triggered domain name management instruction carries an identifier for adding a subdomain. When a user clicks the "Modify Domain Name" button on the domain name management interface provided by the computer device, the triggered domain name management instruction carries an identifier for modifying the domain name. If the user does not click the button, but the fault management process meets the triggering conditions, the triggered domain name management instruction carries an identifier for fault management.

[0077] Based on this, the computer device can parse the triggered domain name management instruction, determine the identification information in the domain name management instruction, and determine the domain name management type corresponding to the domain name management instruction based on the identification information.

[0078] S103: Determine the subdomain to be deployed and the corresponding address list according to the domain name management type, the multiple subdomains and the address list corresponding to each subdomain.

[0079] In an embodiment of the present application, different types of domain name management correspond to different screening methods. After obtaining the domain name management type, the computer device can filter out the subdomains to be deployed from multiple subdomains according to the screening method corresponding to the domain name management type, and filter out the address list corresponding to the subdomain to be deployed from the address list corresponding to each subdomain. For example, assuming that the domain name management type is to add a new primary domain name, the user can filter out the target subdomains that are suitable for the new needs from multiple subdomains based on the new needs, and use the primary domain formed by the multiple target subdomains as the subdomain to be deployed, and use the address list corresponding to the target subdomain as the address list corresponding to the subdomain to be deployed.

[0080] S104, sending a deployment instruction generated based on the subdomain to be deployed and the corresponding address list to the deployment device, and updating the local domain name database; the deployment instruction is used to instruct the deployment device to deploy in the authoritative domain name database.

[0081] In an embodiment of the present application, after determining the subdomain to be deployed and the corresponding address list, the computer device can send the subdomain to be deployed and the corresponding address list to the deployment device. After receiving the subdomain to be deployed and the corresponding address list, the deployment device deploys the subdomain to be deployed and the corresponding address list in the authoritative domain name database to update the authoritative domain name database.

[0082] At the same time, in order to ensure the consistency of the local domain name database and the authoritative domain name database, after the deployment device is deployed in the authoritative domain name database, the subdomains to be deployed and the corresponding address list need to be updated in the local domain name database to ensure data consistency and accuracy.

[0083] In the above-mentioned domain name management method, multiple subdomains and an address list corresponding to each subdomain are pulled from a data center; in response to a triggered domain name management instruction, a domain name management type corresponding to the domain name management instruction is obtained; the subdomain to be deployed and the corresponding address list are determined according to the domain name management type, the multiple subdomains, and the address list corresponding to each subdomain; a deployment instruction generated based on the subdomain to be deployed and the corresponding address list is sent to a deployment device, and a local domain name database is updated; the deployment instruction is used to instruct the deployment device to deploy in the authoritative domain name database. This method can automatically pull multiple subdomains and an address list corresponding to each subdomain from a data center, and according to the domain name management instruction, can quickly filter out the subdomain to be deployed from the multiple subdomains, and filter out the address list corresponding to the subdomain to be deployed from the address list corresponding to each subdomain, and then complete the deployment through the deployment device. The entire process is fully automated, reducing the time required for domain name management and improving domain name management efficiency. In addition, for different domain name management types, the subdomain to be deployed and the corresponding address list corresponding to the domain name management type can be flexibly determined, making the domain name management process applicable to more scenarios.

[0084] Determining the domain name management type is a key step in domain name management. In one embodiment, the specific content of the domain name management type corresponding to the above-mentioned instruction for obtaining domain name management is introduced, and the specific content includes:

[0085] When the domain name management instruction is a domain name update instruction triggered by the user, the domain name management type corresponding to the domain name management instruction is determined to be update management; when the domain name management instruction is an instruction triggered by meeting a preset condition, the domain name management type corresponding to the domain name management instruction is determined to be fault management.

[0086] In an embodiment of the present application, after receiving a domain name management instruction, the computer device can analyze the triggering method of the domain name management instruction to distinguish whether the domain name management instruction was triggered by the user or by the fulfillment of a preset condition. If the domain name management instruction was triggered by the user, the domain name management type can be determined to be update management. Update management methods include adding a new primary domain name and modifying a domain name. If the domain name management instruction was triggered by the fulfillment of a preset condition, the domain name management type can be determined to be fault management.

[0087] In the aforementioned domain name management method, if the domain name management instruction is a user-triggered domain name update instruction, the domain name management type corresponding to the domain name management instruction is determined to be update management; if the domain name management instruction is triggered by the fulfillment of a preset condition, the domain name management type corresponding to the domain name management instruction is determined to be fault management. This method analyzes the triggering method of the domain name management instruction to accurately identify the differences between the triggering methods, thereby accurately determining the domain name management type corresponding to the domain name management instruction.

[0088] Assuming that the update management includes adding a new primary domain name, the following is an example of how to determine the subdomains to be deployed and the corresponding address list according to the domain name management type, multiple subdomains, and the address list corresponding to each subdomain. Figure 3 As shown, the method includes:

[0089] S201: Perform a validity check on the target subdomain selected from multiple subdomains and corresponding parameter information carried in the domain name management instruction.

[0090] The parameter information may include a Start of Authority (SOA) record and a cache time of the subdomain name in the authoritative domain name database.

[0091] In an embodiment of the present application, when the domain name management type is to add a new primary domain name, when the user triggers the domain name management instruction, the user will filter out a target subdomain from multiple subdomains based on the domain name requirements in the domain name management interface of the computer device. The domain name management instruction will then carry the target subdomain selected from the multiple subdomains and corresponding parameter information. The computer device can obtain the target subdomain selected from the multiple subdomains and corresponding parameter information carried in the domain name management instruction by parsing the domain name management instruction.

[0092] The computer device can then use the validity verification rules to verify the validity of the target subdomain and the corresponding parameter information, specifically verifying the validity of the information entered by the user in the domain name management interface. If the validity verification passes, the computer device proceeds to the subsequent repetitive verification process. If the validity verification fails, the computer device displays a prompt message on the domain name management interface indicating the failure. For example, the validity verification may verify that the name of the primary domain (zone) composed of the target subdomain complies with the standard.

[0093] S202: If the validity check passes, a duplication check is performed on the main domain name composed of target subdomain names carried in the domain name management instruction.

[0094] In an embodiment of the present application, after the legitimacy check passes, the computer device may compare the primary domain name composed of each target subdomain name with all primary domain names stored in the local domain name database. If the primary domain name is consistent with any stored primary domain name, it is determined that the duplication check of the primary domain name has failed, and a prompt message is output to the user to indicate that the duplication check has failed. If the primary domain name is inconsistent with all stored primary domain names, it is determined that the duplication check of the primary domain name has succeeded.

[0095] S203: If there is no duplication, the target subdomain is used as the subdomain to be deployed, and the address list of the target subdomain is used as the address list corresponding to the reference domain to be deployed.

[0096] In an embodiment of the present application, when it is determined that there is no duplication, that is, the duplication check is successful, the computer device can directly use the target subdomain as the subdomain to be deployed, and use the address list of the target subdomain as the address list corresponding to the reference domain to be deployed.

[0097] Figure 4 This is a flow chart of adding a new primary domain name, which includes: S11: determining whether the legitimacy check of the primary domain name composed of multiple target subdomain names has passed, if so, executing step S12, if not, executing step S13; S12: determining whether the duplication check of the primary domain name composed of multiple target subdomain names has passed, if so, executing step S14, if not, executing step S13; S13: outputting an alarm message; S14: adding a new primary domain name to the authoritative domain name database.

[0098] In the above-mentioned domain name management method, the target subdomains selected from multiple subdomains and the corresponding parameter information carried in the domain name management instruction are verified for legitimacy. If the legitimacy check passes, the main domain name composed of the target subdomains carried in the domain name management instruction is verified for duplication. If there are no duplications, the target subdomains are used as the subdomains to be deployed, and the address list of the target subdomains is used as the address list corresponding to the reference domain name to be deployed. Through the verification process from the two perspectives of legitimacy and duplication, this method can more comprehensively verify the target subdomains and corresponding parameter information, thereby accurately determining the subdomains to be deployed and the corresponding address list.

[0099] Assuming that update management includes modifying the domain name, in one embodiment, Figure 5 As shown, the specific contents of determining the subdomain to be deployed and the corresponding address list according to the domain name management type, multiple subdomains, and the address list corresponding to each subdomain include:

[0100] S301: Perform a validity check on the modification parameter information carried in the domain name management instruction.

[0101] In an embodiment of the present application, when the domain name management type is to modify a domain name, the user, in the process of triggering the domain name management instruction, will modify other fields besides the primary domain name (zone) in the domain name management interface of the computer device according to the domain name requirements. For example, other fields may be the NS domain name, SOA record, TTL record, and remarks information. In this case, the domain name management instruction will carry the modified parameter information.

[0102] The computer device can then use the validity verification rules to verify the validity of the modified parameter information contained in the domain name management instruction, specifically verifying the validity of the information modified by the user in the domain name management interface. If the validity verification passes, the subsequent judgment steps will be continued; if the validity verification fails, a prompt message will be displayed on the domain name management interface to indicate the failure of the validity verification. For example, the validity verification can verify that the format of the TTL record and SOA record in the modified parameter information complies with the specifications.

[0103] S302: If the validity check passes, determine whether the modified parameter information, the subdomain name corresponding to the modified parameter information, and the address corresponding to the modified parameter information have changed.

[0104] In an embodiment of the present application, after the legitimacy check passes, the computer device can compare the modified parameter information with the parameter information stored in the local domain name database, and compare the subdomain corresponding to the modified parameter information with the subdomain stored in the local domain name database, and compare the address corresponding to the modified parameter information with the address stored in the local domain name database. If the three comparison results are the same, it is determined that no change has occurred. At this time, the content modified by the user does not need to be subsequently deployed, and only needs to be updated in the local central database. If any of the three comparison results are different, it is determined that the modified parameter information has changed.

[0105] S303: If a change occurs, the subdomain corresponding to the modified parameter information is used as the subdomain to be deployed, and the address corresponding to the modified parameter information is used as the address list corresponding to the subdomain to be deployed.

[0106] In an embodiment of the present application, upon determining that a change has occurred, the computer device may use the subdomain corresponding to the modified parameter information as the subdomain to be deployed, and the address corresponding to the modified parameter information as the address list corresponding to the subdomain to be deployed. This facilitates subsequent deployment of the modified parameter information, subdomain, and address on the deployment device.

[0107] Figure 6 This is a flowchart for modifying a domain name, which includes: S21: determining whether the legitimacy check of the modification parameter information carried in the domain name management instruction is passed, if so, executing step S22, if not, executing step S23; S22: determining whether the modification parameter information, the subdomain name corresponding to the modification parameter information, and the address corresponding to the modification parameter information have changed, if so, executing step S24; S23: outputting an alarm message; S24: updating the domain name in the authoritative domain name database.

[0108] In the above-mentioned domain name management method, the modification parameter information carried in the domain name management instruction is verified for validity. If the verification passes, a determination is made as to whether the modification parameter information, the subdomain corresponding to the modification parameter information, and the address corresponding to the modification parameter information have changed. If so, the subdomain corresponding to the modification parameter information is used as the subdomain to be deployed, and the address corresponding to the modification parameter information is used as the address list corresponding to the subdomain to be deployed. By verifying both the validity and whether the deployment information has changed, this method can more comprehensively verify the modification parameter information entered by the user, thereby accurately determining the subdomain to be deployed and the corresponding address list.

[0109] Taking the domain name management type as fault management as an example, in one embodiment, Figure 7 As shown, the specific contents of determining the subdomains to be deployed and the corresponding address lists according to the domain name management type, multiple subdomains, and the address lists corresponding to each subdomain are introduced, including:

[0110] S401: When the domain name management type is fault management, obtain final coverage information formed by the address lists under all subdomains.

[0111] The final coverage information refers to the collection of subdomain names and all address lists, that is, all IP addresses obtained after resolving the domain name.

[0112] In an embodiment of the present application, when the domain name management type is determined to be fault management, after the computer device receives all subdomains and the address list of each subdomain pulled from the data center, it can use the set of all address lists as the final coverage information formed by the address lists under all subdomains.

[0113] S402: Determine whether the final coverage information is consistent with the coverage information in the local domain name database.

[0114] In this embodiment of the present application, for any address in the final coverage information, the computer device may compare the address with the address in the local domain name database. If the comparison result shows that the two addresses are the same, it is determined that the address has not changed; if the comparison result shows that the two addresses are different, it is determined that the address has changed. If all addresses have not changed, the coverage information is determined to be consistent; if any address has changed, the coverage information is determined to be inconsistent.

[0115] S403: If there is inconsistency, filter the subdomain to be deployed from all subdomains, and filter the address list corresponding to the subdomain to be deployed from the addresses of all subdomains.

[0116] In an embodiment of the present application, when it is determined that the coverage information is inconsistent, the computer device can further verify the inconsistent addresses, and based on the verification results, filter the subdomains to be deployed from all subdomains, and filter the address list corresponding to the subdomains to be deployed from the addresses of all subdomains.

[0117] Alternatively, the computer device may further determine a subdomain with inconsistent addresses from all subdomains, and use the subdomain as the subdomain to be deployed, and use the inconsistent addresses within the subdomain as an address list corresponding to the subdomain to be deployed.

[0118] In the above-mentioned domain name management method, when the domain name management type is fault management, the final coverage information formed by the address list under all subdomains is obtained; a determination is made as to whether the final coverage information is consistent with the coverage information in the local domain name database; if not, the subdomains to be deployed are screened from all subdomains, and the address lists corresponding to the subdomains to be deployed are screened from the addresses of all subdomains. This method verifies the consistency of the final coverage information formed by the address list under all subdomains. If a change is determined, the method can accurately screen the subdomains to be deployed from all subdomains, and screen the address lists corresponding to the subdomains to be deployed from the addresses of all subdomains.

[0119] If it is determined that the final coverage information is inconsistent with the coverage information in the local domain name database, subsequent operation steps need to be performed. The following is a detailed description of the specific content of the subsequent operation steps through an embodiment. Figure 8 As shown, the method further includes:

[0120] S501, searching for a newly added address from the address list under all subdomains.

[0121] In an embodiment of the present application, the computer device can determine whether there is an address not present in the local domain name database based on the inconsistent addresses in the coverage information. If so, the address not present in the local domain name database is treated as a newly added address. For example, if the list of addresses under all subdomains includes A1, A2, and A3, and the addresses in the local domain name database include A2 and A3, then address A1 is the newly added address.

[0122] S502: Determine whether the newly added address can run normally in the authoritative domain name database.

[0123] In an embodiment of the present application, the computer device may judge the newly added address according to the operation rules to determine whether the newly added address can operate normally in the authoritative domain name database. Alternatively, the computer device may simulate the operation of the newly added address in the authoritative domain name database and determine whether the newly added address can operate normally in the authoritative domain name database based on the simulation results.

[0124] S503, if yes, then use the subdomain corresponding to the newly added address as the reference domain name to be deployed, and use the newly added address as the address list corresponding to the reference domain name to be deployed; if no, output a first alarm message; the first alarm message is used to prompt that there is an abnormality in the newly added address.

[0125] In an embodiment of the present application, when it is determined that the newly added address can operate normally in the authoritative domain name database, the computer device can use the subdomain corresponding to the newly added address as a reference domain name to be deployed, and use the newly added address as an address list corresponding to the reference domain name to be deployed. This allows the deployment device to deploy the newly added address and the subdomain corresponding to the newly added address in the authoritative domain name database.

[0126] When it is determined that the newly added address cannot operate normally in the authoritative domain name database, the computer device can output a first warning message through the domain name management interface or voice device, and the first warning message includes that there is an abnormality in the newly added address. In this way, the user can obtain the abnormality information and the cause of the abnormality in a timely manner, and can handle the abnormality in a timely manner.

[0127] In the above-mentioned domain name management method, the newly added address is searched from the address list under all subdomains; a determination is made as to whether the newly added address is operating normally in the authoritative domain name database; if so, the subdomain corresponding to the newly added address is used as a reference domain name to be deployed, and the newly added address is used as an address list corresponding to the reference domain name to be deployed; if not, a first alarm message is output; the first alarm message is used to indicate that there is an abnormality with the newly added address. By verifying the operating status of the newly added address in the authoritative domain name database, this method ensures that only addresses that are operating normally are deployed, avoiding service interruptions caused by invalid addresses.

[0128] In one embodiment, Figure 9 As shown, before determining whether the final coverage information is consistent with the coverage information in the local domain name database, the method further includes:

[0129] S601: Determine whether the final coverage information formed by the address lists under all subdomains is empty.

[0130] In an embodiment of the present application, after obtaining the final coverage information formed by the address list under all subdomains from the data center, the computer device can parse the final coverage information to determine whether the address exists in the final coverage information. If so, the final coverage information is determined to be non-empty; if not, the final coverage information is determined to be empty.

[0131] S602: If yes, output a second warning message; the second warning message is used to prompt that there is an abnormality in the final coverage information.

[0132] In an embodiment of the present application, when it is determined that the final coverage information is empty, the computer device can output a second alarm message to the user through the domain name management page or voice device, and the second alarm message includes that there is an abnormality in the final coverage information.

[0133] S603: If not, then perform the step of searching for the newly added address from the address list under all subdomains.

[0134] In the embodiment of the present application, when it is determined that the final coverage information is not empty, the computer device may execute the content in the above step S501.

[0135] In the above-mentioned domain name management method, a determination is made as to whether the final coverage information formed by the address lists under all subdomains is empty. If so, a second warning message is output; the second warning message indicates an anomaly in the final coverage information. If not, a step is performed to search for newly added addresses from the address lists under all subdomains. This method determines whether the final coverage information of the address lists under all subdomains is empty, and if so, promptly outputs a warning message. In other words, by determining the final coverage information, risks of service unavailability due to configuration errors can be detected in advance, thereby improving the accuracy of domain name management.

[0136] Figure 10 This is a flow chart of fault management, which includes: S31: traversing the final coverage information formed by the address lists under all subdomains; S32: judging whether the final coverage information formed by the address lists under all subdomains is empty, if so, executing step S38, if not, executing step S33; S33: judging whether the final coverage information is consistent with the coverage information in the local domain name database, if so, executing step S34; S34: judging whether there is a new address, if so, executing step S35, if not, executing step S37; S35: judging whether the new address can operate normally in the authoritative domain name database, if so, executing step S36, if not, executing step S38; S36: judging whether it is associated with the main domain name, if so, executing step S37, if not, ending; S37: deploying the latest subdomain and address list in the authoritative domain name database; S38: outputting alarm information.

[0137] The above embodiments are all related introductions to the domain name management process. After the domain name management is completed, the deployment of the authoritative domain name database can also be verified. Next, an embodiment is used to describe the above verification process in detail. Figure 11 As shown, the method further includes:

[0138] S701: Send address requests corresponding to the test domain name to the deployment device multiple times.

[0139] In this embodiment of the present application, a user can enter a test domain name on an interface provided by a computer device. After receiving the test domain name, the computer device generates an address request corresponding to the test domain name and sends the address request to the deployment device. It should be noted that multiple test domain names can be the same domain name or different domain names, or the test domain name can represent all domain names in the authoritative domain name database.

[0140] S702: Compare the test address corresponding to each received test domain name with the address in the local domain name database.

[0141] In this embodiment of the present application, after receiving an address request, the deployment device searches the authoritative domain name database for a test address corresponding to the address request and feeds the test address back to the computer device. The computer device then receives the test address corresponding to each test domain name. For each received test address, the computer device compares the test address with the address in the local domain name database to determine whether the two addresses are identical.

[0142] S703: If the comparison results are different for multiple times, it is determined that the deployment process in the authoritative domain name database has failed.

[0143] In an embodiment of the present application, when it is determined that the results of multiple comparisons are different, it indicates that there is an abnormality in the deployment process of the deployment device in the authoritative domain name database, and the subdomain to be deployed and the corresponding address list are not successfully deployed to the authoritative domain name database. It can be determined that the deployment process in the authoritative domain name database has failed.

[0144] In the above-mentioned domain name management method, multiple address requests corresponding to a test domain name are sent to the deployment device; the test address corresponding to each received test domain name is compared with the address in the local domain name database; if the multiple comparison results are different, it is determined that the deployment process in the authoritative domain name database has failed. This method sends multiple address requests to the deployment device, comparing each received test address with the address synchronized in real time in the local database. Through multiple comparison results, it can accurately determine whether the deployment process in the authoritative domain name database has failed, thus avoiding misjudgments caused by a single result.

[0145] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0146] Based on the same inventive concept, embodiments of the present application also provide a domain name management device for implementing the aforementioned domain name management method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of one or more domain name management device embodiments provided below can be found in the aforementioned limitations of the domain name management method and will not be further elaborated here.

[0147] In an exemplary embodiment, Figure 12 As shown, a domain name management device is provided, including: a pulling module 11, an acquisition module 12, a determination module 13 and a processing module 14, wherein:

[0148] A pulling module 11 is used to pull multiple subdomains and an address list corresponding to each subdomain from a data center;

[0149] An acquisition module 12 is configured to acquire a domain name management type corresponding to the domain name management instruction in response to the triggered domain name management instruction;

[0150] A determination module 13 is configured to determine a subdomain to be deployed and a corresponding address list according to a domain name management type, multiple subdomains, and an address list corresponding to each subdomain;

[0151] The processing module 14 is configured to send a deployment instruction generated based on the to-be-deployed subdomain name and the corresponding address list to the deployment device, and to update the local domain name database; the deployment instruction is used to instruct the deployment device to deploy in the authoritative domain name database.

[0152] In an exemplary embodiment, the acquisition module includes: a first determination unit and a second determination unit, wherein:

[0153] a first determining unit, configured to, when the domain name management instruction is a domain name update instruction triggered by a user, determine that the domain name management type corresponding to the domain name management instruction is update management;

[0154] The second determining unit is configured to determine that the domain name management type corresponding to the domain name management instruction is fault management when the domain name management instruction is an instruction triggered by reaching a preset condition.

[0155] In an exemplary embodiment, the determination module includes: a first verification unit, a second verification unit, and a third determination unit, wherein:

[0156] A first verification unit is configured to verify the legitimacy of a target subdomain selected from a plurality of subdomains and corresponding parameter information carried in the domain name management instruction;

[0157] The second verification unit is configured to perform a duplication check on the main domain name composed of the target subdomain names carried in the domain name management instruction when the legality verification passes;

[0158] The third determining unit is configured to, if no duplication exists, use the target subdomain as the subdomain to be deployed, and use the address list of the target subdomain as the address list corresponding to the reference domain to be deployed.

[0159] In an exemplary embodiment, the determination module further includes: a third verification unit, a first judgment unit, and a fourth determination unit, wherein:

[0160] A third verification unit is used to verify the legitimacy of the modification parameter information carried in the domain name management instruction;

[0161] The first judgment unit is used to judge whether the modified parameter information, the subdomain name corresponding to the modified parameter information, and the address corresponding to the modified parameter information have changed when the legality check passes;

[0162] The fourth determining unit is configured to, in the event of a change, use the subdomain corresponding to the modified parameter information as the subdomain to be deployed, and use the address corresponding to the modified parameter information as an address list corresponding to the subdomain to be deployed.

[0163] In an exemplary embodiment, the determination module further includes: an acquisition unit, a second judgment unit, and a fifth determination unit, wherein:

[0164] an acquisition unit, configured to acquire final coverage information formed by address lists under all subdomains when the domain name management type is fault management;

[0165] A second judgment unit is used to judge whether the final coverage information is consistent with the coverage information in the local domain name database;

[0166] The fifth determining unit is configured to, in the event of inconsistency, filter the subdomain to be deployed from all subdomains, and filter the address list corresponding to the subdomain to be deployed from the addresses of all subdomains.

[0167] In an exemplary embodiment, the determination module further includes: a search unit, a third judgment unit, and a sixth determination unit, wherein:

[0168] A search unit is used to search for a newly added address from the address list under all subdomains;

[0169] The third judgment unit is used to judge whether the newly added address can operate normally in the authoritative domain name database;

[0170] The sixth determination unit is used to use the subdomain name corresponding to the newly added address as the reference domain name to be deployed, and the address list corresponding to the newly added address as the reference domain name to be deployed if it can operate normally; if not, output the first alarm information; the first alarm information is used to prompt that there is an abnormality in the newly added address.

[0171] In an exemplary embodiment, the determination module further includes: a fourth judgment unit, a seventh determination unit, and an eighth determination unit, wherein:

[0172] A fourth judgment unit is used to judge whether the final coverage information formed by the address lists under all subdomains is empty;

[0173] The seventh determining unit is configured to output a second warning message when the final coverage information is empty; the second warning message is used to prompt that there is an abnormality in the final coverage information;

[0174] The eighth determining unit is configured to, when the final coverage information is not empty, execute the step of searching for a newly added address from the address lists under all subdomains.

[0175] In an exemplary embodiment, the domain name management device further includes: a sending module, a receiving module, and a deployment determination module, wherein:

[0176] A sending module is used to send address requests corresponding to the test domain name to the deployment device multiple times;

[0177] The receiving module is used to compare the test address corresponding to each received test domain name with the address in the local domain name database;

[0178] The deployment determination module is used to determine that the deployment process in the authoritative domain name database has failed if the comparison results are different for multiple times.

[0179] Each module in the aforementioned domain name management device may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0180] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 13 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store domain name management data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a domain name management method is implemented.

[0181] Those skilled in the art will understand that Figure 13 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0182] In an exemplary embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor implements the content of any one embodiment of the above-mentioned domain name management method when executing the computer program.

[0183] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the content of any embodiment of the above-mentioned domain name management method is implemented.

[0184] In one embodiment, a computer program product is provided, including a computer program, which implements the content of any one embodiment of the above-mentioned domain name management method when executed by a processor.

[0185] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0186] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. In particular, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of a non-volatile memory and a volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), quantum computing-based data processing logic devices, artificial intelligence (AI) processors, and the like.

[0187] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0188] The above embodiments merely illustrate several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art may make various modifications and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A domain name management method, characterized in that: The method comprises: Pull multiple subdomains and a list of addresses corresponding to each subdomain from the data center; In response to the triggered domain name management instruction, obtaining a domain name management type corresponding to the domain name management instruction; Determine the subdomain to be deployed and the corresponding address list according to the domain name management type, the multiple subdomains and the address list corresponding to each subdomain; Sending a deployment instruction generated based on the to-be-deployed subdomain name and the corresponding address list to the deployment device, and updating the local domain name database; the deployment instruction is used to instruct the deployment device to deploy in the authoritative domain name database.

2. The method according to claim 1, characterized in that The obtaining of the domain name management type corresponding to the domain name management instruction includes: In a case where the domain name management instruction is a domain name update instruction triggered by a user, determining that the domain name management type corresponding to the domain name management instruction is update management; In a case where the domain name management instruction is an instruction triggered by reaching a preset condition, it is determined that the domain name management type corresponding to the domain name management instruction is fault management.

3. The method according to claim 2, characterized in that The update management includes adding a new primary domain name; The determining, according to the domain name management type, the multiple subdomains, and the address list corresponding to each subdomain, the subdomain to be deployed and the corresponding address list includes: Performing a validity check on the target subdomain selected from the multiple subdomains and corresponding parameter information carried in the domain name management instruction; If the validity check passes, performing a duplication check on the main domain name composed of each target subdomain name carried in the domain name management instruction; If there is no duplication, the target subdomain is used as the subdomain to be deployed, and the address list of the target subdomain is used as the address list corresponding to the reference domain to be deployed.

4. The method according to claim 2, characterized in that The update management includes modifying the domain name; The determining, according to the domain name management type, the multiple subdomains, and the address list corresponding to each subdomain, the subdomain to be deployed and the corresponding address list includes: Performing a validity check on the modification parameter information carried in the domain name management instruction; If the validity check passes, determine whether the modified parameter information, the subdomain name corresponding to the modified parameter information, and the address corresponding to the modified parameter information have changed; If a change occurs, the subdomain corresponding to the modified parameter information is used as the subdomain to be deployed, and the address corresponding to the modified parameter information is used as the address list corresponding to the subdomain to be deployed.

5. The method according to claim 2, characterized in that The determining, according to the domain name management type, the multiple subdomains, and the address list corresponding to each subdomain, the subdomain to be deployed and the corresponding address list includes: When the domain name management type is fault management, obtaining final coverage information formed by the address list under all subdomains; Determining whether the final coverage information is consistent with the coverage information in the local domain name database; If they are inconsistent, the subdomain to be deployed is filtered from all the subdomains, and an address list corresponding to the subdomain to be deployed is filtered from the addresses of all the subdomains.

6. The method according to claim 5, characterized in that The method further comprises: Search for the newly added address from the address list under all the subdomains; Determine whether the newly added address can operate normally in the authoritative domain name database; If so, the subdomain corresponding to the newly added address is used as the reference domain name to be deployed, and the newly added address is used as the address list corresponding to the reference domain name to be deployed; if not, the first alarm information is output; the first alarm information is used to prompt that there is an abnormality in the newly added address.

7. The method according to claim 6, characterized in that Before determining whether the final coverage information is consistent with the coverage information in the local domain name database, the method further includes: Determine whether the final coverage information formed by the address lists under all subdomains is empty; If yes, output a second warning message; the second warning message is used to prompt that there is an abnormality in the final coverage information; If not, the step of searching for a new address from the address list under all subdomains is performed.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: Sending address requests corresponding to the test domain name to the deployment device multiple times; Comparing the test address corresponding to each received test domain name with the address in the local domain name database; If the comparison results are different for multiple times, it is determined that the deployment process in the authoritative domain name database has failed.

9. A domain name management device, characterized in that: The device comprises: The pull module is used to pull multiple subdomains and the address list corresponding to each subdomain from the data center; An acquisition module, configured to, in response to a triggered domain name management instruction, acquire a domain name management type corresponding to the domain name management instruction; a determination module, configured to determine a subdomain to be deployed and a corresponding address list according to the domain name management type, the multiple subdomains, and the address list corresponding to each subdomain; The processing module is used to send a deployment instruction generated based on the subdomain to be deployed and the corresponding address list to the deployment device, and to update the local domain name database; the deployment instruction is used to instruct the deployment device to deploy in the authoritative domain name database.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

Images