CN114666277A - Data processing method and device based on domain name - Google Patents

Data processing method and device based on domain name Download PDF

Info

Publication number
CN114666277A
CN114666277A CN202210482502.7A CN202210482502A CN114666277A CN 114666277 A CN114666277 A CN 114666277A CN 202210482502 A CN202210482502 A CN 202210482502A CN 114666277 A CN114666277 A CN 114666277A
Authority
CN
China
Prior art keywords
domain name
cache
hotspot
registration
name
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202210482502.7A
Other languages
Chinese (zh)
Other versions
CN114666277B (en
Inventor
左鹏
左拔山
卫俊凯
张海阔
杨卫平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Internet Network Information Center
Original Assignee
China Internet Network Information Center
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Internet Network Information Center filed Critical China Internet Network Information Center
Priority to CN202210482502.7A priority Critical patent/CN114666277B/en
Publication of CN114666277A publication Critical patent/CN114666277A/en
Application granted granted Critical
Publication of CN114666277B publication Critical patent/CN114666277B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015—Name registration, generation or assignment
    • H04L61/302—Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

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

Description

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 method and an apparatus for processing data based on a domain name.
Background
Domain name registration is the process by which a registrar purchases a domain name from a registrar and the registrar registers the domain name with a registry. The domain name registration process is implemented based on an Extensible Provisioning Protocol (EPP) protocol, and a registry is a service end of a registration service and provides the domain name registration service to the outside through a Shared Registration System (SRS).
The potential value and special attributes of some domain names can cause the occurrence of a phenomenon of emergency registration, which is shown in the fact that an SRS system of a registry faces to process ten million concurrent registration requests in a short time, and extremely high requirements are put forward on the performance of registration service. Therefore, alleviating the performance pressure of the SRS system, especially at high concurrency periods, has the most direct meaning for improving the service level and user experience of the registry.
How to reduce the performance pressure of the SRS system, thereby improving the quality of service of the SRS system, is a problem that remains to be solved at present.
Disclosure of Invention
The technical problem to be solved by the present application is how to reduce the performance pressure of the SRS system to improve the service quality of the SRS system, and a method and an apparatus for processing data based on a domain name are provided.
In a first aspect, an embodiment of the present application provides a domain name-based data processing method, which is applied to a registry, and the method includes:
determining a hotspot domain name;
correspondingly storing the name of the hot domain name, the registration state of the hot domain name and the data source corresponding to the hot domain name into a cache, wherein the data source corresponding to the hot domain name is used for storing the information of the hot domain name under the condition that the hot domain name is the registered domain name, and the data source of the hot domain name is as follows: a shared registry SRS database or a hotspot domain name database.
Optionally, the method further includes:
receiving a domain name query request sent by a registrar, wherein the domain name query request comprises a first domain name, and the domain name query request is used for querying the registration state of the first domain name;
determining whether a cache record corresponding to the first domain name is included in the cache based on the first domain name, wherein the cache record corresponding to the first domain name includes 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 is determined to comprise 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;
and sending the obtained registration state of the first domain name to the registrar.
Optionally, the method further includes:
if the cache record corresponding to the first domain name is determined not to be included in the cache, 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.
Optionally, the method further includes:
receiving a domain name registration request sent by a registrar, wherein the domain name registration request comprises a second domain name and is used for requesting to register the second domain name;
determining whether a cache record corresponding to the second domain name is included in the cache based on the second domain name, wherein the cache record corresponding to the second domain name includes 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;
and if the cache is determined to comprise the cache record corresponding to the second domain name and the registration state of the second domain name is registerable, writing the registration information of the second domain name into the hotspot domain name database.
Optionally, the method further includes:
and modifying the registration state of the second domain name in the cache into unregisterable state, and modifying the data source corresponding to the second domain name in the cache into the hotspot domain name database.
Optionally, the method further includes:
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 hotspot domain name database; and modifying the data source corresponding to the second domain name in the cache into the SRS database.
Optionally, the method further includes:
if the cache record corresponding to the second domain name is determined not to be included in the cache, 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 the registration information of the second domain name into the SRS database.
Optionally, the method further includes:
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.
Optionally, the method further includes:
receiving a WHOIS query request sent by a registrar, wherein the WHOIS query request comprises a third domain name and is used for requesting to query the information of the third domain name;
determining whether a cache record corresponding to the third domain name is included in the cache based on the third domain name, wherein the cache record corresponding to the third domain name includes 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 is determined to include the cache record corresponding to the third domain name, querying and obtaining 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;
and returning the obtained information of the third domain name to the registrar.
Optionally, the method further includes:
if the cache record corresponding to the third domain name is determined not to be included in the cache, obtaining information of the third domain name through the SRS database query;
and returning the obtained information of the third domain name to the registrar.
Optionally, the determining the hotspot domain name includes:
determining a domain name of a hot spot to be selected from a target resource;
calculating the hotspot score of the domain name of the hotspot to be selected;
and determining the hotspot domain name based on the hotspot score of the hotspot domain name to be selected.
Optionally, the target resource includes any one or more of the following:
the system comprises a WHOIS inquiry log, a domain name list to be expired, a domain name inquiry request log, a domain name registration request log and third-party hotspot information.
In a second aspect, an embodiment of the present application provides a domain name-based data processing apparatus, which is applied to a registry, and the apparatus includes:
the first determining unit is used for determining the hotspot domain name;
the first storage unit is configured to correspondingly store the name of the hotspot domain name, the registration state of the hotspot domain name, and a data source corresponding to the hotspot domain name into a cache, where the data source corresponding to the hotspot domain name is used to store information of the hotspot domain name when the hotspot domain name is a registered domain name, and the data source of the hotspot domain name is: a shared registry SRS database or a hotspot domain name database.
Optionally, the apparatus further comprises:
a first receiving unit, configured to receive a domain name query request sent by a registrar, where the domain name query request includes a first domain name, and the domain name query request is used to query a registration status of the first domain name;
a second determining unit, configured to determine, based on the first domain name, whether a cache record corresponding to the first domain name is included in the cache, where the cache record corresponding to the first domain name includes a name of the first domain name, a registration state of the first domain name, and a data source corresponding to the first domain name;
a first obtaining unit, configured to obtain a registration state of the first domain name in a cache record corresponding to the first domain name if it is determined that the cache includes the cache record corresponding to the first domain name;
and the first sending unit is used for sending the acquired registration state of the first domain name to the registrar.
Optionally, the apparatus further comprises:
a second obtaining unit, configured to obtain, if it is determined that the cache does not include the cache record corresponding to the first domain name, a registration state of the first domain name through the SRS database;
and the second sending unit is used for sending the obtained registration state of the first domain name to the registrar.
Optionally, the apparatus further comprises:
a second receiving unit, configured to receive a domain name registration request sent by a registrar, where the domain name registration request includes a second domain name, and the domain name registration request is used to request to register the second domain name;
a third determining unit, configured to determine, based on the second domain name, whether a cache record corresponding to the second domain name is included in the cache, where the cache record corresponding to the second domain name includes a name of the second domain name, a registration state of the second domain name, and a data source corresponding to the second domain name;
and the first writing unit is used for writing the registration information of the second domain name into the hotspot domain name database if the cache is determined to comprise the cache record corresponding to the second domain name and the registration state of the second domain name is registerable.
Optionally, the apparatus further comprises:
and the modifying unit is used for modifying the registration state of the second domain name in the cache into unregisterable state and modifying the data source corresponding to the second domain name in the cache into the hotspot domain name database.
Optionally, the apparatus further comprises:
a second writing unit, configured to write the registration information of the second domain name into the SRS database after a certain time, and delete the registration information of the second domain name from the hotspot domain name database; and modifying the data source corresponding to the second domain name in the cache into the SRS database.
Optionally, the apparatus further comprises:
a fourth determining unit, configured to determine, based on the SRS database, a registration state of the second domain name if it is determined that the cache does not include the cache record corresponding to the second domain name;
a third writing unit, configured to write registration information of the second domain name into the SRS database if it is determined that the second domain name is registerable based on the SRS database.
Optionally, the apparatus further comprises:
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 registration status of the second domain name is unregisterable, and the data source corresponding to the second domain name is the SRS database.
Optionally, the apparatus further comprises:
a third receiving unit, configured to receive a WHOIS query request sent by a registrar, where the WHOIS query request includes a third domain name, and the WHOIS query request is used to request to query information of the third domain name;
a fifth determining unit, configured to determine, based on the third domain name, whether a cache record corresponding to the third domain name is included in the cache, where the cache record corresponding to the third domain name includes a name of the third domain name, a registration state of the third domain name, and a data source corresponding to the third domain name;
a third obtaining unit, configured to, if it is determined that the cache includes a cache record corresponding to the third domain name, query and obtain 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;
and the third sending unit is used for returning the obtained information of the third domain name to the registrar.
Optionally, the apparatus further comprises:
a fourth obtaining unit, configured to obtain 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;
and the fourth sending unit is used for returning the obtained information of the third domain name to the registrar.
Optionally, the first determining unit is configured to:
determining a domain name of a hot spot to be selected from a target resource;
calculating the hotspot score of the domain name of the hotspot to be selected;
and determining the hotspot domain name based on the hotspot score of the hotspot domain name to be selected.
Optionally, the target resource includes any one or more of the following:
the domain name registration service system comprises a WHOIS inquiry log, a domain name list to be expired, a domain name inquiry request log, a domain name registration request log and third-party hotspot information.
Compared with the prior art, the embodiment of the application has the following advantages:
the embodiment of the application provides a data processing method based on a domain name, which can be applied to a registry and comprises the following steps: determining a hot domain name, and correspondingly storing the name of the hot domain name, the registration state of the hot domain name and a data source corresponding to the hot domain name into a cache. The cache referred to herein may be a cache managed independently by the registry. The data source corresponding to the hot domain name is used for storing the information of the hot domain name when the hot domain name is a registered domain name, and the data source of the hot domain name is as follows: a shared registry SRS database or a hotspot domain name database. The cache can process and shunt part of requests related to the hot domain name when the registry receives the requests related to the hot domain name, so that the performance pressure of the SRS system is relieved, and correspondingly, the service quality of the SRS system can be improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flowchart of a domain name-based data processing method according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a domain name-based data processing method according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart of a domain name-based data processing method according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart of a domain name-based data processing method according to an embodiment of the present disclosure;
fig. 5 is a schematic diagram of a domain name emergency registration method provided in an embodiment of the present application;
fig. 6 is a schematic structural diagram of a domain name based data processing apparatus according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The inventor of the present application finds, through research, that when a domain name registration service is provided externally by a registry through an SRS, service data related to a domain name can be persistently stored in an SRS database, and when a request related to the domain name is processed, a disk of the SRS database needs to be directly accessed. A large number of disk accesses during peak periods is a key factor affecting the performance of the domain name registration service.
In view of this, embodiments of the present application provide a domain name-based data processing method and apparatus, which can reduce access to an SRS database disk, thereby reducing performance pressure of an SRS system.
Various non-limiting embodiments of the present application are described in detail below with reference to the accompanying drawings.
Exemplary method
Referring to fig. 1, the figure is a schematic flowchart of a domain name-based data processing method according to an embodiment of the present application. The method may be performed by a registry, where a registry is referred to herein as a service side of the registry. In this embodiment, the method may include, for example, the steps of: S101-S102.
S101: determining the hotspot domain name.
In the embodiment of the present application, the hot domain name refers to a domain name that may be preempted in a certain time in the future.
In one example, determining the hotspot domain name is in a particular implementation may include the following steps a 1-A3.
A1: and determining the domain name of the hot spot to be selected from the target resource.
The target resource is not specifically limited in the embodiment of the present application, and the domain name of the hot spot to be selected may be any resource that can generate the domain name of the hot spot to be selected or any resource that can be used to synthesize the domain name to be registered.
In one example, consider that the WHOIS query log reflects the degree of user interest in a particular domain name. Thus, in one example, the target resource may comprise the WHOIS query log. In addition, considering that the query for the domain name that is not registered reflects the potential willingness of the user to register, the target resource may include a record of the domain name that is not registered as a result of the query in the WHOIS query log.
In one example, the target resource may include a list of domain names to expire, which may include a list of domain names to expire, considering that the probability that a domain name to expire from among registered domain names is also high
One or more domain names to be expired may be included. The domain name of the SRS in the list of the domain names to be expired
When the domain name is expired, the information of the domain name in the domain name list to be expired is deleted from the SRS database, and then the state of the deleted domain name is changed into a registrable state.
In one example, the domain name query request log includes domain name query requests sent by registrars to registries, where the domain name query requests are used to query the status of domain names. And the probability that the domain name corresponding to the domain name query request is preempted is also higher, so the target resource can comprise a domain name query request log. In addition, considering that the query for the domain name which is not registered reflects the potential registration intention of the user, the target resource may include the record of the domain name query which is not registered as the result of the query in the domain name query request log.
In one example, the log of domain name registration requests includes domain name registration requests sent by registrars to registries, where the domain name registration requests are used to register domain names. Domain names that have already been registered are still likely to be attempted to be registered by other registrars for a short period of time, and thus the target resource may comprise a log of domain name registration requests.
In one example, third party hotspot information may also generate a hotspot domain name. The third party hotspot information mentioned herein includes, but is not limited to: search index of search engine, consultation index, trademark data, etc. For this case, the target resource may include third-party hotspot information. For this case, the domain name of the hot spot to be selected may be generated based on the third party hot spot information and a specific algorithm.
A2: and calculating the hotspot score of the domain name of the hotspot to be selected.
The hot point score of the hot point domain name to be selected can be calculated and obtained based on the associated information of the hot point domain name to be selected. The association information of the domain name of the hot spot to be selected may include a domain name registration state, a length of the domain name, an information entropy of the domain name, a number of domain name queries, a semantic association degree between the domain name and the current hot spot event, and the like, which are not illustrated here.
When the step a2 is specifically implemented, the association information of the hot spot domain name to be selected may be calculated according to a specific algorithm, so as to obtain the hot spot score of the hot spot domain name to be selected. For example: the hot spot scores respectively corresponding to each item of information in the associated information may be logarithmically added, so as to obtain the hot spot score of the to-be-selected hot spot domain name.
A3: and determining the hotspot domain name based on the hotspot score of the hotspot domain name to be selected.
After determining the hotspot score of each to-be-selected hotspot domain name, in an example, the to-be-selected hotspot domain name with the hotspot score higher than a certain threshold may be determined as the hotspot domain name. In another example, the hotspot domain names may be ranked in order of the hotspot scores from high to low, and a preset number of hotspot domain names to be selected ranked at the top are determined as the hotspot domain names.
In an example, considering that a hotspot domain name has a certain timeliness, the hotspot domain name may be updated according to a preset time period, for example, according to a hotspot score of the hotspot domain name, several hotspot domain names with a later score are deleted.
S102: correspondingly storing the name of the hot domain name, the registration state of the hot domain name and the data source corresponding to the hot domain name into a cache, wherein the data source corresponding to the hot domain name is used for storing the information of the hot domain name under the condition that the hot domain name is the registered domain name, and the data source of the hot domain name is as follows: an SRS database or a hotspot domain name database.
In this embodiment of the present application, correspondingly storing the name of the hot domain name, the registration state of the hot domain name, and the data source corresponding to the hot domain name in a cache means: storing the corresponding relation among the name of the hot domain name, the registration state of the hot domain name and the data source corresponding to the hot domain name into a cache.
In the embodiment of the present application, the registration status of the hotspot domain name may be registered or unregistered.
When the registration state of the hot domain name is unregistered, the data source corresponding to the hot domain name is invalid information; and when the registration state of the hot domain name is registered, the data source corresponding to the hot domain name is used for storing the information of the hot domain name. The data source mentioned here may be an SRS database or a hotspot domain name database.
In an embodiment of the present application, the cache may process part of the request related to the hot domain name when the registry receives the request related to the hot domain name. As can be seen from the above description of the hot domain name, the frequency of receiving the request about the hot domain name by the registry may be relatively high, and therefore, the performance pressure of the SRS system can be effectively reduced by using the cache processing part to process the request related to the hot domain name.
Next, with reference to fig. 2 to 4, a specific implementation of the cache to relieve the performance pressure of the SRS system will be described.
In an example, the method provided by the embodiment of the present application may further include S201 to S205 shown in fig. 2. Fig. 2 is a schematic flowchart of a domain name-based data processing method according to an embodiment of the present disclosure.
S201: receiving a domain name query request sent by a registrar, wherein the domain name query request comprises a first domain name, and the domain name query request is used for querying the registration state of the first domain name.
S202: determining whether a cache record corresponding to the first domain name is included in the cache based on the first domain name, where the cache record corresponding to the first domain name includes 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.
In one example, after receiving the domain name query request, the registry may look up the cache using a first domain name in the domain name query request as an index, so as to determine whether a cache record of the first domain name is included in the cache.
If it is determined that the cache includes the cache record corresponding to the first domain name, S203 is executed, and if it is determined that the cache does not include the cache record corresponding to the first domain name, S204 is executed.
S203: and acquiring the registration state of the first domain name in the cache record corresponding to the first domain name.
As described 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 state of the first domain name may be determined directly through the cache record corresponding to the first domain name.
For this case, a read operation of the SRS database may not be required, thereby alleviating performance pressure on the SRS system. It is understood that, because the first domain name is a hotspot domain name, the registry may receive a large number of domain name query requests related to the first domain name, and by adopting the scheme, the performance pressure of the SRS in a high concurrency period can be effectively relieved.
S204: determining, by the SRS database, a registration status of the first domain name.
When it is determined that the cache record corresponding to the first domain name is not included in the cache, at this time, the registration state of the first domain name may be determined by the SRS database. The SRS data stores information of a registered domain name. In one example, the first domain name may be retrieved in the SRS database, indexed by the first domain name, and if information related to the first domain name is retrieved, it may be determined that the first domain name has been registered, and if information related to the first domain name is not retrieved, it may be determined that the first domain name has not been registered.
S205: and sending the obtained registration state of the first domain name to the registrar.
After obtaining the registration status of the first domain name, the registrar 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 further include S301-S305 shown in fig. 3. Fig. 3 is a schematic flowchart of a domain name-based data processing method according to an embodiment of the present application.
S301: 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 to register the second domain name.
S302: determining whether a cache record corresponding to the second domain name is included in the cache based on the second domain name, where the cache record corresponding to the second domain name includes 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.
In one example, after receiving the domain name registration request, the registry may look up the cache using a second domain name in the domain name registration request as an index, thereby determining whether a cache record of the second domain name is included in the cache.
If it is determined that the cache includes the cache record corresponding to the second domain name and the registration status of the second domain name is registerable, S303 is executed. If it is determined that the cache does not include the cache record corresponding to the second domain name, S304 is performed.
In this embodiment of the present application, if the cache includes the cache record of the second domain name, it may be determined whether the registration state of the second domain name is registerable based on the registration state in the cache record of the second domain name.
S303: and writing the registration information of the second domain name into the hotspot domain name database.
When it is determined that the cache includes the cache record corresponding to the second domain name and the registration state of the second domain name is registrable, it is indicated that the second domain name is unregistered, and at this time, the registration information of the second domain name may be written into the hot domain name database, so that the SRS database is prevented from being written, and the performance pressure of the SRS system is reduced.
As to the registration data corresponding to the second domain name, this embodiment of the present application is not specifically limited, and in an example, the registration data corresponding to the second domain name may include: a registrant of the second domain name, a registrar of the second domain name, an authoritative name server (authoritative name server) corresponding to the second domain name, a registration time of the second domain name, and an expiration time of the second domain name, etc., which are not listed herein.
In an example, considering that the registration status of the second domain name is unregisterable before performing S303, and the registration status of the second domain name is changed after performing S303, as an example, the registrar may further modify the registration status of the second domain name in the cache to be unregisterable, and modify the data source corresponding to the second domain name in the cache to be the hotspot domain name database. So that when the subsequent registry receives a related request, such as a related query request, with the second domain name, the registry performs a corresponding operation based on the updated cache record of the second domain name.
In one example, considering that the popularity of the second domain name may be reduced after the second domain name is registered for a period of time, for this case, if the registration information of the second domain name is continuously stored in the hot domain name database, on one hand, the storage space of the hot domain name database may be occupied, and on the other hand, the effect of reducing the performance pressure of the SRS system may be 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 time, the registration information of the second domain name may be written into the SRS database, and the registration information of the second domain name is deleted from the hotspot 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 time, directly deleting the related information of the second domain name from the cache. Of course, an updating mechanism of the cache itself may also be adopted, and when the hotspot score of the second domain name is ranked later, the related information of the second domain name is automatically deleted from the cache.
S304: determining a registration status of the second domain name based on the SRS database.
In one example, the second domain name may be retrieved from the SRS database, indexed by the second domain name, and if information related to the second domain name is retrieved, it may be determined that the second domain name is already registered, and if information related to the second domain name is not retrieved, it may be determined that the second domain name is not already registered.
S305: and if the second domain name is determined to be registerable based on the SRS database, writing the registration information of the second domain name into the SRS database.
When the second domain name is registerable (i.e., the second domain name is not currently registered), the registration information of the second domain name may be written to the SRS database. For the registration information of the second domain name, reference may be made to the related description above, and this will not be described in detail here.
In one example, the registration request is rejected if it is determined that the second domain name is not registerable (i.e., the second domain name is currently registered) based on the SRS database.
As mentioned above, the domain names that have already been registered may still be preempted for a certain period of time. Thus, after the second domain name is registered, the second domain name may be determined as the hotspot domain name. Accordingly, in an 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 may be stored in the cache, where 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 an example, the method provided in the embodiment of the present application may further include S401-S405 shown in fig. 4. Fig. 4 is a schematic flowchart of a domain name-based data processing method according to an embodiment of the present application.
S401: and receiving a WHOIS query request sent by a registrar, wherein the WHOIS query request comprises a third domain name and is used for requesting to query the information of the third domain name.
Regarding the WHOIS, it should be noted that the WHOIS is also called "WHOIS" and is used to inquire whether a domain name is already registered and detailed information of the registered domain name.
S402: determining whether a cache record corresponding to the third domain name is included in the cache based on the third domain name, where the cache record corresponding to the third domain name includes 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.
In an example, after receiving the WHOIS query request, the registry may look up the cache using a third domain name in the WHOIS query request as an index, thereby determining whether a cache record of the third domain name is included in the cache.
If it is determined that the cache includes the cache record corresponding to the third domain name, S403 is performed, and if it is determined that the cache does not include the cache record corresponding to the third domain name, S404 is performed.
S403: and querying and obtaining 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.
After it is determined that the cache record corresponding to the third domain name is included in the cache, it may be further determined, based on a data source in the cache record of the third domain name, in which database the information of the third domain name is stored, and further, the information of the third domain name is obtained from the database in which the information of the third domain name is stored.
In an example, when the data source corresponding to the third domain name in the third cache record is the hotspot domain name database, the information of the third domain name may be obtained by querying from the hotspot domain name database.
In yet 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 may be obtained by querying the SRS database. For this case, the performance pressure of the SRS system may be reduced.
S404: and querying the SRS database to obtain the information of the third domain name.
When it is determined that the cache record corresponding to the third domain name is not included in the cache, the information of the third domain name can be directly obtained through the SRS database query. For example, the information of the third domain name may be obtained by querying with the third domain name as an index.
S405: and returning the obtained information of the third domain name to the registrar.
After the registry acquires the information of the third domain name, the information of the third domain name may be returned to the registrar.
Based on the data processing method based on the domain name provided by the above embodiment, the domain name preempting process is introduced with reference to fig. 5. Fig. 5 is a schematic diagram of a domain name preemption method provided in an embodiment of the present application.
As shown in fig. 5, domain name 1 is an upcoming expired domain name. Before the domain name 1 is about to be deleted, the domain name of the domain name 1, the registration state of the domain name 1 and the data source corresponding to the domain name 1 are written into the cache. At this time: the registration state of domain name 1 is registered, and the data source corresponding to domain name 1 is SRS. At this time, if the registry receives a registration request for domain name 1, it is determined that domain name 1 has been registered based on the cache record of domain name 1, and thus the registration request is rejected.
After the domain name 1 is deleted, updating the cache record of the domain name 1 in the cache, and modifying the registration state of the domain name 1 into unregistered state, wherein correspondingly, the data source of the domain name 1 is invalid information. At this time, the registry receives the first preemptive request for domain name 1 (i.e., the domain name registration request), and at this time, based on the updated cache, it may be determined that domain name 1 is not registered yet, and therefore, domain name 1 may be registered based on the first preemptive request, and the registration information of domain name 1 is written into the hotspot domain name database. Correspondingly, the cache record of the domain name 1 is updated, the registration state of the domain name 1 is updated to be registered, and the data source of the domain name 1 is modified into a hotspot domain name database. For this case, if the registry receives a repeat request for domain name 1, it is determined that domain name 1 has been registered based on the cache record of domain name 1, and thus the repeat request is rejected.
After a period of time, the possibility that the domain name 1 is preempted is reduced, at this time, the registration information of the domain name 1 can be synchronized to the SRS database from the hotspot domain name database, and after the synchronization is successful (that is, the registration information of the domain name 1 is successfully written into the SRS database), the registration information of the domain name 1 in the hotspot domain name database can be deleted. Further, the cache record of the domain name 1 may be updated, and the data source of the domain name 1 is modified into the SRS database.
Exemplary device
Based on the method provided by the above embodiment, the embodiment of the present application further provides an apparatus, which is described below with reference to the accompanying drawings.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a domain name based data processing apparatus according to an embodiment of the present application. The apparatus 600 may be applied to a registry, and the apparatus 600 may specifically include: a first determination unit 601 and a first storage unit 602.
A first determining unit 601, configured to determine a hotspot domain name;
a first storage unit 602, configured to correspondingly store the name of the hotspot domain name, the registration state of the hotspot domain name, and a data source corresponding to the hotspot domain name into a cache, where the data source corresponding to the hotspot domain name is used to store information of the hotspot domain name when the hotspot domain name is a registered domain name, and the data source of the hotspot domain name is: a shared registry SRS database or a hotspot domain name database.
Optionally, the apparatus further comprises:
a first receiving unit, configured to receive a domain name query request sent by a registrar, where the domain name query request includes a first domain name, and the domain name query request is used to query a registration status of the first domain name;
a second determining unit, configured to determine, based on the first domain name, whether a cache record corresponding to the first domain name is included in the cache, where the cache record corresponding to the first domain name includes a name of the first domain name, a registration state of the first domain name, and a data source corresponding to the first domain name;
a first obtaining unit, configured to obtain a registration state of the first domain name in a cache record corresponding to the first domain name if it is determined that the cache includes the cache record corresponding to the first domain name;
and the first sending unit is used for sending the acquired registration state of the first domain name to the registrar.
Optionally, the apparatus further comprises:
a second obtaining unit, configured to obtain, if it is determined that the cache does not include the cache record corresponding to the first domain name, a registration state of the first domain name through the SRS database;
and the second sending unit is used for sending the obtained registration state of the first domain name to the registrar.
Optionally, the apparatus further comprises:
a second receiving unit, configured to receive a domain name registration request sent by a registrar, where the domain name registration request includes a second domain name, and the domain name registration request is used to request to register the second domain name;
a third determining unit, configured to determine, based on the second domain name, whether a cache record corresponding to the second domain name is included in the cache, where the cache record corresponding to the second domain name includes a name of the second domain name, a registration state of the second domain name, and a data source corresponding to the second domain name;
and the first writing unit is used for writing the registration information of the second domain name into the hotspot domain name database if the cache is determined to comprise the cache record corresponding to the second domain name and the registration state of the second domain name is registerable.
Optionally, the apparatus further comprises:
and the modifying unit is used for modifying the registration state of the second domain name in the cache into unregisterable state and modifying the data source corresponding to the second domain name in the cache into the hotspot domain name database.
Optionally, the apparatus further comprises:
a second writing unit, configured to write the registration information of the second domain name into the SRS database after a certain time, and delete the registration information of the second domain name from the hotspot domain name database; and modifying the data source corresponding to the second domain name in the cache into the SRS database.
Optionally, the apparatus further comprises:
a fourth determining unit, configured to determine, based on the SRS database, a registration state of the second domain name if it is determined that the cache does not include the cache record corresponding to the second domain name;
a third writing unit, configured to write registration information of the second domain name into the SRS database if it is determined that the second domain name is registerable based on the SRS database.
Optionally, the apparatus further comprises:
and the second storage unit is used for 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.
Optionally, the apparatus further comprises:
a third receiving unit, configured to receive a WHOIS query request sent by a registrar, where the WHOIS query request includes a third domain name, and the WHOIS query request is used to request to query information of the third domain name;
a fifth determining unit, configured to determine, based on the third domain name, whether a cache record corresponding to the third domain name is included in the cache, where the cache record corresponding to the third domain name includes a name of the third domain name, a registration state of the third domain name, and a data source corresponding to the third domain name;
a third obtaining unit, configured to, if it is determined that the cache includes a cache record corresponding to the third domain name, query and obtain 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;
and the third sending unit is used for returning the obtained information of the third domain name to the registrar.
Optionally, the apparatus further comprises:
a fourth obtaining unit, configured to obtain, through query of the SRS database, information of the third domain name if it is determined that the cache does not include the cache record corresponding to the third domain name;
and the fourth sending unit is used for returning the obtained information of the third domain name to the registrar.
Optionally, the first determining unit is configured to:
determining a domain name of a hot spot to be selected from a target resource;
calculating the hotspot score of the domain name of the hotspot to be selected;
and determining the hotspot domain name based on the hotspot score of the hotspot domain name to be selected.
Optionally, the target resource includes any one or more of the following:
the system comprises a WHOIS inquiry log, a domain name list to be expired, a domain name inquiry request log, a domain name registration request log and third-party hotspot information.
Since the apparatus 600 is an apparatus corresponding to the method provided in the above method embodiment, and the specific implementation of each unit of the apparatus 600 is the same as that of the above method embodiment, for the specific implementation of each unit of the apparatus 600, reference may be made to the description part of the above method embodiment, and details are not repeated here.
Other embodiments of the present application will be 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 invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice in the art to which the invention pertains. 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 will be understood that the present application is not limited to the precise arrangements that have been described above and shown in the 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 description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (13)

1. A data processing method based on domain name is characterized in that the method is applied to a registry, and the method comprises the following steps:
determining a hotspot domain name;
correspondingly storing the name of the hot domain name, the registration state of the hot domain name and the data source corresponding to the hot domain name into a cache, wherein the data source corresponding to the hot domain name is used for storing the information of the hot domain name under the condition that the hot domain name is the registered domain name, and the data source of the hot domain name is as follows: a shared registry SRS database or a hotspot domain name database.
2. The method of claim 1, further comprising:
receiving a domain name query request sent by a registrar, wherein the domain name query request comprises a first domain name, and the domain name query request is used for querying the registration state of the first domain name;
determining whether a cache record corresponding to the first domain name is included in the cache based on the first domain name, wherein the cache record corresponding to the first domain name includes 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 is determined to comprise 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 record corresponding to the first domain name is determined not to be included in the cache, 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 of claim 1, further comprising:
receiving a domain name registration request sent by a registrar, wherein the domain name registration request comprises a second domain name and is used for requesting to register the second domain name;
determining whether a cache record corresponding to the second domain name is included in the cache based on the second domain name, wherein the cache record corresponding to the second domain name includes 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;
and if the cache is determined to comprise the cache record corresponding to the second domain name and the registration state of the second domain name is registerable, writing the registration information of the second domain name into the hotspot domain name database.
4. The method of claim 3, further comprising:
and modifying the registration state of the second domain name in the cache into unregisterable state, and modifying the data source corresponding to the second domain name in the cache into the hotspot domain name database.
5. The method of claim 4, further comprising:
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 hotspot domain name database; and modifying the data source corresponding to the second domain name in the cache into the SRS database.
6. The method of claim 3, further comprising:
if the cache record corresponding to the second domain name is determined not to be included in the cache, 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 the registration information of the second domain name into the SRS database.
7. The method of claim 6, further comprising:
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 of claim 1, further comprising:
receiving a WHOIS query request sent by a registrar, wherein the WHOIS query request comprises a third domain name and is used for requesting to query the information of the third domain name;
determining whether a cache record corresponding to the third domain name is included in the cache based on the third domain name, wherein the cache record corresponding to the third domain name includes 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 is determined to include the cache record corresponding to the third domain name, querying and obtaining 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 it is determined that the cache does not include the cache record corresponding to the third domain name, querying through the SRS database to obtain information of the third domain name;
and returning the obtained information of the third domain name to the registrar.
9. The method of claim 1, wherein determining the hotspot domain name comprises:
determining a domain name of a hot spot to be selected from a target resource;
calculating the hotspot score of the domain name of the hotspot to be selected;
and determining the hotspot domain name based on the hotspot score of the to-be-selected hotspot domain name.
10. The method of claim 11, wherein the target resource comprises any one or more of:
the domain name registration service system comprises a WHOIS inquiry log, a domain name list to be expired, a domain name inquiry request log, a domain name registration request log and third-party hotspot information.
11. A domain name based data processing apparatus for use in a registry, the apparatus comprising:
the first determining unit is used for determining the hotspot domain name;
the first storage unit is configured to correspondingly store the name of the hotspot domain name, the registration state of the hotspot domain name, and a data source corresponding to the hotspot domain name into a cache, where the data source corresponding to the hotspot domain name is used to store information of the hotspot domain name when the hotspot domain name is a registered domain name, and the data source of the hotspot domain name is: a shared registry SRS database or a hotspot domain name database.
12. The apparatus of claim 11, wherein the first determining unit is configured to:
determining a domain name of a hot spot to be selected from a target resource;
calculating the hotspot score of the domain name of the hotspot to be selected;
and determining the hotspot domain name based on the hotspot score of the hotspot domain name to be selected.
13. The apparatus of claim 12, wherein the target resource comprises any one or more of:
the system comprises a WHOIS inquiry log, a domain name list to be expired, a domain name inquiry request log, a domain name registration request log and third-party hotspot information.
CN202210482502.7A 2022-05-05 2022-05-05 Domain name based data processing method and device Active CN114666277B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210482502.7A CN114666277B (en) 2022-05-05 2022-05-05 Domain name based data processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210482502.7A CN114666277B (en) 2022-05-05 2022-05-05 Domain name based data processing method and device

Publications (2)

Publication Number Publication Date
CN114666277A true CN114666277A (en) 2022-06-24
CN114666277B CN114666277B (en) 2023-10-24

Family

ID=82038011

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210482502.7A Active CN114666277B (en) 2022-05-05 2022-05-05 Domain name based data processing method and device

Country Status (1)

Country Link
CN (1) CN114666277B (en)

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101924799A (en) * 2009-06-15 2010-12-22 北京华智大为科技有限公司 Method and system for querying information of domain name
US20110040867A1 (en) * 2009-08-12 2011-02-17 Cellco Partnership D/B/A Verizon Wireless Mechanism to detect restricted access via internet hotspot
CN103037029A (en) * 2012-12-10 2013-04-10 中国科学院计算机网络信息中心 Binding registration based domain name WHOIS query method and binding registration based domain name WHOIS service system
CN103812963A (en) * 2014-02-19 2014-05-21 互联网域名系统北京市工程研究中心有限公司 Domain name registration method and domain name registration system
CN106487846A (en) * 2015-08-28 2017-03-08 中国电信股份有限公司 The white list updating method of caching system, acquisition and analysis device and caching system
CN107819837A (en) * 2017-10-31 2018-03-20 南京优速网络科技有限公司 A kind of method and log cache analysis system for lifting buffer service quality
CN107979654A (en) * 2016-10-21 2018-05-01 中国移动通信有限公司研究院 The method and system with external information of nslookup
CN110061838A (en) * 2019-04-28 2019-07-26 广州大学 A kind of the decentralization storage system and its realization, information retrieval method of DNS resource record
CN111813826A (en) * 2020-06-02 2020-10-23 深圳市互联工场科技有限公司 WHOIS query method, system and storage medium
WO2021017161A1 (en) * 2019-07-26 2021-02-04 网宿科技股份有限公司 Resource acquisition method and edge computing scheduling server
CN112887447A (en) * 2021-01-22 2021-06-01 北京金山云网络技术有限公司 Domain name query method and device and domain name server

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101924799A (en) * 2009-06-15 2010-12-22 北京华智大为科技有限公司 Method and system for querying information of domain name
US20110040867A1 (en) * 2009-08-12 2011-02-17 Cellco Partnership D/B/A Verizon Wireless Mechanism to detect restricted access via internet hotspot
CN103037029A (en) * 2012-12-10 2013-04-10 中国科学院计算机网络信息中心 Binding registration based domain name WHOIS query method and binding registration based domain name WHOIS service system
CN103812963A (en) * 2014-02-19 2014-05-21 互联网域名系统北京市工程研究中心有限公司 Domain name registration method and domain name registration system
CN106487846A (en) * 2015-08-28 2017-03-08 中国电信股份有限公司 The white list updating method of caching system, acquisition and analysis device and caching system
CN107979654A (en) * 2016-10-21 2018-05-01 中国移动通信有限公司研究院 The method and system with external information of nslookup
CN107819837A (en) * 2017-10-31 2018-03-20 南京优速网络科技有限公司 A kind of method and log cache analysis system for lifting buffer service quality
CN110061838A (en) * 2019-04-28 2019-07-26 广州大学 A kind of the decentralization storage system and its realization, information retrieval method of DNS resource record
WO2021017161A1 (en) * 2019-07-26 2021-02-04 网宿科技股份有限公司 Resource acquisition method and edge computing scheduling server
CN111813826A (en) * 2020-06-02 2020-10-23 深圳市互联工场科技有限公司 WHOIS query method, system and storage medium
CN112887447A (en) * 2021-01-22 2021-06-01 北京金山云网络技术有限公司 Domain name query method and device and domain name server

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
WALAA F. ELSADEK等: "Inter-domain Mobility Management Using SDN for Residential/Enterprise Real Time Services", 《2016 IEEE 4TH INTERNATIONAL CONFERENCE ON FUTURE INTERNET OF THINGS AND CLOUD WORKSHOPS (FICLOUDW)》 *
朱斌;张宏科;郜帅;黄道超;: "EDiNS:基于DHT的新名字解析系统", 计算机技术与发展, no. 01 *

Also Published As

Publication number Publication date
CN114666277B (en) 2023-10-24

Similar Documents

Publication Publication Date Title
US10685017B1 (en) Methods and systems for efficient query rewriting
US6820085B2 (en) Web system having clustered application servers and clustered databases
WO2019165665A1 (en) Domain name resolution method, server and system
CN110046133B (en) Metadata management method, device and system for storage file system
CN107491523B (en) Method and device for storing data object
CN111324665B (en) Log playback method and device
JPH10222407A (en) Method for processing multiple data base transactions in same process for reducing process overhead and redundant retrieval from data base server
CN107153644B (en) Data synchronization method and device
WO2014180232A1 (en) Method and device for responding to a request, and distributed file system
CN108111325B (en) Resource allocation method and device
CN109766318B (en) File reading method and device
US20130290636A1 (en) Managing memory
WO2012010084A1 (en) Domain name resolution method and device
EP2710477A1 (en) Distributed caching and cache analysis
US9380127B2 (en) Distributed caching and cache analysis
US20230409527A1 (en) Method And System For Deleting Obsolete Files From A File System
JPH05143435A (en) Data base system
CN116303661B (en) Processing method, device and system for sequences in distributed database
CN114666277A (en) Data processing method and device based on domain name
CN110750566A (en) Data processing method and device, cache system and cache management platform
CN104661053A (en) IPTV data processing method and system
JP3873975B2 (en) View access control method by domain name, DNS server system apparatus, view access control program by domain name, and storage medium storing view access control program by domain name
JPH06195252A (en) Caching system
CN108073660B (en) Method and system for realizing cache data synchronization
CN110807040A (en) Method, device, equipment and storage medium for managing data

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant