Domain name access method and device, electronic equipment and readable storage medium

Abstract

The application provides a domain name access method and device, electronic equipment and a readable storage medium, comprising: receiving a first input, the first input being application information for requesting access to a target service domain name; in response to the first input, determining a target service label corresponding to the target service domain name; receiving a second input, the second input being the target service label; in response to the second input, matching a converged domain name corresponding to the target service label, and resolving the target service domain name to the converged domain name, and forwarding traffic to the backend service of the target service according to the converged domain name. The application realizes grouping access of multiple domain names according to service attributes, and management can be completed through management of a certain number of converged domain names to manage a large number of service domain names. The management cost is greatly saved, and the management efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of computer network communication technology, and in particular to a domain name access method, apparatus, electronic device, and readable storage medium. Background Technology

[0002] Current domain name management technologies largely rely on proprietary domain name management platforms, displaying all domain names together. Domain name access is generally achieved by directly resolving to backend services. Traditional management methods often involve a stacked, incremental approach, with little focus on domain name categorization. Due to the sheer number of domain names, conventional domain name management technologies fail to categorize them according to business attributes, creating technical barriers in areas such as revenue sharing and cost management. The excessive number of domain names leads to complex and unsystematic domain name management, with low functional differentiation, resulting in difficult and inefficient domain name management. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a domain name access method, apparatus, electronic device, and readable storage medium to solve the problems of difficult and inefficient domain name management.

[0004] According to a first aspect of the present invention, a domain name access method is provided, comprising:

[0005] Receive the first input, which is the application information requesting access to the target business domain name;

[0006] In response to the first input, determine the target business tag corresponding to the target business domain name;

[0007] Receive a second input, which is the target service tag;

[0008] In response to the second input, a convergence domain name corresponding to the target business tag is matched, and the target business domain name is resolved to the convergence domain name. Traffic is then forwarded to the backend service of the target business according to the convergence domain name.

[0009] Optionally, after matching the convergence domain name corresponding to the target service tag, resolving the target service domain name to the convergence domain name, and forwarding traffic to the backend service of the target service according to the convergence domain name, the method further includes:

[0010] Receive a third input, wherein the third input is the input from the backend service of the target service receiving traffic forwarding;

[0011] In response to the third input, the target business domain name is updated to the monitoring configuration;

[0012] Receive a fourth input, which is the domain name resolution failure information of the target business;

[0013] In response to the fourth input, a preset stop-loss operation is performed based on the fault information.

[0014] Optionally, forwarding traffic to the backend service of the target service based on the converged domain name includes:

[0015] The converged domain name is resolved to the same set of VIP addresses, and traffic is forwarded to the backend service of the target business according to the VIP addresses;

[0016] The response to the fourth input, performing a preset stop-loss operation based on the fault information, includes:

[0017] Stop the domain name resolution of the faulty VIP address;

[0018] Forward the traffic from the faulty VIP address to other VIP addresses in the same group.

[0019] Optionally, before receiving the first input, the method further includes:

[0020] Set the target business line and backend service name corresponding to the target business domain name.

[0021] According to a second aspect of the present invention, a domain name access device is provided, comprising:

[0022] The first receiving module is used to receive the first input, which is the application information for requesting access to the target business domain name;

[0023] The determination module, in response to the first input, determines the target business tag corresponding to the target business domain name;

[0024] The second receiving module is used to receive a second input, which is the target service tag;

[0025] The parsing module, in response to the second input, matches the convergence domain name corresponding to the target business tag, resolves the target business domain name to the convergence domain name, and forwards traffic to the backend service of the target business according to the convergence domain name.

[0026] Optionally, the domain name access device further includes:

[0027] The third receiving module is used to receive a third input, which is the input of traffic forwarding received by the backend service of the target service;

[0028] The update module, in response to the third input, updates the target business domain name to the monitoring configuration;

[0029] The fourth receiving module is used to receive a fourth input, which is the target business domain name resolution failure information;

[0030] The fault handling module, in response to the fourth input, performs a preset loss-stopping operation based on the fault information.

[0031] Optionally, the parsing module includes:

[0032] The resolution submodule is used to resolve the converged domain name to the same group of VIP addresses, and forward traffic to the backend service of the target business according to the VIP address;

[0033] The fault handling module includes:

[0034] The fault stop module is used to stop the domain name resolution of a faulty VIP address;

[0035] The traffic forwarding module is used to forward the traffic of a faulty VIP address to other VIP addresses in the same group.

[0036] Optionally, the domain name access device further includes:

[0037] The settings module is used to set the target business line and backend service name corresponding to the target business domain name.

[0038] According to a third aspect of the present invention, an electronic device is provided, comprising:

[0039] Processor; and

[0040] Stored program memory,

[0041] The program includes instructions that, when executed by the processor, cause the processor to perform the method according to any one of the first aspects of the invention.

[0042] According to a fourth aspect of the present invention, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are configured to cause a computer to perform the method according to any one of the first aspects of the present invention.

[0043] The one or more technical solutions provided in this application embodiment divide target business domain names according to business attributes, determine the tags corresponding to the target business domain names based on the division results, identify the target business domain names and resolve them to a unified business convergence domain name. The convergence domain name can be named according to business attributes, and then the convergence domain name performs the actual resolution and forwarding of traffic. This achieves the grouping and access of multiple domain names according to business attributes, and in terms of management, a large number of business domain names can be managed by managing a certain number of convergence domain names. This greatly saves management costs and improves management efficiency. Attached Figure Description

[0044] Further details, features, and advantages of the invention are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:

[0045] Figure 1 A schematic diagram of an example system in which the various methods described herein may be implemented according to exemplary embodiments of the present invention is shown;

[0046] Figure 2 A flowchart of a domain name access method according to an exemplary embodiment of the present invention is shown;

[0047] Figure 3 A domain name access architecture diagram according to an exemplary embodiment of the present invention is shown;

[0048] Figure 4 A domain name convergence logic diagram according to an exemplary embodiment of the present invention is shown;

[0049] Figure 5 A loss prevention logic diagram according to an exemplary embodiment of the present invention is shown;

[0050] Figure 6 A schematic block diagram of a domain name access device according to an exemplary embodiment of the present invention is shown;

[0051] Figure 7 A structural block diagram of an exemplary electronic device that can be used to implement embodiments of the present invention is shown. Detailed Implementation

[0052] Embodiments of the present invention will now be described in more detail with reference to the accompanying drawings. While some embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the invention. It should be understood that the accompanying drawings and embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the invention.

[0053] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0054] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc., mentioned in this invention are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0055] It should be noted that the terms "a" and "a plurality of" used in this invention are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0056] The names of the messages or information exchanged between the multiple devices in the embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0057] The present invention will now be described with reference to the accompanying drawings. The technical solutions provided by the embodiments of this application will be explained in detail through specific examples and application scenarios.

[0058] like Figure 1 As shown, to address the problem of excessive domain names and the resulting complexity and difficulty in management, this embodiment adopts a convergent domain name access approach based on the attributes and tags of different target business domain names. Domain names with the same business attributes are resolved to the same or several convergent domain names with business attribute tags. The converged domain names are then resolved to a unified traffic forwarding platform (BFE), which forwards the traffic to the actual service backend.

[0059] Furthermore, this embodiment builds the loss mitigation plan based on the converged domain names. By only creating a loss mitigation plan for the converged domain names, it can complete the failure mitigation for all domain names that resolve to the converged domain name. This greatly simplifies the construction of the loss mitigation plan and enables effective loss mitigation switching for business lines.

[0060] like Figure 2 As shown, Figure 2 This is a flowchart illustrating a domain name access method provided in an embodiment of this application. The method may include the following steps S201 to S204:

[0061] S201, Receive the first input, whereby the first input is the application information requesting access to the target business domain name.

[0062] In this embodiment, a 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.

[0063] In one optional embodiment, such as Figure 4 As shown, the application information for the target business domain name includes the domain name of the target business domain name, the corresponding backend service, and the business line of the target business domain name.

[0064] S202, in response to the first input, determine the target business tag corresponding to the target business domain name.

[0065] In this embodiment, after receiving the application information of the target business domain name, the control center of the domain name access system that implements domain name access processes it and determines the target business tag to which the target business domain name in the application information belongs.

[0066] S203, Receive the second input, the second input being the target service tag.

[0067] S204, in response to the second input, match the convergence domain name corresponding to the target service tag, resolve the target service domain name to the convergence domain name, and forward traffic to the backend service of the target service according to the convergence domain name.

[0068] In one optional embodiment, such as Figure 3 As shown, the target business service owner applies for a target business domain name, fills in the business line, business domain name, and backend service name to be forwarded, and submits the application after confirmation. The domain name access system's control center module processes the application, determines the target business tag to which the applied target business domain name belongs, and sends the processing instruction to the scheduling center. Finally, the scheduling center collects domain name resources from the pool to match the corresponding target business's collection domain name, and resolves the CNAME of the domain name applied for by the business service owner to the target business's collection domain name. The collection domain name resolves to multiple VIP addresses, and the VIP access BFE forwards traffic to the target business service's backend service, completing the access of the target business domain name. Here, BFE is a modern, open-source, seven-layer traffic access system based on Baidu Unified Access Frontend (Baidu FrontEnd). Backend service: specifically refers to the destination of traffic forwarded by BFE, here referring to the BNS service. BNS (Baidu Naming Service) is a name service launched by the Baidu Noah platform team, widely used for service registration, service discovery, authorization management, and traffic scheduling. It supports various programming languages ​​and provides command-line tools and NSS plugin support.

[0069] like Figure 4 As shown, the starting point and target of domain traffic access are the domain name and the backend service, respectively. There are situations where multiple domain names access the same service. Therefore, the relationship between the domain name and the backend service is actually many-to-one or many-to-many. Since the backend service has business attributes, the corresponding domain name should also have business attributes. From a management perspective, the shared business attributes of multiple domain names should be key to management. This embodiment adopts a domain name convergence scheme based on business attributes. At the initial stage of domain name application, relevant backend service business attributes are collected, and this information is processed and judged by the control center. After receiving the input information from the control center, the scheduling center configures the convergence domain name corresponding to the business. Domain name convergence refers to resolving multiple domain names to the same domain name, and then resolving this single domain name to an IP address.

[0070] In an optional embodiment, after matching the convergence domain name corresponding to the target service tag, resolving the target service domain name to the convergence domain name, and forwarding traffic to the backend service of the target service according to the convergence domain name, the method further includes:

[0071] S205, Receive a third input, wherein the third input is the input of traffic forwarding received by the backend service of the target service;

[0072] S206, in response to the third input, update the target business domain name to the monitoring configuration;

[0073] S207, Receive a fourth input, wherein the fourth input is the target service domain name resolution failure information;

[0074] S208, in response to the fourth input, execute a preset stop-loss operation based on the fault information.

[0075] In this embodiment, due to the shortcomings of existing domain name access device failure prevention and contingency plan development being scattered and inefficient, the monitoring system configuration is updated synchronously after domain name access, incorporating the newly applied domain name into the new monitoring system. When a domain name fails, such as a failure of some VIPs resolved by the converged domain name, this failure information can be sent as an input signal to the contingency plan prevention platform. If a contingency plan for this failure has been prepared in advance, the contingency plan prevention platform can switch the resolution of the failed VIP at the converged domain name level, thereby ensuring that all domain names of the target business can still provide normal service. This embodiment innovatively classifies and converges business domain names in multi-domain access management with business attributes, narrowing the scope of traffic control and unifying the scheduling of traffic for domains with the same attributes. This embodiment uses multi-level domain name convergence forwarding, making the setting of contingency plans and loss prevention more efficient and concise, and the traffic path clearer. This avoids the complexity and redundancy of adding and formulating contingency plans for each domain name when the number of domain name accesses reaches hundreds or thousands.

[0076] VIP is the IP address resolved to by the domain name; it's actually the load balancer's IP address, which connects to the domain name and backend services. A contingency plan is an emergency response plan developed in advance based on assessment and analysis or experience, considering the type and impact of potential or possible emergencies. Loss mitigation refers to actions that effectively prevent the failure from continuing or its impact from escalating when it occurs.

[0077] In an optional embodiment, forwarding traffic to the backend service of the target service based on the converged domain name includes:

[0078] S2041, resolve the converged domain name to the same group of VIP addresses, and forward the traffic to the backend service of the target business according to the VIP addresses;

[0079] Based on this, the response to the fourth input, and the execution of a preset stop-loss operation according to the fault information, includes:

[0080] S2081, Stop domain name resolution for the faulty VIP address;

[0081] S2082 forwards the traffic of the faulty VIP address to other VIP addresses in the same group.

[0082] In this embodiment, as Figure 5As shown, traditional domain name access typically uses a single business domain name corresponding to different backend service IPs, requiring operation on each domain name during fault mitigation. This application's embodiment uses a method of converging domain names with the same business attributes and resolving them to the same group of VIPs. Different fault-switching contingency plans are configured on the fault mitigation platform. For example, when the monitoring platform detects a fault in one of the VIPs, it transmits the fault signal to the fault mitigation platform, which automatically stops the domain name resolution of the faulty VIP, redirecting traffic to the normal VIPs. This ensures that the domain name can provide normal service capabilities. Thus, fault mitigation can be achieved simply by changing the resolution of the converged domain names.

[0083] This application embodiment monitors domain names by measuring indicators such as traffic through a monitoring system. Once multiple domain names with the same business attributes experience a failure in a single data center or a single operator, the system transmits the failure signal to the contingency plan and loss prevention system. By executing the loss prevention plan set for the converged domain names, the stability of the business is ensured, which greatly saves manpower and costs in the construction of contingency plans.

[0084] Before receiving the first input, the method further includes:

[0085] S201a, Set the target business line and backend service name corresponding to the target business domain name.

[0086] In this embodiment, a domain name convergence scheme based on business attributes is adopted. At the initial stage of domain name application, relevant backend service business attributes are collected. This information is then processed by the control center to determine the business attributes. After receiving input information from the control center, the scheduling center configures the converged domain name for the corresponding business. Domain name convergence refers to resolving multiple domain names to the same domain name, and then resolving that single domain name to an IP address.

[0087] The domain name access method provided in this application embodiment divides the target business domain name according to its business attributes, determines the tag corresponding to the target business domain name based on the division result, identifies the target business domain name and resolves it to a unified business convergence domain name. The convergence domain name can be named according to its business attributes, and then the convergence domain name performs the actual resolution and forwarding of traffic. This achieves the grouping and access of multiple domain names according to their business attributes, and in terms of management, a large number of business domain names can be managed by managing a certain number of convergence domain names. This greatly saves management costs and improves management efficiency.

[0088] Corresponding to the above embodiments, see [link to relevant documentation]. Figure 6 This application also provides a domain name access device 600, comprising:

[0089] The first receiving module 601 is used to receive a first input, wherein the first input is application information requesting access to the target business domain name;

[0090] The determining module 602, in response to the first input, determines the target business tag corresponding to the target business domain name;

[0091] The second receiving module 603 is used to receive a second input, wherein the second input is the target service tag;

[0092] The parsing module 604, in response to the second input, matches the convergence domain name corresponding to the target business tag, resolves the target business domain name to the convergence domain name, and forwards traffic to the backend service of the target business according to the convergence domain name.

[0093] Optionally, the domain name access device 600 further includes:

[0094] The third receiving module is used to receive a third input, which is the input of traffic forwarding received by the backend service of the target service;

[0095] The update module, in response to the third input, updates the target business domain name to the monitoring configuration;

[0096] The fourth receiving module is used to receive a fourth input, which is the target business domain name resolution failure information;

[0097] The fault handling module, in response to the fourth input, performs a preset loss-stopping operation based on the fault information.

[0098] Optionally, the parsing module includes:

[0099] The resolution submodule is used to resolve the converged domain name to the same group of VIP addresses, and forward traffic to the backend service of the target business according to the VIP address;

[0100] The fault handling module includes:

[0101] The fault stop module is used to stop the domain name resolution of a faulty VIP address;

[0102] The traffic forwarding module is used to forward the traffic of a faulty VIP address to other VIP addresses in the same group.

[0103] Optionally, the domain name access device 600 further includes:

[0104] The settings module is used to set the target business line and backend service name corresponding to the target business domain name.

[0105] The domain name access method provided in this application embodiment divides the target business domain name according to its business attributes, determines the tag corresponding to the target business domain name based on the division result, identifies the target business domain name and resolves it to a unified business convergence domain name. The convergence domain name can be named according to its business attributes, and then the convergence domain name performs the actual resolution and forwarding of traffic. This achieves the grouping and access of multiple domain names according to their business attributes, and in terms of management, a large number of business domain names can be managed by managing a certain number of convergence domain names. This greatly saves management costs and improves management efficiency.

[0106] An exemplary embodiment of the present invention also provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the electronic device to perform a method according to an embodiment of the present invention.

[0107] An exemplary embodiment of the present invention also provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a computer's processor, is used to cause the computer to perform a method according to an embodiment of the present invention.

[0108] An exemplary embodiment of the present invention also provides a computer program product, including a computer program, wherein, when executed by a computer's processor, the computer program is used to cause the computer to perform a method according to an embodiment of the present invention.

[0109] refer to Figure 7 The present invention will now be described in the form of a structural block diagram of an electronic device 700 that can serve as a server or client of the present invention, which is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0110] like Figure 7As shown, the electronic device 700 includes a computing unit 701, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) 702 or a computer program loaded from a storage unit 708 into a random access memory (RAM) 703. The RAM 703 may also store various programs and data required for the operation of the device 700. The computing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0111] Multiple components in electronic device 700 are connected to I / O interface 705, including: input unit 706, output unit 707, storage unit 708, and communication unit 709. Input unit 706 can be any type of device capable of inputting information to electronic device 700. Input unit 706 can receive input digital or character information and generate key signal inputs related to user settings and / or function control of electronic device. Output unit 707 can be any type of device capable of presenting information and may include, but is not limited to, a display, speaker, video / audio output terminal, vibrator, and / or printer. Storage unit 708 may include, but is not limited to, disk and optical disk. Communication unit 709 allows electronic device 700 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers, and / or chipsets, such as Bluetooth™ devices, WiFi devices, WiMax devices, cellular communication devices, and / or the like.

[0112] The computing unit 701 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 701 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 701 performs the various methods and processes described above. For example, in some embodiments, the auditing method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 708. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 700 via ROM 702 and / or communication unit 709. In some embodiments, the computing unit 701 may be configured to perform the auditing method by any other suitable means (e.g., by means of firmware).

[0113] The program code used to implement the methods of the present invention can be written in any combination of one or more programming languages. This program code can be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0114] In the context of this invention, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0115] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and / or apparatus (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0116] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0117] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0118] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other.

Claims

1. A domain name access method, characterized in that, include: Receive the first input, which is the application information requesting access to the target business domain name; In response to the first input, determine the target business tag corresponding to the target business domain name; Receive a second input, which is the target service tag; In response to the second input, a convergence domain name corresponding to the target business tag is matched, and the target business domain name is resolved to the convergence domain name. Traffic is then forwarded to the backend service of the target business according to the convergence domain name.

2. The domain name access method according to claim 1, characterized in that, The process of matching the convergence domain name corresponding to the target business tag, resolving the target business domain name to the convergence domain name, and forwarding traffic to the backend service of the target business according to the convergence domain name further includes: Receive a third input, wherein the third input is the input of traffic forwarding received by the backend service of the target service; In response to the third input, the target business domain name is updated to the monitoring configuration; Receive a fourth input, which is the domain name resolution failure information of the target business; In response to the fourth input, a preset stop-loss operation is performed based on the fault information.

3. The domain name access method according to claim 2, characterized in that, The step of forwarding traffic to the backend service of the target business based on the converged domain name includes: The converged domain name is resolved to the same set of VIP addresses, and traffic is forwarded to the backend service of the target business according to the VIP addresses; The response to the fourth input, performing a preset stop-loss operation based on the fault information, includes: Stop the domain name resolution of the faulty VIP address; Forward the traffic from the faulty VIP address to other VIP addresses in the same group.

4. The domain name access method according to claim 1, characterized in that, Before receiving the first input, the method further includes: Set the target business line and backend service name corresponding to the target business domain name.

5. A domain name access device, characterized in that, include: The first receiving module is used to receive the first input, which is the application information for requesting access to the target business domain name; The determination module, in response to the first input, determines the target business tag corresponding to the target business domain name; The second receiving module is used to receive a second input, which is the target service tag; The parsing module, in response to the second input, matches the convergence domain name corresponding to the target business tag, resolves the target business domain name to the convergence domain name, and forwards traffic to the backend service of the target business according to the convergence domain name.

6. The domain name access device according to claim 5, characterized in that, The domain name access device also includes: The third receiving module is used to receive a third input, which is the input of traffic forwarding received by the backend service of the target service; The update module, in response to the third input, updates the target business domain name to the monitoring configuration; The fourth receiving module is used to receive a fourth input, which is the target business domain name resolution failure information; The fault handling module, in response to the fourth input, performs a preset loss-stopping operation based on the fault information.

7. The domain name access device according to claim 6, characterized in that, The parsing module includes: The resolution submodule is used to resolve the converged domain name to the same group of VIP addresses, and forward traffic to the backend service of the target business according to the VIP address; The fault handling module includes: The fault stop module is used to stop the domain name resolution of a faulty VIP address; The traffic forwarding module is used to forward the traffic of a faulty VIP address to other VIP addresses in the same group.

8. The domain name access device according to claim 5, characterized in that, The domain name access device also includes: The settings module is used to set the target business line and backend service name corresponding to the target business domain name.

9. An electronic device, comprising: processor; as well as Stored program memory, The program includes instructions that, when executed by the processor, cause the processor to perform the method according to any one of claims 1-4.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-4.

Images