CN115378907A - MSP domain name resolution configuration management method, system, device and medium - Google Patents
MSP domain name resolution configuration management method, system, device and medium Download PDFInfo
- Publication number
- CN115378907A CN115378907A CN202210994240.2A CN202210994240A CN115378907A CN 115378907 A CN115378907 A CN 115378907A CN 202210994240 A CN202210994240 A CN 202210994240A CN 115378907 A CN115378907 A CN 115378907A
- Authority
- CN
- China
- Prior art keywords
- domain name
- service provider
- dns service
- record
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 29
- 238000000034 method Methods 0.000 claims abstract description 41
- 238000004458 analytical method Methods 0.000 claims description 45
- 238000012986 modification Methods 0.000 claims description 16
- 230000004048 modification Effects 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 14
- 238000000354 decomposition reaction Methods 0.000 claims description 11
- 238000012217 deletion Methods 0.000 claims description 11
- 230000037430 deletion Effects 0.000 claims description 11
- 238000012795 verification Methods 0.000 claims description 6
- 230000000694 effects Effects 0.000 claims description 5
- 238000001914 filtration Methods 0.000 claims description 4
- 238000007781 pre-processing Methods 0.000 claims description 4
- 239000000284 extract Substances 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000004883 computer application Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to an MSP domain name resolution configuration management method, system, device and medium. The method comprises the following steps: an operator first submits DNS service provider data and secondary domain name base data to the MSP system and stores the data information in the MSP system. When an operator submits a domain name resolution configuration request through the MSP system, the MSP system finds the DNS service provider where the secondary domain name is located in the domain name resolution configuration according to the secondary domain name basic data, and automatically configures the domain name resolution configuration data into the DNS service provider. By adopting the method, the dependence on the technical ability of operators can be reduced, and the efficiency of domain name resolution configuration can be improved.
Description
Technical Field
The present application relates to the field of computer applications and cloud computing technologies, and in particular, to a method, a system, a device, and a medium for MSP domain name resolution configuration management.
Background
The Domain Name System DNS (Domain Name System) is a distributed database on the internet as a mapping between Domain names and IP addresses, and enables a user to access the internet more conveniently without having to remember IP strings that can be directly read by a machine, and a process of finally obtaining IP addresses corresponding to host names by host names is called Domain Name resolution. When configuring domain name resolution, a user needs to operate through a page console system of a DNS service provider or call their API (Application Programming Interface).
When the domain name resolution is configured through the page console system, the domain name information in the existing system needs to be operated in the page console in a manual mode, and for complex domain name configuration, the complexity, the error easiness and the timeliness of the operation are increased. Although manual secondary manual operation of the domain name can be avoided through the API, the DNS service provider usually provides only basic operation, and for complex configuration requirements, disassembly is very easy to call errors, resulting in unexpected effects. When a user has a plurality of secondary domain names distributed in different DNS service providers, the operation needs to be performed on the corresponding DNS service provider according to the secondary domain name. The whole domain name resolution operation is more complicated because the design, system limitation and API calling mode of the page console of each DNS service provider are different.
Disclosure of Invention
In view of the foregoing, there is a need to provide an MSP domain name resolution configuration management method, system, device and medium capable of improving efficiency of domain name resolution configuration.
An MSP domain name system resolution configuration management method comprises the following steps:
an operator submits DNS service provider data and second-level domain name basic data to the MSP system; the DNS service provider data comprises the name of the DNS service provider and access key information for calling the API of the DNS service provider; the second-level domain name basic data comprises a second-level domain name and a DNS service provider name where the second-level domain name is located;
an operator submits a domain name resolution configuration request through an MSP system; the domain name resolution configuration request comprises resolution records of sub domain names; the sub-domain name comprises a host name and a secondary domain name; the analysis record comprises an intelligent analysis line, a DNS record type, a record value, TTL and weight information;
acquiring a DNS service provider corresponding to a secondary domain name in the domain name resolution configuration according to the secondary domain name basic data;
and performing operation decomposition on the resolution record of the sub domain name, and configuring the resolution record into a corresponding DNS service provider.
In one embodiment, the method further comprises the following steps: the MSP system checks DNS service provider data;
and verifying the validity of the access key by calling an API (application programming interface) of the DNS service provider for acquiring the domain name list, and writing the DNS service provider data into the MSP (Mixed service provider) system after the verification is passed.
In one embodiment, the method further comprises the following steps: the DNS service provider name where the second-level domain name is located is obtained by selecting from a name list of the DNS service provider;
the MSP system checks the basic data of the secondary domain name; searching whether a secondary domain name is in a DNS service provider system or not by calling an API (application program interface) of the DNS service provider for obtaining a domain name list; when the secondary domain name is not in the DNS service provider system, prompting an operator to create a secondary domain name for the DNS service provider through the MSP system; when the secondary domain name is in the DNS service provider system, the MSP system writes the information of the secondary domain name returned by the DNS service provider into the MSP system; the information of the secondary domain name returned by the DNS service provider comprises the name, the number, the service state and the domain name package type of the secondary domain name;
the MSP system obtains intelligent analysis circuit list information supported by the secondary domain name by calling an API (application program interface) of the DNS service provider for obtaining the intelligent analysis circuit list according to the domain name package type of the secondary domain name returned by the DNS service provider, and writes the intelligent analysis circuit list information into the MSP system.
In one embodiment, the method further comprises the following steps: the intelligent analysis line is an intelligent analysis line list supported by a secondary domain name stored in the current MSP system;
the MSP system checks the submitted data of the domain name resolution configuration request;
the MSP system checks the validity of each field in the analysis record, and the operator is prompted to process the verification failure.
In one embodiment, the method further comprises the following steps: the MSP system extracts second-level domain name information in the domain name resolution configuration request;
acquiring a DNS service provider corresponding to a secondary domain name in domain name resolution configuration according to the basic data of the secondary domain name in the MSP system;
and when the DNS service provider is failed to acquire, the operator is informed to process.
In one embodiment, the method further comprises the following steps: the configured analysis record in the DNS service provider is called as a configured record, and the analysis record to be configured is called as a record to be updated;
preprocessing the request content of the update record, and setting an addition zone bit for each record to be updated;
inquiring a complete analysis record of a sub domain name in a DNS service provider, and setting a deletion flag bit for a configured record obtained after filtering;
comparing the record to be updated with the configured record for multiple times, setting a modification flag bit and clearing a deletion flag bit of the configured record with partial inconsistent data of the record to be updated and the configured record, and clearing an addition flag bit of the current record to be updated; clearing the deletion flag bit of the configured record with the consistent data of the two data, and clearing the addition flag bit of the current record to be updated;
classifying the data to be operated according to the zone bits to obtain newly added records, modified records and deleted records of the data to be operated;
and configuring and taking effect of the classified data to be operated by calling the API of the corresponding DNS service provider.
In one embodiment, the method further comprises the following steps: calling an API (application program interface) of the added records of the DNS (domain name system) service provider, and adding the newly added records one by one or in batches;
calling an API (application programming interface) of a DNS (domain name system) service provider for modifying records, and modifying the modified records one by one or modifying the modified records in batches;
and calling the API of the DNS service provider for deleting the records, and deleting the deleted records one by one or deleting the deleted records in batches.
An MSP domain name resolution configuration management system, the system comprising:
the data acquisition module is used for acquiring DNS service provider data and second-level domain name basic data submitted to the MSP system by an operator; the DNS service provider data comprises the name of the DNS service provider and access key information for calling the API of the DNS service provider; the second-level domain name basic data comprises a second-level domain name and a DNS service provider name where the second-level domain name is located;
the configuration request receiving module is used for receiving a domain name resolution configuration request submitted by an operator through the MSP system; the domain name resolution configuration request comprises resolution records of the sub-domain names; the sub-domain name comprises a host name and a secondary domain name; the analysis record comprises an intelligent analysis line, a DNS record type, a record value, TTL and weight information;
the domain name configuration module is used for acquiring a DNS service provider corresponding to a secondary domain name in domain name resolution configuration according to the secondary domain name basic data; and performing operation decomposition on the resolution record of the sub domain name, and configuring the resolution record into a corresponding DNS service provider.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
an operator submits DNS service provider data and second-level domain name basic data to the MSP system; the DNS service provider data comprises the name of the DNS service provider and access key information for calling the DNS service provider API; the second-level domain name basic data comprises a second-level domain name and a DNS service provider name where the second-level domain name is located;
an operator submits a domain name resolution configuration request through an MSP system; the domain name resolution configuration request comprises resolution records of the sub-domain names; the sub-domain name comprises a host name and a secondary domain name; the analysis record comprises an intelligent analysis line, a DNS record type, a record value, TTL and weight information;
acquiring a DNS service provider corresponding to a secondary domain name in the domain name resolution configuration according to the secondary domain name basic data;
and performing operation decomposition on the resolution record of the sub domain name, and configuring the resolution record into a corresponding DNS service provider.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
an operator submits DNS service provider data and second-level domain name basic data to the MSP system; the DNS service provider data comprises the name of the DNS service provider and access key information for calling the API; the second-level domain name basic data comprises a second-level domain name and a DNS service provider name where the second-level domain name is located;
an operator submits a domain name resolution configuration request through an MSP system; the domain name resolution configuration request comprises resolution records of sub domain names; the sub-domain name comprises a host name and a secondary domain name; the analysis record comprises an intelligent analysis line, a DNS record type, a record value, TTL and weight information;
acquiring a DNS service provider corresponding to a secondary domain name in the domain name resolution configuration according to the secondary domain name basic data;
and performing operation decomposition on the resolution record of the sub domain name, and configuring the resolution record into a corresponding DNS service provider.
According to the MSP domain name resolution configuration management method, the system, the equipment and the medium, through the MSP system, firstly, an operator submits DNS service provider data and secondary domain name basic data to the MSP system, and the data information is stored in the MSP system. When an operator submits a domain name resolution configuration request through the MSP system, the MSP system finds the DNS service provider where the secondary domain name is located in the domain name resolution configuration according to the secondary domain name basic data, and automatically configures the domain name resolution configuration data into the DNS service provider.
Drawings
FIG. 1 is a flow diagram of a MSP domain name resolution configuration management method in one embodiment;
FIG. 2 is an MSP domain name resolution configuration management system in one embodiment;
FIG. 3 is a diagram illustrating an MSP domain name configuration management system in accordance with an embodiment;
FIG. 4 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
When an operator performs domain name resolution configuration through an MSP (Managed Service Provider) system, the MSP system automatically submits the domain name resolution configuration to a corresponding DNS (domain name server) Provider, and feeds back a resolution configuration result to the operator.
In one embodiment, as shown in fig. 1, there is provided an MSP domain name resolution configuration management method, including the following steps:
In this embodiment, the DNS service provider data includes a name of the DNS service provider and access key (AK/SK) information for calling the DNS service provider API; the access key is obtained through a console page system of a DNS service provider; the basic data of the second-level domain name comprises a second-level domain name and a DNS service provider where the second-level domain name is located, wherein the DNS service provider name where the second-level domain name is located is obtained by selecting from a name list of the DNS service provider.
In this embodiment, the domain name resolution configuration request includes resolution records of sub-domain names; the sub-domain name comprises a host name and a secondary domain name; the analysis record comprises an intelligent analysis line, a DNS record type, a record value, TTL and weight information; specifically, the type of the domain name resolution configuration request includes querying a record, updating a record, and deleting a record. The query record is a complete resolution record requesting a single sub-domain name, which consists of a host record + a secondary domain name. The request content is a single host record + a secondary domain name. The result of the analysis records is a set of all the analysis records configured for the sub-domain name, and each analysis record comprises: resolving lines, DNS record types, record values, TTL and weight information. The update record is a complete resolution record that updates a single sub-domain name, comprising a collection of single or multiple domain name resolution records. Each parse record includes: resolving lines, DNS record types, record values, TTL and weight information. The delete record is a complete resolution record for deleting a single sub-domain name, and the request content is a single host record + a secondary domain name.
And step 106, acquiring a DNS service provider corresponding to the secondary domain name in the domain name resolution configuration according to the secondary domain name basic data.
In this embodiment, the basic data of the secondary domain name includes the name of the secondary domain name and the DNS service provider where the secondary domain name is located, so that the secondary domain name corresponds to the DNS service provider one by one, and the corresponding DNS service provider is found according to the acquired secondary domain name and the corresponding relationship between the secondary domain name and the DNS service provider. Optionally, when the DNS service provider does not support the configuration weight information, the method automatically skips unsupported fields.
And step 108, performing operation decomposition on the resolution record of the sub-domain name, and configuring the resolution record to a corresponding DNS service provider.
In this embodiment, a configured resolution record in the DNS service provider is referred to as a configured record, and a resolution record to be configured is referred to as a record to be updated. The update record request contains a complete resolution record of a single sub-domain name, and the resolution record has 3 flag bits: "add", "modify", "delete". The record to be updated only supports the 'adding' flag bit, and the configured record only supports the 'modifying' flag bit and the 'deleting' flag bit. The method of deleting a record request will multiplex the updated record, since there is no record to be updated, only the configured record is operated.
The specific steps of performing operation decomposition on the data of the domain name resolution configuration request are as follows: preprocessing request content of the update record, wherein the request content may contain a plurality of domain name resolution records, and setting an 'adding' flag bit for each record to be updated; inquiring the complete resolution record of the sub-domain name in a DNS service provider, and setting a 'deletion' flag bit for the configured record obtained after filtering; in this embodiment, the data to be updated and the data to be configured are compared for multiple times, and the content of the data comparison includes an analysis line, a record value, a TTL, and weight information. And traversing the list of the configured records from the first record to be updated, skipping the data without setting a 'delete' flag bit in the configured records, and only comparing the data with the same analytical circuit and record values, wherein the inconsistent data are not compared temporarily. And if the TTL or the weight information is inconsistent, setting the configured record as a 'modification' zone bit, and transmitting the TTL or the weight information corresponding to the record to be updated to the field to be updated of the configured record. And clearing the 'adding' flag bit of the current record to be updated and the 'deleting' flag bit of the current configured record. After comparison, if the current configured record has not set the 'modification' flag bit, it indicates that the two data are consistent, and the data does not need to be changed. And skipping the data without the 'adding' flag bit in the record to be updated from the first record to be updated, traversing the list of the configured records, skipping the data without the 'deleting' flag bit in the configured records, only comparing the data with the consistent analytical lines, and not comparing the data with the inconsistent analytical lines. And if the record value, the TTL or the weight information are inconsistent, setting the configured record as a 'modification' flag bit, and transmitting the record value, the TTL or the weight information corresponding to the record to be updated to the field to be updated of the configured record. And clearing the 'adding' flag bit of the current record to be updated and the 'deleting' flag bit of the current configured record. After comparison, if the current configured record has not set the 'modification' flag bit, it indicates that the two data are consistent, and the data does not need to be changed.
Classifying data to be operated into three types: i.e. newly added records, modified records and deleted records. In this embodiment, the newly added record refers to data set as an "added" flag bit in the record to be updated; the modified record refers to data which is set as a 'modified' flag bit in the configured record; delete records refer to data in a configured record that is set to the "delete" flag bit. And configuring and taking effect of the classified data to be operated by calling an API of a DNS service provider.
In this embodiment, the newly added record calls an API of the added record of the DNS service provider, and is added one by one or added in batch; the modification records call the API of the modification records of the DNS service provider, and are modified one by one or in batches; deleting the record calls an API of the DNS service provider for deleting the record, and deleting the record one by one or deleting the record in batches.
In the above MSP domain name resolution configuration management method, firstly, an operator submits DNS service provider data and secondary domain name base data to the MSP system, and stores the data information in the MSP system. When an operator submits a domain name resolution configuration request through the MSP system, the MSP system finds the DNS service provider where the secondary domain name is located in the domain name resolution configuration according to the secondary domain name basic data, and automatically configures the domain name resolution configuration data into the DNS service provider.
In one embodiment, an operator submits DNS service provider data to an MSP system, comprising: the MSP system checks DNS service provider data; carrying out validity verification on the access key by calling an API (application programming interface) of the DNS service provider for obtaining the domain name list, and writing DNS service provider data into an MSP (mixed-mode host protocol) system after the verification is passed; and prompting an operator to check after the check fails.
In this embodiment, if the access key fails to be verified, the MSP interface prompts an operator to check and feed back the reason for the failure.
In another embodiment, the DNS service provider name where the secondary domain name is located is selected from a name list of the DNS service provider; an operator submits the basic data of the second-level domain name to the MSP system, and the method comprises the following steps:
the MSP system verifies the basic data of the second-level domain name; searching whether a secondary domain name is in a DNS service provider system or not by calling an API (application program interface) of the DNS service provider for obtaining a domain name list; when the secondary domain name is not in the DNS service provider system, prompting an operator to create a secondary domain name for the DNS service provider through the MSP system; when the secondary domain name is in the DNS service provider system, the MSP system writes the information of the secondary domain name returned by the DNS service provider into the MSP system; the information of the secondary domain name returned by the DNS service provider comprises the name, the number, the service state and the domain name package type of the secondary domain name; the MSP system obtains the intelligent analysis line list information supported by the secondary domain name by calling the API of the DNS provider for obtaining the intelligent analysis line list according to the domain name package type of the secondary domain name returned by the DNS provider, and writes the intelligent analysis line list information into the MSP system.
In this embodiment, the intelligent resolution route list supported by the secondary domain name is used in the subsequent domain name resolution configuration process, and is provided for the operator to select by the MSP system.
In another embodiment, the intelligent analysis line is an intelligent analysis line list supported by a secondary domain name stored in the current MSP system; an operator submits a domain name resolution configuration request through an MSP system, and the method comprises the following steps: the MSP system checks the submitted data of the domain name resolution configuration request; the MSP system checks the validity of each field in the analysis record, and the operator is prompted to process the verification failure.
In another embodiment, a DNS service provider corresponding to a secondary domain name in a domain name resolution configuration is obtained according to secondary domain name base data, including: the MSP system extracts second-level domain name information in the domain name resolution configuration request; acquiring a DNS service provider corresponding to a secondary domain name in domain name resolution configuration according to the basic data of the secondary domain name in the MSP system; and when the DNS service provider is failed to acquire, the operator is informed to process.
In this embodiment, one secondary domain name can only provide domain name resolution service in one DNS service provider at the same time, and the corresponding DNS service provider is found according to the correspondence between the secondary domain name and the DNS service provider. Alternatively, when the DNS service provider does not support the configuration weight information, the method will automatically skip the fields that are not supported.
In another embodiment, the parsing record of the sub-domain name is decomposed and configured to the corresponding DNS service provider, and the steps include: preprocessing the request content of the update record, and setting an addition zone bit for each record to be updated; in this embodiment, when the API of the DNS service provider for obtaining the domain name resolution record is called, because some DNS service providers support the hostname fuzzy query, the hostname in the result needs to be compared with the requested hostname, and data with inconsistent hostnames needs to be filtered. When the requested host name is not configured in the DNS service provider, obtaining null data, and setting a deletion flag bit for the configured record obtained after filtering; comparing the record to be updated with the configured record for multiple times, setting a modification flag bit and clearing a deletion flag bit of the configured record with partial inconsistent data of the record to be updated and the configured record, and clearing an addition flag bit of the current record to be updated; clearing the deletion flag bit of the configured record with the consistent data of the two data, and clearing the addition flag bit of the current record to be updated; classifying the data to be operated according to the zone bit to obtain new records, modified records and deleted records of the data to be operated; and configuring and taking effect of the classified data to be operated by calling the API of the corresponding DNS service provider.
In this embodiment, the newly added record refers to data set as an addition flag bit in the record to be updated; the modified record refers to data set as a modified flag bit in a configured record; delete record refers to data set to the delete flag bit in a configured record.
In another embodiment, the configuring and validating the classified data to be operated by calling the API of the corresponding DNS service provider includes: calling an API (application program interface) of the added records of the DNS (domain name system) service provider, and adding the newly added records one by one or in batches; calling an API (application programming interface) of a modification record of a DNS (domain name system) service provider, and modifying the modification record one by one or modifying the modification record in batches; and calling the API of the DNS service provider for deleting the records, and deleting the deleted records one by one or deleting the deleted records in batches.
In this embodiment, if the list of data types to be operated is empty, the operation of the data of the type is skipped. And finally, returning an analysis configuration result. If part of API operation fails to feed back, the system rolls back the operated data and feeds back the failure result to the operator. Deleting the added records one by one; for the modified data, the original data is modified again; and adding the deleted data again, and finally feeding back the result to an operator to prompt the success or failure of the operation.
It should be understood that, although the steps in the flowchart of fig. 1 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least some of the sub-steps or stages of other steps.
In another embodiment, as shown in fig. 2, there is provided an MSP domain name resolution configuration management system, comprising: a data acquisition module 202, a configuration request receiving module 204, and a domain name configuration module 206, wherein:
a data obtaining module 202, configured to obtain DNS service provider data and second-level domain name base data that are submitted to the MSP system by an operator; the DNS service provider data includes a name of the DNS service provider and access key (AK/SK) information calling a DNS service provider API; the second-level domain name basic data comprises a second-level domain name and a DNS service provider name where the second-level domain name is located.
A configuration request receiving module 204, configured to receive a domain name resolution configuration request submitted by an operator through the MSP system; the domain name resolution configuration request comprises resolution records of the sub-domain names; the sub-domain name comprises a host name and a secondary domain name; the analysis record comprises an intelligent analysis line, a DNS record type, a record value, TTL and weight information.
A domain name configuration module 206, configured to obtain, according to the second-level domain name basic data, a DNS service provider corresponding to the second-level domain name in the domain name resolution configuration; and performing operation decomposition on the resolution record of the sub domain name, and configuring the resolution record into a corresponding DNS service provider.
For specific limitations of the MSP domain name resolution configuration management system, reference may be made to the above limitations of the MSP domain name resolution configuration management method, which are not described herein again. All or part of each module in the MSP domain name resolution configuration management system can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent of a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In another embodiment, as shown in fig. 3, there is provided an MSP domain name configuration management system comprising: MSP interface module 302, DNS service provider management module 304, DNS service provider API module 306.
The MSP interface module 302 is used to provide an interface for operations to MSP system pages, and is mainly divided into two types: MSP domain name system configuration interface, MSP domain name system analysis interface.
In this embodiment, the MSP DNS configuration interface is divided into basic data for updating DNS service provider data and updating secondary domain names. The MSP domain name system analysis interface comprises an intelligent domain name analysis line query, a domain name analysis record update and a domain name analysis record deletion. The intelligent domain name resolution line is inquired to request a line list supported by the secondary domain name on the DNS service provider. After obtaining the line list, the MSP system provides the operator with the choice in configuring domain name resolution. The query domain name resolution record is a complete resolution record requesting a single sub-domain name, and the sub-domain name consists of a host name and a secondary domain name. The request content is a single host name + a secondary domain name. Updating a domain name resolution record is updating a complete resolution record for a single sub-domain name, comprising a collection of single or multiple domain name resolution records. Deleting the domain name resolution record is deleting the complete resolution record of a single sub-domain name, and the request content is a single host name plus a secondary domain name.
A DNS service provider management module 304, configured to initialize a DNS service provider and maintain a relationship between the secondary domain name and the DNS service provider.
In this embodiment, when an interface for updating DNS service provider data is called in the MSP interface module 302, the DNS service provider management module 304 initializes the corresponding DNS service provider according to data incoming from the MSP interface module 302, where the incoming data includes a name of the DNS service provider and access key (AK/SK) information for calling a DNS service provider API. The DNS service provider management module 304 is configured to check the validity of the access key by calling the API of the DNS service provider for obtaining the domain name list according to the access key. If the AK/SK check fails, the MSP interface module 302 feeds back the reason of the failure to the operator. When an interface for updating the basic data of the secondary domain name is called in the MSP interface module 302, the DNS service provider management module 304 checks the incoming data according to the module in the MSP interface module 302, where the incoming data includes the name of the secondary domain name and the DNS service provider where the secondary domain name is located. The DNS service provider management module 304 is used to find whether the incoming secondary domain name is in the secondary domain name list that the selected DNS service provider has created by calling the DNS service provider's get domain name list API. When the incoming secondary domain name is not in the created domain name list, feedback will be provided to the operator via the MSP interface module 302 prompting the operator to create a secondary domain name to the DNS service provider via the MSP system. When the incoming second-level domain name is in the created domain name list, the DNS service provider management module 304 calls an API of the DNS service provider for obtaining an intelligent resolution line list according to a package type configured by the current second-level domain name in the DNS service provider, obtains intelligent resolution line list information supported by the current second-level domain name, returns the intelligent resolution line list information to the MSP system through the MSP interface module 302, and subsequently uses the line list supported by the second-level domain name for selection by an operator during domain name resolution configuration.
The DNS service provider API module 306 is configured to receive a request from the MSP interface module and the DNS service provider management module, and implement related functions by calling an API of the DNS service provider, including obtaining a created domain name list, obtaining an intelligent resolution line list, creating a secondary domain name, querying a domain name resolution record, updating the domain name resolution record, and deleting the domain name resolution record.
In this embodiment, the functions of obtaining the created domain name list, obtaining the intelligent resolution line list, creating the secondary domain name, and querying the domain name resolution record may be implemented by directly calling an API of the DNS service provider. Updating the domain name resolution record and deleting the domain name resolution record can be realized by calling the API of the DNS service provider for multiple times after operation and decomposition are required.
In another embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 4. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program when executed by a processor implements a MSP domain name resolution configuration management method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the configuration shown in fig. 4 is a block diagram of only a portion of the configuration associated with the present application, and is not intended to limit the computing device to which the present application may be applied, and that a particular computing device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In an embodiment, a computer device is provided, comprising a memory storing a computer program and a processor implementing the steps of the above method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not to be construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, and these are all within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. An MSP domain name resolution configuration management method, the method comprising:
an operator submits DNS service provider data and second-level domain name basic data to the MSP system; the DNS service provider data comprises the name of the DNS service provider and access key information for calling an API of the DNS service provider; the second-level domain name basic data comprises a second-level domain name and a DNS service provider name where the second-level domain name is located;
an operator submits a domain name resolution configuration request through an MSP system; the domain name resolution configuration request comprises resolution records of sub domain names; the sub-domain name comprises a host name and a secondary domain name; the analysis record comprises an intelligent analysis line, a DNS record type, a record value, TTL and weight information;
acquiring a DNS service provider corresponding to a secondary domain name in domain name resolution configuration according to the secondary domain name basic data;
and performing operation decomposition on the resolution records of the sub domain names, and configuring the resolution records to corresponding DNS service providers.
2. The method of claim 1, wherein the operator submits DNS service provider data to the MSP system comprising:
the MSP system checks the DNS service provider data;
verifying the validity of the access key by calling an API (application programming interface) of a DNS (domain name service) provider for acquiring a domain name list, and writing the DNS provider data into an MSP (mixed-server process) system after the DNS service provider data passes verification;
and prompting an operator to check after the check fails.
3. The method according to claim 1, wherein the DNS service provider name where the secondary domain name is located is selected from a name list of the DNS service provider;
the method comprises the following steps that an operator submits secondary domain name basic data to an MSP system, and the method comprises the following steps:
the MSP system verifies the secondary domain name basic data; searching whether the secondary domain name is in the DNS service provider system or not by calling an API of the DNS service provider for obtaining a domain name list; when the secondary domain name is not in the DNS service provider system, prompting an operator to create the secondary domain name to the DNS service provider through an MSP system; when the secondary domain name is in the DNS service provider system, the MSP system writes the information of the secondary domain name returned by the DNS service provider into the MSP system; the information of the secondary domain name returned by the DNS service provider comprises the name, the number, the service state and the domain name package type of the secondary domain name;
and the MSP system obtains the intelligent analysis line list information supported by the secondary domain name by calling the API of the DNS provider for obtaining the intelligent analysis line list according to the domain name package type of the secondary domain name returned by the DNS provider and writes the intelligent analysis line list information into the MSP system.
4. The method of claim 1, wherein the intelligent resolution lines are a list of intelligent resolution lines supported by the secondary domain name saved in a current MSP system;
the operator submits a domain name resolution configuration request through an MSP system, and the method comprises the following steps:
the MSP system checks the submitted data of the domain name resolution configuration request;
and the MSP system checks the validity of each field in the analysis record, and the operator is prompted to process if the check is successful.
5. The method according to claim 1, wherein a DNS service provider corresponding to the secondary domain name in a domain name resolution configuration is obtained according to the secondary domain name base data, and the step includes:
the MSP system extracts second-level domain name information in the domain name resolution configuration request;
acquiring a DNS service provider corresponding to the secondary domain name in the domain name resolution configuration according to the secondary domain name basic data in the MSP system;
and informing an operator to process the DNS service when the DNS service provider fails to acquire the DNS service provider.
6. The method according to claim 1, wherein the configured resolution record in the DNS service provider is called a configured record, and the resolution record to be configured is called a record to be updated;
and performing operation decomposition on the resolution record of the sub-domain name, and configuring the resolution record into a corresponding DNS service provider, wherein the steps comprise:
preprocessing the request content of the update record, and setting an adding flag bit for each record to be updated;
querying a complete resolution record of a sub-domain name in the DNS service provider, and setting a deletion flag bit for the configured record obtained after filtering;
comparing the record to be updated with the configured record for multiple times, setting a modification flag bit and clearing a deletion flag bit of the configured record with partial inconsistent data of the record to be updated and the configured record, and clearing an addition flag bit of the current record to be updated; clearing the deletion flag bit of the configured record with the consistent data of the two data, and clearing the addition flag bit of the current record to be updated;
classifying the data to be operated according to the zone bit to obtain new records, modified records and deleted records of the data to be operated;
and configuring and taking effect of the classified data to be operated by calling the API of the corresponding DNS service provider.
7. The method according to claim 6, wherein the configuring and validating the sorted data to be operated by calling an API of a corresponding DNS service provider comprises:
calling an API (application program interface) of the added records of the DNS service provider, and adding the newly added records one by one or in batches;
calling an API of a modification record of the DNS service provider, and modifying the modification record one by one or modifying the modification record in batches;
and calling the API of the DNS service provider for deleting the records, and deleting the deleted records one by one or deleting the deleted records in batches.
8. An MSP domain name resolution configuration management system, the system comprising:
the data acquisition module is used for acquiring DNS service provider data and second-level domain name basic data submitted to the MSP system by an operator; the DNS service provider data comprises the name of the DNS service provider and access key information for calling an API of the DNS service provider; the second-level domain name basic data comprises a second-level domain name and a DNS service provider name where the second-level domain name is located;
the configuration request receiving module is used for receiving a domain name resolution configuration request submitted by an operator through the MSP system; the domain name resolution configuration request comprises resolution records of sub domain names; the sub-domain names include a host name and a secondary domain name; the analysis record comprises an intelligent analysis line, a DNS record type, a record value, TTL and weight information;
the domain name configuration module is used for acquiring a DNS service provider corresponding to a secondary domain name in domain name resolution configuration according to the secondary domain name basic data; and performing operation decomposition on the resolution records of the sub domain names, and configuring the resolution records to corresponding DNS service providers.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor when executing the computer program performs the steps of the method according to any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210994240.2A CN115378907B (en) | 2022-08-18 | 2022-08-18 | MSP domain name resolution configuration management method, system, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210994240.2A CN115378907B (en) | 2022-08-18 | 2022-08-18 | MSP domain name resolution configuration management method, system, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115378907A true CN115378907A (en) | 2022-11-22 |
| CN115378907B CN115378907B (en) | 2024-03-15 |
Family
ID=84066009
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210994240.2A Active CN115378907B (en) | 2022-08-18 | 2022-08-18 | MSP domain name resolution configuration management method, system, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115378907B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016177284A1 (en) * | 2015-05-07 | 2016-11-10 | 阿里巴巴集团控股有限公司 | Domain name resolution method and device |
| US20190166085A1 (en) * | 2017-04-19 | 2019-05-30 | Peking University Shenzhen Graduate School | Blockchain-based domain name resolution system |
| CN110445850A (en) * | 2019-07-24 | 2019-11-12 | 深圳壹账通智能科技有限公司 | Block chain node access method and device, storage medium, electronic equipment |
| CN111818196A (en) * | 2020-07-22 | 2020-10-23 | 深圳市有方科技股份有限公司 | Domain name resolution method, domain name resolution device, computer equipment and storage medium |
| CN111919506A (en) * | 2018-06-06 | 2020-11-10 | 英特尔公司 | Vehicle-to-outside session and service continuity in automotive edge computing systems |
| CN112261174A (en) * | 2020-10-21 | 2021-01-22 | 北京云联壹云技术有限公司 | Multi-cloud-fusion DNS (Domain name Server) analysis method and device |
| CN112738294A (en) * | 2020-12-30 | 2021-04-30 | 北京百度网讯科技有限公司 | Domain name resolution method and device based on block chain, electronic equipment and storage medium |
| CN112954683A (en) * | 2021-05-13 | 2021-06-11 | 中兴通讯股份有限公司 | Domain name resolution method, domain name resolution device, electronic equipment and storage medium |
-
2022
- 2022-08-18 CN CN202210994240.2A patent/CN115378907B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016177284A1 (en) * | 2015-05-07 | 2016-11-10 | 阿里巴巴集团控股有限公司 | Domain name resolution method and device |
| US20190166085A1 (en) * | 2017-04-19 | 2019-05-30 | Peking University Shenzhen Graduate School | Blockchain-based domain name resolution system |
| CN111919506A (en) * | 2018-06-06 | 2020-11-10 | 英特尔公司 | Vehicle-to-outside session and service continuity in automotive edge computing systems |
| CN110445850A (en) * | 2019-07-24 | 2019-11-12 | 深圳壹账通智能科技有限公司 | Block chain node access method and device, storage medium, electronic equipment |
| CN111818196A (en) * | 2020-07-22 | 2020-10-23 | 深圳市有方科技股份有限公司 | Domain name resolution method, domain name resolution device, computer equipment and storage medium |
| CN112261174A (en) * | 2020-10-21 | 2021-01-22 | 北京云联壹云技术有限公司 | Multi-cloud-fusion DNS (Domain name Server) analysis method and device |
| CN112738294A (en) * | 2020-12-30 | 2021-04-30 | 北京百度网讯科技有限公司 | Domain name resolution method and device based on block chain, electronic equipment and storage medium |
| CN112954683A (en) * | 2021-05-13 | 2021-06-11 | 中兴通讯股份有限公司 | Domain name resolution method, domain name resolution device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 秦臻等: "基于云的域名解析服务模型", 《通信学报》, vol. 34, no. 02, pages 19 - 26 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115378907B (en) | 2024-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108090064B (en) | Data query method and device, data storage server and system | |
| CN110162720B (en) | Webpage loading method and device, computer equipment and storage medium | |
| CN108829838B (en) | Batch processing method of account information and server | |
| CN112417360B (en) | Webpage rendering method and device | |
| CN111898102A (en) | Authority configuration method and device, computer equipment and storage medium | |
| CN111083054B (en) | Route configuration processing method and device, computer equipment and storage medium | |
| CN110659019B (en) | Parameter verification method, device and server | |
| CN109684303B (en) | Communication code attribution inquiry method and device, computer equipment and storage medium | |
| CN111858588A (en) | Distributed application index service platform and data processing method | |
| CN116680278B (en) | Data processing method, device, electronic equipment and storage medium | |
| CN115378907A (en) | MSP domain name resolution configuration management method, system, device and medium | |
| CN111866197B (en) | Domain name resolution method and system | |
| CN109710861B (en) | System and method for generating URL | |
| CN112637085B (en) | Flow recording method and device, computer equipment and storage medium | |
| CN114969612A (en) | Multi-tenant data isolation method, system and computer equipment | |
| CN115544132A (en) | Data import method and system and electronic equipment | |
| CN110928598B (en) | System configuration method, device, computer equipment and storage medium | |
| CN114610973A (en) | Information search matching method and device, computer equipment and storage medium | |
| CN110781189B (en) | Document platform construction method and device, electronic equipment and storage medium | |
| CN113438331A (en) | Short domain name management method, system, electronic device and storage medium | |
| CN115130037A (en) | Information processing system, recording medium, and information processing method | |
| CN112579459A (en) | Method and device for testing application program and computer equipment | |
| CN107517280B (en) | Domain name resolution method and device | |
| KR101790594B1 (en) | Method for managing attribute information of file and computing device using the same | |
| KR20020085996A (en) | Method of Providing a Web Page Using Client Cache Memory |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |