CN108234209B

CN108234209B - Domain name fault diagnosis method, device, system, computing equipment and storage medium

Info

Publication number: CN108234209B
Application number: CN201711487339.9A
Authority: CN
Inventors: 巫俊峰
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Group Jiangsu Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Group Jiangsu Co Ltd
Priority date: 2017-12-30
Filing date: 2017-12-30
Publication date: 2021-06-29
Anticipated expiration: 2037-12-30
Also published as: CN108234209A

Abstract

The embodiment of the invention discloses a domain name fault diagnosis method, a device, a system, a computing device and a storage medium, wherein the method comprises the following steps: generating a diagnosis domain name according to a preset rule based on the domain name to be checked; acquiring first diagnostic information of a domain name to be checked from a DNS network management server; and saving the diagnostic domain name in association with the first diagnostic information in the database. By the scheme, the troubleshooting difficulty and the communication cost can be reduced, troubleshooting steps are simplified, and the domain name fault processing efficiency is improved.

Description

Domain name fault diagnosis method, device, system, computing equipment and storage medium

Technical Field

The present invention relates to the field of network management technologies, and in particular, to a method, an apparatus, a system, a computing device, and a storage medium for domain name fault diagnosis.

Background

The DNS (domain name system) is a distributed database in which domain names and IP addresses are mapped to each other. The domain name resolution is to obtain an IP address corresponding to the host name. The DNS can be divided into an authoritative DNS and a recursive DNS according to functions, the authoritative DNS is a server for analyzing domain names through upper-level authorization, and the recursive DNS (LDNS) is generally erected by an operator and an ISP (Internet service provider) and used for receiving the query of a user for any domain name and returning a final analysis result to the user.

The authoritative DNS authorization server is scheduled according to the method that the LDNS back-end recursive address (not the original client IP of the requesting user) is obtained from the DNS request, so that the nearest resource node is returned. Because the LDNS is deployed by taking provinces as units, the DNS scheduling precision can only reach the province level, and accurate scheduling of the city level cannot be realized. With the development of large-flow video services, CDN scheduling according to an operator or province granularity is not enough to meet the demand of optimizing user perception, and finer service scheduling needs to be performed for a user IP.

When domain name resolution has problems, nslookup and dig fault removal commands carried by a main stream operating system are difficult to locate faults, a DNS (domain name system) administrator is required to log in a network management system to check whether a domain name is subjected to a local optimization strategy on an LDNS (laser direct structuring) or not, if the domain name is subjected to the local optimization strategy, the source party and the strategy reason of the domain name strategy are also required to be checked, the DNS administrator provides interface handler information (such as a web cache manager and a domain name plugging contact person) of the source party for a barrier person to perform next processing, and if the DNS administrator cannot respond in time, the fault processing efficiency is greatly influenced.

In the prior art, when an LDNS deploys an ECS function, an operator needs to map a client source IP private network address and a legal public network address carried by a carrier source request with each other, and also needs to manually identify an assigned domain name as an ECS domain name according to a service requirement, so that the configuration complexity is increased, and the difficulty in removing domain names is increased.

Disclosure of Invention

Aiming at the problem of low domain name fault diagnosis efficiency, the embodiment of the invention provides a domain name fault diagnosis method, a domain name fault diagnosis device, a server, computing equipment and a storage medium, which can enable maintenance personnel to quickly locate faults, reduce the difficulty of fault troubleshooting and the communication cost, simplify the fault processing steps and improve the maintenance efficiency of an ISP DNS.

In a first aspect, an embodiment of the present invention provides a domain name fault diagnosis method, where the method includes:

generating a diagnosis domain name according to a preset rule based on the domain name to be checked;

acquiring first diagnostic information of a domain name to be checked from a DNS network management server; and

the diagnostic domain name is stored in the database in association with the first diagnostic information.

In a second aspect, an embodiment of the present invention provides a domain name fault diagnosis apparatus, including: the device comprises a generating module, an obtaining module and a storing module.

The generating module may generate the diagnostic domain name according to a predetermined rule based on the domain name to be looked up.

The acquisition module can acquire first diagnostic information of the domain name to be searched from a DNS network management server.

The saving module may save the diagnosis domain name generated by the generating module in the database in association with the first diagnosis information acquired by the acquiring module.

In a third aspect, the present invention provides a domain name fault diagnosis system, which comprises a configuration server, a presence server and a client, wherein,

the configuration server generates a diagnosis domain name according to a preset rule based on the domain name to be checked, acquires first diagnosis information of the domain name to be checked from a DNS network management server, and stores the diagnosis domain name and the first diagnosis information in a database in a correlation manner;

the client generates a diagnosis domain name according to a preset rule based on the domain name to be checked, so as to send out a fault positioning request for the diagnosis domain name;

the presence server responds to a fault location request of a domain name to be searched by the client, queries the database to acquire first diagnosis information, and sends the domain name diagnosis information including the first diagnosis information to the client.

In a fourth aspect, an embodiment of the present invention provides a computing device, including: at least one processor, at least one memory, and computer program instructions stored in the memory, which when executed by the processor, implement the method of the first aspect of the embodiments described above.

In a fifth aspect, embodiments of the present invention provide a computer-readable storage medium, on which computer program instructions are stored, which, when executed by a processor, implement the method of the first aspect in the above embodiments.

According to the domain name fault diagnosis method, device, system, computing equipment and storage medium provided by the embodiment of the invention, the diagnosis information is directly presented to maintenance personnel, so that the fault is quickly positioned, the fault troubleshooting difficulty and communication cost are reduced, the fault troubleshooting steps are simplified, and the DNS maintenance efficiency is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 shows a schematic flow diagram of a domain name fault diagnosis method according to an embodiment of the present invention.

Fig. 2 shows a schematic block diagram of a domain name fault diagnosis system according to an embodiment of the present invention.

Fig. 3 is a block diagram showing a schematic configuration of a domain name fault diagnosis apparatus according to an embodiment of the present invention.

FIG. 4 shows a schematic block diagram of a computing device in accordance with an embodiment of the invention.

Detailed Description

Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present invention by illustrating examples of the present invention.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The domain name fault diagnosis method capable of improving the DNS fault elimination efficiency by showing domain name diagnosis information is provided for solving the problems that a fault person cannot automatically and quickly locate the fault reason, a DNS manager needs to respond in time in the fault elimination process, and the domain name configuration is complex in the existing solution. Fig. 1 shows a schematic flow diagram of a domain name fault diagnosis method according to an embodiment of the present invention.

As shown in fig. 1, a diagnostic domain name may be generated according to a predetermined rule based on a domain name to be looked up in step S100.

Wherein, the domain name to be checked is an original domain name to be checked, such as www.abc.com. The diagnosis domain name can be information which is added on the basis of the original domain name according to a certain rule planned in advance and can play a role of identification. The diagnosis domain name can be compatible with the existing DNS client software, and is suitable for dig under Linux and nslokup under Windows.

According to an embodiment of the invention, a prefix or a suffix can be added to the domain name to be searched, so as to generate a diagnostic domain name corresponding to the domain name to be searched.

For example, a new domain name (not necessarily a legitimate domain name) is generated regularly based on the original failed domain name by adding a prefix, adding a suffix, etc., such as www.abc.com plus debug suffix generation www.abc.com.debug diagnoses the domain name.

In step S200, first diagnostic information of the domain name to be checked may be obtained from the DNS server.

For example, the DNS server may configure first diagnostic information, construct a resource record for a diagnostic domain name by extracting basic information (scheduling policy, whether an ECS domain name is present, information about a processing interface person, and the like) of the domain name to be checked, and store the first diagnostic information. Resource records include host (A) records, alias (CNAME) records, mail switch (MX) records, Pointer (PTR) records, service location (SRV) records, and the like. The domain name diagnostic information may be stored in any of the resource records. Because the CNAME allows a plurality of names to be mapped to the same computer, when a plurality of domain names need to point to the same server IP, one domain name can be used as an A record to point to the server IP, and then other domain names are used as alias names (CNAME) to the domain name of the A record; when the server IP address changes, it is not necessary to point to a domain name change, only the domain name recorded in a needs to be changed to the new IP address of the server, and the pointing of the domain names of other aliases (i.e., CNAME) will be automatically changed to the new IP address. Therefore, the CNAME record is adopted in the scheme to store the first diagnosis information of the domain name.

According to an embodiment of the present invention, the first diagnostic information may include: the optimization strategy information, the source and/or reason of the optimization strategy and the ECS information, which are executed once by the domain name to be searched.

The optimization strategy generally refers to a local optimization strategy on the LDNS, and may include recursive analysis, forward analysis, forced analysis, blocking analysis strategy, and the like. For example, the first diagnostic information may be configured with the following information (multiple line extensions may be supported):

the first line CNAME displays basic diagnostic information including mandatory resolution, security interface blocking, forward, domain name resolution source, etc.

The second line CNAME displays the configuration reason of the policy source, the processing interface person information, the contact information and the like.

The third line CNAME shows whether it is an ECS domain name and shows the relevant information of the ECS domain name.

The ESC domain name related information comprises ECS identification information and ECS mapping information.

The diagnostic domain name may be saved in the database in association with the first diagnostic information in step S300.

According to an embodiment of the present invention, the method may further include: responding to a fault positioning request of a client to-be-checked domain name, and inquiring a database to acquire first diagnosis information associated with a diagnosis domain name corresponding to the to-be-checked domain name; and sending the domain name diagnosis information to the client, wherein the domain name diagnosis information comprises first diagnosis information.

The client can be any computer user capable of sending a request to the server, such as a common user, a maintenance person, a disabled person, a DNS administrator, and the like.

The LOCAL DNS (LDNS for short) of the operator generally has two functional modules: the front-end LOCAL DNS cache query module is responsible for receiving a domain name query request of a user and directly returning if a cache exists; otherwise, sending recursive query to a back-end LOCAL DNS recursive resolution module. And the back-end LOCAL DNS recursive resolution module receives the domain name request sent by the front-end DNS and carries out iterative query on the external authoritative DNS.

The embodiment of the invention also provides a domain name fault diagnosis system, which comprises a configuration server, a presentation server and a client, wherein,

Fig. 2 shows a schematic block diagram of a domain name fault diagnosis system according to an embodiment of the present invention. As shown in fig. 2, the diagnostic information configuration module is integrated into the DNS network manager, and is used to extract the basic information of the domain name to be checked (scheduling policy, whether the ECS domain name is available, information such as processing interface person, etc.), generate the diagnostic domain name with a special structure and the corresponding resource record including the first diagnostic information according to the rule agreed in advance, and finally send the constructed diagnostic domain name and the corresponding resource record to the diagnostic information presentation module.

The diagnosis information presentation module specially resolves diagnosis domain names with special formats, such as adding prefixes or suffixes.

According to an embodiment of the present invention, the method may further include: the client generates a diagnosis domain name according to a preset rule based on the domain name to be checked, so that a fault positioning request for the diagnosis domain name is sent out.

In this way, when the client sends a fault location request to the DNS cache query module through the generated diagnosis domain name, such as www.abc.com.debug, the first diagnosis information associated with the diagnosis domain name corresponding to the domain name to be checked may be obtained by querying the database, and the diagnosis information presentation module may present the first diagnosis information to the client.

According to an embodiment of the present invention, the method may further include: and generating second diagnosis information, wherein the second diagnosis information comprises a client source IP address, and the domain name diagnosis information also comprises the second diagnosis information.

For example, when the client locates a fault in diagnosing domain name query, the DNS cache query module passes through the diagnosing domain name resolution request to this module for processing. The module receives the configuration sent by the diagnosis information configuration module to carry out local storage, adds instant IP address information accessed by the client on the basis, constructs all diagnosis information of the diagnosis domain name, and pushes the diagnosis information to the front-end cache for display.

Thus, the fourth row CNAME may display the client source IP address.

According to an embodiment of the present invention, the method may further include: and judging whether the client source IP address is subjected to network address translation, wherein the second diagnostic information also comprises information indicating whether the client source IP address is subjected to network address translation.

The method comprises the steps that NAT (network address translation) converts a local address into a public IP address, when a user requests DNS, a DNS server supports that IP information (or an IP subnet) of the user is used as record types of cname, txt and the like, even an additional field is returned to the user, the user can quickly judge whether a DNS request passes through the NAT according to the IP information, and when the fault of DNS scheduling is checked, packet capture analysis on the DNS server is not needed.

According to an embodiment of the present invention, the second diagnostic information may further include main domain name record information virtually set for the diagnostic domain name.

For example, the fifth row CNAME may display the A record information. The user can set the main domain name and point to the IP address of the WEB server of the user, so that the function of finding the corresponding webpage by finding the server through the domain name is realized. The diagnostic domain name itself is invalid, assuming a uniform set of 127.0.0.1.

According to an embodiment of the present invention, the method may further include: setting a domain name diagnosis switch to control whether to display diagnosis information; and judging whether to allow the domain name diagnosis information to be sent to the client side or not based on the domain name diagnosis switch.

The domain name diagnosis function is generally hidden for common users, but is open for all maintenance personnel of an ISP (Internet service provider), the domain name fault maintenance personnel can check corresponding diagnosis information only through a simple nslookup or dig command according to a rule agreed in advance, a DNS (domain name system) manager can be skipped to a great extent to cooperate with a troubleshooting link, and related department personnel are directly contacted to perform fault treatment at the first time.

Fig. 3 is a block diagram showing a schematic configuration of a domain name fault diagnosis apparatus according to an embodiment of the present invention. As shown in fig. 3, the apparatus 300 may include: a generation module 310, an acquisition module 320, and a save module 330.

The generation module 310 may generate a diagnostic domain name according to a predetermined rule based on the domain name to be looked up.

The obtaining module 320 may obtain the first diagnostic information of the domain name to be checked from the DNS network management server.

The saving module 330 may save the diagnosis domain name generated by the generating module in a database in association with the first diagnosis information acquired by the acquiring module.

According to an embodiment of the present invention, the apparatus 300 may further include: the device comprises a response module and a sending module.

The response module can respond to a fault location request of a domain name to be checked of a client side, and queries a database to obtain first diagnosis information associated with a diagnosis domain name corresponding to the domain name to be checked.

The sending module may send domain name diagnosis information to the client, where the domain name diagnosis information includes first diagnosis information.

According to an embodiment of the present invention, the apparatus 300 may further include: and a second generation module.

The second generating module may generate second diagnostic information, the second diagnostic information including the client source IP address, the domain name diagnostic information further including the second diagnostic information.

According to an embodiment of the present invention, the apparatus 300 may further include: and a judging module.

The determination module may determine whether the client source IP address is subject to network address translation, wherein the second diagnostic information further includes information indicating whether the client source IP address is subject to network address translation.

According to an embodiment of the present invention, the apparatus 300 may further include: and a request module.

The request module may issue a client fault location request for the diagnostic domain name.

According to an embodiment of the present invention, the apparatus 300 may further include: the device comprises a setting module and a judging module.

The setting module may set a domain name diagnosis switch to control whether to display the diagnosis information.

The determining module may determine whether to allow the domain name diagnosis information to be sent to the client based on the domain name diagnosis switch.

In summary, according to the scheme, the domain name diagnosis information is displayed by constructing the special domain name (such as adding a prefix and a suffix) or adding a hidden switch through the DNS domain name system, the domain name diagnosis information is completely compatible with the existing DNS client software, and the domain name diagnosis information is applicable to both dig under Linux and nslookup under windows.

When a user requests a DNS, the DNS server supports that the IP information (or IP subnet) of the user is used as the record types of cname, txt and the like, even an additional field is returned to the user, the user can quickly judge whether the DNS request passes through the NAT according to the IP information, and when the fault of DNS scheduling is checked, packet capture analysis on the DNS server is not needed any more.

The method can quickly position whether the domain name is subjected to forward, forced solution, plugging, ECS identification and other operations, and the fault is quickly positioned by the barrier according to the diagnosis information, so that the domain name fault processing efficiency is improved, and the fault troubleshooting steps are simplified.

In addition, the domain name fault diagnosis method of the embodiment of the present invention described in conjunction with fig. 1 may be implemented by a computing device. Fig. 4 is a schematic diagram illustrating a hardware structure of a computing device according to an embodiment of the present invention.

The computing device may include a processor 401 and a memory 402 storing computer program instructions.

Specifically, the processor 401 may include a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or may be configured as one or more Integrated circuits implementing embodiments of the present invention.

Memory 402 may include mass storage for data or instructions. By way of example, and not limitation, memory 402 may include a Hard Disk Drive (HDD), floppy Disk Drive, flash memory, optical Disk, magneto-optical Disk, tape, or Universal Serial Bus (USB) Drive or a combination of two or more of these. Memory 402 may include removable or non-removable (or fixed) media, where appropriate. The memory 402 may be internal or external to the data processing apparatus, where appropriate. In a particular embodiment, the memory 402 is a non-volatile solid-state memory. In a particular embodiment, the memory 402 includes Read Only Memory (ROM). Where appropriate, the ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory or a combination of two or more of these.

The processor 401 reads and executes the computer program instructions stored in the memory 402 to implement any one of the domain name fault diagnosis methods in the above-described embodiments.

In one example, the computing device may also include a communication interface 403 and a bus 410. As shown in fig. 4, the processor 401, the memory 402, and the communication interface 403 are connected via a bus 410 to complete communication therebetween.

The communication interface 403 is mainly used for implementing communication between modules, apparatuses, units and/or devices in the embodiments of the present invention.

Bus 410 includes hardware, software, or both to couple components of the computing device to one another. By way of example, and not limitation, a bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hypertransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics standards association local (VLB) bus, or other suitable bus or a combination of two or more of these. Bus 410 may include one or more buses, where appropriate. Although specific buses have been described and shown in the embodiments of the invention, any suitable buses or interconnects are contemplated by the invention.

In addition, in combination with the domain name fault diagnosis method in the foregoing embodiment, the embodiment of the present invention may provide a computer-readable storage medium to implement. The computer readable storage medium having stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement any of the domain name fault diagnosis methods in the above embodiments.

In conclusion, the transmittable diagnostic information is added to the domain name information, so that the maintenance personnel can quickly locate the fault, the fault troubleshooting difficulty and the communication cost are reduced, the fault processing steps are simplified, and the maintenance efficiency of the ISP DNS is improved.

It is to be understood that the invention is not limited to the specific arrangements and instrumentality described above and shown in the drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present invention are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications and additions or change the order between the steps after comprehending the spirit of the present invention.

The functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, Erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, Radio Frequency (RF) links, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.

It should also be noted that the exemplary embodiments mentioned in this patent describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be performed in an order different from the order in the embodiments, or may be performed simultaneously.

As described above, only the specific embodiments of the present invention are provided, and it can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the module and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present invention, and these modifications or substitutions should be covered within the scope of the present invention.

Claims

1. A domain name fault diagnosis method, characterized in that the method comprises:

acquiring first diagnostic information of the domain name to be checked from a Domain Name System (DNS) network management server; and

storing the diagnostic domain name in a database in association with the first diagnostic information;

responding to a fault positioning request of a client to-be-checked domain name, and inquiring the database to acquire the first diagnosis information associated with a diagnosis domain name corresponding to the to-be-checked domain name; and

sending domain name diagnosis information to the client, wherein the domain name diagnosis information comprises the first diagnosis information.

2. The method according to claim 1, wherein the generating a diagnosis domain name according to a predetermined rule based on the domain name to be checked comprises:

and adding a prefix or a suffix in the domain name to be searched to generate a diagnostic domain name corresponding to the domain name to be searched.

3. The method of claim 1, further comprising:

and the client generates a diagnosis domain name according to the preset rule based on the domain name to be checked, so as to send out a fault positioning request for the diagnosis domain name.

4. The method of claim 1, further comprising:

and generating second diagnosis information, wherein the second diagnosis information comprises the IP address of the client source, and the domain name diagnosis information also comprises the second diagnosis information.

5. The method of claim 4, further comprising:

determining whether the client source IP address is subject to network address translation, wherein the second diagnostic information further comprises information indicating whether the client source IP address is subject to network address translation.

6. The method according to claim 4, wherein the second diagnostic information further includes main domain name record information virtually set for the diagnostic domain name.

7. The method of claim 1, further comprising:

setting a domain name diagnosis switch to control whether to display the domain name diagnosis information; and

and judging whether the domain name diagnosis information is allowed to be sent to the client side or not based on the domain name diagnosis switch.

8. The method of claim 1, wherein the first diagnostic information comprises at least one of:

optimizing strategy information which is executed aiming at the domain name to be checked;

the source and/or reason for the optimization strategy;

ECS information.

9. The method according to claim 8, wherein the optimization policy information that has been performed for the domain name to be looked up comprises: a forced analysis strategy, a forward strategy and a safety interface plugging strategy.

10. The method of claim 8,

the ESC information comprises ECS identification information, ECS mapping information and ECS domain name information, and the source of the optimization strategy comprises processing interface person information.

11. A domain name fault diagnosis apparatus, characterized in that the apparatus comprises:

the generating module is used for generating a diagnosis domain name according to a preset rule based on the domain name to be checked;

the acquisition module is used for acquiring first diagnostic information of the domain name to be checked from a DNS network management server; and

the storage module is used for storing the diagnosis domain name generated by the generation module and the first diagnosis information acquired by the acquisition module in a database in a correlation manner;

the response module is used for responding to a fault positioning request of a client to-be-checked domain name, and inquiring the database to acquire the first diagnosis information associated with the diagnosis domain name corresponding to the to-be-checked domain name; and

and the sending module is used for sending domain name diagnosis information to the client, wherein the domain name diagnosis information comprises the first diagnosis information.

12. A domain name fault diagnosis system, characterized in that the system comprises a configuration server, a presence server and a client, wherein,

the client generates a diagnosis domain name according to the preset rule based on the domain name to be checked, so as to send out a fault positioning request for the diagnosis domain name;

and the presence server responds to a fault positioning request of the client to the domain name to be checked, queries the database to acquire the first diagnosis information, and sends the domain name diagnosis information including the first diagnosis information to the client.

13. A computing device, comprising: at least one processor, at least one memory, and computer program instructions stored in the memory that, when executed by the processor, implement the method of any of claims 1-10.

14. A computer-readable storage medium having computer program instructions stored thereon, which when executed by a processor implement the method of any one of claims 1-10.