Method, device, system, electronic device and storage medium for data management

Abstract

The application provides a data management method, device, system, equipment and storage medium. The method comprises the following steps: a central server sends first information to a client detection system, wherein the first information comprises a domain name to be resolved; the central server receives second information sent by the client detection system, wherein the second information comprises resolution data obtained by a local DNS server of the client detection system when resolving the domain name; and the central server processes the second information to obtain the resolution of the domain name of the client detection system. Since the embodiment of the application can realize the collection and processing of DNS resolution data without deploying DNS detection scripts in different regions by operation and maintenance personnel, the embodiment of the application can help to improve the efficiency of DNS resolution data management.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to methods, apparatus, systems, electronic devices, and storage media for data management. Background Technology

[0002] To ensure a consistent user experience and meet local compliance requirements for Internet users across different countries and regions, relevant component servers need to be deployed locally or regionally. Therefore, it is essential to guarantee that users can correctly connect to the local component server when using various client applications. For this to work, the client must resolve the component's domain name to the local component server's Internet Protocol (IP) address.

[0003] To achieve the above goals, it is necessary to understand or monitor the DNS resolution status of each region. However, currently, to collect DNS resolution data in different regions, operations and maintenance personnel need to deploy DNS probe scripts in different regions, which cannot achieve automatic reporting and collection of DNS resolution data, resulting in low data management efficiency. Summary of the Invention

[0004] This application provides a data management method, apparatus, device, and storage medium that can help improve the efficiency of domain name management.

[0005] Firstly, a data management method is provided, including:

[0006] Send the first information to the client detection system, the first information including the domain name to be resolved;

[0007] The system receives second information sent by the client detection system, the second information including the resolution data obtained by the local DNS server of the client detection system for resolving the domain name;

[0008] The second information is processed to obtain the domain name resolution information of the client detection system.

[0009] Secondly, a data management method is provided, including:

[0010] The first information sent by the receiving center server includes the domain name that needs to be resolved;

[0011] Based on the first information, send a domain name resolution request to the local DNS server;

[0012] Receive a domain name resolution response sent by the local DNS server, the domain name resolution response including the resolution data obtained by the local DNS server in resolving the domain name;

[0013] Send a second message to the central server, the second message including the parsed data.

[0014] Thirdly, a data management apparatus is provided, comprising:

[0015] The transceiver unit is used to send first information to the client probing system, the first information including the domain name to be resolved;

[0016] The transceiver unit is also used to receive second information sent by the client detection system, the second information including the resolution data obtained by the local DNS server of the client detection system for resolving the domain name;

[0017] The processing unit is used to process the second information and obtain the domain name resolution information of the client detection system.

[0018] A fourth method provides a data management apparatus, comprising:

[0019] The transceiver unit is used to receive first information sent by the central server, the first information including the domain name to be resolved;

[0020] The transceiver unit is further configured to send a domain name resolution request to the local DNS server based on the first information;

[0021] The transceiver unit is also used to receive a domain name resolution response sent by the local DNS server, the domain name resolution response including the resolution data obtained by the local DNS server in resolving the domain name;

[0022] The transceiver unit is also used to send second information to the central server, the second information including the parsed data.

[0023] Fifthly, this application provides a data management system, including the apparatus as described in the third aspect and the apparatus as described in the fourth aspect.

[0024] Sixthly, this application provides an electronic device, comprising:

[0025] Processor, adapted to implement computer instructions; and,

[0026] The memory stores computer instructions adapted for loading by a processor and executing the method of the first aspect above, or the method of the second aspect above.

[0027] In a seventh aspect, embodiments of this 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.

[0028] Eighthly, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and 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.

[0029] Based on the above technical solution, the central server can send the domain names to be resolved to the client probing system, and receive the resolution data obtained by the client probing system through the local DNS server. By processing this resolution data, the central server can obtain the domain name resolution status of the client probing system. Since the collection and processing of DNS resolution data can be achieved without requiring maintenance personnel to deploy DNS probing scripts in different regions, this embodiment can help improve the efficiency of DNS resolution data management. Attached Figure Description

[0030] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application;

[0031] Figure 2 This is a schematic flowchart illustrating a data management method according to an embodiment of this application;

[0032] Figure 3A A schematic diagram of a central server provided in an embodiment of this application;

[0033] Figure 3B A schematic diagram of the client detection system provided in the embodiments of this application;

[0034] Figure 4A This is an example of a screenshot showing the daily DNS resolution statistics.

[0035] Figure 4B This is an example of a screenshot showing the monthly statistics of domain name resolution.

[0036] Figure 5 This is an example of an interface that displays statistics on domain name resolution by different regions.

[0037] Figure 6 An example of a graphical interface for configuring a domain name resolution interface;

[0038] Figure 7 A schematic flowchart illustrating another data management method provided in an embodiment of this application;

[0039] Figure 8 A schematic block diagram of a data management device provided for embodiments of this application;

[0040] Figure 9 A schematic block diagram of another data management apparatus provided for embodiments of this application;

[0041] Figure 10 This is a schematic block diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0042] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0043] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A. In one implementation, B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0044] In the description of this application, unless otherwise stated, "at least one" means one or more, and "multiple" means two or more. Additionally, "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0045] It should also be understood that the descriptions of "first", "second", etc. appearing in the embodiments of this application are only for illustration and to distinguish the objects being described, and there is no order to them. They do not indicate any special limitation on the number of devices in the embodiments of this application, and cannot constitute any limitation on the embodiments of this application.

[0046] It should also be understood that specific features, structures, or characteristics relating to embodiments in the specification are included in at least one embodiment of this application. Furthermore, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0047] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such processes, methods, products, or devices.

[0048] The following describes the relevant terms used in the embodiments of this application.

[0049] Domain Name System (DNS): A core service of the Internet, it is a distributed database that maps domain names to IP addresses, enabling users to access the Internet more conveniently without having to remember the IP address strings that can be directly read by machines.

[0050] Domain name: also known as a network domain, is the name of a computer or group of computers on the Internet, consisting of a string of names separated by dots. It is used to locate and identify the computer during data transmission.

[0051] DNS namespace: refers to the set of names that defines all possible domain names. It has a hierarchical structure and can be viewed as a tree structure, where different nodes can use the same tags. The domain name of a node is composed of the tags of all nodes from that node to the root, which can be separated by dots.

[0052] DNS Servers: The hierarchical structure of a DNS namespace is divided into different zones according to its subtrees. Each zone can be viewed as a manageable authority entity responsible for that part of the nodes in the hierarchy. Each zone has a corresponding DNS server, and the information contained within each zone is stored on that DNS server. When a DNS server receives a request from a user, it queries its own set of resource records and returns the resolution result. Here, the resource record can be a domain name-to-value binding, and the value can represent the result returned by the resolution, such as an IP address, which is the final answer the user wants.

[0053] dig is a flexible tool that queries the DNS domain name service and provides the query results from the requested DNS, returning the DNS name service's DNS information.

[0054] A Software Development Kit (SDK) is a collection of development tools used by software engineers to create application software for specific software packages, frameworks, hardware platforms, operating systems, etc. It can be as simple as some documentation providing an Application Programming Interface (API) for a programming language, but may also include complex hardware capable of communicating with an embedded system. SDKs often also include sample code, supporting technical annotations, or other supporting documentation to clarify any ambiguities in basic reference materials.

[0055] API: An API is a calling interface provided by the operating system for applications. Applications call the operating system's API to make the operating system execute the application's commands (or actions).

[0056] Currently, in order for clients to resolve the IP address of the local component server when resolving the domain name of a component, operations and maintenance personnel need to deploy DNS probe scripts in different regions to collect DNS resolution data. This does not enable automatic reporting and collection of DNS resolution data, resulting in low data management efficiency.

[0057] In view of this, this application provides a data management method and system. A central server distributes the domain name to be resolved to a client probing system and receives the resolution data obtained by the client probing system through a local DNS server. The central server processes this resolution data to obtain the domain name resolution status of the client probing system. Since the collection and processing of DNS resolution data does not require maintenance personnel to deploy DNS probing scripts in different regions, this application can help improve the efficiency of DNS resolution data management.

[0058] Figure 1 This is a schematic diagram of an application scenario involved in an embodiment of this application.

[0059] like Figure 1 As shown, it includes a central server, n client detection systems in different regions, and a local DNS server corresponding to each client detection system. Optionally, the central server may also include a database and a management page. The central server provides management services for DNS resolution in the n regions, and the client detection systems are client programs deployed locally in different regions.

[0060] For example, the client probing system can use the dig command to probe the domain name sent by the central server and return the probed data to the central server. After receiving the probe data returned by the client probing system, the central server can summarize and statistically analyze the data and finally save it in the database or display it on the webpage through the management page.

[0061] For example, the client detection system can be deployed on user devices, such as mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), or other terminal devices with browser installation capabilities.

[0062] For example, the central server can be one or more servers. When there are multiple central servers, at least two servers are used to provide different services, and / or at least two servers are used to provide the same service, such as providing the same service in a load-balanced manner. This application embodiment does not limit this.

[0063] The aforementioned servers can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. Servers can also serve as nodes in a blockchain.

[0064] For example, when the central server has a display function, the management page can be a display page on the central server's monitor. For example, administrators can send instructions to the central server through the management page, or obtain information about domain name resolution through the management page.

[0065] For example, the management page and the server are different devices, and the management page is connected to the central server via a network. The network can be an intranet, the Internet, Global System for Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), 4G network, 5G network, Bluetooth, Wi-Fi, voice network, or other wireless or wired networks.

[0066] Figure 2This illustration shows a schematic interactive flowchart of a data management method 200 provided in an embodiment of this application. Method 200 can be applied to a DNS monitoring system to monitor the DNS resolution behavior of clients in different regions to local components. The DNS monitoring system may include a central server and client detection systems in different regions.

[0067] Figure 3A and Figure 3B A schematic diagram of the central server and client detection system provided in an embodiment of this application is shown. Figure 3A As shown, the central server may include modules or units such as account management, domain name configuration management, data processing, client API, and database. Figure 3B As shown, a client-side detection system can include modules or units such as domain name information synchronization, domain name resolution, and domain name resolution result reporting. The following can be combined with... Figure 3A and Figure 3B Method 200 is described.

[0068] like Figure 2 As shown, method 200 includes steps 210 to 250.

[0069] 210. The central server sends the first information to the client probing system, which includes the domain name that needs to be resolved.

[0070] Here, the domain name that needs to be resolved is the same domain name that the client detection system needs to resolve. For example, this domain name can be bound to the client system.

[0071] Optionally, the aforementioned client detection system can be multiple client detection systems in multiple different regions. For example, an administrator can deploy client detection systems in different regions as needed.

[0072] As an example, a client detection system could be a resident process deployed on local machines in different regions. When this process is first allowed to run, it can register with a central server, allowing the central server to become aware that a new client detection system has been deployed. See also [example description missing]. Figure 3A The client probing system can be registered through account registration in account management. Account management includes functions such as account registration, account information modification, login authentication, and account deletion. When new domains need to be probed, they can be promptly synchronized to the client system. For example, step 210 above can be achieved through domain information synchronization in the client API, sending the first information containing the domains to be resolved to the client probing system.

[0073] Accordingly, once the client detection system successfully connects to the central server, it can receive the aforementioned first piece of information and obtain the domain name that needs to be resolved. For example, see... Figure 3B The client-side probe system can receive this initial information by synchronizing the domain name resolution information. For example, it can use the `dig` command to probe the domain name sent by the central server. As an example, the probe time can be 10 seconds.

[0074] Optionally, before step 210, the domain name and the IP address it is expected to resolve to can be configured, whereby the domain name is bound to the client detection system. For example, administrators can configure the domain name to be resolved and the IP address it is expected to resolve to (i.e., the corresponding IP address) on the central server's management page. See also... Figure 3A Domain configuration management allows for the configuration of domain names and their corresponding IP addresses. This management function can be used to manage the addition, deletion, modification, and querying of domain names that need to be probed. Optional features include... Figure 3A As shown, domain configuration management also allows you to add, modify, or delete domains to perform operations on the corresponding IP addresses of the domain machines.

[0075] 220. The client probing system sends a domain name resolution request to the local DNS server. This domain name resolution request may include the domain name that needs to be resolved.

[0076] For example, the client detection system can send a domain name resolution request to its local DNS server based on the first information mentioned above, including the domain name to be resolved.

[0077] 230. The local DNS server sends a domain name resolution response to the client's probing system.

[0078] For example, after obtaining the domain name that needs to be resolved, the local DNS server can query its own set of resource records based on the domain name and return the resolution result, which may include the resolution data obtained by resolving the domain name, such as the IP address.

[0079] 240. The client probing system sends a second piece of information to the central server, including the resolution data obtained by the client probing system's local DNS server in resolving the domain name, such as the IP address and / or the time taken. For example, the time taken can be obtained by the client probing system, such as the time difference between the client probing system receiving the domain name resolution response and sending the domain name resolution request. As an example, the time taken can be in milliseconds (ms).

[0080] For example, see Figure 3B The domain name resolution result reporting module in the client-side detection system can send this second piece of information to the central server. See also... Figure 3AThe second piece of information is obtained by reporting the parsing results from the client API in the central server.

[0081] 250. The central server processes the second piece of information to obtain the domain name resolution status.

[0082] For example, the central server can determine whether the IP address obtained by resolving the domain name in the second information is accurate based on the IP address that the domain name is expected to resolve to. For instance, if the IP address obtained by resolving the domain name in the second information returned by the client probing system is the same as the IP address that the domain name is expected to resolve to, it can be determined that the local DNS server of the client probing system has resolved the domain name correctly; if the IP address obtained by resolving the domain name in the second information returned by the client probing system is inconsistent with the IP address that the domain name is expected to resolve to, it can be determined that the local DNS server of the client probing system has resolved the domain name incorrectly. In some embodiments, when it is determined that the resolved IP address is inconsistent with the expected IP address, all of the second information can be recorded, for example, stored separately in a database, and used to issue a warning to administrators (e.g., in the form of an email).

[0083] For example, see Figure 3A The resolution result determination unit in the central server can determine whether the IP address in the second information is correct.

[0084] Optionally, in step 250, the central server can obtain at least one of the second information sent by the client probe system at different times during the first period, and then determine the success rate of resolving the IP address obtained by the domain name within the first period based on at least one of the second information and the IP address that the domain name is expected to resolve.

[0085] Optionally, when the resolution data also includes the time spent by the local DNS server resolving the domain name, the central server can also determine the average time required for the local DNS server to resolve the domain name during the first cycle, based on at least one of the second pieces of information. For example, see... Figure 3A The statistical resolution time unit in the central server can determine the average time required to resolve a domain name in a certain period.

[0086] For example, the first period can be one day, one week, or one month, that is, the resolution status of the domains to be monitored within a unit of time, measured in days, weeks, or months.

[0087] Optionally, in step 250, the central server can also obtain second information sent by multiple client probing systems in different regions. This second information may include resolution data of the local servers in the corresponding regions for the same or different domain names. After collecting this resolution data, the central server can process it. For example, the central server can statistically analyze the success rate of domain name resolution by client probing systems in different regions, as well as the average time required to resolve the domain name, within a given time unit (e.g., a day or a month). Alternatively, the central server can statistically analyze the success rate of domain name resolution by client probing systems in one region, as well as the average time required to resolve each domain name, within a given time unit (e.g., a day or a month).

[0088] Therefore, this embodiment of the application sends the domain name to be resolved to the client probing system through a central server, and receives the resolution data obtained by the client probing system through the local DNS server. The central server, by processing this resolution data, can obtain the domain name resolution status of the client probing system. Since the collection and processing of DNS resolution data can be achieved without requiring maintenance personnel to deploy DNS probing scripts in different regions, this embodiment of the application can help improve the efficiency of DNS resolution data management.

[0089] Optionally, in this embodiment, the central server may also store and / or display domain name resolution information. For example, the central server may store the domain name resolution information in a database or display it to administrators through a management page. For instance, administrators can directly access the central server's management interface through a browser to view the domain name resolution information for different regions.

[0090] Figure 4A This is an example of a graphical interface that displays daily statistics on domain name resolution. Figure 4B This shows an example of a user interface that displays monthly statistics on domain name resolution. Figure 4A and Figure 4B As shown in the diagram, the interface displays the IP information resolved to each domain name, the average resolution time, and the resolution success rate.

[0091] Figure 5 This is an example of a graphical interface that displays statistics on domain name resolution by different regions. Figure 5 As shown, the interface can display the domain name resolution status of a certain region (such as Australia AU) over a period of time (such as one day), including the IP information resolved to each domain name, the average resolution time, and the resolution success rate.

[0092] In addition, in some embodiments of this application, the central server can also display an interface for configuring the domain names that need to be resolved through a management page. This interface can display information about the client detection system deployed in each region, such as "JP: XXX.XX.XX.X". Figure 6 The example interface shown allows administrators to input the domain name to be resolved, the desired IP address, and select the corresponding client detection system. After clicking submit, the entered data is saved to the backend database, and the domain name to be resolved is synchronized to the corresponding client system. Optionally, users can also edit or delete configured domain names through this interface.

[0093] Figure 7 This illustration shows a specific example of a data management method provided in an embodiment of this application. It should be understood that this example is for ease of understanding of the method in this application and does not constitute any limitation on the embodiments of this application. Figure 7 As shown, the data management method includes steps 701 to 708.

[0094] 701, The client detection system establishes a connection with the central server.

[0095] 702. The central server pushes the domain name that the client's detection system needs to resolve, based on the domain name configured by the administrator.

[0096] 703. After receiving the domain name to be probed, the client-side probing system requests the local DNS server to resolve the domain name. For example, the client-side probing system can use the `dig` command to interact with the local DNS server for domain name resolution.

[0097] 704, the local DNS server returns the resolution result to the client's probing system.

[0098] 705, the client detection system will push the parsing results and parsing time to the central server.

[0099] For example, this resolution time is the time spent by the client's detection system resolving the domain name. This resolution time can be obtained by the client through monitoring and is not limited to this.

[0100] 706, the central server processes the data.

[0101] For example, after receiving the parsed data pushed by the client's probing system, the central server begins processing the data. For instance, the central server can determine whether the resolved IP address matches the expected IP address. If they match, the server can statistically analyze the results and store them in the database; if they do not match, the server can record the reason for the error, statistically analyze the results, and store them in the database.

[0102] 707 indicates that the management page displays domain name resolution information, such as the IP addresses obtained from domain name resolution in different time units and regions, average resolution time, and resolution success rate.

[0103] 708. Administrators log in to the central server to check the domain name resolution status.

[0104] For example, administrators can log in to the central server's display page to view the domain name resolution status.

[0105] Therefore, the solution provided in this application embodiment can integrate DNS resolution information from different regions into a single system, facilitating the management and querying of domain name resolution status in various locations. This allows administrators to quickly understand the DNS domain name resolution situation in each region. If the resolution success rate of the client detection system in a certain region is too low, a contingency plan can be specified to avoid impacting the experience of local users.

[0106] This application's embodiments can be applied to gaming scenarios. For example, by deploying a central server and client detection systems in different regions, the DNS resolution status of game clients from different regions can be monitored, ensuring that the game client can correctly connect to the local component's server when players use it. Furthermore, if a region's game client has a low domain name resolution success rate, a solution can be specified to avoid impacting the gaming experience of players in that region.

[0107] The specific embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application.

[0108] It should also be understood that, in the various method embodiments of this application, the sequence numbers of the above processes do not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. It should be understood that these sequence numbers can be interchanged where appropriate so that the embodiments of this application described can be implemented in a sequence other than those illustrated or described.

[0109] The method embodiments of this application have been described in detail above. The following description, in conjunction with... Figures 8 to 10This describes an embodiment of the apparatus described in this application.

[0110] Figure 8 This is a schematic block diagram of a Domain Name System (DNS) data management apparatus 600 according to an embodiment of this application. The apparatus 600 may, for example, be the central server mentioned above. Figure 8 As shown, the data management device 600 may include a transceiver unit 610 and a processing unit 620.

[0111] The transceiver unit 610 is used to send first information to the client probing system, the first information including the domain name to be resolved;

[0112] The transceiver unit 610 is further configured to receive second information sent by the client detection system, the second information including the resolution data obtained by the local DNS server of the client detection system for resolving the domain name;

[0113] The processing unit 620 is used to process the second information and obtain the domain name resolution status of the client detection system.

[0114] In some alternative embodiments, the parsed data includes IP address and / or time spent.

[0115] In some optional embodiments, the processing unit 620 is specifically used to determine whether the IP address obtained by resolving the domain name in the second information is accurate based on the IP address that the domain name is expected to resolve to.

[0116] In some optional embodiments, the processing unit 620 is specifically used to acquire at least one of the second information sent by the client detection system at different times during the first period;

[0117] Based on at least one of the second pieces of information and the IP address that the domain name is expected to resolve to, determine the success rate of resolving the IP address obtained by resolving the domain name within the first period.

[0118] In some optional embodiments, the processing unit 620 is further configured to determine, based on at least one of the second pieces of information, the average time required for the local DNS server to resolve the domain name in the first period.

[0119] In some alternative embodiments, the client detection system is a client detection system in multiple different regions.

[0120] In some optional embodiments, the processing unit 620 is further configured to configure the domain name and the IP address that the domain name is expected to resolve to, wherein the domain name is bound to the client detection system.

[0121] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, they will not be repeated here. Specifically, in this embodiment, the data management device 600 can correspond to the central server executing the method 200 of the embodiments of this application, and the foregoing and other operations and / or functions of each module in the device 600 are respectively for implementing the corresponding processes of the central server in each method 200 above. For the sake of brevity, they will not be repeated here.

[0122] Figure 9 This is a schematic block diagram of a Domain Name System (DNS) data management apparatus 700 according to an embodiment of this application. The apparatus 700 can, for example, be the client detection system described above. Figure 9 As shown, the data management device 700 may include a transceiver unit 710. Optionally, the device 700 may also include a processing unit 720.

[0123] The transceiver unit 710 is used to receive first information sent by the central server, the first information including the domain name to be resolved;

[0124] The transceiver unit 710 is further configured to send a domain name resolution request to the local DNS server based on the first information;

[0125] The transceiver unit 710 is further configured to receive a domain name resolution response sent by the local DNS server, the domain name resolution response including the resolution data obtained by the local DNS server in resolving the domain name;

[0126] The transceiver unit 710 is also used to send second information to the central server, the second information including the parsed data.

[0127] Optionally, the processing unit 720 can be used to generate the domain name resolution request based on the first information, and to generate the second information based on the resolution data.

[0128] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, they will not be repeated here. Specifically, in this embodiment, the data management device 700 can correspond to the client detection system that executes the method 200 of the present application embodiments, and the foregoing and other operations and / or functions of each module in the device 700 are respectively for implementing the corresponding processes of the client detection system in each of the methods 200 above. For the sake of brevity, they will not be repeated here.

[0129] This application also provides a data management system, including the data management device 600 and the data management device 700 described above.

[0130] The apparatus and system of this application embodiments have been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that these functional modules can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the methods disclosed in this application embodiments can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0131] like Figure 10 This is a schematic block diagram of the electronic device 800 provided in the embodiments of this application.

[0132] like Figure 10 As shown, the electronic device 800 may include:

[0133] The system includes a memory 810 and a processor 820. The memory 810 stores computer programs and transfers the program code to the processor 820. In other words, the processor 820 can retrieve and run the computer program from the memory 810 to implement the methods described in the embodiments of this application.

[0134] For example, the processor 820 can be used to execute the corresponding steps of the central server or the corresponding steps of the client probe system in the method 200 described above, according to the instructions in the computer program.

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

[0136] General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

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

[0138] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0139] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 810 and executed by the processor 820 to complete the encoding method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the electronic device 800.

[0140] Optionally, the electronic device 800 may also include:

[0141] Transceiver 830, which can be connected to processor 820 or memory 810.

[0142] The processor 820 can control the transceiver 830 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include antennas, and the number of antennas may be one or more.

[0143] It should be understood that the various components in the electronic device 800 are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.

[0144] According to one aspect of this application, a communication device is provided, including a processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory, causing the encoder to perform the method of the above-described method embodiment.

[0145] According to one aspect of this application, a computer storage medium is provided that stores a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0146] According to another aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method described in the above-described method embodiments.

[0147] In other words, when implemented using software, it can be implemented wholly or partially in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0148] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0149] In the several embodiments provided in this application, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or modules may be electrical, mechanical, or other forms.

[0150] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0151] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data management method, characterized in that, Applied to a central server, the method includes: The system sends first information to the client detection system, the first information including the domain name to be resolved; wherein, the client detection system is a resident process deployed on local machines in different regions and has been registered with the central server; the domain name is bound to the client detection system; The system receives second information sent by the client detection system, the second information including the resolution data obtained by the local Domain Name System (DNS) server of the client detection system from resolving the domain name; The second information is processed to obtain the domain name resolution information of the client detection system; The step of processing the second information to obtain the domain name resolution information of the client detection system includes: Based on the IP address that the domain name is expected to resolve to, determine whether the IP address obtained by resolving the domain name in the second information is accurate; The step of sending the first information to the client detection system, which includes the domain name to be resolved, also includes: Configure the domain name and the IP address that the domain name is expected to resolve to.

2. The method according to claim 1, characterized in that, The parsed data includes IP address and / or time spent.

3. The method according to claim 1, characterized in that, The step of processing the second information to obtain the domain name resolution information of the client detection system includes: Obtain at least one of the second pieces of information sent by the client detection system at different times during the first period; Based on at least one of the second pieces of information and the IP address that the domain name is expected to resolve to, determine the success rate of resolving the IP address obtained by resolving the domain name within the first period.

4. The method according to claim 3, characterized in that, Also includes: Based on at least one of the second pieces of information, determine the average time required for the local DNS server to resolve the domain name during the first period.

5. The method according to any one of claims 1-4, characterized in that, The client detection system consists of multiple client detection systems located in different regions.

6. A data management device, characterized in that, include: The transceiver unit is used to send first information to the client detection system, the first information including the domain name to be resolved; wherein, the client detection system is a resident process deployed on local machines in different regions and has been registered with the central server; the domain name is bound to the client detection system; The transceiver unit is also used to receive second information sent by the client detection system, the second information including the resolution data obtained by the local domain name system DNS server of the client detection system for resolving the domain name; The processing unit is used to process the second information and obtain the domain name resolution status of the client detection system; The processing unit is specifically used to determine whether the IP address obtained by resolving the domain name in the second information is accurate, based on the IP address that the domain name is expected to resolve to. The configuration unit is used to configure the domain name and the IP address that the domain name is expected to resolve to before sending the first information to the client probe system.

7. An electronic device, characterized in that, The method includes a processor and a memory, wherein the memory stores instructions, and when the processor executes the instructions, it causes the processor to perform the method according to any one of claims 1-5.

8. A computer storage medium, characterized in that, Used for storing computer programs, said computer programs including methods for performing any one of claims 1-5.

9. A computer program product, characterized in that, It includes computer program code that, when executed by an electronic device, causes the electronic device to perform the method of any one of claims 1-5.

Images