Method, device, equipment, medium and product for acquiring IP (Internet Protocol) of DNS (Domain Name Server) exit

Abstract

The invention relates to the technical field of cloud computing CDN (Content Delivery Network), and discloses a method, device, equipment, medium and product for acquiring a DNS (Domain Name Server) exit IP (Internet Protocol), comprising the following steps: in response to an access operation on a target domain name, sending a request to a server rear end, the request at least comprising a target identifier; initiating a DNS request to an authoritative DNS server based on the target identifier; receiving a DNS response returned by the authoritative DNS server in response to the DNS request; and analyzing the DNS response, determining a DNS exit IP and displaying the DNS exit IP on the front-end page, the DNS exit IP corresponding to the target identifier. According to the scheme, the authoritative DNS server stores the corresponding relation between the DNS exit IP and the target identifier, when the DNS request is initiated at the rear end of the server, the DNS exit IP is returned according to the target identifier in the request, a user can quickly obtain the DNS exit IP in a web access mode, other additional operation is not needed, the boundary is simple, and the usability is high.

Description

Technical Field

[0001] The present invention relates to the field of cloud computing CDN technology, and in particular to methods, devices, equipment, media and products for obtaining DNS egress IP addresses. Background Art

[0002] DNS (Domain Name System) is a component of the Internet's standard protocols, responsible for translating domain names into Internet Protocol (IP) addresses, which computers use to identify each other. Currently, CDN (Content Delivery Network) acceleration relies primarily on server clusters deployed at edge nodes around the world. Through load balancing, content distribution, content management, and content storage, CDN server clusters offload the pressure from source site server clusters, allowing users to access cached resources nearby, avoiding network congestion and accelerating access speeds.

[0003] A user's access request first reaches a recursive DNS server, which then sends a query request to an authoritative DNS server for an edge service node. Typically, the authoritative DNS server determines which edge service node to use based on the recursive DNS server's egress IP address. If a user's recursive DNS server is misconfigured, the authoritative DNS server will be unable to accurately provide the user with the nearest edge service node. Related technologies typically use a client-side dig method for a fixed domain name, or a web page accessing a fixed domain name followed by a 302 redirect. This process is complex and difficult to use for users unfamiliar with the technology. Summary of the Invention

[0004] In view of this, the present invention provides a method, apparatus, device, medium and product for obtaining a DNS egress IP address, so as to solve the problem of high complexity in obtaining a DNS egress IP address.

[0005] In a first aspect, the present invention provides a method for obtaining a DNS egress IP address, the method comprising:

[0006] In response to an access operation to a target domain name, a request is sent to a server backend, wherein the request includes at least a target identifier;

[0007] Initiate a DNS request to the authoritative DNS server based on the target identifier;

[0008] Receiving a DNS response returned by the authoritative DNS server in response to the DNS request;

[0009] Parse the DNS response, determine the DNS exit IP and display the DNS exit IP on the front-end page, where the DNS exit IP corresponds to the target identifier.

[0010] In an optional implementation, in response to the access operation to the target domain name, issuing a request to the server backend includes:

[0011] In response to the access operation to the target domain name, a request is initiated to the server backend, and the request carries the target identifier.

[0012] In an optional implementation manner, initiating a DNS request to an authoritative DNS server based on the target identifier includes:

[0013] generating a first domain name corresponding to the target identifier based on the target identifier;

[0014] Generate a DNS request command based on the first domain name, and initiate the DNS request command to the authoritative DNS server.

[0015] In an optional implementation, the DNS response includes the DNS egress IP corresponding to the target identifier, and the DNS response is generated by the authoritative server based on a preset format.

[0016] In an optional embodiment, the method further includes:

[0017] The recursive server receives a first query request for the first domain name and sends the first query request to an authoritative server;

[0018] The recursive server receives the target domain name returned by the authoritative server in response to the first query request;

[0019] The target domain name is displayed, where the target domain name is used to access the front-end page.

[0020] In an optional embodiment, the method further includes:

[0021] The authoritative server records the DNS exit IP of the first query request in a memory in response to the first query request.

[0022] The method for obtaining a DNS exit IP provided in this embodiment includes: in response to an access operation to a target domain name, issuing a request to a server backend, wherein the request includes at least a target identifier; initiating a DNS request to an authoritative DNS server based on the target identifier; receiving a DNS response returned by the authoritative DNS server in response to the DNS request; parsing the DNS response, determining the DNS exit IP, and displaying the DNS exit IP on a front-end page, wherein the DNS exit IP corresponds to the target identifier. In this solution, the authoritative DNS server stores the correspondence between the DNS exit IP and the target identifier. When a DNS request is initiated on the server backend, the DNS exit IP is returned based on the target identifier in the request. Users can quickly obtain the DNS exit IP through web access without any additional operations, thus having a simple boundary and high usability.

[0023] In a second aspect, the present invention provides a device for obtaining a DNS egress IP, the device comprising:

[0024] A request issuing module, configured to issue a request to a server backend in response to an access operation to a target domain name, wherein the request includes at least a target identifier;

[0025] DNS request module, used to initiate a DNS request to the authoritative DNS server based on the target identifier;

[0026] a response receiving module, configured to receive a DNS response returned by the authoritative DNS server in response to the DNS request;

[0027] The response parsing module is used to parse the DNS response, determine the DNS exit IP and display the DNS exit IP on the front-end page, and the DNS exit IP corresponds to the target identifier.

[0028] In a third aspect, the present invention provides a computer device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0029] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method of the first aspect or any corresponding embodiment thereof.

[0030] In a fifth aspect, the present invention provides a computer program product comprising computer instructions for causing a computer to execute the method of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0032] Figure 1 1 is a flow chart of a method for obtaining a DNS egress IP address according to an embodiment of the present invention;

[0033] Figure 2 1 is a flow chart of another method for obtaining a DNS egress IP address according to an embodiment of the present invention;

[0034] Figure 3 1 is a flow chart of a method for obtaining a DNS egress IP address according to an embodiment of the present invention;

[0035] Figure 4 1 is a structural block diagram of an apparatus for obtaining a DNS egress IP address according to an embodiment of the present invention;

[0036] Figure 5 Schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0037] To make the purpose, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present invention.

[0038] The DNS system architecture typically includes two types of DNS servers, recursive servers and authoritative servers. Recursive DNS servers (LocalDNS) are servers that perform "queries," searching for information that connects users to websites. Authoritative DNS servers store the final record of domain names and respond to requests for domain names stored within their respective regions (the answers are usually configured by the domain name owner). There are multiple types of authoritative DNS servers, each with a specific function in the DNS hierarchy. Currently, CDN acceleration mainly relies on server clusters deployed at edge nodes around the world. Through load balancing, content publishing, content management, and content storage, the CDN server cluster shares the pressure of the source site server cluster, allowing users to obtain cached access resources nearby, avoiding network congestion and speeding up access.

[0039] A user's access request first reaches a recursive DNS server, which then sends a query request to an authoritative DNS server to obtain an edge service node. Typically, the authoritative DNS server determines which edge service node to use based on the recursive DNS server's egress IP address. If the user's recursive DNS server is misconfigured, the authoritative DNS server will be unable to accurately provide the nearest edge service node to the user. To ensure that users can access resources nearby, the recursive DNS server used by users to access resources is particularly important, as it directly affects the quality of user access. To promptly identify access quality issues, a method is needed to quickly obtain the DNS egress IP address used by the user.

[0040] According to an embodiment of the present invention, an embodiment of a method for obtaining a DNS egress IP is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0041] In this embodiment, a method for obtaining a DNS egress IP is provided. Figure 1 Flowchart of a method for obtaining a DNS egress IP according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0042] Step S101: In response to an access operation to a target domain name, a request is sent to a server backend.

[0043] The request includes at least a target identifier. The target domain name is a UUID (Universally Unique Identifier) domain name, which is the resolved IP address obtained by the user from the authoritative DNS server when accessing the DNS query website. The UUID is the target identifier. The UUID is used as a unique identifier for information. In this solution, the UUID is used to generate a unique subdomain name. This ensures that the subdomain name generated each time a user accesses is unique, ensuring that each DNS query is fresh and not affected by caching.

[0044] The user accesses the web front end of the IP address through a browser, and the web front end initiates a request to the web server back end, and inputs the UUID (target identifier) as a parameter in the request.

[0045] Step S102: Initiate a DNS request to an authoritative DNS server based on the target identifier.

[0046] After receiving the request from the web front-end, the server backend obtains the target identifier from the request and concatenates the target identifiers to generate a DNS request. Specifically, it generates the corresponding domain name based on the target identifier and initiates a TXT-type DNS request to the authoritative DNS server.

[0047] Step S103: Receive a DNS response returned by the authoritative DNS server in response to the DNS request.

[0048] After the server backend initiates a DNS request to the authoritative DNS server, it enters a waiting state, waiting for the authoritative DNS server to process the request and return a result. After receiving the DNS request, the authoritative DNS server searches its stored domain name resolution records for the IP address corresponding to the target identifier, namely the DNS egress IP address. The authoritative DNS server assembles a TXT-type DNS response with the DNS egress IP address corresponding to the target identifier in its memory and returns it to the server backend.

[0049] Optionally, the DNS response may also include other relevant information, such as TTL (Time To Live), which indicates the validity period of the DNS record in the cache. After this time, the record in the cache needs to be re-queried and updated.

[0050] In some optional implementations, the DNS response includes the DNS exit IP corresponding to the target identifier. The DNS response is generated by the authoritative server based on a preset format.

[0051] The authoritative DNS server will return a TXT-type DNS response to the server backend using the DNS export IP address corresponding to the UUID domain name in memory. For example, if the DNS export IP address is 2.2.2.2, the returned DNS response is as follows:

[0052] 123456789.dns.a.comTXT2.2.2.2.

[0053] Step S104, parse the DNS response, determine the DNS exit IP and display the DNS exit IP on the front-end page.

[0054] After the server backend receives the DNS response returned by the authoritative DNS server, it parses the DNS response. After the server backend resolves the DNS exit IP, it passes the DNS exit IP to the front-end page. The front-end page receives the DNS exit IP and displays it at the specified location on the page.

[0055] Specifically, if the DNS response is in TXT format: 123456789.dns.a.comTXT2.2.2.2, it is parsed to obtain the DNS exit IP: 2.2.2.2, and 2.2.2.2 is displayed on the front-end page.

[0056] The method for obtaining a DNS exit IP provided in this embodiment includes: in response to an access operation to a target domain name, issuing a request to a server backend, wherein the request includes at least a target identifier; initiating a DNS request to an authoritative DNS server based on the target identifier; receiving a DNS response returned by the authoritative DNS server in response to the DNS request; parsing the DNS response, determining the DNS exit IP, and displaying the DNS exit IP on a front-end page, wherein the DNS exit IP corresponds to the target identifier. In this solution, the authoritative DNS server stores the correspondence between the DNS exit IP and the target identifier. When a DNS request is initiated on the server backend, the DNS exit IP is returned based on the target identifier in the request. Users can quickly obtain the DNS exit IP through web access without any additional operations, thus having a simple boundary and high usability.

[0057] This embodiment provides a method for obtaining a DNS egress IP address, which includes the following steps:

[0058] Step S201: In response to an access operation to a target domain name, a request is sent to a server backend.

[0059] Specifically, step S201 includes: in response to an access operation to a target domain name, initiating a request to a server backend.

[0060] The request carries the target identifier. For example, if the target domain name is 1.1.1.1 and the target identifier is 123456789, the user uses a browser to access the web frontend corresponding to the address 1.1.1.1. The web frontend initiates a request to the web server backend and inputs the target identifier as a parameter. The target identifier is a randomly generated UUID.

[0061] Step S202: Initiate a DNS request to an authoritative DNS server based on the target identifier.

[0062] Specifically, step S202 includes:

[0063] Step S2021: Generate a first domain name corresponding to the target identifier based on the target identifier.

[0064] Step S2022: Generate a DNS request command based on the first domain name, and initiate the DNS request command to the authoritative DNS server.

[0065] After receiving the request from the web front-end, the web server backend extracts the target identifier (i.e., UUID) from the request. Taking the target identifier 123456789 as an example, it generates the first domain name 123456789.dns.a.com by splicing. Based on the first domain name, it initiates a TXT-type DNS request to the authoritative DNS server. As an example, the request command is as follows:

[0066] Dig@<authoritative DNS server IP>123456789.dns.a.com -t TXT.

[0067] Step S203: Receive a DNS response returned by the authoritative DNS server in response to the DNS request.

[0068] For details, please see Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.

[0069] Step S204, parse the DNS response, determine the DNS exit IP and display the DNS exit IP on the front-end page.

[0070] For details, please see Figure 1 Step S104 of the illustrated embodiment will not be described in detail here.

[0071] This embodiment provides a method for obtaining the DNS egress IP. Figure 2 Flowchart of a method for obtaining a DNS egress IP according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0072] Step S301: The recursive server receives a first query request for a first domain name, and sends the first query request to an authoritative server.

[0073] A user uses a browser to access the web frontend corresponding to the website domain name. The web frontend randomly generates a UUID string, which is the target identifier, and creates a UUID domain name webpage prefixed with the UUID. The browser then initiates a first query request for the first domain name to the entry IP address of the recursive DNS (LocalDNS) server. The recursive server initiates the first query request to the authoritative DNS server via the exit IP address.

[0074] As an example, a user visits the web front end corresponding to the first domain name: www.a.com through a browser, and the web front end randomly generates a target identifier (UUID) and embeds a UUID domain name web page with the UUID as a prefix through an iframe. For example:

[0075] UUID: 123456789;

[0076] The following is an example of embedding code in a web page:

[0077] <iframe id="myFrame"src="http: / /

[0078] 123456789.dns.a.com / 123456789">.

[0079] The browser initiates a first query request for the UUID domain name 123456789.dns.a.com (the first domain name) to the entry IP of the recursive server. The first query request is a UUID domain name request.

[0080] The recursive server initiates a first query request for 123456789.dns.a.com (the first domain name) to the authoritative DNS server through the egress IP.

[0081] Step S302: The recursive server receives the target domain name returned by the authoritative server in response to the first query request.

[0082] After receiving the first query request, the authoritative server returns a domain name resolution record to the recursive server, where the domain name resolution record includes the target domain name.

[0083] In some optional implementations, the authoritative server records the DNS exit IP of the first query request in a memory in response to the first query request.

[0084] After receiving the first query request, the authoritative DNS server will not only return the domain name resolution record, but also record the DNS exit IP that initiated the first query request in the memory.

[0085] As an example, in response to the first query request, the authoritative server returns a domain name resolution record including the target domain name 1.1.1.1, and records in the memory the DNS exit IP address that initiated the first query request as 2.2.2.2.

[0086] Step S303: Display the target domain name, where the target domain name is used to access the front-end page.

[0087] After receiving the target domain name from the authoritative server, the recursive server returns the target domain name to the browser, and the user can access the front-end corresponding to the target domain name through the browser.

[0088] As an example, the recursive server returns the UUID domain name resolution record 1.1.1.1 (target domain name) to the browser, and the user accesses the front end corresponding to the 1.1.1.1 address through the browser.

[0089] In this embodiment, a method for obtaining the DNS egress IP is provided, such as Figure 3As shown, the method includes the following steps:

[0090] First, the user can access the web front-end of the domain name website through a browser. The web front-end randomly generates a target identifier UUID and generates a corresponding domain name web page. It initiates a UUID domain name DNS query request (first query request) to the recursive DNS, and the recursive DNS initiates the first query request to the authoritative DNS. The authoritative DNS returns a DNS response to the recursive DNS. The recursive DNS feeds back the target domain name in the response to the front-end web page and records the DNS exit IP in the memory. When the user accesses the front-end web page of the target domain name through a browser, it initiates a DNS query request to the server back-end. The authoritative DNS responds to the request and feeds back a DNS response, which includes the DNS exit IP, and displays the DNS exit IP on the front-end page.

[0091] The present invention generates a random UUID domain name by embedding it in a web page. The authoritative DNS server saves the DNS exit IP address in the TXT record of the UUID domain name. The web backend initiates a TXT query request and returns the result, displaying the DNS exit IP address to the user. This allows for quick access to the DNS exit IP address used without requiring any additional user operations, making it simple, convenient, and easy to use.

[0092] This embodiment also provides a device for obtaining a DNS egress IP address. This device is used to implement the above-mentioned embodiments and preferred embodiments, and will not be repeated here. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0093] This embodiment provides a device for obtaining DNS egress IP, such as Figure 4 Shown, including:

[0094] A request issuing module, configured to issue a request to a server backend in response to an access operation to a target domain name, wherein the request includes at least a target identifier;

[0095] DNS request module, used to initiate a DNS request to the authoritative DNS server based on the target identifier;

[0096] a response receiving module, configured to receive a DNS response returned by the authoritative DNS server in response to the DNS request;

[0097] The response parsing module is used to parse the DNS response, determine the DNS exit IP and display the DNS exit IP on the front-end page, and the DNS exit IP corresponds to the target identifier.

[0098] In some optional implementations, the request issuing module includes:

[0099] The request issuing unit is used to initiate a request to the server backend in response to an access operation to the target domain name, wherein the request carries a target identifier.

[0100] In some optional implementations, the DNS request module includes:

[0101] A first domain name generating unit, configured to generate a first domain name corresponding to the target identifier based on the target identifier;

[0102] A command initiating unit is used to generate a DNS request command based on the first domain name and initiate the DNS request command to the authoritative DNS server.

[0103] In some optional implementations, the DNS response includes the DNS egress IP corresponding to the target identifier, and the DNS response is generated by the authoritative server based on a preset format.

[0104] In some optional embodiments, the device further comprises:

[0105] a first query request module, configured to receive, by the recursive server, a first query request for the first domain name, and send the first query request to the authoritative server;

[0106] a domain name receiving module, configured for the recursive server to receive a target domain name returned by the authoritative server in response to the first query request;

[0107] The domain name display module is used to display the target domain name, and the target domain name is used to access the front-end page.

[0108] In some optional embodiments, the device further comprises:

[0109] A memory recording module is used for the authoritative server to record the DNS exit IP of the first query request in the memory in response to the first query request.

[0110] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0111] The device for obtaining the DNS exit IP in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0112] The embodiment of the present invention also provides a computer device having the above Figure 4 The device shown is used to obtain the DNS exit IP.

[0113] See also Figure 5 , Figure 5 is a structural diagram of a computer device provided by an optional embodiment of the present invention, such as Figure 5 As shown, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components utilize different buses to communicate with each other and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in the memory or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Equally, multiple computer devices can be connected, and each device provides part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 5 A processor 10 is taken as an example.

[0114] The processor 10 may be a central processing unit, a network processor, or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic, or any combination thereof.

[0115] The memory 20 stores instructions that can be executed by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0116] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store data created based on the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0117] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0118] The computer device further includes a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0119] The embodiment of the present invention also provides a computer-readable storage medium. The above-mentioned method according to the embodiment of the present invention can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the method shown in the above embodiment is implemented.

[0120] A portion of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the form in which the computer program instruction exists in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc. Accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium that can be accessed by the computer.

[0121] Although the embodiments of the present invention have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention. Such modifications and variations are all within the scope defined by the present invention.

Claims

1. A method for obtaining a DNS exit IP, characterized in that: The method comprises: In response to an access operation to a target domain name, a request is sent to a server backend, wherein the request includes at least a target identifier; Initiate a DNS request to the authoritative DNS server based on the target identifier; Receiving a DNS response returned by the authoritative DNS server in response to the DNS request; Parse the DNS response, determine the DNS exit IP and display the DNS exit IP on the front-end page, where the DNS exit IP corresponds to the target identifier.

2. The method according to claim 1, characterized in that The step of sending a request to a server backend in response to an access operation to a target domain name includes: In response to the access operation to the target domain name, a request is initiated to the server backend, and the request carries the target identifier.

3. The method according to claim 1, characterized in that The initiating a DNS request to the authoritative DNS server based on the target identifier includes: generating a first domain name corresponding to the target identifier based on the target identifier; Generate a DNS request command based on the first domain name, and initiate the DNS request command to the authoritative DNS server.

4. The method according to claim 3, characterized in that The DNS response includes the DNS exit IP corresponding to the target identifier, and the DNS response is generated by the authoritative server based on a preset format.

5. The method according to claim 3, characterized in that The method further comprises: The recursive server receives a first query request for the first domain name and sends the first query request to an authoritative server; The recursive server receives the target domain name returned by the authoritative server in response to the first query request; The target domain name is displayed, where the target domain name is used to access the front-end page.

6. The method according to claim 5, characterized in that The method further comprises: The authoritative server records the DNS exit IP of the first query request in a memory in response to the first query request.

7. A device for obtaining a DNS exit IP, characterized in that: The device comprises: A request issuing module, configured to issue a request to a server backend in response to an access operation to a target domain name, wherein the request includes at least a target identifier; DNS request module, used to initiate a DNS request to the authoritative DNS server based on the target identifier; a response receiving module, configured to receive a DNS response returned by the authoritative DNS server in response to the DNS request; The response parsing module is used to parse the DNS response, determine the DNS exit IP and display the DNS exit IP on the front-end page, and the DNS exit IP corresponds to the target identifier.

8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for obtaining a DNS exit IP according to any one of claims 1 to 6 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for obtaining a DNS egress IP address according to any one of claims 1 to 6.

10. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the method for obtaining a DNS egress IP address according to any one of claims 1 to 6.

Images