CN114666277B - Domain name based data processing method and device - Google Patents

Abstract

The application discloses a data processing method based on domain name, which can be applied to a registry, and comprises the following steps: and determining a hot spot domain name, and correspondingly storing the name of the hot spot domain name, the registration state of the hot spot domain name and a data source corresponding to the hot spot domain name into a cache. The cache referred to herein may be a cache independently managed by the registry. The data source corresponding to the hot spot domain name is used for storing the information of the hot spot domain name when the hot spot domain name is a registered domain name, and the data source of the hot spot domain name is: a shared registry SRS database or a hotspot domain name database. The caching can process and shunt part of the requests related to the hot spot domain name when the registry receives the requests related to the hot spot domain name, so that the performance pressure of the SRS system is reduced, and correspondingly, the service quality of the SRS system can be improved.

Description

A data processing method and device based on domain name

Technical field

The present application relates to the field of computer software, and in particular to a domain name-based data processing method and device.

Background technique

Domain name registration is a process in which a registrant purchases a domain name from a registrar and the registrar registers a domain name with the registry. The domain name registration process is implemented based on the extensible provisioning protocol (EPP) protocol. The registry is the server of the registration service and provides external domain name registration services through the shared registration system (SRS).

The potential value and special attributes of some domain names will lead to the phenomenon of squatting, which means that the SRS system of the registry needs to handle tens of millions of concurrent registration requests in a short period of time, which puts extremely high requirements on the performance of the registration service. Therefore, reducing the performance pressure on the SRS system, especially during periods of high concurrency, is of the most direct significance to improving the service level and user experience of the registry.

How to reduce the performance pressure of the SRS system and thereby improve the service quality of the SRS system is a problem that has yet to be solved.

Contents of the invention

The technical problem to be solved by this application is how to reduce the performance pressure of the SRS system to improve the service quality of the SRS system, and provide a domain name-based data processing method and device.

In the first aspect, embodiments of this application provide a data processing method based on domain name, which is applied to the registry. The method includes:

Determine hot domain names;

Store the name of the hot domain name, the registration status of the hot domain name, and the data source corresponding to the hot domain name in the cache. The data source corresponding to the hot domain name is used when the hot domain name is registered. In the case of a domain name, the information of the hot domain name is stored. The data source of the hot domain name is: the shared registration system SRS database or the hot domain name database.

Optionally, the method also includes:

Receive a domain name query request sent by the registrar, the domain name query request includes the first domain name, and the domain name query request is used to query the registration status of the first domain name;

Based on the first domain name, determine from the cache whether a cache record corresponding to the first domain name is included. The cache record corresponding to the first domain name includes the name of the first domain name and the registration of the first domain name. status, and the data source corresponding to the first domain name;

If it is determined that the cache includes a cache record corresponding to the first domain name, obtain the registration status of the first domain name in the cache record corresponding to the first domain name;

Send the obtained registration status of the first domain name to the registrar.

Optionally, the method also includes:

If it is determined that the cache does not include the cache record corresponding to the first domain name, obtain the registration status of the first domain name through the SRS database;

Send the obtained registration status of the first domain name to the registrar.

Optionally, the method also includes:

Receive a domain name registration request sent by the registrar, the domain name registration request includes a second domain name, and the domain name registration request is used to request the registration of the second domain name;

Based on the second domain name, determine from the cache whether a cache record corresponding to the second domain name is included. The cache record corresponding to the second domain name includes the name of the second domain name and the registration of the second domain name. status, and the data source corresponding to the second domain name;

If it is determined that the cache includes a cache record corresponding to the second domain name, and the registration status of the second domain name is registrable, then the registration information of the second domain name is written into the hot domain name database.

Optionally, the method also includes:

Modify the registration status of the second domain name in the cache to unregisterable, and modify the data source corresponding to the second domain name in the cache to the hot domain name database.

Optionally, the method also includes:

After a certain period of time, the registration information of the second domain name is written into the SRS database, and the registration information of the second domain name is deleted from the hot domain name database; the second domain name in the cache is deleted. The data source corresponding to the domain name is modified to the SRS database.

Optionally, the method also includes:

If it is determined that the cache does not include the cache record corresponding to the second domain name, determine the registration status of the second domain name based on the SRS database;

If it is determined based on the SRS database that the second domain name is registrable, the registration information of the second domain name is written into the SRS database.

Optionally, the method also includes:

The name of the second domain name, the registration status of the second domain name, and the data source corresponding to the second domain name are correspondingly stored in the cache, wherein the registration status of the second domain name is unregisterable, The data source corresponding to the second domain name is the SRS database.

Optionally, the method also includes:

Receive a WHOIS query request sent by the registrar, the WHOIS query request includes a third domain name, and the WHOIS query request is used to request information about the third domain name;

Based on the third domain name, determine from the cache whether a cache record corresponding to the third domain name is included. The cache record corresponding to the third domain name includes the name of the third domain name and the registration of the third domain name. status, and the data source corresponding to the third domain name;

If it is determined that the cache includes the cache record corresponding to the third domain name, query and obtain the information of the third domain name through the data source corresponding to the third domain name in the cache record corresponding to the third domain name;

Return the obtained information of the third domain name to the registrar.

Optionally, the method also includes:

If it is determined that the cache does not include the cache record corresponding to the third domain name, obtain the information of the third domain name through the SRS database query;

Return the obtained information of the third domain name to the registrar.

Optionally, the hot domain names determined include:

Determine the hot domain names to be selected from the target resources;

Calculate the hotspot score of the selected hotspot domain name;

The hotspot domain name is determined based on the hotspot score of the candidate hotspot domain name.

Optionally, the target resources include any one or more of the following:

WHOIS query log, domain name list to be expired, domain name query request log, domain name registration request log, and third-party hotspot information.

In the second aspect, embodiments of this application provide a data processing device based on domain name, which is applied to the registration office. The device includes:

The first determination unit is used to determine hot domain names;

The first storage unit is used to store the name of the hot domain name, the registration status of the hot domain name, and the data source corresponding to the hot domain name in the cache. The data source corresponding to the hot domain name is used to store the hot domain name in the cache. When the hot domain name is a registered domain name, the information of the hot domain name is stored. The data source of the hot domain name is: Shared Registration System SRS database or hot domain name database.

Optionally, the device also includes:

The first receiving unit is configured to receive a domain name query request sent by the registrar, the domain name query request includes the first domain name, and the domain name query request is used to query the registration status of the first domain name;

The second determination unit is configured to determine from the cache based on the first domain name whether a cache record corresponding to the first domain name is included. The cache record corresponding to the first domain name includes the name of the first domain name, The registration status of the first domain name and the data source corresponding to the first domain name;

A first acquisition unit configured to acquire the registration status of the first domain name in the cache record corresponding to the first domain name if it is determined that the cache includes a cache record corresponding to the first domain name;

The first sending unit is configured to send the obtained registration status of the first domain name to the registrar.

Optionally, the device also includes:

The second acquisition unit is configured to acquire the registration status of the first domain name through the SRS database if it is determined that the cache does not include the cache record corresponding to the first domain name;

The second sending unit is configured to send the obtained registration status of the first domain name to the registrar.

Optionally, the device also includes:

The second receiving unit is configured to receive a domain name registration request sent by the registrar, the domain name registration request includes a second domain name, and the domain name registration request is used to request the registration of the second domain name;

A third determination unit configured to determine from the cache based on the second domain name whether a cache record corresponding to the second domain name is included. The cache record corresponding to the second domain name includes the name of the second domain name, The registration status of the second domain name and the data source corresponding to the second domain name;

A first writing unit configured to write the registration information of the second domain name if it is determined that the cache includes a cache record corresponding to the second domain name and the registration status of the second domain name is registrable. in the hot domain name database.

Optionally, the device also includes:

A modification unit configured to modify the registration status of the second domain name in the cache to unregistrable, and modify the data source corresponding to the second domain name in the cache to the hot domain name database.

Optionally, the device also includes:

The second writing unit is configured to write the registration information of the second domain name into the SRS database after a certain period of time, and delete the registration information of the second domain name from the hot domain name database; The data source corresponding to the second domain name in the cache is modified to the SRS database.

Optionally, the device also includes:

A fourth determination unit configured to determine the registration status of the second domain name based on the SRS database if it is determined that the cache does not include a cache record corresponding to the second domain name;

The third writing unit is configured to write the registration information of the second domain name into the SRS database if it is determined based on the SRS database that the second domain name is registrable.

Optionally, the device also includes:

A second storage unit configured to correspondingly store the name of the second domain name, the registration status of the second domain name, and the data source corresponding to the second domain name into the cache, where the second domain name The registration status of is unregisterable, and the data source corresponding to the second domain name is the SRS database.

Optionally, the device also includes:

The third receiving unit is configured to receive a WHOIS query request sent by the registrar, the WHOIS query request includes a third domain name, and the WHOIS query request is used to request information about the third domain name;

The fifth determination unit is configured to determine from the cache based on the third domain name whether a cache record corresponding to the third domain name is included. The cache record corresponding to the third domain name includes the name of the third domain name, The registration status of the third domain name and the data source corresponding to the third domain name;

The third acquisition unit is configured to query and obtain the cache record corresponding to the third domain name through the data source corresponding to the third domain name in the cache record corresponding to the third domain name if it is determined that the cache contains the cache record corresponding to the third domain name. Information about the third domain name;

The third sending unit is configured to return the obtained information of the third domain name to the registrar.

Optionally, the device also includes:

The fourth acquisition unit is configured to obtain the information of the third domain name through the SRS database query if it is determined that the cache does not include the cache record corresponding to the third domain name;

The fourth sending unit is used to return the obtained information of the third domain name to the registrar.

Optionally, the first determination unit is used for:

Determine the hot domain names to be selected from the target resources;

Calculate the hotspot score of the selected hotspot domain name;

The hotspot domain name is determined based on the hotspot score of the candidate hotspot domain name.

Optionally, the target resources include any one or more of the following:

WHOIS query log, domain name list to be expired, domain name query request log, domain name registration request log, and third-party hotspot information.

Compared with the existing technology, the embodiments of the present application have the following advantages:

The embodiment of the present application provides a data processing method based on domain name, which method can be applied to the registration office. The method includes: determining a hot domain name, and combining the name of the hot domain name, the registration status of the hot domain name and the The data source corresponding to the hot domain name is stored in the cache. The cache mentioned here can be a cache managed independently by the registry. Wherein, the data source corresponding to the hot domain name is used to store the information of the hot domain name when the hot domain name is a registered domain name. The data source of the hot domain name is: Shared Registration System SRS database or hot domain name database . The cache can process and divert some requests related to the hot domain name when the registry receives a request for the hot domain name, thereby alleviating the performance pressure on the SRS system and, accordingly, improving the service quality of the SRS system.

Description of the drawings

In order to explain the embodiments of the present application or the technical solutions in the prior art more clearly, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only These are some embodiments recorded in this application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts.

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

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

Figure 3 is a schematic flowchart of a domain name-based data processing method provided by an embodiment of the present application;

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

Figure 5 is a schematic diagram of a domain name squatting method provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a domain name-based data processing device provided by an embodiment of the present application.

Detailed ways

In order to enable those in the technical field to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only These are part of the embodiments of this application, but not all of them. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

The inventor of this application found through research that when the registry provides external domain name registration services through SRS, the domain name-related business data can be persistently stored in the SRS database. When processing domain name-related requests, direct access is required. SRS database disk. A large number of disk accesses during peak periods are a key factor affecting the performance of domain name registration services.

In view of this, embodiments of the present application provide a domain name-based data processing method and device, which can reduce access to the SRS database disk, thereby alleviating the performance pressure of the SRS system.

Various non-limiting embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Example methods

Refer to Figure 1, which is a schematic flow chart of a domain name-based data processing method provided by an embodiment of the present application. The method can be executed by the registration bureau. The registration bureau mentioned here refers to the server of the registration bureau. In this embodiment, the method may include, for example, the following steps: S101-S102.

S101: Determine hot domain names.

In the embodiment of this application, the hot domain names refer to domain names that may be preemptively registered within a certain period of time in the future.

In one example, specific implementation of determining the hot domain name may include the following steps A1-A3.

A1: Determine the hot domain name to be selected from the target resources.

The embodiment of this application does not specifically limit the target resource. The candidate hot domain name may be any resource that can generate the candidate hot domain name or any resource that can be used to synthesize the domain name to be registered.

In one example, consider that WHOIS query logs reflect user attention to a specific domain name. Therefore, in one example, the target resource may include the WHOIS query log. In addition, considering that queries for unregistered domain names reflect users' potential registration intentions, the target resources may include domain name query records in the WHOIS query log whose query results are unregistered.

In one example, considering that the domain names to be expired among the registered domain names are also likely to be preempted, the target resource may include a list of domain names to be expired, and the list of domain names to be expired may be

Can include one or more domain names to be expired. SRS domain names in the list of domain names to be expired

Upon expiration, the domain name information in the domain name list to be expired will be deleted from the SRS database, and then the status of the deleted domain name will become registrable.

In one example, the domain name query request log includes a domain name query request sent by the registrar to the registry, where the domain name query request is used to query the status of the domain name. The domain name corresponding to the domain name query request is also more likely to be registered. Therefore, the target resource may include a domain name query request log. In addition, considering that a query for an unregistered domain name reflects the user's potential registration intention, the target resource may include a domain name query record in the domain name query request log whose query result is unregistered.

In one example, the domain name registration request log includes domain name registration requests sent by the registrar to the registry, where the domain name registration requests are used to register the domain name. A registered domain name may still be attempted to be registered by other registrars within a short period of time. Therefore, the target resource may include a domain name registration request log.

In one example, third-party hotspot information may also generate hotspot domain names. The third-party hot information mentioned here includes but is not limited to: search engine search index, consultation index, trademark data and other third-party data. For this case, the target resource may include third-party hotspot information. For this situation, candidate hotspot domain names can be generated based on the third-party hotspot information and a specific algorithm.

A2: Calculate the hotspot score of the candidate hotspot domain name.

The hotspot score of the candidate hotspot domain name can be calculated based on the associated information of the candidate hotspot domain name. Among them, the associated information of the candidate hot domain name may include domain name registration status, domain name length, information entropy of the domain name, number of domain name queries, and semantic correlation between the domain name and the current hot event, etc., which will not be listed here. illustrate.

When step A2 is specifically implemented, the associated information of the candidate hotspot domain name can be calculated according to a specific algorithm, thereby obtaining the hotspot score of the candidate hotspot domain name. For example, the hotspot scores corresponding to each piece of information in the associated information can be logarithmically added to obtain the hotspot score of the candidate hotspot domain name.

A3: Determine the hotspot domain name based on the hotspot score of the candidate hotspot domain name.

After determining the hotspot score of each candidate hotspot domain name, in one example, the candidate hotspot domain name with a hotspot score higher than a certain threshold can be determined as the hotspot domain name. In yet another example, the hotspot scores can be sorted from high to low, and a preset number of candidate hotspot domain names with top rankings can be determined as the hotspot domain names.

In one example, considering that the hot domain name has a certain timeliness, the hot domain name can also be updated according to a preset time period. For example, according to the hot score of the hot domain name, delete several low-scoring ones. Hot domain names.

S102: Store the name of the hot domain name, the registration status of the hot domain name, and the data source corresponding to the hot domain name in the cache. The data source corresponding to the hot domain name is used when the hot domain name is If the domain name has been registered, the information of the hot domain name is stored. The data source of the hot domain name is: SRS database or hot domain name database.

In the embodiment of this application, storing the name of the hot domain name, the registration status of the hot domain name, and the data source corresponding to the hot domain name in the cache means: storing the name of the hot domain name, the The corresponding relationship between the registration status of the hot domain name and the data source corresponding to the hot domain name is stored in the cache.

In the embodiment of this application, the registration status of the hotspot domain name may be registered or unregistered.

When the registration status of the hot domain name is unregistered, the data source corresponding to the hot domain name is invalid information; when the registration status of the hot domain name is registered, the data source corresponding to the hot domain name is used to store the hot domain name Information. The data source mentioned here can be an SRS database or a hot domain name database.

In this embodiment of the present application, the cache may process part of the requests related to the hot domain name when the registry receives a request for the hot domain name. As can be seen from the above description of popular domain names, the registry may receive requests for hot domain names more frequently. Therefore, using the cache to process some of the requests related to the hot domain names can effectively reduce the performance pressure on the SRS system.

Next, with reference to Figures 2 to 4, the specific implementation method of caching to reduce the performance pressure of the SRS system is introduced.

In one example, the method provided by the embodiment of the present application may also include S201-S205 shown in Figure 2. FIG. 2 is a schematic flowchart of a domain name-based data processing method provided by an embodiment of the present application.

S201: Receive a domain name query request sent by the registrar, the domain name query request includes the first domain name, and the domain name query request is used to query the registration status of the first domain name.

S202: Determine from the cache based on the first domain name whether a cache record corresponding to the first domain name is included. The cache record corresponding to the first domain name includes the name of the first domain name, the first domain name registration status, and the data source corresponding to the first domain name.

In one example, after receiving the domain name query request, the registration office may search the cache using the first domain name in the domain name query request as an index, thereby determining whether the cache includes the first domain name. Cache records for domain names.

If it is determined that the cache includes the cache record corresponding to the first domain name, S203 is executed. If it is determined that the cache does not include the cache record corresponding to the first domain name, S204 is executed.

S203: Obtain the registration status of the first domain name in the cache record corresponding to the first domain name.

As mentioned above, the cache record corresponding to the first domain name includes the registration status of the first domain name. Therefore, when it is determined that the cache includes the cache record corresponding to the first domain name, the registration status of the first domain name can be determined directly through the cache record corresponding to the first domain name.

In this case, there is no need to perform a read operation on the SRS database, thereby reducing the performance pressure on the SRS system. It is easy to understand that since the first domain name is a hot domain name, the registry may receive a large number of domain name query requests for the first domain name. Using this solution can effectively reduce the performance pressure of SRS during high concurrency periods.

S204: Determine the registration status of the first domain name through the SRS database.

When it is determined that the cache does not include a cache record corresponding to the first domain name, at this time, the registration status of the first domain name may be determined through the SRS database. Among them, the SRS data stores information about registered domain names. In one example, the first domain name can be used as an index to search in the SRS database. If information related to the first domain name is retrieved, it can be determined that the first domain name has been registered. If not, If the information related to the first domain name is retrieved, it can be determined that the first domain name has not been registered.

S205: Send the obtained registration status of the first domain name to the registrar.

After obtaining the registration status of the first domain name, the registration office may return the registration status of the first domain name to the registrar.

In one example, the method provided by the embodiment of the present application may also include S301-S305 shown in Figure 3. Figure 3 is a schematic flowchart of a domain name-based data processing method provided by an embodiment of the present application.

S301: Receive a domain name registration request sent by the registrar, the domain name registration request includes a second domain name, and the domain name registration request is used to request registration of the second domain name.

S302: Determine from the cache based on the second domain name whether a cache record corresponding to the second domain name is included. The cache record corresponding to the second domain name includes the name of the second domain name, the second domain name registration status, and the data source corresponding to the second domain name.

In one example, after receiving the domain name registration request, the registration office may search the cache using the second domain name in the domain name registration request as an index, thereby determining whether the cache includes the second domain name. Cache records for domain names.

If it is determined that the cache includes a cache record corresponding to the second domain name, and the registration status of the second domain name is registrable, then perform S303. If it is determined that the cache does not include the cache record corresponding to the second domain name, perform S304.

In this embodiment of the present application, if the cache includes a cache record of the second domain name, it can be determined whether the registration status of the second domain name is available based on the registration status in the cache record of the second domain name. register.

S303: Write the registration information of the second domain name into the hot domain name database.

When it is determined that the cache includes a cache record corresponding to the second domain name and the registration status of the second domain name is registrable, it means that the second domain name is in an unregistered status. At this time, the third domain name can be The registration information of the second domain name is written into the hot domain name database, thereby avoiding writing operations on the SRS database and reducing the performance pressure of the SRS system.

The registration data corresponding to the second domain name is not specifically limited in the embodiment of this application. In one example, the registration data corresponding to the second domain name may include: the registrant of the second domain name, the third domain name The registrar of the second domain name, the authoritative name server corresponding to the second domain name, the registration time of the second domain name, and the expiration (expiration) time of the second domain name, etc., are not included here. List and explain one by one.

In one example, considering that before executing S303, the registration status of the second domain name is unregisterable, and after executing S303, the registration status of the second domain name changes, therefore, as an example, The registration office may also modify the registration status of the second domain name in the cache to unregisterable, and modify the data source corresponding to the second domain name in the cache to the hot domain name database. This is so that when the registration office subsequently receives a request related to the second domain name, such as a related query request, it can perform corresponding operations based on the updated cache record of the second domain name.

In one example, considering that the popularity of the second domain name will decrease after the second domain name is registered for a period of time, in this case, if the registration information of the second domain name continues to be stored in the hotspot In the domain name database, on the one hand, it will occupy the storage space of the hot domain name database, and on the other hand, its effect of reducing the performance pressure of the SRS system is also limited.

In view of this, in an implementation manner of the embodiment of the present application, after the second domain name is registered for a certain period of time, the registration information of the second domain name can be written into the SRS database, and the second domain name can be added to the SRS database. The registration information of the domain name is deleted from the hot domain name database, and accordingly, the data source corresponding to the second domain name in the cache is modified to the SRS database. Or, after the second domain name is registered for a certain period of time, the relevant information of the second domain name is directly deleted from the cache. Of course, the update mechanism of the cache itself can also be used to automatically delete the relevant information of the second domain name from the cache when the hotspot score of the second domain name is ranked lower.

S304: Determine the registration status of the second domain name based on the SRS database.

In one example, the second domain name can be used as an index to search in the SRS database. If information related to the second domain name is retrieved, it can be determined that the second domain name has been registered. If not, If the information related to the second domain name is retrieved, it can be determined that the second domain name has not been registered.

S305: If it is determined based on the SRS database that the second domain name is registrable, write the registration information of the second domain name into the SRS database.

When the second domain name is registrable (that is, the second domain name is not currently registered), the registration information of the second domain name can be written into the SRS database. Regarding the registration information of the second domain name, you can refer to the relevant description above, and will not be described in detail this time.

In one example, if it is determined based on the SRS database that the second domain name cannot be registered (that is, the second domain name is currently registered), the registration request is rejected.

As mentioned before, domain names that have already been registered may still be registered within a certain period of time. Therefore, after the second domain name is registered, the second domain name can be determined as a hot domain name. Correspondingly, in one example, the name of the second domain name, the registration status of the second domain name, and the data source corresponding to the second domain name can be correspondingly stored in the cache, wherein the third domain name The registration status of the second domain name is registered, and the data source corresponding to the second domain name is the SRS database.

In one example, the method provided by the embodiment of the present application may also include S401-S405 shown in Figure 4. FIG. 4 is a schematic flowchart of a domain name-based data processing method provided by an embodiment of the present application.

S401: Receive a WHOIS query request sent by the registrar, the WHOIS query request includes a third domain name, and the WHOIS query request is used to request information about the third domain name.

Regarding WHOIS, it should be noted that WHOIS, also known as "who is", is used to query whether a domain name has been registered and the detailed information of the registered domain name.

S402: Determine from the cache based on the third domain name whether a cache record corresponding to the third domain name is included. The cache record corresponding to the third domain name includes the name of the third domain name, the third domain name registration status, and the data source corresponding to the third domain name.

In one example, after receiving the WHOIS query request, the registration office may search the cache using the third domain name in the WHOIS query request as an index, thereby determining whether the cache includes the third domain name. Cache records for domain names.

If it is determined that the cache includes the cache record corresponding to the third domain name, S403 is executed. If it is determined that the cache does not include the cache record corresponding to the third domain name, S404 is executed.

S403: Query and obtain information about the third domain name through the data source corresponding to the third domain name in the cache record corresponding to the third domain name.

After it is determined that the cache includes a cache record corresponding to the third domain name, it may be further determined in which database the information of the third domain name is stored based on the data source in the cache record of the third domain name, and further The information of the third domain name is obtained from a database that stores the information of the third domain name.

In one example, when the data source corresponding to the third domain name in the third cache record is the hot domain name database, the information of the third domain name can be obtained from the hot domain name database.

In another example, when the data source corresponding to the third domain name in the third cache record is the SRS database, the information of the third domain name can be obtained from the SRS database by query. For this situation, the performance pressure on the SRS system can be reduced.

S404: Obtain the information of the third domain name through querying the SRS database.

When it is determined that the cache does not include the cache record corresponding to the third domain name, the information of the third domain name can be obtained directly through the SRS database query. For example, the third domain name can be used as an index to query and obtain the information of the third domain name.

S405: Return the obtained information of the third domain name to the registrar.

After obtaining the information of the third domain name, the registration office may return the information of the third domain name to the registrar.

Based on the domain name-based data processing method provided in the above embodiments, the domain name squatting process is now introduced with reference to Figure 5. Figure 5 is a schematic diagram of a domain name squatting method provided by an embodiment of the present application.

As shown in Figure 5, domain name 1 is a domain name that is about to expire. Before domain name 1 is about to be deleted, write the domain name of domain name 1, the registration status of domain name 1, and the data source corresponding to domain name 1 into the cache. At this time: the registration status of domain name 1 is registered, and the data source corresponding to domain name 1 is SRS. At this time, if the registration office receives a registration request for domain name 1, it determines that domain name 1 has been registered based on the cache record of domain name 1, and therefore the registration request is rejected.

After domain name 1 is deleted, the cache record of domain name 1 in the cache is updated, and the registration status of domain name 1 is changed to unregistered. Correspondingly, at this time, the data source of domain name 1 is invalid information. At this time, the registration office receives the first registration request for domain name 1 (i.e. domain name registration request). At this time, based on the updated cache, it can be determined that domain name 1 has not been registered. Therefore, based on the first A squatting request is made to register domain name 1, and the registration information of domain name 1 is written into the hot domain name database. Correspondingly, it is necessary to update the cache record of domain name 1, update the registration status of domain name 1 to registered, and modify the data source of domain name 1 to the hot domain name database. In this case, if the registration office receives a repeated registration request for domain name 1, based on the cache record of domain name 1, it is determined that domain name 1 has been registered, so the repeated registration request is rejected.

After a period of time, the possibility of domain name 1 being preemptively registered decreases. At this time, the registration information of domain name 1 can be synchronized from the hot domain name database to the SRS database. After the synchronization is successful (that is: the registration information of domain name 1 is successfully written After the SRS database), the registration information of the domain name 1 in the hot domain name database can be deleted. Further, the cache record of domain name 1 can be updated, and the data source of domain name 1 can be modified to the SRS database.

Example device

Based on the method provided in the above embodiment, the embodiment of the present application also provides a device. The device will be introduced below with reference to the accompanying drawings.

Referring to Figure 6, Figure 6 is a schematic structural diagram of a domain name-based data processing device provided by an embodiment of the present application. The device 600 may be applied to a registration office. The device 600 may specifically include: a first determination unit 601 and a first storage unit 602, for example.

The first determining unit 601 is used to determine hot domain names;

The first storage unit 602 is used to store the name of the hot domain name, the registration status of the hot domain name, and the data source corresponding to the hot domain name into the cache. The data source corresponding to the hot domain name is used for When the hot domain name is a registered domain name, the information of the hot domain name is stored, and the data source of the hot domain name is: a shared registration system SRS database or a hot domain name database.

Optionally, the device also includes:

The first receiving unit is configured to receive a domain name query request sent by the registrar, the domain name query request includes the first domain name, and the domain name query request is used to query the registration status of the first domain name;

The second determination unit is configured to determine from the cache based on the first domain name whether a cache record corresponding to the first domain name is included. The cache record corresponding to the first domain name includes the name of the first domain name, The registration status of the first domain name and the data source corresponding to the first domain name;

A first acquisition unit configured to acquire the registration status of the first domain name in the cache record corresponding to the first domain name if it is determined that the cache includes a cache record corresponding to the first domain name;

The first sending unit is configured to send the obtained registration status of the first domain name to the registrar.

Optionally, the device also includes:

The second acquisition unit is configured to acquire the registration status of the first domain name through the SRS database if it is determined that the cache does not include the cache record corresponding to the first domain name;

The second sending unit is configured to send the obtained registration status of the first domain name to the registrar.

Optionally, the device also includes:

The second receiving unit is configured to receive a domain name registration request sent by the registrar, the domain name registration request includes a second domain name, and the domain name registration request is used to request the registration of the second domain name;

A third determination unit configured to determine from the cache based on the second domain name whether a cache record corresponding to the second domain name is included. The cache record corresponding to the second domain name includes the name of the second domain name, The registration status of the second domain name and the data source corresponding to the second domain name;

A first writing unit configured to write the registration information of the second domain name if it is determined that the cache includes a cache record corresponding to the second domain name and the registration status of the second domain name is registrable. in the hot domain name database.

Optionally, the device also includes:

A modification unit configured to modify the registration status of the second domain name in the cache to unregistrable, and modify the data source corresponding to the second domain name in the cache to the hot domain name database.

Optionally, the device also includes:

The second writing unit is configured to write the registration information of the second domain name into the SRS database after a certain period of time, and delete the registration information of the second domain name from the hot domain name database; The data source corresponding to the second domain name in the cache is modified to the SRS database.

Optionally, the device also includes:

A fourth determination unit configured to determine the registration status of the second domain name based on the SRS database if it is determined that the cache does not include a cache record corresponding to the second domain name;

The third writing unit is configured to write the registration information of the second domain name into the SRS database if it is determined based on the SRS database that the second domain name is registrable.

Optionally, the device also includes:

A second storage unit configured to correspondingly store the name of the second domain name, the registration status of the second domain name, and the data source corresponding to the second domain name into the cache, where the second domain name The registration status of is unregisterable, and the data source corresponding to the second domain name is the SRS database.

Optionally, the device also includes:

The third receiving unit is configured to receive a WHOIS query request sent by the registrar, the WHOIS query request includes a third domain name, and the WHOIS query request is used to request information about the third domain name;

The fifth determination unit is configured to determine from the cache based on the third domain name whether a cache record corresponding to the third domain name is included. The cache record corresponding to the third domain name includes the name of the third domain name, The registration status of the third domain name and the data source corresponding to the third domain name;

The third acquisition unit is configured to query and obtain the cache record corresponding to the third domain name through the data source corresponding to the third domain name in the cache record corresponding to the third domain name if it is determined that the cache contains the cache record corresponding to the third domain name. Information about the third domain name;

The third sending unit is configured to return the obtained information of the third domain name to the registrar.

Optionally, the device also includes:

The fourth acquisition unit is configured to obtain the information of the third domain name through the SRS database query if it is determined that the cache does not include the cache record corresponding to the third domain name;

The fourth sending unit is used to return the obtained information of the third domain name to the registrar.

Optionally, the first determination unit is used for:

Determine the hot domain names to be selected from the target resources;

Calculate the hotspot score of the selected hotspot domain name;

The hotspot domain name is determined based on the hotspot score of the candidate hotspot domain name.

Optionally, the target resources include any one or more of the following:

WHOIS query log, domain name list to be expired, domain name query request log, domain name registration request log, and third-party hotspot information.

Since the device 600 is a device corresponding to the method provided by the above method embodiment, the specific implementation of each unit of the device 600 is the same concept as the above method embodiment. Therefore, the details about each unit of the device 600 For specific implementation, reference may be made to the description of the above method embodiments, which will not be described again here.

Other embodiments of the present application will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application that follow the general principles of the application and include common knowledge or customary technical means in the technical field that are not disclosed in the present disclosure. . It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise structures described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

The above are only preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection of the present application. within the range.

Claims (9)

1. A domain name based data processing method for use with a registry, the method comprising:

determining a hot spot domain name, wherein the hot spot domain name is a predicted domain name which can be preempted in a preset time period;

storing the name of the hot spot domain name, the registration state of the hot spot domain name and the data source corresponding to the hot spot domain name into a cache, wherein the data source corresponding to the hot spot domain name is used for storing the information of the hot spot domain name under the condition that the hot spot domain name is a registered domain name, and the data sources of the hot spot domain name are as follows: sharing a registration system SRS database or a hot spot domain name database;

the determining the hotspot domain name comprises the following steps:

determining a hot spot domain name to be selected from target resources, wherein the target resources comprise: WHOIS query log, domain name list to be outdated, domain name query request log, domain name registration request log and third party hotspot information;

calculating a hotspot score of the hotspot domain name to be selected;

and determining the hot spot domain name based on the hot spot score of the hot spot domain name to be selected.

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

receiving a domain name inquiry request sent by a registrar, wherein the domain name inquiry request comprises a first domain name, and the domain name inquiry request is used for inquiring the registration state of the first domain name;

Determining whether a cache record corresponding to the first domain name is included in the cache or not based on the first domain name, wherein the cache record corresponding to the first domain name comprises the name of the first domain name, the registration state of the first domain name and a data source corresponding to the first domain name;

if the cache comprises the cache record corresponding to the first domain name, acquiring the registration state of the first domain name in the cache record corresponding to the first domain name; if the cache does not comprise the cache record corresponding to the first domain name, acquiring the registration state of the first domain name through the SRS database;

and sending the obtained registration state of the first domain name to the registrar.

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

receiving a domain name registration request sent by a registrar, wherein the domain name registration request comprises a second domain name, and the domain name registration request is used for requesting registration of the second domain name;

determining whether a cache record corresponding to the second domain name is included in the cache or not based on the second domain name, wherein the cache record corresponding to the second domain name comprises the name of the second domain name, the registration state of the second domain name and a data source corresponding to the second domain name;

If it is determined that the cache includes a cache record corresponding to the second domain name and the registration state of the second domain name is registrable, writing registration information of the second domain name into the hotspot domain name database.

4. A method according to claim 3, characterized in that the method further comprises:

modifying the registration state of the second domain name in the cache to be unregisterable, and modifying the data source corresponding to the second domain name in the cache to be the hot spot domain name database.

5. The method according to claim 4, wherein the method further comprises:

after a certain time, writing the registration information of the second domain name into the SRS database, and deleting the registration information of the second domain name from the hot spot domain name database; and modifying the data source corresponding to the second domain name in the cache into the SRS database.

6. A method according to claim 3, characterized in that the method further comprises:

if the cache does not comprise the cache record corresponding to the second domain name, determining the registration state of the second domain name based on the SRS database;

and if the second domain name is determined to be registerable based on the SRS database, writing registration information of the second domain name into the SRS database.

7. The method of claim 6, wherein the method further comprises:

and correspondingly storing the name of the second domain name, the registration state of the second domain name and the data source corresponding to the second domain name into the cache, wherein the registration state of the second domain name is unregisterable, and the data source corresponding to the second domain name is the SRS database.

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

receiving a WHOIS query request sent by a registrar, wherein the WHOIS query request comprises a third domain name, and the WHOIS query request is used for requesting to query information of the third domain name;

determining whether a cache record corresponding to the third domain name is included in the cache or not based on the third domain name, wherein the cache record corresponding to the third domain name comprises the name of the third domain name, the registration state of the third domain name and a data source corresponding to the third domain name;

if the cache comprises the cache record corresponding to the third domain name, inquiring to obtain the information of the third domain name through a data source corresponding to the third domain name in the cache record corresponding to the third domain name; if the cache does not comprise the cache record corresponding to the third domain name, obtaining information of the third domain name through inquiring the SRS database;

And returning the obtained information of the third domain name to the registrar.

9. A domain name based data processing apparatus for use with a registry, the apparatus comprising:

the first determining unit is used for determining a hot spot domain name, wherein the hot spot domain name is a predicted domain name which can be preempted in a preset time period;

the first storage unit is configured to store the name of the hot spot domain name, the registration state of the hot spot domain name, and the data source corresponding to the hot spot domain name in the cache correspondingly, where the data source corresponding to the hot spot domain name is used to store information of the hot spot domain name when the hot spot domain name is a registered domain name, and the data source of the hot spot domain name is: sharing a registration system SRS database or a hot spot domain name database;

the first determining unit is specifically configured to determine a hot spot domain name to be selected from a target resource, where the target resource includes: WHOIS query log, domain name list to be outdated, domain name query request log, domain name registration request log and third party hotspot information; calculating a hotspot score of the hotspot domain name to be selected; and determining the hot spot domain name based on the hot spot score of the hot spot domain name to be selected.