CN114301872B - Domain name based access method and device, electronic equipment and storage medium - Google Patents

Abstract

The application provides a domain name-based access method and device, electronic equipment and storage medium, wherein the method comprises the steps of intercepting a user access request initiated by a client under a user login state; determining a target domain name list to which the domain name belongs according to the domain name carried by the user access request; and obtaining an internet protocol address corresponding to the domain name according to a domain name resolution path corresponding to the target domain name list, and returning the internet protocol address to the client. Therefore, an intranet domain name server is not required to forward the domain name, the resolution efficiency of the domain name is improved, and the access efficiency is improved.

Description

Domain name-based access methods and devices, electronic equipment, and storage media

Technical field

This application relates to the field of communication technology, and in particular to a domain name-based access method and device, electronic equipment, and storage media.

Background technique

DNS (Domain Name System) is a distributed database that records the mapping relationship between domain names and IP addresses. DNS resolution is to find the IP address corresponding to the mapping relationship of the domain name and return it.

Domain names can help users remember and manage resource services more conveniently. After logging in to the access control system, users can access authorized resources through intranet IP addresses or domain names. Intranet domain names rely on intranet DNS resolution. In traditional mode, all domain name requests are intercepted on the client and sent to the internal domain name server through the tunnel. If the internal domain name server is deployed in an environment that cannot access the external network, it usually cannot resolve the external network domain name, resulting in the external network domain name entering the internal network DNS being unavailable; if the internal network domain name server is cascaded to a server that can resolve the external network DNS, then the external domain name will be unavailable. As the cascade depth increases, the access efficiency decreases greatly.

Contents of the invention

The embodiment of this application provides an access method based on domain name to improve access efficiency.

The embodiment of this application provides a domain name-based access method, including:

When the user is logged in, intercept user access requests initiated by the client;

According to the domain name carried in the user access request, determine the target domain name list to which the domain name belongs;

According to the domain name resolution path corresponding to the target domain name list, the Internet protocol address corresponding to the domain name name is obtained, and the Internet protocol address is returned to the client.

In one embodiment, determining the target domain name list to which the domain name belongs based on the domain name carried in the user access request includes:

According to the domain name carried in the user's access request, determine whether the domain name appears in the virtual domain name list, the external network domain name list, or the intranet domain name list;

The domain name list in which the domain name appears is used as the target domain name list.

In one embodiment, the method further includes:

If any domain name appears in both the external network domain name list and the internal network domain name list, the external network domain name list is used as the target domain name list.

In one embodiment, obtaining the Internet protocol address corresponding to the domain name based on the domain name resolution path corresponding to the target domain name list includes:

If the target domain name list is a virtual domain name list, query the Internet protocol address corresponding to the domain name name locally.

In one embodiment, obtaining the Internet protocol address corresponding to the domain name based on the domain name resolution path corresponding to the target domain name list includes:

If the target domain name list is an external network domain name list, send the domain name name to the external network domain name server, and obtain the Internet protocol address corresponding to the domain name name returned by the external network domain name server.

In one embodiment, obtaining the Internet protocol address corresponding to the domain name based on the domain name resolution path corresponding to the target domain name list includes:

If the target domain name list is an intranet domain name list, send the domain name name to the intranet domain name server, and obtain the Internet protocol address corresponding to the domain name name returned by the intranet domain name server.

In one embodiment, before intercepting the user access request initiated by the client in the user login state, the method further includes:

Create a domain name service locally on the client, and set the highest priority of the domain name service to intercept user access requests initiated by the client.

In one embodiment, the method further includes:

When the user is not logged in, the user access request is sent to the external network domain name server, and the Internet protocol address corresponding to the domain name returned by the external network domain name server is obtained.

In one embodiment, determining the target domain name list to which the domain name belongs based on the domain name carried in the user access request includes:

According to the domain name and domain name type carried in the user access request, if the domain name type is a virtual domain name, search for the domain name in the virtual domain name list;

If the domain name is found in the virtual domain name list, the virtual domain name list is determined to be the target domain name list.

The embodiment of this application also provides a domain name-based access device, including:

The request interception module is used to intercept user access requests initiated by the client when the user is logged in;

A list determination module, configured to determine the target domain name list to which the domain name belongs based on the domain name carried in the user access request;

The domain name processing module is configured to obtain the Internet protocol address corresponding to the domain name name according to the domain name resolution path corresponding to the target domain name list, and return the Internet protocol address to the client.

An embodiment of the present application also provides an electronic device, where the electronic device includes:

processor;

Memory used to store instructions executable by the processor;

Wherein, the processor is configured to execute the above domain name-based access method.

Embodiments of the present application also provide a computer-readable storage medium, the storage medium stores a computer program, and the computer program can be executed by a processor to complete the above domain name-based access method.

The technical solution provided by the above embodiments of this application intercepts the user access request initiated by the client; determines the target domain name list to which the domain name belongs based on the domain name carried by the user access request; and obtains the target domain name list according to the domain name resolution path corresponding to the target domain name list. The Internet protocol address corresponding to the domain name name eliminates the need for the intranet domain name server to forward the domain name, improves the domain name resolution efficiency, and thus improves the access efficiency.

Description of drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the drawings required to be used in the embodiments of the present application will be briefly introduced below.

Figure 1 is a schematic diagram of the application scenario of the domain name-based access method provided by the embodiment of the present application;

Figure 2 is a schematic structural diagram of an electronic device provided by an embodiment of the present application;

Figure 3 is a schematic flow chart of a domain name-based access method provided by an embodiment of the present application;

Figure 4 is a schematic diagram of the overall architecture of the domain name-based access method provided by the embodiment of the present application;

Figure 5 is a schematic diagram of the domain name resolution status when the user is not logged in to the access control system;

Figure 6 is a schematic diagram of the domain name resolution status after the user logs in to the access control system;

Figure 7 is a block diagram of a domain name-based access device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

Similar reference numerals and letters refer to similar items in the following figures, so that once an item is defined in one figure, it does not need further definition or explanation in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", etc. are only used to differentiate the description and cannot be understood as indicating or implying relative importance.

Figure 1 is a schematic diagram of the application scenario of the domain name-based access method provided by the embodiment of the present application. As shown in Figure 1, the application scenario includes a first terminal 110, an internal network DNS server 120, an external network DNS server 130, an internal network resource server 140, and an external network resource server 150. The first terminal 110 is connected to the internal network DNS server 120, the external network DNS server 130, the internal network resource server 140 and the external network resource server 150 respectively.

The first terminal 110 may be a desktop computer, a notebook computer, a smartphone, or other smart terminal. The first terminal 110 can run a client such as a browser and can also run an access control system. The access control system of the first terminal 110 can execute the method provided in the embodiments of this application to intercept user access requests initiated by the client when the user is logged in. ; According to the domain name carried in the user access request, determine the target domain name list to which the domain name belongs; according to the domain name resolution path corresponding to the target domain name list, obtain the Internet Protocol address (IP address) corresponding to the domain name, and returns the Internet Protocol address to the client.

In one embodiment, if the domain name is in the intranet domain name list, the access control system may send the domain name to the intranet DNS server 120 for analysis, and obtain the IP address and return it to the client. The client can then access the intranet resource server 140 according to the IP address returned by the intranet DNS server 120 .

In another embodiment, if the domain name is in the external network domain name list, the access control system can send the domain name to the external network DNS server 130 for analysis, and obtain the IP address and return it to the client. The client can then access the external network resource server 150 based on the IP address returned by the external DNS server 130, thereby improving access efficiency based on the domain name.

FIG. 2 is a schematic structural diagram of an electronic device provided by an embodiment of the present application. The electronic device 200 can serve as the above-mentioned first terminal 110, and the electronic device 200 can be used to execute the domain name-based access method provided in the embodiment of the present application. As shown in FIG. 2 , the electronic device 200 includes: one or more processors 202 and one or more memories 204 that store instructions executable by the processors. The processor 202 is configured to execute the domain name-based access method provided in the following embodiments of this application.

The processor 202 may be a device including a central processing unit (CPU), a graphics processing unit (GPU), or other forms of processing units with data processing capabilities and/or instruction execution capabilities, and may perform processing on the electronic device 200 The data of other components is processed, and other components in the electronic device 200 can also be controlled to perform desired functions.

The memory 204 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and/or cache memory (cache). The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 202 may execute the program instructions to implement the domain name-based access method described below. Various application programs and various data, such as various data used and/or generated by the application programs, may also be stored in the computer-readable storage medium.

In one embodiment, the electronic device 200 shown in FIG. 2 may also include an input device 206, an output device 208, and a data acquisition device 210. These components are interconnected through a bus system 212 and/or other forms of connection mechanisms (not shown). . It should be noted that the components and structures of the electronic device 200 shown in FIG. 2 are only exemplary and not restrictive. The electronic device 200 may also have other components and structures as needed.

The input device 206 may be a device used by the user to input instructions, and may include one or more of a keyboard, a mouse, a microphone, a touch screen, and the like. The output device 208 may output various information (eg, images or sounds) to the outside (eg, a user), and may include one or more of a display, a speaker, and the like. The data acquisition device 210 can acquire images of objects and store the acquired images in the memory 204 for use by other components. For example, the data collection device 210 may be a camera.

In one embodiment, each component in the example electronic device 200 used to implement the domain name-based access method in the embodiment of the present application can be integrated or distributed, such as the processor 202, the memory 204, the input device 206 and the The output device 208 is integrated into one body, while the data collection device 210 is provided separately.

In one embodiment, the example electronic device 200 used to implement the domain name-based access method of the embodiment of the present application can be implemented as a smart device such as a laptop computer, a desktop computer, a smart phone, etc.

Figure 3 is a schematic flowchart of a domain name-based access method provided by an embodiment of the present application. This method can be executed by the first terminal 110 in the application scenario shown in Figure 1. As shown in Figure 3, the method includes the following steps S310 to S330.

Step S310: In the user login state, intercept the user access request initiated by the client.

The first terminal is deployed with an access control system, and the user can log in to the access control system through the account and password, thereby entering the user login state. The access control system can intercept user access requests initiated by the client. For example, the client can be a browser. User access requests can include information such as domain name and domain name type. The access control system can intercept the domain name request message initiated by the client (ie, user access request), parse the message content, and obtain the domain name name and query type queried by the user.

It should be noted that when multiple DNS addresses are configured, DNS priority is used to indicate the order in which the operating system sends DNS requests. For example, the Windows operating system can be configured with a preferred DNS server and an alternative DNS server. The preferred DNS server takes precedence over the alternative. The two For DNS addresses, those with lower interface hops take precedence over those with higher hops; Linux operating systems and Mac operating systems can configure the global DNS order. The higher the position, the higher the priority.

Therefore, after the user logs in to the access control system, the access control system can create a domain name service locally on the client and set the highest priority of the domain name service. Therefore, access requests can first pass through the locally created domain name service, thereby intercepting user access requests initiated by the client. In one embodiment, a DNS service can be created on the client's local 127.0.0.1 address port 53 to listen for local user access requests. The local domain name service policy can perform corresponding processing actions based on the domain name requested by the user, including directly constructing a DNS response to return the IP address bound to the domain name, sending the domain name to the intranet DNS server for resolution, or sending the domain name to Resolve to the external DNS server, see below for details.

Step S320: Determine a target domain name list to which the domain name belongs based on the domain name carried in the user access request.

This application embodiment may have three types of domain name lists, a virtual domain name list, an external network domain name list, and an intranet domain name list. The target domain name list may be any of the above three domain name lists. Which domain name list the domain name is in is the target domain name list.

For example, the domain name may be demo.c.com. In one embodiment, based on the domain name carried in the user's access request, it may be determined whether the domain name appears in the virtual domain name list, the external domain name list, or the internal domain name list. Domain name list; use the domain name list in which the domain name appears as the target domain name list.

The virtual domain name list, external network domain name list and intranet domain name list can be configured in advance. The virtual domain name list is relative to the real domain name and does not require domain name server resolution. The IP address corresponding to the virtual domain name can be directly queried locally. The domain name in the intranet domain name list is parsed by the intranet domain name server to obtain the IP address corresponding to the domain name. The domain name in the external network domain name list is parsed by the external network domain name server to obtain the IP address corresponding to the domain name.

For example, if a domain name appears in a virtual domain list, the virtual domain name list is the target domain name list. If the domain name appears in the intranet domain name list, the intranet domain name list is the target domain name list. If the domain name appears in the external domain name list, the external domain name list is the target domain name list.

Step S330: Obtain the Internet protocol address corresponding to the domain name name according to the domain name resolution path corresponding to the target domain name list, and return the Internet protocol address to the client. The domain name resolution path is used to represent which domain name service system is responsible for parsing the domain name and obtaining the IP address. The IP address can be returned to the client that initiated the user access request, and the client can then perform a handshake operation with the resource server corresponding to the IP address based on the IP address to establish a connection. The client begins to construct a request message and requests the resource server to obtain resources.

In one embodiment, if the target domain name list is a virtual domain name list, the Internet protocol address corresponding to the domain name name is locally queried.

Configure the one-to-one correspondence between virtual domain names and IPs through policies. The domain name here does not need to be resolved on the DNS server. Compared with configuring it on the DNS server, user access is faster because a DNS response packet is directly constructed after local query and the IP address is returned. , will no longer be passed out. Achieving efficient response to user access requests can also solve the problem of using domain names by binding IPs to virtual domain names when there is no DNS server.

In one embodiment, if the target domain name list is an external network domain name list, the domain name name is sent to the external network domain name server, and the Internet protocol address corresponding to the domain name name returned by the external network domain name server is obtained. If the target domain name list is an intranet domain name list, send the domain name name to the intranet domain name server, and obtain the Internet protocol address corresponding to the domain name name returned by the intranet domain name server.

The technical solution provided by the above embodiments of this application intercepts the user access request initiated by the client; determines the target domain name list to which the domain name belongs based on the domain name carried by the user access request; and obtains the target domain name list according to the domain name resolution path corresponding to the target domain name list. The Internet protocol address corresponding to the domain name name eliminates the need for the intranet domain name server to forward the domain name, improves the domain name resolution efficiency, and thus improves the access efficiency.

In one embodiment, if any domain name appears in both the external network domain name list and the internal network domain name list, the external network domain name list can be used as the target domain name list.

For example, the domain name format *.demo.d.com is in the intranet domain name list, and the domain name is bbs.demo.d.com, which points to external network resources. The description rules of the above domain name format are the same, so the domain name bbs.demo.d.com can be considered to appear in both the external network domain name list and the internal network domain name list. At this time, the external network domain name list can be used as the target domain name list.

Of course, depending on the specific application scenarios, you can also configure that when a domain name appears in both the external network domain name list and the internal network domain name list, the internal network domain name list will be used as the target domain name list by default.

In one embodiment, the user access request may include the domain name type in addition to the domain name. The access control system may search the virtual domain name list according to the domain name name and domain name type carried by the user access request. If the domain name type is a virtual domain name, The domain name name; if the domain name name is found in the virtual domain name list, determine that the virtual domain name list is the target domain name list.

It should be noted that the domain name type is used to indicate whether the domain name is a virtual domain name or a real domain name. If the domain name type is a virtual domain name, you can directly search whether the domain name exists in the virtual domain name list, thereby improving the efficiency of determining which list the domain name belongs to.

Figure 4 is a schematic diagram of the overall architecture of the domain name-based access method provided by the embodiment of the present application. As shown in Figure 4, it includes the following processes:

(1) Create a local DNS service: Create a DNS service on the client's local 127.0.0.1 address port 53 and listen for local DNS requests;

(2) Set the local DNS service to have the highest priority, so that DND requests go through the local DNS service first;

(3) DNS interception: intercept user access requests initiated by the client, and obtain the domain name and domain name type through analysis;

(4) Separation strategy: Based on the domain name requested by the user, perform corresponding processing actions, including directly constructing a DNS response to return the bound IP address, sending the domain name to the intranet DNS server for resolution, and sending the domain name to the external network DNS server. parse.

Among them, the local original DNS configuration refers to the default sending address of user access requests before enabling the local high-priority DNS service. In one embodiment, when the user is not logged in, the user access request is directly sent to the external domain name server, and the Internet protocol address corresponding to the domain name returned by the external domain name server is obtained.

In one embodiment, the following types of resources may be available under the user login access control system:

Resource A, intranet resource, fixed intranet IP is 10.92.2.250. To facilitate user memory, configure the domain name binding IP in the DNS policy, demo.a.com@10.92.2.250;

Resource B is an intranet resource. The domain name is fixed demo.b.com and the IP is not fixed. The updated IP address will be synchronized with the intranet DNS server;

Resource C1, intranet resource, domain name demo.c.com;

Resource C2, external network resource, domain name demo.c.com, C1 and C2 share the domain name demo.c.com, pointing to different resources at different times. Before logging in to the access control system, it points to the external network resource C2, and after logging in to the access control system, it points to the intranet. ResourceC1;

Resource D, intranet resources, a collection of multiple intranet resources with the same domain name suffix, the domain name format is *.demo.d.com;

Resource E is an external network resource. The domain name is bbs.demo.d.com. It has the same description rules as resource D, but it points to external network resources.

Figure 5 is a schematic diagram of the domain name resolution status when the user is not logged in to the access control system. The intranet domain name cannot be resolved to the correct intranet IP address, involving resource A, resource B, and resource D; demo.c.com points to the outside through external network DNS resolution. Network resource C2; bbs.demo.d.com points to external network resource E through external network DNS resolution.

Figure 6 is a schematic diagram of the domain name resolution status after the user logs in to the access control system. demo.a.com is in the virtual domain name list. According to the IP address bound to the domain name, it is directly located to resource A; demo.b.com, demo.c. In the list of intranet domain names, com and oa.demo.d.com obtain IP addresses through intranet DNS server resolution and point to corresponding intranet resources respectively; bbs.demo.d.com sets an exception for intranet resolution (that is, the external domain name list), the IP address is obtained directly from the external network DNS and points to the external network resource E.

In the existing technology, if the internal domain name server is deployed in an environment that cannot access the external network, it is usually unable to resolve the external network domain name, resulting in the external network domain name entering the internal network DNS being unavailable; if the internal network domain name server is cascaded, it can resolve the external network DNS For servers, as the cascade depth increases, the access efficiency drops greatly. The solution provided by the above embodiments of the present application can avoid relying on system logic such as DNS timeout switching, active/standby switching, and unresponsive switching, and accurately support user domain name access requests.

The above solution can realize cross-domain name usage scenarios between internal and external networks by flexibly configuring intranet DNS servers and external network DNS servers without modifying the existing DNS server configuration and cascade status, and efficiently complete domain name resolution and forwarding.

The following are device embodiments of the present application, which can be used to execute the above domain name-based access method embodiments of the present application. For details not disclosed in the device embodiments of this application, please refer to the domain name-based access method embodiments of this application.

Figure 7 is a block diagram of a domain name-based access device according to an embodiment of the present application. As shown in Figure 7, the device includes: a request interception module 710, a list determination module 720, and a domain name processing module 730.

The request interception module 710 is used to intercept user access requests initiated by the client when the user is logged in;

The list determination module 720 is configured to determine the target domain name list to which the domain name belongs based on the domain name carried in the user access request;

The domain name processing module 730 is configured to obtain the Internet protocol address corresponding to the domain name name according to the domain name resolution path corresponding to the target domain name list, and return the Internet protocol address to the client.

For details on the implementation process of the functions and roles of each module in the above device, please refer to the implementation process of the corresponding steps in the above domain name-based access method, which will not be described again here.

In the several embodiments provided in this application, the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are only illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the possible implementation architecture, functions and functions of the devices, methods and computer program products according to multiple embodiments of the present application. operate. In this regard, each block in the flowchart or block diagram may represent a module, segment, or portion of code that contains one or more executable functions for implementing the specified logical function instruction. In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two consecutive blocks may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. It will also be noted that each block of the block diagram and/or flowchart illustration, and combinations of blocks in the block diagram and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts. , or can be implemented using a combination of specialized hardware and computer instructions.

In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, each module can exist alone, or two or more modules can be integrated to form an independent part.

If functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .

Claims (11)

1. The access method based on the domain name is characterized in that domain name service is locally created at a client, the highest priority of the domain name service is set, a user access request firstly passes through the locally created domain name service, and the domain name service plays a role in intercepting the user access request initiated by the client, and the method comprises the following steps:

under the user login state, intercepting a user access request initiated by a client;

determining a target domain name list to which the domain name belongs according to the domain name carried by the user access request;

according to the domain name resolution path corresponding to the target domain name list, obtaining an internet protocol address corresponding to the domain name, and returning the internet protocol address to the client; the domain name resolution path is used to characterize which domain name service system is responsible for resolving the domain name to obtain the internet protocol address.

2. The method according to claim 1, wherein the determining, according to the domain name carried by the user access request, a target domain name list to which the domain name belongs includes:

judging whether the domain name appears in a virtual domain name list, an external network domain name list or an internal network domain name list according to the domain name carried by the user access request;

and taking the domain name list with the domain name as the target domain name list.

3. The method according to claim 2, wherein the method further comprises:

and if any domain name appears in the external network domain name list and the internal network domain name list at the same time, taking the external network domain name list as the target domain name list.

4. The method according to claim 1, wherein the obtaining the internet protocol address corresponding to the domain name according to the domain name resolution path corresponding to the target domain name list includes:

and if the target domain name list is a virtual domain name list, locally inquiring an Internet protocol address corresponding to the domain name.

5. The method according to claim 1, wherein the obtaining the internet protocol address corresponding to the domain name according to the domain name resolution path corresponding to the target domain name list includes:

and if the target domain name list is an external network domain name list, sending the domain name to an external network domain name server, and obtaining an internet protocol address corresponding to the domain name returned by the external network domain name server.

6. The method according to claim 1, wherein the obtaining the internet protocol address corresponding to the domain name according to the domain name resolution path corresponding to the target domain name list includes:

and if the target domain name list is an intranet domain name list, sending the domain name to an intranet domain name server, and obtaining an internet protocol address corresponding to the domain name returned by the intranet domain name server.

7. The method according to claim 1, wherein the method further comprises:

and in the state that the user is not logged in, sending the user access request to an external network domain name server to obtain an internet protocol address corresponding to the domain name returned by the external network domain name server.

8. The method according to claim 1, wherein the determining, according to the domain name carried by the user access request, a target domain name list to which the domain name belongs includes:

according to the domain name and the domain name type carried by the user access request, if the domain name type is a virtual domain name, searching the domain name in a virtual domain name list;

and if the domain name is found in the virtual domain name list, determining the virtual domain name list as the target domain name list.

9. A domain name based access device, characterized in that domain name service is locally created at a client, and the highest priority of the domain name service is set, a user access request first passes through the locally created domain name service, and the domain name service plays a role in intercepting the user access request initiated by the client, the device comprises:

the request interception module is used for intercepting a user access request initiated by the client under a user login state;

the list determining module is used for determining a target domain name list to which the domain name belongs according to the domain name carried by the user access request;

the domain name processing module is used for obtaining an internet protocol address corresponding to the domain name according to a domain name resolution path corresponding to the target domain name list and returning the internet protocol address to the client; the domain name resolution path is used to characterize which domain name service system is responsible for resolving the domain name to obtain the internet protocol address.

10. An electronic device, the electronic device comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to perform the domain name based access method of any of claims 1-8.

11. A computer readable storage medium, characterized in that the storage medium stores a computer program executable by a processor to perform the domain name based access method of any of claims 1-8.