CN116980386A - Domain name access method and device, electronic equipment and readable storage medium - Google Patents
Domain name access method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN116980386A CN116980386A CN202311111673.XA CN202311111673A CN116980386A CN 116980386 A CN116980386 A CN 116980386A CN 202311111673 A CN202311111673 A CN 202311111673A CN 116980386 A CN116980386 A CN 116980386A
- Authority
- CN
- China
- Prior art keywords
- domain name
- input
- target service
- service
- receiving
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000012545 processing Methods 0.000 claims description 11
- 238000012544 monitoring process Methods 0.000 claims description 10
- 230000004044 response Effects 0.000 claims description 4
- 238000004590 computer program Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- RZVAJINKPMORJF-UHFFFAOYSA-N Acetaminophen Chemical compound CC(=O)NC1=CC=C(O)C=C1 RZVAJINKPMORJF-UHFFFAOYSA-N 0.000 description 1
- 238000009825 accumulation Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a domain name access method, a domain name access device, electronic equipment and a readable storage medium, wherein the domain name access method comprises the following steps: receiving a first input, wherein the first input is application information for requesting to access a target service domain name; responding to the first input, and determining a target service label corresponding to the target service domain name; receiving a second input, wherein the second input is the target service label; and responding to the second input, matching a convergence domain name corresponding to the target service label, resolving the target service domain name to the convergence domain name, and forwarding the traffic to the back-end service of the target service according to the convergence domain name. The application makes the multi-domain name according to the business attribute group access, and can manage a plurality of business domain names by managing a certain number of convergent domain names. The management cost is greatly saved, and the management efficiency is improved.
Description
Technical Field
The present application relates to the field of computer network communications technologies, and in particular, to a domain name access method, a domain name access device, an electronic device, and a readable storage medium.
Background
Most of the current domain name management technologies rely on own domain name management platforms to display domain names together, and the access mode of the domain names is basically directly resolved to the back-end service. The traditional management mode is mostly stacked accumulation, and less attention is paid to classification of domain names. Because of the huge number of domain names, the conventional domain name management technology does not divide domain names according to service attributes, so that domain name management without service attribute labels has technical barriers in aspects of service accounting, cost management and the like. Because of the excessive number of access domain names, the domain name management is complex and not systemized, and the domain name function distinction degree is not high, so that the domain name management is difficult and the management efficiency is not high.
Disclosure of Invention
In view of the above, the embodiments of the present application provide a domain name access method, a device, an electronic apparatus, and a readable storage medium, so as to solve the problems of difficult domain name management and low management efficiency.
According to an aspect of the present application, there is provided a domain name access method, including:
receiving a first input, wherein the first input is application information for requesting to access a target service domain name;
responding to the first input, and determining a target service label corresponding to the target service domain name;
receiving a second input, wherein the second input is the target service label;
and responding to the second input, matching a convergence domain name corresponding to the target service label, resolving the target service domain name to the convergence domain name, and forwarding the traffic to the back-end service of the target service according to the convergence domain name.
Optionally, after the matching the convergence domain name corresponding to the target service label, resolving the target service domain name to the convergence domain name, forwarding the traffic to the back-end service of the target service according to the convergence domain name, the method further includes:
receiving a third input, wherein the third input is an input for receiving flow forwarding for the back-end service of the target service;
updating the target service domain name to a monitoring configuration in response to the third input;
receiving a fourth input, wherein the fourth input is the target service domain name resolution fault information;
and responding to the fourth input, and executing a preset damage stopping operation according to the fault information.
Optionally, the forwarding the traffic to the backend service of the target service according to the convergence domain name includes:
resolving the converged domain name to the same group of VIP addresses, and forwarding the traffic to the back-end service of the target service according to the VIP addresses;
the responding to the fourth input, executing the preset damage stopping operation according to the fault information, comprises the following steps:
stopping domain name resolution of the fault VIP address;
traffic for the failed VIP address is forwarded to other VIP addresses of the same group.
Optionally, before receiving the first input, the method further includes:
and setting a target service line and a rear-end service name corresponding to the target service domain name.
According to a second aspect of the present application, there is provided a domain name access device comprising:
the first receiving module is used for receiving a first input, wherein the first input is application information for requesting to access a target service domain name;
the determining module is used for responding to the first input and determining a target service label corresponding to the target service domain name;
the second receiving module is used for receiving a second input, and the second input is the target service label;
and the analysis module responds to the second input, matches the convergence domain name corresponding to the target service label, analyzes the target service domain name to the convergence domain name, and forwards the flow to the back-end service of the target service according to the convergence domain name.
Optionally, the domain name access device further includes:
the third receiving module is used for receiving a third input, wherein the third input is the input of receiving the flow forwarding by the back-end service of the target service;
the updating module is used for responding to the third input and updating the target service domain name to a monitoring configuration;
the fourth receiving module is used for receiving a fourth input, and the fourth input is the fault information of the domain name resolution of the target service;
and the fault processing module responds to the fourth input and executes preset damage stopping operation according to the fault information.
Optionally, the parsing module includes:
the analysis submodule is used for analyzing the converged domain name to the same group of VIP addresses, and forwarding the traffic to the back-end service of the target service according to the VIP addresses;
the fault handling module comprises:
the fault stopping module is used for stopping domain name resolution of the fault VIP address;
and the traffic forwarding module is used for forwarding the traffic of the fault VIP address to other VIP addresses in the same group.
Optionally, the domain name access device further includes:
and the setting module is used for setting a target service line and a rear-end service name corresponding to the target service domain name.
According to a third aspect of the present application, there is provided an electronic device comprising:
a processor; and
a memory in which a program is stored,
wherein the program comprises instructions which, when executed by the processor, cause the processor to perform the method according to any of the first aspects of the application.
According to a fourth aspect of the present application there is provided a non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the method according to any one of the first aspects of the present application.
According to one or more technical schemes provided by the embodiment of the application, the target service domain name is divided according to the service attribute, the label corresponding to the target service domain name is determined according to the division result, the target service domain name is identified and resolved to a unified service convergence domain name, the convergence domain name can be named through the service attribute, and then the convergence domain name is used for actually resolving and forwarding the traffic. The multi-domain names are accessed in groups according to the service attributes, so that the management of a large number of service domain names can be completed by managing a certain number of converged domain names. The management cost is greatly saved, and the management efficiency is improved.
Drawings
Further details, features and advantages of the application are disclosed in the following description of exemplary embodiments with reference to the following drawings, in which:
FIG. 1 illustrates a schematic diagram of an example system in which various methods described herein may be implemented, according to an example embodiment of the application;
fig. 2 shows a flow chart of a domain name access method according to an exemplary embodiment of the application;
fig. 3 illustrates a domain name access architecture diagram according to an exemplary embodiment of the present application;
FIG. 4 illustrates a domain name convergence logic diagram in accordance with an exemplary embodiment of the present application;
FIG. 5 illustrates a plan loss stop logic diagram in accordance with an exemplary embodiment of the present application;
fig. 6 shows a schematic block diagram of a domain name access device according to an exemplary embodiment of the present application;
fig. 7 shows a block diagram of an exemplary electronic device that can be used to implement an embodiment of the application.
Detailed Description
Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While the application is susceptible of embodiment in the drawings, it is to be understood that the application may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided to provide a more thorough and complete understanding of the application. It should be understood that the drawings and embodiments of the application are for illustration purposes only and are not intended to limit the scope of the present application.
It should be understood that the various steps recited in the method embodiments of the present application may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the application is not limited in this respect.
The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part 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. Related definitions of other terms will be given in the description below. It should be noted that the terms "first," "second," and the like herein are merely used for distinguishing between different devices, modules, or units and not for limiting the order or interdependence of the functions performed by such devices, modules, or units.
It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those skilled in the art will appreciate that "one or more" is intended to be construed as "one or more" unless the context clearly indicates otherwise.
The names of messages or information interacted between the devices in the embodiments of the present application are for illustrative purposes only and are not intended to limit the scope of such messages or information.
The following describes the scheme of the present application with reference to the drawings, and the technical scheme provided by the embodiment of the present application is described in detail through specific embodiments and application scenarios thereof.
As shown in fig. 1, to solve the problem of excessive number of domain names, management is complicated and difficult. In this embodiment, based on the attributes and labels of different target service domain names, convergence type domain name access is formulated, domain name resolution of the same service attribute is accessed to the same or several convergence domain names with service attribute labels, then the converged domain names are resolved to a unified flow forwarding platform BFE, and the BFE forwards the flow to the actual service back end.
Meanwhile, in the embodiment, the damage stopping plan is built on the basis of the converged domain name, and the damage stopping plan is built only for the converged domain name, so that the fault damage stopping of all domain names resolved to the converged domain name can be completed. The construction of the loss stopping plan is greatly simplified, and the effective loss stopping switching of the service line can be realized.
As shown in fig. 2, fig. 2 is a flow chart of a domain name access method according to an embodiment of the present application, where the method may include steps S201 to S204 as follows:
s201, receiving a first input, wherein the first input is application information for requesting to access a target service domain name.
In this embodiment, a Domain Name (also called a network Domain) is a Name of a computer or a computer group on the internet, which is formed by a series of names separated by dots, and is used for locating and identifying the computer during data transmission.
In an alternative manner of this embodiment, as shown in fig. 4, the application information of the target service domain name includes the domain name of the target service domain name, the corresponding backend service, and the service line of the target service domain name.
S202, responding to the first input, and determining a target service label corresponding to the target service domain name.
In this embodiment, after receiving the application information of the target service domain name, the control center of the domain name access system performing domain name access processes the application information, and determines the target service label to which the target service domain name in the application information belongs.
S203, receiving a second input, wherein the second input is the target service label.
S204, responding to the second input, matching the convergence domain name corresponding to the target service label, resolving the target service domain name to the convergence domain name, and forwarding the flow to the back-end service of the target service according to the convergence domain name.
In an alternative manner of this embodiment, as shown in fig. 3, the target service owner applies for the target service domain name, fills in the service line, the service domain name and the back-end service name that need to be forwarded of the target service, and submits the application after confirmation. The control center module of the domain name access system for implementing domain name access processes the domain name access, judges the target service label to which the applied target service domain name belongs, sends a processing instruction to the dispatching center, finally, the dispatching center removes the converged domain name resource pool to match the converged domain name of the corresponding target service, analyzes the domain name cname of the service server owner application to the converged domain name of the target service, analyzes the converged domain name to a plurality of VIP addresses, and the VIP access BFE forwards the flow to the rear end service of the target service to complete the access of the target service domain name. The BFE is a modern seven-layer flow access system based on hundred-degree unified access front end (Baidu front end) open source. Back-end service: in particular, the end point of traffic forwarded by the BFE, herein referred to as BNS service. BNS (Baidu Naming Service), which is a hundred degree name service, is widely used for service registration, service discovery, authorization management, traffic scheduling, supporting various development languages, and simultaneously providing command line tools and nss plug-in support.
As shown in fig. 4, in the domain name traffic access process, the starting point and the target are respectively the domain name and the back-end service, and there is a case that the same service has multiple domain name accesses, so the relationship between the domain name and the back-end service is actually a many-to-one or many-to-many relationship, and the back-end service has a service attribute, so the corresponding domain name should also follow the service attribute, and in terms of management, the same service attribute of multiple domain names should be the key of management. In the embodiment, a domain name convergence scheme based on service attributes is adopted, related back-end service attributes are acquired at the beginning of domain name application, information is sent to a control center for processing and judging the service attributes, and after receiving input information of the control center, a dispatching center is configured to analyze a convergence domain name of a corresponding service. The domain name convergence refers to resolving a plurality of domain names to the same domain name, and resolving the domain name to the IP.
In an optional manner of this embodiment, after the matching the convergence domain name corresponding to the target service label, resolving the target service domain name to the convergence domain name, forwarding the traffic to the back-end service of the target service according to the convergence domain name, further includes:
s205, receiving a third input, wherein the third input is the input of receiving flow forwarding by the back-end service of the target service;
s206, responding to the third input, and updating the target service domain name to a monitoring configuration;
s207, receiving a fourth input, wherein the fourth input is the target service domain name resolution fault information;
s208, responding to the fourth input, and executing preset damage stopping operation according to the fault information.
In this embodiment, because the existing domain name access device has the disadvantages of loss stopping after failure, scattered overall preparation of the plan, inefficiency, and the like, the configuration of the monitoring system is synchronously updated after domain name access, and the newly applied domain name is incorporated into a new monitoring system. When a domain name fails, for example, a part of the VIP which is resolved by the converged domain name fails, the failure information can be used as an input signal to a pre-scheme loss stopping platform, and the pre-scheme loss stopping platform can complete switching of the failed VIP in the converged domain name level under the condition that the loss stopping pre-scheme of the failure is established in advance, so that normal service can still be provided for all domain names of target service. In the multi-domain name access management with service attributes, the embodiment of the application can creatively classify and converge service domain names, reduce the flow control range and uniformly close and schedule domain name flow with the same attribute.
The VIP is an IP address resolved by the domain name, actually is a load-balanced IP address, and can interface the domain name and the back-end service. The protocol is an emergency treatment protocol formulated in advance for the type and extent of impact of a potential or possible incident based on evaluation analysis or experience. The failure stop means that the failure can be effectively prevented from continuing or the expansion can be effectively influenced when the failure occurs.
In an optional manner of this embodiment, the forwarding, according to the convergence domain name, the traffic to the backend service of the target service includes:
s2041, resolving the converged domain name to the same group of VIP addresses, and forwarding the traffic to the back-end service of the target service according to the VIP addresses;
on the basis, the responding to the fourth input, executing the preset damage stopping operation according to the fault information, and comprises the following steps:
s2081, stopping domain name resolution of the fault VIP address;
and S2082, forwarding the traffic of the fault VIP address to other VIP addresses in the same group.
In this embodiment, as shown in fig. 5, the conventional domain name access generally adopts a form that a single service domain name corresponds to different backend service IPs, and when the failure is stopped, each domain name needs to be operated. The embodiment of the application adopts the method that the domain names with the same service attribute are converged and resolved on the same group of VIPs. And when the fault switching plans are configured on the fault stopping platform, for example, when the monitoring platform detects that one of the VIP accesses fails, a fault signal is transmitted to the fault stopping platform, and the fault stopping platform can automatically stop the domain name analysis of the failed VIP, so that the traffic is intensively scheduled to the normal VIP, the normal service capability of the domain name can be ensured, and the fault stopping can be completed only by changing the analysis condition of the converged domain name.
In the embodiment of the application, the indexes such as the flow rate and the like of the domain name are monitored through the monitoring system, once a single-side machine room or a single operator fault occurs to the multi-domain name with the same service attribute, the system transmits a fault signal to the pre-project damage stopping system, and the damage stopping pre-project is executed by setting the converged domain name, so that the stability of the service is ensured, and the labor and the cost of pre-project construction are greatly saved.
Before receiving the first input, the method further comprises:
s201a, setting a target service line and a back-end service name corresponding to the target service domain name.
In this embodiment, a domain name convergence scheme based on service attributes is adopted, related backend service attributes are collected at the beginning of domain name application, information is delivered to a control center for processing and judging the service attributes, and after receiving input information of the control center, a dispatching center is configured to analyze a convergence domain name of a corresponding service. The domain name convergence refers to resolving a plurality of domain names to the same domain name, and resolving the domain name to the IP.
According to the domain name access method provided by the embodiment of the application, the target service domain name is divided according to the service attribute, the label corresponding to the target service domain name is determined according to the division result, the target service domain name is identified and resolved to be a unified service convergence domain name, the convergence domain name can be named through the service attribute, and then the convergence domain name is used for carrying out actual resolving and forwarding of the flow. The multi-domain names are accessed in groups according to the service attributes, so that the management of a large number of service domain names can be completed by managing a certain number of converged domain names. The management cost is greatly saved, and the management efficiency is improved.
Corresponding to the above embodiment, referring to fig. 6, an embodiment of the present application further provides a domain name access device 600, including:
a first receiving module 601, configured to receive a first input, where the first input is application information for requesting to access a target service domain name;
a determining module 602, configured to determine, in response to the first input, a target service label corresponding to the target service domain name;
a second receiving module 603, configured to receive a second input, where the second input is the target service label;
and a resolving module 604, responsive to the second input, for matching a convergence domain name corresponding to the target service label, resolving the target service domain name to the convergence domain name, and forwarding the traffic to a backend service of the target service according to the convergence domain name.
Optionally, the domain name access device 600 further includes:
a third receiving module 605, configured to receive a third input, where the third input is an input that the back-end service of the target service receives traffic forwarding;
an update module 606, responsive to the third input, to update the target business domain name to a monitoring configuration;
a fourth receiving module 607, configured to receive a fourth input, where the fourth input is the target service domain name resolution failure information;
the fault handling module 608, in response to the fourth input, performs a preset damage stopping operation according to the fault information.
Optionally, the parsing module 604 includes:
the resolution submodule 6041 is configured to resolve the converged domain name to the same group of VIP addresses, and forward the traffic to the back-end service of the target service according to the VIP addresses;
the fault handling module 608 includes:
a failure stopping module 6081 for stopping domain name resolution of the failure VIP address;
traffic forwarding module 6082 is configured to forward traffic of the failed VIP address to other VIP addresses in the same group.
Optionally, the domain name access device 600 further includes:
a setting module 609 is configured to set a target service line and a backend service name corresponding to the target service domain name.
According to the domain name access method provided by the embodiment of the application, the target service domain name is divided according to the service attribute, the label corresponding to the target service domain name is determined according to the division result, the target service domain name is identified and resolved to be a unified service convergence domain name, the convergence domain name can be named through the service attribute, and then the convergence domain name is used for carrying out actual resolving and forwarding of the flow. The multi-domain names are accessed in groups according to the service attributes, so that the management of a large number of service domain names can be completed by managing a certain number of converged domain names. The management cost is greatly saved, and the management efficiency is improved.
The exemplary embodiment of the application also provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor. The memory stores a computer program executable by the at least one processor for causing the electronic device to perform a method according to an embodiment of the application when executed by the at least one processor.
The exemplary embodiments of the present application also provide a non-transitory computer readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is for causing the computer to perform a method according to an embodiment of the present application.
The exemplary embodiments of the application also provide a computer program product comprising a computer program, wherein the computer program, when being executed by a processor of a computer, is for causing the computer to perform a method according to an embodiment of the application.
Referring to fig. 7, a block diagram of an electronic device 700 that may be a server or a client of the present application will now be described, which is an example of a hardware device that may be applied to aspects of the present application. Electronic devices are intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the applications described and/or claimed herein.
As shown in fig. 7, the electronic device 700 includes a computing unit 701 that can perform various appropriate actions and processes according to 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. In the RAM 703, various programs and data required for the operation of the device 700 may also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
Various components in the electronic device 700 are connected to the I/O interface 705, including: an input unit 706, an output unit 707, a storage unit 708, and a communication unit 709. The input unit 706 may be any type of device capable of inputting information to the electronic device 700, and the input unit 706 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device. The output unit 707 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. Storage unit 708 may include, but is not limited to, magnetic disks, optical disks. The communication unit 709 allows the 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 (TM) devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.
The computing unit 701 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 701 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized 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 that is tangibly embodied on 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 onto the electronic device 700 via the ROM 702 and/or the 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).
Program code for carrying out methods of the present application may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Claims (10)
1. A domain name access method, comprising:
receiving a first input, wherein the first input is application information for requesting to access a target service domain name;
responding to the first input, and determining a target service label corresponding to the target service domain name;
receiving a second input, wherein the second input is the target service label;
and responding to the second input, matching a convergence domain name corresponding to the target service label, resolving the target service domain name to the convergence domain name, and forwarding the traffic to the back-end service of the target service according to the convergence domain name.
2. The domain name access method according to claim 1, wherein the matching the convergent domain name corresponding to the target service label, resolving the target service domain name to the convergent domain name, and forwarding the traffic to the back-end service of the target service according to the convergent domain name, further comprises:
receiving a third input, wherein the third input is an input for receiving flow forwarding for the back-end service of the target service;
updating the target service domain name to a monitoring configuration in response to the third input;
receiving a fourth input, wherein the fourth input is the target service domain name resolution fault information;
and responding to the fourth input, and executing a preset damage stopping operation according to the fault information.
3. The domain name access method according to claim 2, wherein forwarding traffic to the backend service of the target traffic according to the converged domain name comprises:
resolving the converged domain name to the same group of VIP addresses, and forwarding the traffic to the back-end service of the target service according to the VIP addresses;
the responding to the fourth input, executing the preset damage stopping operation according to the fault information, comprises the following steps:
stopping domain name resolution of the fault VIP address;
traffic for the failed VIP address is forwarded to other VIP addresses of the same group.
4. The domain name access method according to claim 1, wherein before receiving the first input, further comprising:
and setting a target service line and a rear-end service name corresponding to the target service domain name.
5. A domain name access device, comprising:
the first receiving module is used for receiving a first input, wherein the first input is application information for requesting to access a target service domain name;
the determining module is used for responding to the first input and determining a target service label corresponding to the target service domain name;
the second receiving module is used for receiving a second input, and the second input is the target service label;
and the analysis module responds to the second input, matches the convergence domain name corresponding to the target service label, analyzes the target service domain name to the convergence domain name, and forwards the flow to the back-end service of the target service according to the convergence domain name.
6. The domain name access device of claim 5, wherein the domain name access device further comprises:
the third receiving module is used for receiving a third input, wherein the third input is the input of receiving the flow forwarding by the back-end service of the target service;
the updating module is used for responding to the third input and updating the target service domain name to a monitoring configuration;
the fourth receiving module is used for receiving a fourth input, and the fourth input is the fault information of the domain name resolution of the target service;
and the fault processing module responds to the fourth input and executes preset damage stopping operation according to the fault information.
7. The domain name access device of claim 6, wherein the resolution module comprises:
the analysis submodule is used for analyzing the converged domain name to the same group of VIP addresses, and forwarding the traffic to the back-end service of the target service according to the VIP addresses;
the fault handling module comprises:
the fault stopping module is used for stopping domain name resolution of the fault VIP address;
and the traffic forwarding module is used for forwarding the traffic of the fault VIP address to other VIP addresses in the same group.
8. The domain name access device of claim 5, wherein the domain name access device further comprises:
and the setting module is used for setting a target service line and a rear-end service name corresponding to the target service domain name.
9. An electronic device, comprising:
a processor; and
a memory in which a program is stored,
wherein the program comprises instructions which, when executed by the processor, cause the processor to perform the method according to any of claims 1-4.
10. A non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311111673.XA CN116980386A (en) | 2023-08-30 | 2023-08-30 | Domain name access method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311111673.XA CN116980386A (en) | 2023-08-30 | 2023-08-30 | Domain name access method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116980386A true CN116980386A (en) | 2023-10-31 |
Family
ID=88481615
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311111673.XA Pending CN116980386A (en) | 2023-08-30 | 2023-08-30 | Domain name access method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116980386A (en) |
-
2023
- 2023-08-30 CN CN202311111673.XA patent/CN116980386A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110839084B (en) | Session management method, device, equipment and medium | |
| CN113742031B (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN111935752B (en) | Gateway access method, device, computer equipment and storage medium | |
| WO2023066084A1 (en) | Computing power distribution method and apparatus, and computing power server | |
| EP4068725A1 (en) | Load balancing method and related device | |
| CN111897643B (en) | Thread pool configuration system, method, device and storage medium | |
| CN108600344A (en) | A kind of network access request dispatching method, device and storage medium | |
| CN108989399A (en) | A kind of cluster common data querying method, system, device and readable storage medium storing program for executing | |
| WO2021190659A1 (en) | System data acquisition method and apparatus, and medium and electronic device | |
| CN110519354A (en) | Distributed object storage system and service processing method and storage medium thereof | |
| CN114201294A (en) | Task processing method, device and system, electronic equipment and storage medium | |
| CN113012695B (en) | Intelligent control method and device, electronic equipment and computer readable storage medium | |
| EP3709571A1 (en) | Device management clustering | |
| CN116980386A (en) | Domain name access method and device, electronic equipment and readable storage medium | |
| CN113360689B (en) | Image retrieval system, method, related device and computer program product | |
| CN115827265A (en) | Transaction processing method, device, equipment and storage medium | |
| CN114070889A (en) | Configuration method, traffic forwarding method, device, storage medium, and program product | |
| CN114221906A (en) | Flow control method and device, electronic equipment and storage medium | |
| CN113285833B (en) | Method and device for acquiring information | |
| CN114006902B (en) | Cloud mobile phone restarting method, device, equipment and storage medium | |
| CN107124293A (en) | The protocol managerial approach and system of a kind of distributed network system (DNS) | |
| CN118227308A (en) | Task execution method and device, electronic equipment and storage medium | |
| CN116846866A (en) | Traffic scheduling method and device, electronic equipment and readable storage medium | |
| CN117478764A (en) | Service grid configuration method and device, electronic equipment and storage medium | |
| CN116112437A (en) | Traffic scheduling method and device, electronic equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |