Dns domain name processing method, device, system, equipment and medium

Abstract

The application provides a DNS domain name processing method, device, system, equipment and medium, wherein the method comprises: in response to a DNS domain name processing request, displaying a domain name update window on a visual interface of a front end, the domain name update window being used for configuring domain name information; in response to an operation result of the domain name update window, obtaining a target domain name, a target domain name resolution address and a target domain name resolution server; generating domain name update information based on the target domain name, the target domain name resolution address and the target domain name resolution server, and generating an update code file based on the domain name update information; and transmitting the update code file to a back end, so that the back end updates a DNS domain name based on the update code file after backing up a current domain name zone file. Through the above method, automatic domain name update processing can be realized, the domain name update efficiency is effectively improved, and the domain name update error rate is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a DNS domain name processing method, device, system, equipment and medium. BACKGROUND

[0002] In the construction of a PaaS cloud platform of a banking institution, all cloud applications are required to be reformed by domain names, and the traditional ip+port access mode is modified to a domain name access mode. This involves allocating a corresponding domain name to each application system.

[0003] At present, the PaaS cloud platform usually provides a domain name service for cloud applications in a banking institution, and allocates domain names for application systems. Therefore, the PaaS cloud platform management team will face a relatively complex PaaS domain name management task. In the domain name management process, an administrator usually needs to log in to the domain name management system background environment first, and then modify the zone file of the corresponding subdomain. When modifying the zone file, in addition to adding the corresponding relationship between the domain name and the IP address, it is usually necessary to adjust the serial value of the current zone file and restart the domain name resolution server. In the PaaS cloud platform environment, multiple domain name resolution servers are deployed, so the above steps need to be repeated multiple times.

[0004] As can be seen, the current domain name management work is very complex, and too many manual interventions will lead to the easy occurrence of domain name configuration errors or non-effective configurations. SUMMARY

[0005] The present application provides a DNS domain name processing method, device, system, equipment and medium to at least solve one of the above problems.

[0006] According to an aspect of the present application, a DNS domain name processing method is provided, comprising:

[0007] In response to a DNS domain name processing request, a domain name update window is displayed on a visual interface at the front end, and the domain name update window is used to configure domain name information;

[0008] In response to the operation result of the domain name update window, a target domain name, a target domain name resolution address and a target domain name resolution server are obtained;

[0009] Based on the target domain name, the target domain name resolution address and the target domain name resolution server, domain name update information is generated, and an update code file is generated based on the domain name update information;

[0010] The update code file is transmitted to the back end, so that the back end backs up the current domain name zone file, and then updates the DNS domain name based on the update code file.

[0011] In one implementation, the domain name update window includes a relative domain name input field, a domain name resolution address input field, a subdomain selection field, and a domain name resolution server selection field.

[0012] The operation result in response to the domain name update window, obtaining the target domain name, the target domain name resolution address, and the target domain name resolution server, includes:

[0013] In response to the first input information in the relative domain name input field and the first selection information in the subdomain selection field, the target domain name is obtained based on the first input information and the first selection information.

[0014] In response to the second input information in the domain name resolution address input field, the target domain name resolution address is obtained;

[0015] In response to the second selection information of the domain name resolution server selection option, the target domain name resolution server is obtained.

[0016] In one implementation, obtaining the target domain name based on the first input information and the first selection information includes:

[0017] In response to the verification result that the first input information conforms to the first preset rule, the target domain name is obtained based on the first input information and the first selection information, wherein the first preset rule includes that the character length of the first input information is within a preset range.

[0018] In one implementation, obtaining the target domain name based on the first input information and the first selection information includes:

[0019] In response to the verification result that the first input information does not conform to the first preset rule, a prompt message for re-entering the relative domain name is issued in the domain name update window.

[0020] In one implementation, obtaining the target domain name resolution address includes: in response to the verification result that the second input information conforms to a second preset rule, obtaining the target domain name resolution address, wherein the second preset rule includes the second input information carrying an address information, and / or the second input information being an IPv4 address.

[0021] In one implementation, the domain name update window further includes a record type selection option, and / or a Time-to-Live (TTL) value input field or a TTL selection option.

[0022] In response to the third selection information in the record type selection options, obtain the target parsing type; and / or,

[0023] In response to the third input information of the TTL input item or the fourth selection information of the TTL selection item, the target parsing lifetime is obtained;

[0024] The step of generating domain name update information based on the target domain name, the target domain name resolution address, and the target domain name resolution server includes: generating domain name update information based on the target domain name, the target domain name resolution address, the target domain name resolution server, the target resolution type, and / or the target resolution time-to-live.

[0025] According to another aspect of this application, a DNS domain name processing apparatus is provided, comprising:

[0026] The display module is configured to display a domain name update window on the front-end visual interface in response to DNS domain name processing requests. The domain name update window is used to configure domain name information.

[0027] The acquisition module is configured to acquire the target domain name, the target domain name resolution address, and the target domain name resolution server in response to the operation result of the domain name update window.

[0028] The generation module is configured to generate domain name update information based on the target domain name, the target domain name resolution address, and the target domain name resolution server, and to generate an update code file based on the domain name update information;

[0029] The backup and update module is configured to transmit the update code file to the backend, so that the backend can update the DNS domain name based on the update code file after backing up the current domain name zone file.

[0030] According to another aspect of this application, a DNS domain name processing system is provided, comprising:

[0031] The front end is used to display a domain name update window on a visual interface. The domain name update window is used to configure domain name information. In response to the operation result of the domain name update window, the front end obtains the target domain name, the target domain name resolution address and the target domain name resolution server, and generates domain name update information based on the target domain name, the target domain name resolution address and the target domain name resolution server, and generates an update code file based on the domain name update information.

[0032] The backend is used to receive the domain name update code file sent by the frontend, and after backing up the current domain name zone file, update the DNS domain name based on the update code file.

[0033] According to another aspect of this application, an electronic device is provided, comprising: a processor and a memory;

[0034] The memory stores computer-executed instructions;

[0035] The processor executes computer execution instructions stored in the memory, causing the electronic device to perform the DNS domain name processing method.

[0036] According to another aspect of this application, a computer-readable storage medium is provided, wherein computer-executable instructions are stored therein, which, when executed by a processor, are used to implement the DNS domain name processing method described above.

[0037] As is understood, the DNS domain name processing method, apparatus, system, device, and medium provided in this application, in response to a DNS domain name processing request, display a domain name update window on a front-end visual interface. This domain name update window is used to configure domain name information. In response to the operation result of the domain name update window, the target domain name, the target domain name resolution address, and the target domain name resolution server are obtained. Domain name update information is generated based on the target domain name, the target domain name resolution address, and the target domain name resolution server, and an update code file is generated based on the domain name update information. The update code file is transmitted to the back-end so that the back-end backs up the current domain name zone file and then updates the DNS domain name based on the update code file. Through the above method, automated domain name update processing can be achieved, effectively improving domain name update efficiency and reducing the domain name update error rate. Attached Figure Description

[0038] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0039] Figure 1 This is a schematic diagram of a possible scenario provided for an embodiment of this application;

[0040] Figure 2 A flowchart illustrating a DNS domain name processing method provided in an embodiment of this application;

[0041] Figure 3 This is an example diagram of the relative domain name input field in the embodiments of this application;

[0042] Figure 4 This is an example diagram of the subdomain selection option in an embodiment of this application;

[0043] Figure 5 This is an example diagram of the domain name resolution server selection option in the embodiments of this application;

[0044] Figure 6 This is an example diagram of the record type selection options in the embodiments of this application;

[0045] Figure 7This is a schematic diagram of the structure of a DNS domain name processing device provided in an embodiment of this application;

[0046] Figure 8 This is a schematic diagram of the structure of a DNS domain name processing system provided in an embodiment of this application;

[0047] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0048] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0049] To facilitate understanding of the embodiments of this application, the following terms will be explained before a detailed description of the embodiments:

[0050] Domain Name: A name of a computer or group of computers on the Internet, consisting of a string of names separated by dots, used to locate the computer during data transmission.

[0051] Domain Name Server (DNS) is a server or group of servers on the internet that provides domain name resolution services and is usually open to the entire network.

[0052] Relative domain: A domain name that does not end with a dot. The actual domain name is composed of the relative domain name and the source domain specified in $ORIGIN.

[0053] Absolute domain name: A domain name ending with a dot "." is a complete domain name.

[0054] TTL (Time To Live): The lifespan of a domain name. When the time limit for a domain name stored locally by the resolver and in the cache server exceeds the TTL, the resolver will request domain name resolution from the domain name resolution server again.

[0055] Bind: A commonly used domain name resolution server software.

[0056] Subdomain: The next level below the top-level domain, which can contain multiple subdomains.

[0057] zonefile: The file that stores the mapping between domain names and IP addresses, also known as the zone file.

[0058] Serial number: A unique identifier within the zonefile, which cannot be duplicated. It is often a combination of time and number of modifications.

[0059] Python: A programming language designed by Guido van Rossum of the Netherlands Research Institute of Mathematics and Computer Science.

[0060] Django: An open-source web application framework powered by the Python programming language.

[0061] layUI: An open-source web UI solution that adopts its own classic modular specifications and follows native HTML / CSS / JS development methods.

[0062] The pythondns package: A Python wrapper for DNS tools that enables various operations on the DNS system, including zone transfer, domain name updates, domain name deletion, and remote control of domain name resolution servers.

[0063] The relevant terms used in the embodiments of this application have been briefly explained above. The embodiments of this application are described below in conjunction with the detailed technical background.

[0064] In related technologies, automated domain name update tools have been introduced to improve domain name management efficiency. For example, for domain name resolution servers built using Bind, Bind provides a set of background `nsupdate` commands, which can be used to perform domain name updates in the background. Using the `nsupdate` command first requires installing the `bind-utils` package on a Linux server. This package contains several `bind` tools. Executing the `nsupdate` command requires logging into a Linux server backend and knowing the domain name resolution server address. The tool uses commands to add a domain name, specifying the resolution type and TTL, and finally uses the `send` command to send the domain name update information to the domain name resolution server. Currently, the `nsupdate` command execution tool supports specifying a domain name resolution server, adding domain names, and deleting domain names. After adding a domain name, the result of the added domain name resolution can be viewed using the `nslookup` command, and the domain name can be deleted by calling the `nsupdate` command after use.

[0065] However, the nsupdate tool requires users to log in to the server backend with high privileges (root), which is not conducive to access control. Furthermore, this command must be installed on a fixed server, and using command-line tools to modify domain names still requires a significant amount of manual input, including manually specifying the DNS server. If the DNS server is specified incorrectly, subsequent command executions will not report errors, increasing the difficulty of troubleshooting DNS configuration failures. Moreover, this command line can only update domain names; it cannot back up the existing DNS records on the DNS server. If a domain name is accidentally deleted during the command, it will result in an unrecoverable DNS record. Therefore, directly using the nsupdate command for backend domain name updates is not a good choice, as it consumes additional server resources and requires higher privileges. It also demands a high level of skill and accuracy from the operator.

[0066] In view of this, this application provides a DNS domain name processing method, apparatus, system, device, and medium to address the aforementioned technical problems, achieving visualized domain name management. By displaying a domain name update window in a front-end visual interface, this window is used to configure domain name information, such as relative domain name, DNS record type, subdomain, DNS address, and DNS server. This effectively avoids directly logging into the server to execute complex domain name update commands. Furthermore, information such as the DNS server, subdomain, DNS record type, and TTL are fixed at the front end, effectively reducing potential human input errors during domain name updates. After configuring the domain name update information at the front end, the zone file of the subdomain to be updated is backed up at the back end. The domain name update is then completed based on the updated information, allowing for recovery using the backup file in case of a DNS resolution system failure. The entire process does not consume significant server or permission resources and effectively reduces the risk of domain name failures due to human error.

[0067] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below with reference to the accompanying drawings. In the drawings, the same or similar reference numerals denote the same or similar components or components having the same or similar functions throughout. The described embodiments are some, but not all, embodiments of this application. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0068] Please refer to Figure 1 , Figure 1This illustration shows a possible scenario for an embodiment of the present application, including a terminal device 110 and a server 120, which are interconnected via a wired or wireless network. Optionally, the terminal device 110 runs a front-end that receives DNS domain name processing requests, displays a domain name update window, generates domain name update information based on the operation results of the domain name update window, and transmits it to the server 120. The server 120 runs a back-end that backs up the domain name file and completes the DNS domain name update based on the data provided by the terminal front-end. Optionally, during the DNS domain name update process, the server 120 undertakes the main computational work, and the terminal device 110 undertakes the secondary computational work; or, the server 120 undertakes the secondary computational work, and the terminal device 110 undertakes the main computational work; or, the server 120 or the terminal device 110 can each independently undertake the computational work.

[0069] Optionally, the front-end and back-end in this embodiment can be protected in a virtual machine. The virtual machine operating system can be CentOS Linux release 7.6.1810 (Core). The programming language of the front-end can be LayUI version 1.1.0, and the programming language of the back-end can be Python version 3.6.13.

[0070] Among them, the terminal device 110 may include, but is not limited to, computers, smartphones, tablets, e-book readers, Moving Picture Experts Group Audio Layer III (MP3) players, Moving Picture Experts Group Audio Layer IV (MP4) players, portable computers, in-vehicle computers, wearable devices, desktop computers, set-top boxes, smart TVs, etc.

[0071] Server 120 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0072] Optionally, the number of terminals 110 or servers 120 may be more or less, and this application embodiment does not limit this. In some embodiments, the terminals 110 and servers 120 may also act as nodes in a blockchain system, synchronizing domain name update data with other nodes in the blockchain to achieve widespread application of domain name update data.

[0073] 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, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0074] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating a DNS domain name processing method provided in an embodiment of this application. This embodiment is applied to... Figure 1 Taking terminal device 110 as an example, this application will explain in detail the DNS domain name processing method provided in the embodiments.

[0075] Step S201: In response to the DNS domain name processing request, a domain name update window is displayed on the front-end visual interface. The domain name update window is used to configure domain name information.

[0076] In this embodiment, during the processes of adding and deleting domain names, a combination of front-end and back-end methods is used to automate domain name updates, effectively improving update efficiency and reducing error rates. Specifically, the front-end visual interface displays a domain name update window, which may include relative domain name input (i.e., the domain name input box in the figure), domain name resolution address input (i.e., the resolution address input box in the figure), subdomain selection (i.e., the subdomain selection box in the figure), domain name resolution server selection (i.e., the domain name server box in the figure), and other input or selection items (such as the record type selection box in the figure). The system or operators can configure domain name information through the visual interface.

[0077] Understandably, in response to, is used to indicate the conditions or states on which the operation being performed depends. When the conditions or states on which it depends are met, one or more operations being performed can be performed in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations being performed are executed.

[0078] Step S202: In response to the operation result of the domain name update window, obtain the target domain name, the target domain name resolution address, and the target domain name resolution server.

[0079] In this embodiment, the operation result can be either a system operation result or a user operation result. This embodiment takes the user operation result as an example. In some embodiments, the system operation result may be to obtain relevant data information through communication and perform corresponding operations to obtain information such as the target domain name, the target domain name resolution address, and the target domain name resolution server. This embodiment, by configuring domain name information on the front end, replaces the frequent information operations on the server in related technologies, which can effectively reduce the error rate and improve the domain name processing efficiency.

[0080] In one implementation, to further reduce the domain name information error rate, this embodiment fixes the selection of subdomains and domain name resolution servers in the domain name update window. Specifically, the domain name update window includes a relative domain name input field, a domain name resolution address input field, a subdomain selection field, and a domain name resolution server selection field. Step S202, in response to the operation result of the domain name update window, obtains the target domain name, the target domain name resolution address, and the target domain name resolution server, and may include the following steps:

[0081] In response to the first input information in the relative domain name input field and the first selection information in the subdomain selection field, the target domain name is obtained based on the first input information and the first selection information.

[0082] In response to the second input information in the domain name resolution address input field, the target domain name resolution address is obtained;

[0083] In response to the second selection information of the domain name resolution server selection option, the target domain name resolution server is obtained.

[0084] Specifically, the relative domain name input field can be a text input box, such as... Figure 3 As shown, users can enter a relative domain name in the text input box. This relative input field can also include the default content "loadbalancer". In some embodiments, to further reduce the error rate of domain name information, a domain name verification step is added to the relative input field, that is, the first input information is verified, and if the verification fails, the user is prompted to re-enter.

[0085] Specifically, the subdomain selection option can be a drop-down selection box, such as... Figure 4 As shown, users can select from the dropdown menu a list of subdomains already authorized to the DNS server, such as "paas.test.abc", "oc.paas.test.abc", and "openshift4.paas.test.abc" in the image. It's understandable that this subdomain list can be stored and maintained in the backend code, where the default subdomain can be set to "paas.test.abc".

[0086] As is understandable, in this embodiment, the domain name is a combination of the relative domain name entered in the input field and the subdomain selected in the subdomain selection field to form a complete domain name.

[0087] Specifically, in this embodiment, the domain name resolution address input field can be a text input box, such as... Figure 5 As shown, users can enter the domain name resolution address in this input box. Optionally, to further reduce the error rate, the input box can be further improved, for example, only IPv4 addresses can be entered, and only one address can be entered, with the default content being "127.0.0.1", and the text box cannot be empty.

[0088] Specifically, in this embodiment, the domain name resolution server selection option can be a drop-down selection box, which can contain only first-level authoritative domain name resolution servers, and the number of such servers can be one or more. Because the domain name resolution server information is fixed, errors caused by frequent input of domain name resolution server information (such as character errors) in related technologies are effectively avoided.

[0089] Furthermore, considering the possibility of input errors in relative domain names, this embodiment adds a domain name verification step to reduce the error rate. Specifically, obtaining the target domain name based on the first input information and the first selection information may include the following steps:

[0090] In response to the verification result that the first input information conforms to the first preset rule, the target domain name is obtained based on the first input information and the first selection information, wherein the first preset rule includes that the character length of the first input information is within a preset range.

[0091] In response to the verification result that the first input information does not conform to the first preset rule, a prompt message for re-entering the relative domain name is issued in the domain name update window.

[0092] It should be noted that those skilled in the art can adapt the preset range by combining existing technology or practical applications, for example, within 65 characters. Furthermore, in addition to verifying the character length of the first input information, the first preset rule in this embodiment may also include other verification rules. Those skilled in the art can adapt the first preset rule by combining it with practical applications. For example, it may also restrict the character content, verify whether illegal characters appear in the first input information, and so on. This embodiment will not elaborate further on these aspects.

[0093] Furthermore, considering the possibility of input errors in the domain name resolution address, this embodiment adds an address verification step to reduce the error rate. Specifically, obtaining the target domain name resolution address includes: in response to the verification result that the second input information conforms to the second preset rule, obtaining the target domain name resolution address, wherein the second preset rule includes the second input information carrying an address information, and / or the second input information being an IPv4 address.

[0094] It should be noted that the first and second preset rules in this embodiment are only used to distinguish similar objects and have no other substantial meaning; they can be the same content or different content. Furthermore, in addition to verifying the number of addresses and / or address information carried by the second input information, the second preset rule in this embodiment may also include other verification rules. Those skilled in the art can adapt the first preset rule to suit actual applications, and this embodiment will not elaborate further.

[0095] Understandably, IPv4 (Internet Protocol version 4), also known as the fourth version of the Internet Protocol, is the fourth revision in the development process of the Internet Protocol and the first version of the protocol to be widely deployed.

[0096] Furthermore, the domain name update window in this embodiment also adds a record type selection option and a TTL input field to improve the domain name processing efficiency. The domain name update window also includes a record type selection option and / or a Time-to-Live (TTL) value input field or a TTL selection option.

[0097] In response to the third selection information in the record type selection options, obtain the target parsing type; and / or,

[0098] In response to the third input information of the TTL input item or the fourth selection information of the TTL selection item, the target parsing lifetime is obtained;

[0099] The step of generating domain name update information based on the target domain name, the target domain name resolution address, and the target domain name resolution server includes: generating domain name update information based on the target domain name, the target domain name resolution address, the target domain name resolution server, the target resolution type, and / or the target resolution time-to-live.

[0100] In one implementation, the record type selection option can be a drop-down selection box, such as... Figure 6 As shown, you can select "A" (IPv4 address resolution record), "MX" (email address resolution record), and "PRT" (reverse lookup record).

[0101] In this embodiment, the domain name update window has five parameter input boxes: domain name input, record type selection, DNS address input, subdomain selection, and domain name server selection. The update function key can be set to "domain update," and the front end generates domain name update information when it receives a trigger signal for this function key.

[0102] Step S203: Generate domain name update information based on the target domain name, the target domain name resolution address, and the target domain name resolution server, and generate update code file based on the domain name update information.

[0103] In this embodiment, after obtaining information such as the target domain name, target domain name resolution address, and target domain name resolution server based on the domain name update window, corresponding domain name update information is generated, and then corresponding update code files are generated. In one implementation, the front-end can design its code based on Django's template model, storing common functions and common display content in the base.html file. When other HTML files are loaded, they first include base.html into the current page and generate the update code file domain_add.html. Then, the front-end can use the GET method to access the interface provided by the back-end service and pass the update code file generated based on the domain name update information to the back-end service.

[0104] In some embodiments, after generating the domain name update information, the front end can return the domain name update result in a visual interface. For example, if the update is successful, it will return "result 0", and if the update fails, it will return a 500 error.

[0105] Step S204: The update code file is transmitted to the backend so that the backend can back up the current domain name zone file and update the DNS domain name based on the update code file.

[0106] In this embodiment, the backend receives the update code file from the frontend. Based on the corresponding parameters in the update code file, it first backs up the zone file of the subdomain to be updated. After completing the backup operation, it begins to update the domain name according to the domain name update information. In one implementation, the backend can be written in Python, such as the dnspython package, with the sys and time packages used for input and output. It can also generate update_domain.py code, which is executed to complete the domain name update.

[0107] In some embodiments, when the backend updates the domain name, the zone file can be edited directly, and after editing, the zone file can be reloaded or the bind process can be restarted.

[0108] In some embodiments, the backend can return the corresponding resolution result to the frontend after updating the new domain name into the domain name resolution server, so that any abnormalities can be handled in a timely manner.

[0109] This embodiment also provides a DNS domain name processing device, such as... Figure 7 As shown, it includes:

[0110] Display module 71 is configured to display a domain name update window on a front-end visual interface in response to a DNS domain name processing request. The domain name update window is used to configure domain name information.

[0111] The acquisition module 72 is configured to acquire the target domain name, the target domain name resolution address, and the target domain name resolution server in response to the operation result of the domain name update window.

[0112] The generation module 73 is configured to generate domain name update information based on the target domain name, the target domain name resolution address, and the target domain name resolution server, and to generate an update code file based on the domain name update information;

[0113] The backup update module 74 is configured to transmit the update code file to the backend, so that the backend can update the DNS domain name based on the update code file after backing up the current domain name zone file.

[0114] In one implementation, the domain name update window includes a relative domain name input field, a domain name resolution address input field, a subdomain selection field, and a domain name resolution server selection field.

[0115] The acquisition module 71 includes:

[0116] The first acquisition unit is configured to acquire the target domain name based on the first input information and the first selection information in response to the first input information in the relative domain name input item and the first selection information in the subdomain selection item.

[0117] The second acquisition unit is configured to acquire the target domain name resolution address in response to the second input information in the domain name resolution address input field.

[0118] The third acquisition unit is configured to acquire the target domain name resolution server in response to the second selection information of the domain name resolution server selection item.

[0119] In one embodiment, the first acquisition unit is specifically configured to acquire a target domain name based on the first input information and the first selection information in response to the verification result that the first input information conforms to a first preset rule, wherein the first preset rule includes the character length of the first input information being within a preset range.

[0120] In one implementation, the first acquisition unit is specifically configured to issue a re-entry prompt message for the relative domain name in the domain name update window in response to the verification result that the first input information does not conform to the first preset rule.

[0121] In one embodiment, the second acquisition unit is specifically configured to acquire the target domain name resolution address in response to the verification result that the second input information conforms to the second preset rule, wherein the second preset rule includes the second input information carrying an address information, and / or the second input information being an IPv4 address.

[0122] In one embodiment, the domain name update window further includes a record type selection option, and / or a Time-to-Live (TTL) value input field or a TTL selection option, and the device further includes:

[0123] The fourth acquisition unit is configured to acquire the target parsing type in response to the third selection information in the selection of the record type; and / or,

[0124] The fifth acquisition unit is configured to acquire the target parsing lifetime in response to the third input information of the TTL input item or the fourth selection information of the TTL selection item;

[0125] The generation module 73 is specifically configured to generate domain name update information based on the target domain name, the target domain name resolution address, the target domain name resolution server, the target resolution type, and / or the target resolution time-to-live.

[0126] It should be noted that the device provided in this application can implement all the method steps implemented by the terminal device in the above method embodiment and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0127] This application also provides a DNS domain name processing system, such as... Figure 8 As shown, it includes:

[0128] Frontend 81, the frontend is used to display a domain name update window in a visual interface, the domain name update window is used to configure domain name information, in response to the operation result of the domain name update window, to obtain the target domain name, the target domain name resolution address and the target domain name resolution server, and to generate domain name update information based on the target domain name, the target domain name resolution address and the target domain name resolution server, and to generate an update code file based on the domain name update information;

[0129] Backend 82 is used to receive the domain name update code file sent by the frontend, and update the DNS domain name based on the update code file after backing up the current domain name zone file.

[0130] It should be noted that the system provided in this application can implement all the method steps implemented by the terminal device in the above method embodiments and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0131] This application also provides an electronic device, such as... Figure 9 As shown, it includes: processor 91 and memory 92;

[0132] The memory 91 stores computer-executed instructions;

[0133] The processor 92 executes the computer execution instructions stored in the memory 91, causing the electronic device to perform the DNS domain name processing method.

[0134] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the DNS domain name processing method.

[0135] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to execute the DNS domain name processing method.

[0136] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory to execute the DNS domain name processing method.

[0137] It should be noted that the devices, media, programs and chips provided in this application can implement all the method steps implemented by the terminal device in the above method embodiments and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0138] In summary, the technical solution provided in this application can automate the domain name management process, effectively improving domain name management efficiency. Furthermore, through front-end and back-end design, domain name update information is generated on the front-end and the domain name update is executed on the back-end, effectively avoiding errors caused by executing complex domain name update commands on the login server or frequent information interaction during the domain name update process. The front-end visual interface for domain name updates displays the relative domain name, DNS record type, subdomain, DNS address, and authoritative DNS server through window decomposition. Simultaneously, the options for the front-end DNS server, subdomain, DNS type, and TTL are fixed, effectively avoiding manual input errors during domain name updates. In addition, after receiving the domain name update request from the front-end, the back-end first backs up the zone file of the subdomain to be updated before executing the domain name update, allowing for recovery using the backup file in case of a domain name resolution system failure.

[0139] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media).

[0140] As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer.

[0141] Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0142] In the description of the embodiments of this application, the term "and / or" merely indicates a relationship describing the associated objects, meaning that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the term "at least one" indicates any combination of at least two of a plurality of options, for example, including at least one of A, B, and C, which can represent any one or more elements selected from a set including communication between A, B, and C. Furthermore, the term "multiple" means two or more, unless otherwise precisely specified.

[0143] In the description of the embodiments of this application, the terms "first," "second," "third," "fourth," etc. (if present) are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0144] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A DNS domain name processing method, characterized in that, include: In response to a DNS domain name processing request, a domain name update window is displayed on the front-end visual interface. The domain name update window is used to configure domain name information. The domain name update window includes a relative domain name input field, a domain name resolution address input field, a subdomain selection field, a domain name resolution server selection field, a record type selection field, and a Time to Live (TTL) value input field or a TTL selection field. In response to the first input information in the relative domain name input field and the first selection information in the subdomain selection field, the target domain name is obtained based on the first input information and the first selection information. In response to the second input information in the domain name resolution address input field, the target domain name resolution address is obtained; In response to the second selection information of the domain name resolution server selection option, obtain the target domain name resolution server; In response to the third selection information in the record type selection options, the target parsing type is obtained; In response to the third input information of the TTL input item or the fourth selection information of the TTL selection item, the target parsing time-to-live is obtained; Domain name update information is generated based on the target domain name, the target domain name resolution address, the target domain name resolution server, the target resolution type, and the target resolution time-to-live, and an update code file is generated based on the domain name update information; The update code file is transmitted to the backend so that the backend can back up the current domain name zone file and update the DNS domain name based on the update code file.

2. The method according to claim 1, characterized in that, The step of obtaining the target domain name based on the first input information and the first selection information includes: In response to the verification result that the first input information conforms to the first preset rule, the target domain name is obtained based on the first input information and the first selection information, wherein the first preset rule includes that the character length of the first input information is within a preset range.

3. The method according to claim 1, characterized in that, The step of obtaining the target domain name based on the first input information and the first selection information includes: In response to the verification result that the first input information does not conform to the first preset rule, a prompt message for re-entering the relative domain name is issued in the domain name update window.

4. The method according to claim 1, characterized in that, The step of obtaining the target domain name resolution address includes: in response to the verification result that the second input information conforms to the second preset rule, obtaining the target domain name resolution address, wherein the second preset rule includes the second input information carrying an address information, and / or the second input information being an IPv4 address.

5. A DNS domain name processing device, characterized in that, include: The display module is configured to display a domain name update window on the front-end visual interface in response to DNS domain name processing requests. The domain name update window is used to configure domain name information. The domain name update window includes a relative domain name input field, a domain name resolution address input field, a subdomain selection field, a domain name resolution server selection field, a record type selection field, and a Time to Live (TTL) value input field or a TTL selection field. The acquisition module is configured to acquire the target domain name, the target domain name resolution address, and the target domain name resolution server in response to the operation result of the domain name update window. The generation module is configured to generate domain name update information based on the target domain name, the target domain name resolution address, and the target domain name resolution server, and to generate an update code file based on the domain name update information; The backup and update module is configured to transmit the update code file to the backend, so that the backend can update the DNS domain name based on the update code file after backing up the current domain name zone file; The acquisition module includes: The first acquisition unit is configured to acquire the target domain name based on the first input information and the first selection information in response to the first input information in the relative domain name input item and the first selection information in the subdomain selection item. The second acquisition unit is configured to acquire the target domain name resolution address in response to the second input information in the domain name resolution address input field. The third acquisition unit is configured to acquire the target domain name resolution server in response to the second selection information of the domain name resolution server selection item. The fourth acquisition unit is configured to acquire the target parsing type in response to the third selection information in the selection option of the record type; The fifth acquisition unit is configured to acquire the target parsing lifetime in response to the third input information of the TTL input item or the fourth selection information of the TTL selection item; The generation module is specifically configured to generate domain name update information based on the target domain name, the target domain name resolution address, the target domain name resolution server, the target resolution type, and the target resolution time-to-live.

6. A DNS domain name processing system, characterized in that, include: The front end is used to display a domain name update window in a visual interface, and the domain name update window is used to configure domain name information. The domain name update window includes a relative domain name input field, a domain name resolution address input field, a subdomain selection field, a domain name resolution server selection field, a record type selection field, and a Time to Live (TTL) value input field or a TTL selection field. In response to the first input information in the relative domain name input field and the first selection information in the subdomain selection field, the target domain name is obtained based on the first input information and the first selection information. In response to the first input information in the relative domain name input field and the first selection information in the subdomain selection field, the target domain name is obtained based on the first input information and the first selection information. In response to the second input information in the domain name resolution address input field, the target domain name resolution address is obtained; In response to the second selection information of the domain name resolution server selection option, obtain the target domain name resolution server; In response to the third selection information in the record type selection options, the target parsing type is obtained; In response to the third input information of the TTL input item or the fourth selection information of the TTL selection item, the target DNS record time is obtained; and based on the target domain name, the target domain name resolution address, the target domain name resolution server, the target resolution type, and the target DNS record time, domain name update information is generated, and an update code file is generated based on the domain name update information; The backend is used to receive the domain name update code file sent by the frontend, and after backing up the current domain name zone file, update the DNS domain name based on the update code file.

7. An electronic device, comprising: Processor and memory; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the electronic device to perform the DNS domain name processing method according to any one of claims 1 to 4.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the DNS domain name processing method as described in any one of claims 1 to 4.

Images