CN116708363A

CN116708363A - Data management method, device, system, electronic equipment and storage medium

Info

Publication number: CN116708363A
Application number: CN202210188078.5A
Authority: CN
Inventors: 刘志杰
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-02-28
Filing date: 2022-02-28
Publication date: 2023-09-05

Abstract

The application provides a data management method, a data management device, a data management system, a data management device and a storage medium. The method comprises the steps that a central server sends first information to a client detection system, wherein the first information comprises domain names needing to be resolved; receiving second information sent by the client detection system, wherein the second information comprises analysis data obtained by analyzing the domain name by a local DNS server of the client detection system; and processing the second information to acquire the domain name resolution condition of the client detection system. The embodiment of the application can collect and process the DNS analysis data without arranging DNS detection scripts in different areas by operation and maintenance personnel, so that the embodiment of the application can be beneficial to improving the efficiency of DNS analysis data management.

Description

Data management method, device, system, electronic equipment and storage medium

Technical Field

The present application relates to the field of computers, and more particularly, to a method, apparatus, system, electronic device, and storage medium for data management.

Background

To meet the consistent user experience and local compliance requirements of Internet (Internet) users in different countries or regions, related component servers are required to be deployed in situ, or in the field. Thus, there is a need for a guaranteed user to be able to properly link to the server of the local component while using each client. If the client is able to correctly link the server of the local component, the client is required to resolve the domain name of the component to the internet protocol (Internet Protocol, IP) address of the server of the local component.

To achieve the above objective, it is necessary to know or monitor the resolution of the local domain name system (Domain Name System, DNS) in each region. However, aiming at the analysis conditions of DNS in different regions, operation and maintenance personnel need to deploy DNS probe scripts in different regions to collect analysis data, automatic reporting and collection of DNS analysis data cannot be realized, and the data management efficiency is low.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a storage medium for data management, which can help to improve the efficiency of domain name management.

In a first aspect, a method of data management is provided, comprising:

sending first information to a client detection system, wherein the first information comprises a domain name to be resolved;

receiving second information sent by the client detection system, wherein the second information comprises analysis data obtained by analyzing the domain name by a local DNS server of the client detection system;

and processing the second information to obtain the domain name resolution condition of the client detection system.

In a second aspect, there is provided a method of data management, comprising:

receiving first information sent by a central server, wherein the first information comprises a domain name to be resolved;

According to the first information, a domain name resolution request is sent to a local DNS server;

receiving a domain name resolution response sent by the local DNS server, wherein the domain name resolution response comprises resolution data obtained by resolving the domain name by the local DNS server;

and sending second information to the central server, wherein the second information comprises the analysis data.

In a third aspect, an apparatus for data management is provided, comprising:

the receiving and transmitting unit is used for transmitting first information to the client detection system, wherein the first information comprises a domain name to be resolved;

the receiving and transmitting unit is further configured to receive second information sent by the client detection system, where the second information includes resolution data obtained by resolving the domain name by a local DNS server of the client detection system;

and the processing unit is used for processing the second information and acquiring the domain name resolution condition of the client detection system.

A fourth method provides an apparatus for data management, comprising:

the receiving and transmitting unit is used for receiving first information sent by the central server, wherein the first information comprises a domain name to be resolved;

the receiving and transmitting unit is further configured to send a domain name resolution request to a local DNS server according to the first information;

The receiving and transmitting unit is further configured to receive a domain name resolution response sent by the local DNS server, where the domain name resolution response includes resolution data obtained by resolving the domain name by the local DNS server;

the transceiver unit is further configured to send second information to the central server, where the second information includes the parsed data.

In a fifth aspect, the present application provides a system for data management comprising an apparatus as in the third aspect and an apparatus as in the fourth aspect.

In a sixth aspect, the present application provides an electronic device, including:

a processor adapted to implement computer instructions; the method comprises the steps of,

a memory storing computer instructions adapted to be loaded by a processor and to perform the method of the first aspect, or the method of the second aspect, described above.

In a seventh aspect, embodiments of the present application provide a computer-readable storage medium storing computer instructions that, when read and executed by a processor of a computer device, cause the computer device to perform the method of the first aspect, or the method of the second aspect, described above.

In an eighth aspect, embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from a computer readable storage medium, the processor executes the computer instructions, causing the computer device to perform the method of the first aspect or the method of the second aspect described above.

Based on the technical scheme, the method and the system can realize that the center server transmits the domain name to be resolved to the client detection system and receives the resolved data obtained by resolving the domain name by the client detection system through the local DNS server, and the center server can acquire the domain name resolution condition of the client detection system through processing the resolved data. The DNS analysis data can be collected and processed without arranging DNS detection scripts in different areas by operation and maintenance personnel, so that the embodiment of the application can be beneficial to improving the efficiency of DNS analysis data management.

Drawings

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application;

FIG. 2 is a schematic flow chart of a method of data management according to an embodiment of the application;

FIG. 3A is a schematic diagram of a central server according to an embodiment of the present application;

FIG. 3B is a schematic diagram of a client probe system according to an embodiment of the present application;

FIG. 4A is an example of an interface diagram for a per-day domain name resolution;

FIG. 4B is an example of an interface diagram for a monthly statistical domain name resolution scenario;

FIG. 5 is an example of an interface diagram for counting resolution of domain names by different regions;

FIG. 6 is one example of an interface diagram for configuring a domain name to be resolved;

FIG. 7 is a schematic flow chart diagram of another method of data management provided by an embodiment of the present application;

FIG. 8 is a schematic block diagram of an apparatus for data management according to an embodiment of the present application;

FIG. 9 is a schematic block diagram of another apparatus for data management provided by an embodiment of the present application;

fig. 10 is a schematic block diagram of an electronic device provided by an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

It should be understood that in embodiments of the present application, "B corresponding to a" means that B is associated with a. In one implementation, B may be determined from a. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.

In the description of the present application, unless otherwise indicated, "at least one" means one or more, and "a plurality" means two or more. In addition, "and/or" describes an association relationship of the association object, and indicates that there may be three relationships, for example, a and/or B may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

It should be further understood that the description of the first, second, etc. in the embodiments of the present application is for illustration and distinction of descriptive objects, and is not intended to represent any limitation on the number of devices in the embodiments of the present application, nor is it intended to constitute any limitation on the embodiments of the present application.

It should also be appreciated that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In the following, related terms related to the embodiments of the present application are described.

Domain name system (Domain Name System, DNS): is a core service of the Internet, which is a distributed database that maps domain names and IP addresses to each other, and enables users to access the Internet more conveniently without memorizing IP strings that can be directly read by a machine.

Domain name: the network domain is the name of a computer or computer group on the Internet, which is composed of a series of names separated by points, and is used for locating and identifying the computer during data transmission.

Namespaces of DNS: refers to a collection of names defining all possible domain names, having a hierarchical structure, which can be seen as a tree structure, wherein different nodes can use the same labels. The domain name of a node is made up of marked connections from that node to all nodes of the root, which may be split in dots.

DNS server: the hierarchy of namespaces of a DSN is divided into different regions by its subtrees, each region being seen as a manageable authority responsible for this part of the nodes in the hierarchy. Wherein each zone has a corresponding DNS server on which information contained in each zone is stored. And the DNS server queries the resource record set of the DNS server after receiving the request sent by the user, and returns a resolution result. Here, the resource record may be a binding of domain name to a value, which may represent the result returned by the resolution, e.g. IP address, i.e. the final answer the user wants to get.

dig: is a flexible tool for querying DNS nameservices and can provide queries and displayed answers from the requested return name service DNS.

Software development kit (Software Development Kit, SDK): is a collection of development tools used by software engineers to create application software for a particular software package, software framework, hardware platform, operating system, etc. It may simply be some file providing an application programming interface (Application Program Interface, API) for a certain programming language, but may also include complex hardware capable of communicating with a certain embedded system. SDKs also often include example code, supporting technical notes, or other supporting documents that clarify the suspects for the underlying reference material.

API: is a call interface that the operating system leaves to the application program, which causes the operating system to execute commands (or actions) of the application program by calling the API of the operating system.

Currently, in order to achieve that when a client resolves a domain name of a component, an IP address of a local component server can be resolved, operation and maintenance personnel need to deploy DNS detection scripts in different areas to collect DNS resolved data, automatic reporting and collection of DNS resolved data cannot be achieved, and management efficiency of the data is low.

In view of this, in the method and system for data management according to the embodiments of the present application, a deployed central server issues a domain name to be resolved to a client detection system, and receives resolved data obtained by resolving the domain name by the client detection system through a local DNS server, where the central server can obtain a domain name resolution condition of the client detection system through processing the resolved data. The DNS analysis data can be collected and processed without arranging DNS detection scripts in different areas by operation and maintenance personnel, so that the embodiment of the application can be beneficial to improving the efficiency of DNS analysis data management.

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

As shown in fig. 1, the client probe system comprises a central server, n client probe systems in different areas and a local DNS server corresponding to each client probe system. Optionally, the central server may further include a database and a management page. The central server is used for providing management services of DNS analysis of the n areas, and the client detection system is a client program deployed in different areas.

The client detection system may detect the domain name sent by the central server by using the dig instruction, and return the detected data to the central server, where after the central server receives the detected data returned by the client detection system, the data may be summarized and counted, and finally stored in a database or displayed on a web page through a management page.

By way of example, the client probe system may be deployed on a user device, such as a cell phone, tablet, notebook, palm top, mobile internet device (mobile internet device, MID) or other terminal device with browser-mounted functionality.

The central server may be one or more servers, for example. When the central server is a plurality of servers, at least two servers exist for providing different services and/or at least two servers exist for providing the same service, such as providing the same service in a load balancing manner, embodiments of the present application are not limited in this regard.

The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), basic cloud computing services such as big data and artificial intelligence platforms. Servers may also become nodes of the blockchain.

For example, when the central server has a display function, the management page may be a display page on a display of the central server. For example, the manager may send an instruction to the central server through the management page, or learn about domain name resolution through the management page.

The management page is illustratively a distinct device from the server, and the management page is connected to the central server via a network. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a global system for mobile communications (Global System of Mobile communication, GSM), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA), a 4G network, a 5G network, bluetooth (Bluetooth), wi-Fi, a telephony network, etc.

Fig. 2 shows a schematic interaction flow diagram of a method 200 for data management according to an embodiment of the application. The method 200 may be applied to a DNS monitoring system for monitoring DNS resolution of local components by clients of different areas, which may include a central server and client probing systems of different areas.

Fig. 3A and 3B respectively show a schematic diagram of a central server and a client probing system according to an embodiment of the present application. As shown in fig. 3A, the central server may include modules or units of account management, domain name configuration management, data processing, client APIs, and databases. As shown in fig. 3B, the client probing system may include modules or units for resolving domain name information synchronization, domain name resolution, reporting of domain name resolution results, and the like. The method 200 may be described below in conjunction with fig. 3A and 3B.

As shown in fig. 2, method 200 includes steps 210 through 250.

210, the central server sends first information to the client probe system, where the first information includes a domain name that needs to be resolved.

Here, the domain name to be resolved is the domain name to be resolved by the client probe system. Illustratively, the domain name may be bound to the client system.

Alternatively, the client probing system may be a plurality of client probing systems in a plurality of different regions. For example, an administrator may deploy the client exploration system in different regions as desired.

As an example, the client probe system may be a resident process deployed on machines local to different locales. When the process is first allowed to run, a registration may be performed with the central server in order to allow the central server to perceive that a new client probe system has been deployed. For example, referring to fig. 3A, registration of the client probe system may be accomplished by account registration in account management, which may, for example, accomplish account registration, account information modification, login authentication, account deletion, and the like. When a new domain name to be detected is available later, the method can be synchronized to the client system in time, for example, the step 210 can be implemented by synchronizing domain name information in the client API, and the first information including the domain name to be resolved is sent to the client detection system.

Correspondingly, after the client detection system is successfully connected with the central server, the first information can be received, and the domain name to be resolved is obtained. For example, referring to fig. 3B, resolved domain name information synchronization in the client probing system may receive the first information, e.g., may probe domain names sent by a central server using dig instructions. As an example, the detection time may be 10s.

Optionally, before step 210, the domain name and the IP address that the domain name desires to resolve may also be configured, where the domain name is bound to the client probe system. For example, a manager may configure a domain name to be resolved and an IP address that the domain name desires to resolve (i.e., correspond to) on a management page of a central server. Referring to fig. 3A, the configuration of the domain name and the corresponding IP address may be implemented by domain name configuration management, which may be used to manage addition, deletion, modification, inspection, etc. of the domain name to be probed. Optionally, as shown in fig. 3A, the domain name configuration management may also implement a corresponding operation on the IP address corresponding to the domain name machine by adding a domain name, modifying a domain name, or deleting a domain name.

220, the client probing system sends a domain name resolution request to the local DNS server, where the domain name resolution request may include the domain name to be resolved.

For example, the client probing system may send a domain name resolution request to its local DNS server according to the first information, where the domain name is required to be resolved.

230, the local DNS server sends a domain name resolution response to the client probing system.

For example, after obtaining a domain name to be resolved, the local DNS server may query its own resource record set according to the domain name, and return a resolution result, where resolution data obtained by resolving the domain name, such as an IP address, may be included.

The client probe system sends 240 second information to the central server, including resolution data, such as an IP address and/or time consuming, of the domain name resolved by the local DNS server of the client probe system. For example, the time spent may be obtained by the client probe system, e.g., the time difference between receiving the domain name resolution response and sending the domain name resolution request for the client probe system. As an example, the spent time may be in milliseconds (ms).

For example, referring to fig. 3B, the domain name resolution result reporting module in the client probe system may send the second information to the central server. Correspondingly, referring to fig. 3A, the parsing result in the client API in the central server is reported to obtain the second information.

And 250, the central server processes the second information to obtain the domain name resolution condition.

For example, the central server may determine, according to the IP address that the domain name desires to resolve, whether the IP address obtained by resolving the domain name in the second information is accurate. For example, when the IP address obtained by resolving the domain name in the second information returned by the client detection system is the same as the IP address expected to be resolved by the domain name, it may be determined that the resolution result of the local DNS server of the client detection system on the domain name is correct; when the IP address obtained by resolving the domain name in the second information returned by the client detection system is inconsistent with the IP address expected to be resolved by the domain name, the incorrect resolution result of the local DNS server of the client detection system on the domain name can be determined. In some embodiments, when it is determined that the resolved IP address does not match the IP address desired to be resolved, the second information may be recorded in its entirety, e.g., may be stored separately in a database, and used to alert a manager (e.g., in the form of a mail).

For example, referring to fig. 3A, the resolution result determination unit in the center server may determine whether the IP address in the second information is correct.

Optionally, in the step 250, the central server may obtain at least one piece of the second information sent by the client probing system at different times in the first period, and then determine, according to at least one piece of the second information and the IP address that the domain name is expected to resolve, a success rate of resolving the IP address obtained by resolving the domain name in the first period.

Optionally, when the resolution data further includes a time taken for the local DNS server to resolve the domain name, the central server may further determine an average time required for the local DNS server to resolve the domain name in the first period according to at least one of the second information. For example, referring to fig. 3A, a statistical resolution time-consuming unit in a central server may determine the average time required to resolve a domain name in a certain period.

For example, the first period may be one day, one week or one month, that is, in units of days, weeks or months, and the resolution of the domain name to be monitored in unit time is counted.

Optionally, in the step 250, the central server may further obtain second information sent by the multiple client detection systems in different regions, where the second information may include resolution data of the local servers in the corresponding regions for the same domain name, or different domain names. After collecting the resolved data, the central server may process the resolved data. For example, the central server may count the success rate of domain name resolution by client probe systems in different regions over a unit of time (e.g., a day or a month), as well as the average time required to resolve a domain name. For another example, the central server may count the success rate of a client probe system for a region to resolve different domain names in a unit of time (e.g., a day or a month), as well as the average time required to resolve each domain name.

Therefore, in the embodiment of the application, the domain name to be resolved is issued to the client detection system through the deployed center server, and the resolution data obtained by resolving the domain name through the local DNS server by the client detection system is received, and the center server can acquire the domain name resolution condition of the client detection system through processing the resolution data. The DNS analysis data can be collected and processed without arranging DNS detection scripts in different areas by operation and maintenance personnel, so that the embodiment of the application can be beneficial to improving the efficiency of DNS analysis data management.

Optionally, in the embodiment of the present application, the central server may further store the domain name resolution condition, and/or display the domain name resolution condition. For example, the central server may save the domain name resolution to a database or present the domain name resolution to a manager through a management page. By way of example, a manager may directly access the management interface of the central server through a browser, so that the domain name resolution of each region may be seen.

Fig. 4A shows an example of an interface diagram of a case of resolution of a domain name by day statistics, and fig. 4B shows an example of an interface diagram of a case of resolution of a domain name by month statistics. As shown in fig. 4A and fig. 4B, the interface diagram may show the resolved IP information, the average resolution time, and the resolution success rate corresponding to each domain name.

Fig. 5 shows an example of an interface diagram of the case of resolution of statistical domain names by different regions. As shown in fig. 5, the interface diagram may show the domain name resolution condition in a certain area (such as australian AU) for a period of time (such as one day), such as the resolved IP information, average resolution time and resolution success rate corresponding to each domain name.

In addition, in some embodiments of the present application, the central server may further display an interface for configuring a domain name to be resolved through a management page, where the interface may display information of a client probe system deployed in each region, for example, "JP: XXX.XX.XX.X). Fig. 6 shows an example of the interface through which an administrator can input a domain name to be resolved, an IP address desired to be resolved, and select a corresponding client probing system. After the administrator clicks and submits, the input data can be saved in a background database, and the domain name to be resolved can be synchronized to the corresponding client system. Optionally, the user can edit or delete the configured domain name through the interface.

Fig. 7 shows a specific example of a method for data management according to an embodiment of the present application. It should be understood that this example is for the purpose of facilitating understanding of the method of the embodiments of the present application, and is not intended to limit the embodiments of the present application in any way. As shown in fig. 7, the method of data management includes steps 701 to 708.

701, the client probe system establishes a connection with a central server.

And 702, pushing the domain name which is required to be resolved by the client detection system by the central server according to the domain name configured by the administrator.

703, after receiving the domain name to be detected, the client detection system requests the local DNS server to resolve the domain name. For example, the client probing system may interact with a local DNS server using dig instructions for domain name resolution.

The local DNS server returns 704 the resolved results to the client probing system.

705, the client detection system pushes the analysis result and the analysis time to the center server.

Illustratively, the resolution time is the time it takes for the client probe system to resolve the domain name. The parsing time can be obtained by the client through monitoring, and is not limited.

706, the central server performs data processing.

Illustratively, the central server begins processing the parsed data pushed by the client probe system after receiving the data. For example, the central server may determine whether the IP address obtained by parsing is consistent with the IP address desired to be parsed, and if so, may count the result and store it in the database; if the error causes are inconsistent, the statistics result can be recorded and stored in a database.

707, the management page shows domain name resolution conditions, such as IP addresses obtained by domain name resolution of different time units and different areas, average resolution time, resolution success rate, and the like.

At 708, the administrator logs into the central server to view the domain name resolution.

For example, the administrator may log in to a presentation page of the central server to view the resolution of the domain name.

Therefore, by the scheme provided by the embodiment of the application, the DNS analysis conditions of different areas can be integrated into one system, and the analysis conditions of domain names of all areas can be managed and queried, so that a manager can quickly know the DNS analysis conditions of all areas. If the resolution success rate of the regional client exploration system is too low, then a countermeasures can be specified to avoid affecting the experience of the local user.

The embodiment of the application can be applied to game scenes. By means of the method, the server and the client detection system, monitoring of DNS analysis conditions of game clients of players in different areas can be achieved through deployment of a central server and client detection systems in different areas, and accordingly the fact that the game clients can be correctly connected to the server of a local component when the players use the game clients can be guaranteed. In addition, if the domain name resolution success rate of the regional game client is too low, a countermeasures can be specified to avoid affecting the gaming experience of the regional player.

The specific embodiments of the present application have been described in detail above with reference to the accompanying drawings, but the present application is not limited to the specific details of the above embodiments, and various simple modifications can be made to the technical solution of the present application within the scope of the technical concept of the present application, and all the simple modifications belong to the protection scope of the present application. For example, the specific features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various possible combinations are not described further. As another example, any combination of the various embodiments of the present application may be made without departing from the spirit of the present application, which should also be regarded as the disclosure of the present application.

It should be further understood that, in the various method embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application. It is to be understood that the numbers may be interchanged where appropriate such that the described embodiments of the application may be practiced otherwise than as shown or described.

The method embodiments of the present application are described above in detail, and the apparatus embodiments of the present application are described below in conjunction with fig. 8 to 10.

Fig. 8 is a schematic block diagram of an apparatus 600 for domain name system data management in accordance with an embodiment of the present application. The apparatus 600 may be, for example, a central server as above. As shown in fig. 8, the data management apparatus 600 may include a transceiving unit 610 and a processing unit 620.

A transceiver unit 610, configured to send first information to a client detection system, where the first information includes a domain name to be resolved;

the transceiver unit 610 is further configured to receive second information sent by the client detection system, where the second information includes resolution data obtained by resolving the domain name by a local DNS server of the client detection system;

and a processing unit 620, configured to process the second information to obtain a domain name resolution of the client detection system.

In some alternative embodiments, the parsed data includes an IP address and/or takes time.

In some optional embodiments, the processing unit 620 is specifically configured to determine, according to the IP address that the domain name desires to resolve, whether the IP address obtained by resolving the domain name in the second information is accurate.

In some optional embodiments, the processing unit 620 is specifically configured to obtain at least one of the second information sent by the client probing system at different times in the first period;

and determining the success rate of the IP address obtained by analyzing the domain name in the first period according to at least one piece of second information and the IP address expected to be analyzed by the domain name.

In some alternative embodiments, processing unit 620 is further configured to determine an average time required for the local DNS server to resolve the domain name in the first cycle based on at least one of the second information.

In some alternative embodiments, the client probe system is a client probe system of a plurality of different regions.

In some alternative embodiments, processing unit 620 is further configured to configure the domain name and the IP address that the domain name desires to resolve, wherein the domain name and the client probe system are bound.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. To avoid repetition, no further description is provided here. Specifically, the apparatus 600 for data management in this embodiment may correspond to a central server executing the method 200 of the embodiment of the present application, and the foregoing and other operations and/or functions of each module in the apparatus 600 are respectively for implementing the corresponding procedures of the central server in each method 200 above, which are not described herein for brevity.

Fig. 9 is a schematic block diagram of an apparatus 700 for domain name system data management in accordance with an embodiment of the present application. The apparatus 700 may be, for example, the client probe system above. As shown in fig. 9, the data management apparatus 700 may include a transceiving unit 710. Optionally, the apparatus 700 may further comprise a processing unit 720.

A transceiver unit 710, configured to receive first information sent by a central server, where the first information includes a domain name to be resolved;

the transceiver unit 710 is further configured to send a domain name resolution request to a local DNS server according to the first information;

the transceiver unit 710 is further configured to receive a domain name resolution response sent by the local DNS server, where the domain name resolution response includes resolution data obtained by resolving the domain name by the local DNS server;

the transceiver unit 710 is further configured to send second information to the central server, where the second information includes the parsed data.

Alternatively, the processing unit 720 may be configured to generate the domain name resolution request according to the first information, and generate the second information according to the resolution data.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. To avoid repetition, no further description is provided here. Specifically, the apparatus 700 for data management in this embodiment may correspond to a client probe system performing the method 200 of the embodiment of the present application, and the foregoing and other operations and/or functions of each module in the apparatus 700 are respectively for implementing the corresponding flow of the client probe system in each method 200 above, which is not described herein for brevity.

The embodiment of the application also provides a data management system, which comprises the data management device 600 and the data management device 700.

The apparatus and system of embodiments of the present application are described above in terms of functional modules in connection with the accompanying drawings. It should be understood that the functional module may be implemented in hardware, or may be implemented by instructions in software, or may be implemented by a combination of hardware and software modules. Specifically, each step of the method embodiment in the embodiment of the present application may be implemented by an integrated logic circuit of hardware in a processor and/or an instruction in a software form, and the steps of the method disclosed in connection with the embodiment of the present application may be directly implemented as a hardware decoding processor or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in a well-established storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory, and the processor reads information in the memory, and in combination with hardware, performs the steps in the above method embodiments.

Fig. 10 is a schematic block diagram of an electronic device 800 provided by an embodiment of the application.

As shown in fig. 10, the electronic device 800 may include:

a memory 810 and a processor 820, the memory 810 being for storing a computer program and transmitting the program code to the processor 820. In other words, the processor 820 may call and run a computer program from the memory 810 to implement the methods in embodiments of the present application.

For example, the processor 820 may be configured to perform the corresponding steps of the central server in the method 200 described above, or the corresponding steps of the client probe system, according to instructions in the computer program.

In some embodiments of the application, the processor 820 may include, but is not limited to:

a general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like.

In some embodiments of the application, the memory 810 includes, but is not limited to:

volatile memory and/or nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct memory bus RAM (DR RAM).

In some embodiments of the application, the computer program may be partitioned into one or more modules that are stored in the memory 810 and executed by the processor 820 to perform the encoding methods provided by the present application. The one or more modules may be a series of computer program instruction segments capable of performing the specified functions, which are used to describe the execution of the computer program in the electronic device 800.

Optionally, the electronic device 800 may further include:

a transceiver 830, the transceiver 830 being connectable to the processor 820 or the memory 810.

Processor 820 may control transceiver 830 to communicate with other devices, and in particular, may send information or data to other devices or receive information or data sent by other devices. Transceiver 830 may include a transmitter and a receiver. Transceiver 830 may further include antennas, the number of which may be one or more.

It should be appreciated that the various components in the electronic device 800 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

According to an aspect of the present application, there is provided a communication device comprising a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, such that the encoder performs the method of the above-described method embodiment.

According to an aspect of the present application, there is provided a computer storage medium having stored thereon a computer program which, when executed by a computer, enables the computer to perform the method of the above-described method embodiments. Alternatively, embodiments of the present application also provide a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method of the method embodiments described above.

According to another aspect of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium and executes the computer instructions to cause the computer device to perform the method of the above-described method embodiments.

In other words, when implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, functional modules in various embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of data management, applied to a central server, the method comprising:

Receiving second information sent by the client detection system, wherein the second information comprises analysis data obtained by analyzing the domain name by a local Domain Name System (DNS) server of the client detection system;

2. The method according to claim 1, wherein the parsed data includes an IP address and/or takes time.

3. The method according to claim 1 or 2, wherein the processing the second information to obtain a domain name resolution of the client probe system includes:

and determining whether the IP address obtained by analyzing the domain name in the second information is accurate according to the IP address expected to be analyzed by the domain name.

4. The method according to claim 1 or 2, wherein the processing the second information to obtain a domain name resolution of the client probe system includes:

acquiring at least one piece of second information sent by the client detection system at different times in a first period;

5. The method as recited in claim 4, further comprising:

and determining the average time required by the local DNS server to resolve the domain name in the first period according to at least one piece of second information.

6. The method of any of claims 1-5, wherein the client probe system is a client probe system of a plurality of different regions.

7. The method according to any one of claims 1-6, wherein the sending the first information to the client probe system, before the first information includes the domain name to be resolved, further includes:

and configuring the domain name and the IP address which the domain name desires to resolve, wherein the domain name is bound with the client detection system.

8. A method of data management, for application to a client probe system, the method comprising:

according to the first information, a domain name resolution request is sent to a local Domain Name System (DNS) server;

9. An apparatus for data management, comprising:

the receiving and transmitting unit is further configured to receive second information sent by the client detection system, where the second information includes resolution data obtained by resolving the domain name by a DNS server of a local domain name system of the client detection system;

10. An apparatus for data management, comprising:

the receiving and transmitting unit is further configured to send a domain name resolution request to a DNS server of the local domain name system according to the first information;

11. A system for data management comprising the apparatus of claim 9 and the apparatus of claim 10.

12. An electronic device comprising a processor and a memory, the memory having instructions stored therein that when executed by the processor cause the processor to perform the method of any of claims 1-8.

13. A computer storage medium for storing a computer program, the computer program comprising instructions for performing the method of any one of claims 1-8.

14. A computer program product comprising computer program code which, when run by an electronic device, causes the electronic device to perform the method of any one of claims 1-8.