CN114553826B - Domain name management method, device, electronic equipment, medium and program product - Google Patents
Domain name management method, device, electronic equipment, medium and program product Download PDFInfo
- Publication number
- CN114553826B CN114553826B CN202210028841.8A CN202210028841A CN114553826B CN 114553826 B CN114553826 B CN 114553826B CN 202210028841 A CN202210028841 A CN 202210028841A CN 114553826 B CN114553826 B CN 114553826B
- Authority
- CN
- China
- Prior art keywords
- domain name
- resolution
- server
- user
- domain
- 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.)
- Active
Links
Classifications
-
- 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/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the disclosure discloses a domain name management method, a device, an electronic device, a medium and a program product, comprising the following steps: obtaining a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name; transmitting a third domain name; when the first domain name can be resolved to the third domain name by a domain name server, resolution from the first domain name to the second domain name is added.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a domain name management method, a device, an electronic apparatus, a medium, and a program product.
Background
Currently, access to the socket domain name based on the user domain name can be achieved by adding an analytic mode to the user domain name and the socket domain name of a logical space socket (bucket) used by the user in the object storage service (Object Storage Service, OSS) in the domain name server, so that the user does not need to record the socket domain name of the socket of the actual data storage of the user, but can conveniently use the user domain name defined by the user to access the user domain name. However, this operation mode does not perform security verification on the domain name of the user, and there is a great potential safety hazard.
Disclosure of Invention
To solve the problems in the related art, embodiments of the present disclosure provide a domain name management method, apparatus, electronic device, medium, and program product.
In a first aspect, a domain name management method is provided in an embodiment of the present disclosure.
Specifically, the domain name management method includes:
obtaining a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name;
transmitting a third domain name;
when the first domain name can be resolved to the third domain name by a domain name server, resolution from the first domain name to the second domain name is added.
With reference to the first aspect, in a first implementation manner of the first aspect, the present disclosure includes:
the obtaining the domain name binding request comprises obtaining the domain name binding request from a user client;
the domain name binding request comprises information of legal users of the second domain name;
transmitting a third different domain name for the first different domain name;
and the sending the third domain name comprises sending the third domain name to the client.
With reference to the first implementation manner of the first aspect, in a second implementation manner of the first aspect, the present disclosure includes:
The third domain name comprises a random domain name;
the client sends the third domain name and the first domain name to the domain name server to add resolution from the first domain name to the third domain name.
With reference to the first aspect, in a third implementation manner of the first aspect, the adding resolution from the first domain name to the second domain name when the first domain name can be resolved into the third domain name by a domain name server includes:
when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the third domain name to the second domain name at the domain name server.
With reference to the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the present disclosure further includes:
when the second domain name is deleted, resolution from the third domain name to the second domain name is deleted.
With reference to the first aspect, in a fifth implementation manner of the first aspect, the adding resolution from the first domain name to the second domain name when the first domain name can be resolved into the third domain name by a domain name server includes:
And when the first domain name can be resolved into the third domain name by a domain name server, transmitting the second domain name to the client, wherein the client deletes resolution from the first domain name to the third domain name from the domain name server after receiving the second domain name, and adds resolution from the first domain name to the second domain name at the domain name server.
In a second aspect, a domain name management method is provided in an embodiment of the present disclosure.
Specifically, the domain name management method includes:
sending a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name;
receiving a third domain name;
transmitting the third domain name and the first domain name to a domain name server to add resolution from the first domain name to the third domain name;
after successfully adding the resolution of the first domain name to the third domain name, the resolution from the first domain name to the second domain name is added.
With reference to the second aspect, in a first implementation manner of the second aspect, the sending a domain name binding request includes sending the domain name binding request to a management server of the second domain name, and the method further includes:
After successfully adding the resolution of the first domain name to the third domain name, sending a notification to the management server;
receiving the second domain name from the management server, wherein the management server sends the second domain name in response to receiving the notification;
deleting the resolution from the first domain name to the third domain name from the domain name server, and adding the resolution from the first domain name to the second domain name at the domain name server.
In a third aspect, a domain name management apparatus is provided in an embodiment of the present disclosure.
Specifically, the domain name management apparatus includes:
the obtaining module is used for obtaining a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name;
the first sending module is used for sending the third domain name;
and the first adding module is used for adding resolution from the first domain name to the second domain name when the first domain name can be resolved into the third domain name by the domain name server.
With reference to the third aspect, in a first implementation manner of the third aspect, the present disclosure includes:
the obtaining the domain name binding request comprises obtaining the domain name binding request from a user client;
The first domain name comprises information of legal users of the second domain name;
transmitting a third different domain name for the first different domain name;
and the sending the third domain name comprises sending the third domain name to the client.
With reference to the first implementation manner of the third aspect, in a second implementation manner of the third aspect, the present disclosure is provided, wherein:
the third domain name comprises a random domain name;
the client sends the third domain name and the first domain name to the domain name server to add resolution from the first domain name to the third domain name.
With reference to the third aspect, in a third implementation manner of the third aspect, the adding resolution from the first domain name to the second domain name when the first domain name can be resolved into the third domain name by a domain name server includes:
when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the third domain name to the second domain name at the domain name server.
With reference to the third implementation manner of the third aspect, in a fourth implementation manner of the third aspect, the first adding module is further configured to delete resolution from the third domain name to the second domain name when the second domain name is deleted.
With reference to the third aspect, in a fifth implementation manner of the third aspect, the adding resolution from the first domain name to the second domain name when the first domain name can be resolved into the third domain name by a domain name server includes:
and when the first domain name can be resolved into the third domain name by a domain name server, transmitting the second domain name to the client, wherein the client deletes resolution from the first domain name to the third domain name from the domain name server after receiving the second domain name, and adds resolution from the first domain name to the second domain name at the domain name server.
In a fourth aspect, a domain name management apparatus is provided in an embodiment of the present disclosure.
Specifically, the domain name management apparatus includes: the second sending module is used for sending a domain name binding request, wherein the domain name binding request is used for adding resolution from the first domain name to the second domain name;
the receiving module is used for receiving the third domain name;
a second adding module, configured to send the third domain name and the first domain name to a domain name server to add resolution from the first domain name to the third domain name; wherein a resolution from the first domain name to the second domain name is added after successfully adding the resolution of the first domain name to the third domain name.
With reference to the fourth aspect, in a first implementation manner of the fourth aspect, the sending a domain name binding request includes sending the domain name binding request to a management server of the second domain name, and the receiving module is further configured to:
after successfully adding the resolution of the first domain name to the third domain name, sending a notification to the management server;
receiving the second domain name from the management server, wherein the management server sends the second domain name in response to receiving the notification;
the second adding module is further configured to delete resolution from the first domain name to the third domain name from the domain name server, and add resolution from the first domain name to the second domain name at the domain name server.
In a fifth aspect, embodiments of the present disclosure provide an electronic device comprising a memory and a processor, wherein the memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method according to any one of the first implementation manner of the first aspect to the second aspect.
In a sixth aspect, in an embodiment of the present disclosure, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement a method according to any one of the first implementation manners of the first to second aspects.
In a seventh aspect, embodiments of the present disclosure provide a computer program product comprising computer instructions which, when executed by a processor, implement the method steps as in any of the first implementation forms of the first aspect to the second aspect.
According to the technical scheme provided by the embodiment of the disclosure, the domain name binding request is firstly obtained and used for adding the resolution from the first domain name to the second domain name, then the third domain name is sent, when the first domain name can be resolved into the third domain name by the domain name server, the resolution from the first domain name to the second domain name is added, and before the resolution from the first domain name to the second domain name is added, the validity verification is carried out on the user domain name through the third domain name, so that the security of domain name management is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
Other features, objects and advantages of the present disclosure will become more apparent from the following detailed description of non-limiting embodiments, taken in conjunction with the accompanying drawings. In the drawings:
FIG. 1 illustrates a flow chart of a domain name management method according to an embodiment of the present disclosure;
FIG. 2 illustrates a flow chart of another domain name management method according to an embodiment of the present disclosure;
fig. 3A is a schematic diagram illustrating a specific application scenario of a domain name management method according to an embodiment of the present disclosure;
FIG. 3B is a schematic diagram showing a specific application scenario of another domain name management method according to an embodiment of the present disclosure;
fig. 4 shows a block diagram of a domain name management apparatus according to an embodiment of the present disclosure;
FIG. 5 illustrates a block diagram of another domain name management device according to an embodiment of the present disclosure;
fig. 6 shows a block diagram of an electronic device according to an embodiment of the disclosure;
fig. 7 shows a schematic diagram of a computer system suitable for use in implementing methods according to embodiments of the present disclosure.
Detailed Description
Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. In addition, for the sake of clarity, portions irrelevant to description of the exemplary embodiments are omitted in the drawings.
In this disclosure, it should be understood that terms such as "comprises" or "comprising," etc., are intended to indicate the presence of features, numbers, steps, acts, components, portions, or combinations thereof disclosed in this specification, and are not intended to exclude the possibility that one or more other features, numbers, steps, acts, components, portions, or combinations thereof are present or added.
In addition, it should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
In the present disclosure, the acquisition of user information or user data is an operation that is authorized, confirmed, or actively selected by the user.
First, terms related to one or more embodiments of the present disclosure will be explained.
Object store service (Object Storage Service, OSS): a cloud storage service with mass, safety, low cost and high reliability is suitable for storing any type of files.
Socket: the logical space in OSS for storing user files can be understood as a folder, and theoretically, an unlimited number of files can be stored under one socket.
Socket domain name: each socket has a unique domain name that can be requested to be accessed by hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) to access the files under the socket.
DNS: known collectively as domain name servers (Domain Name Service) for resolving domain names to internet protocol (Internet Protocol, IP) addresses or other domain names.
As mentioned above, currently, access to the socket domain name based on the user domain name may be achieved by adding resolution in the domain name server for the user domain name and the socket domain name of the logical space socket used by the user in the object storage service (Object Storage Service, OSS), so that the user does not need to record the socket domain name of the socket of which data is actually stored, but can conveniently use the user domain name defined by himself to access. However, this operation mode does not perform security verification on the validity of the domain name of the user, and has a great potential safety hazard.
In view of this, the present disclosure proposes a domain name management method, by first obtaining a domain name binding request for adding resolution from a first domain name to a second domain name, and then sending a third domain name, when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the first domain name to the second domain name, and before adding resolution from the first domain name to the second domain name, performing validity verification on a user domain name by the third domain name, thereby improving security of domain name management.
Fig. 1 shows a flow chart of a domain name management method according to an embodiment of the present disclosure. As shown in fig. 1, the domain name management method includes the following steps S101 to S103:
in step S101, a domain name binding request is obtained, where the domain name binding request is used to add resolution from a first domain name to a second domain name;
in step S102, a third domain name is sent;
in step S103, when the first domain name can be resolved into the third domain name by a domain name server, resolution from the first domain name to the second domain name is added.
In the embodiment of the present disclosure, the domain name management method may be applied to various scenarios of providing a service based on a domain name, for example, a scenario of performing domain name management in an object storage service OSS, and the like. For convenience of description, the description and the explanation will be given below taking an example of implementing the domain name management method in a management server scenario of an object storage service OSS.
In the embodiment of the present disclosure, the obtaining a domain name binding request refers to that the management server of the object storage service OSS obtains a domain name binding request from a user client, where the domain name binding request is used to add resolution from a first domain name to a second domain name. Wherein the first domain name may be a user's own user domain name, such as example, aaa, com, and the second domain name may be a domain name of a socket in the object store service OSS, for example, a socket, bbb, com, which is a socket that a user can use, for example, a socket created by the user or a socket that the user is authorized to use. Further, the domain name binding request may include legal user information, such as account number and password information, of the second domain name, so that the management server of the OSS determines whether the socket corresponding to the second domain name is usable by the user. When the resolution of the addition from the first domain name to the second domain name is completed, the first domain name can be resolved into the second domain name by a domain name server. Specifically, after the adding is completed, after the user inputs the first domain name in the address field, the domain name server resolves the first domain name to a second domain name, so that the user can access an IP address or a storage space corresponding to the second domain name. For example, after the first domain name example, aaa.com is added to the second domain name socket, bbb.com is resolved, the user may access the socket corresponding to the socket, bbb.com by inputting example, aaa.com in the address bar.
In an embodiment of the present disclosure, the sending a third domain name refers to that the management server of the object storage service OSS sends the third domain name to the user client, where the third domain name may include a random domain name. For a different first domain name, the management server of the object store service OSS sends a different third domain name to the user client. Specifically, after receiving a domain name binding request from a user client, the management server of the object storage service OSS randomly generates a third domain name, for example, random. The step of randomly generating a third domain name according to the second domain name information may be that the third domain name is generated according to the second domain name and the additional information, or the third domain name is generated according to the information of the socket corresponding to the second domain name and the additional information, or the third domain name is generated according to the second domain name, the information of the socket corresponding to the second domain name, and the additional information. The additional information may include a current time and/or a random number, and the socket information corresponding to the second domain name may include a name and/or an IP address of the socket information corresponding to the second domain name.
In the embodiment of the disclosure, the third domain name is in one-to-one correspondence with the first domain name, and in particular, the unique index may be used in the database to constrain the third domain name to generate the third domain name in one-to-one correspondence with the first domain name. In the embodiment of the present disclosure, in order to improve the resource utilization efficiency and further improve the security, an expiration time may also be set for the third domain name.
In the embodiment of the present disclosure, when the first domain name can be resolved into the third domain name by the domain name server, it means that after the management server of the object storage service OSS sends the third domain name to the user client, the user may add the resolution from the first domain name to the third domain name at the domain name server. The management server of the object store service OSS queries the domain name server periodically or in response to a received query instruction to determine whether the first domain name can be resolved to the third domain name. For example, after the management server of the object store service OSS sends the third domain name random.bbb.com to the user client, the user client adds the resolution of the first domain name example.aaa.com and the third domain name random.bbb.com to the domain name server. When the added resolution is effective, the management server of the object storage service OSS can query in a domain name server, and the first domain name example. Aaa.com can be resolved into the third domain name random. If the first domain name example aaa.com can be resolved by the domain name server to said third domain name random.bbb.com, this indicates that the user successfully added resolution from the first domain name to the third domain name at the domain name server, which in turn indicates that the user is a legitimate owner of the first domain name. By adopting the mode of adding the resolution between the first domain name of the user and the third domain name which is in one-to-one correspondence with the first domain name in the domain name server, the verification of whether the user has the ownership of the first domain name can be realized. After verifying that the user is a legitimate owner of the first domain name, resolution from the first domain name to the second domain name is added, thereby improving security of domain name management.
In an embodiment of the present disclosure, when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the first domain name to the second domain name includes: when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the third domain name to the second domain name at the domain name server, thereby completing addition of resolution from the first domain name to the second domain name. Specifically, when the management server of the object store service OSS determines that the first domain name can be resolved to the third domain name, the management server of the object store service OSS adds resolution from the third domain name to the second domain name at the domain name server to enable the first domain name to be resolved to the second domain name. For example, when the management server of the object store service OSS determines that the first domain name example.aaa.com can be resolved by the domain name server to a third domain name random.bbb.com, the management server of the object store service OSS adds the resolution of the third domain name random.bbb.com to the second domain name socket.bbb.com at the domain name server. At this time, if the user inputs the first domain name example, aaa, com in the address bar, the domain name server first parses the first domain name to a third domain name random, bbb, com according to the parsing from the first domain name to the third domain name added by the user, and then parses the third domain name random, bbb, com to a second domain name, socket, bbb, com according to the parsing from the third domain name to the second domain name added by the management server of the object storage service OSS, thereby realizing the parsing from the first domain name example, aaa, com to the second domain name socket.
By resolving the first domain name to the third domain name and then resolving the third domain name to the second domain name, the attack of the subdomain name taking over can be effectively avoided. Sub-domain name takeover refers to the following scenario. For example, if the user a has added a user domain name owned by the user a to the resolution of the first socket domain name of the first socket created by the user a in the OSS in the domain name server, the user a forgets to delete the resolution of the user domain name to the first socket domain name in the domain name server when deleting the first socket, and at this time, the user B may create a second socket having the same name as the first socket in the OSS, that is, the resolution of the user domain name left in the domain name server to the first socket domain name may be utilized, so that the user accessing the user domain name is guided to the second socket, and thus cannot obtain the desired result. If the second socket contains a virus, the user may be under a virus attack.
In the embodiment of the disclosure, because the resolution from the third domain name to the second domain name is added on the domain name server by the management server of the object storage service OSS, the user only needs to add the resolution from the first domain name to the third domain name on the domain name server, the operation is simpler, and the user experience is ensured. Meanwhile, because the first domain name of the user is resolved to the third domain name on the domain name server first and then is resolved to the second domain name from the third domain name, when the user deletes the socket corresponding to the second domain name, the management server of the OSS can delete the resolution from the third domain name to the second domain name, so that even if the user forgets to delete the resolution from the first domain name to the third domain name on the domain name server, the problem of taking over the subdomain name can be effectively avoided.
Specifically, in an embodiment of the present disclosure, the domain name management method may further include: when the second domain name is deleted, resolution from the third domain name to the second domain name is deleted. Specifically, in the scenario of performing domain name management in the object storage service OSS, when the second domain name is deleted, the operation of deleting the resolution from the third domain name to the second domain name may be that, when the second domain name is deleted in a socket corresponding to the object storage service OSS, the management server of the OSS deletes the resolution from the third domain name to the second domain name in the domain name server. In other application scenarios based on the domain name providing service, the deleting the resolution from the third domain name to the second domain name when the second domain name is deleted may be deleting the resolution from the third domain name to the second domain name in a domain name server when the second domain name is deleted in the server based on the domain name providing service.
According to the technical scheme provided by the embodiment of the disclosure, when deleting the second domain name, the resolution from the third domain name to the second domain name is deleted, so that when a user forgets to delete the resolution from the first domain name to the third domain name in the domain name server due to deleting the second domain name, even if a malicious user creates the same domain name as the second domain name and provides malicious service by using the domain name, the user is not led to the newly created domain name of the malicious user when accessing the first domain name, and the problem of taking over the subdomain name is effectively avoided.
In an embodiment of the disclosure, when the first domain name can be resolved into the third domain name by a domain name server, an alternative implementation manner of adding resolution from the first domain name to the second domain name may be to send the second domain name to the client when the first domain name can be resolved into the third domain name by a domain name server, wherein the client deletes resolution from the first domain name to the third domain name from the domain name server after receiving the second domain name, and adds resolution from the first domain name to the second domain name at the domain name server.
In an embodiment of the present disclosure, when the first domain name can be resolved to the third domain name by the domain name server, an alternative implementation manner of adding resolution from the first domain name to the second domain name may be that, after the user client finishes adding resolution from the first domain name to the third domain name at the domain name server, the user client actively invokes an application program interface (Application Programming Interface, API) of the object storage service OSS to inform a management server of the object storage service OSS that adding of resolution from the first domain name to the third domain name is completed, and then verifies by the management server of the object storage service OSS whether the first domain name can be resolved to the third domain name by the domain name server. And when the verification is passed, the management server of the object storage service OSS sends the second domain name to the user client, wherein after receiving the second domain name, the user client deletes the resolution from the first domain name to the third domain name at the domain name server and adds the resolution from the first domain name to the second domain name.
According to the technical scheme provided by the embodiment of the disclosure, after the domain name server finishes the addition of the resolution from the first domain name to the third domain name, the user client actively calls the API of the OSS to inform the management server of the OSS that the addition is finished, and the management server of the OSS sends the second domain name to the user client after receiving the notification, so that the user client can automatically add the resolution from the first domain name to the second domain name at the domain name server, and therefore after the ownership verification of the user on the first domain name by using the third domain name is finished, the user client automatically adds the resolution from the first domain name to the second domain name, and the safety of domain name management is improved.
Fig. 2 illustrates a flow chart of another domain name management method according to an embodiment of the present disclosure. As shown in fig. 2, the domain name management method includes the following steps S201 to S204:
in step S201, a domain name binding request is sent, where the domain name binding request is used to add resolution from a first domain name to a second domain name;
in step S202, a third domain name is received;
in step S203, the third domain name and the first domain name are sent to a domain name server to add resolution from the first domain name to the third domain name;
In step S204, after the resolution of the first domain name to the third domain name is successfully added, the resolution from the first domain name to the second domain name is added.
In the embodiment of the present disclosure, the domain name management method may be applied to various scenarios of providing a service based on a domain name, for example, a scenario of performing domain name management in an object storage service OSS, and the like. For ease of description, the description and illustration below will be given by taking as an example the implementation of the domain name management method in a user client that needs to access an object store service OSS.
In the embodiment of the present disclosure, the sending a domain name binding request refers to that the user client sends a domain name binding request to a management server of the object storage service OSS, where the domain name binding request is used to add resolution from a first domain name to a second domain name. Wherein the first domain name may be a user's own user domain name, such as example, aaa, com, and the second domain name may be a domain name of a socket in the object store service OSS, for example, a socket, bbb, com, which is a socket that a user can use, for example, a socket created by the user or a socket that the user is authorized to use. Further, the domain name binding request may include legal user information, such as account number and password information, of the second domain name, so that the management server of the OSS determines whether the socket corresponding to the second domain name is usable by the user. When the resolution of the addition from the first domain name to the second domain name is completed, the first domain name can be resolved into the second domain name by a domain name server. Specifically, after the adding is completed, after the user inputs the first domain name in the address field, the domain name server resolves the first domain name to a second domain name, so that the user can access an IP address or a storage space corresponding to the second domain name. For example, after the first domain name example, aaa.com is added to the second domain name socket, bbb.com is resolved, the user may access the socket corresponding to the socket, bbb.com by inputting example, aaa.com in the address bar.
In an embodiment of the present disclosure, the receiving the third domain name refers to the user client receiving the third domain name sent by the management server of the object storage service OSS, where the third domain name may include a random domain name. For a different first domain name, the management server of the object store service OSS sends a different third domain name to the user client. Specifically, after receiving a domain name binding request from a user client, the management server of the object storage service OSS randomly generates a third domain name, for example, random. The step of randomly generating a third domain name according to the second domain name information may be that the third domain name is generated according to the second domain name and the additional information, or the third domain name is generated according to the information of the socket corresponding to the second domain name and the additional information, or the third domain name is generated according to the second domain name, the information of the socket corresponding to the second domain name, and the additional information. The additional information may include a current time and/or a random number, and the socket information corresponding to the second domain name may include a name and/or an IP address of the socket information corresponding to the second domain name.
In the embodiment of the disclosure, the third domain name corresponds to the first domain name one-to-one. The third domain name may be constrained in the database using a unique index to generate a third domain name that corresponds one-to-one to the first domain name. In the embodiment of the present disclosure, in order to improve the resource utilization efficiency and further improve the security, an expiration time may also be set for the third domain name.
In the embodiment of the disclosure, the sending the third domain name and the first domain name to a domain name server to add resolution from the first domain name to the third domain name means that the user client sends the received third domain name and the first domain name to the domain name server to add resolution from the first domain name to the third domain name. For example, the user client, after receiving a third domain name random.bbb.com sent by the management server of the object storage service OSS, sends the third domain name random.bbb.com and the first domain name example.aaa.com to the domain name server to add resolution from the first domain name example.aaa.com to the third domain name random.bbb.com.
In the embodiment of the present disclosure, the adding of the resolution from the first domain name to the second domain name after the successfully adding of the resolution from the first domain name to the third domain name may be that the user client sends a notification to a management server of an object storage service OSS after the successfully adding of the resolution from the first domain name to the third domain name by a domain name server; the management server of the object store service OSS, upon receiving the notification, adds resolution from the third domain name to the second domain name at a domain name server, thereby completing the addition of resolution from the first domain name to the second domain name. For example, after the domain name server successfully adds the resolution of the first domain name example, aaa.com, to the third domain name random, bbb.com, the user client sends a notification to the management server of the object store service OSS, and after receiving the notification, the management server of the object store service OSS adds the resolution of the third domain name random, bbb.com, to the second domain name socket, bbb.com, to the domain name server. At this time, if the user inputs the first domain name example, aaa, com in the address bar, the domain name server first parses the first domain name to a third domain name random, bbb, com according to the parsing from the first domain name to the third domain name added by the user, and then parses the third domain name random, bbb, com to a second domain name, socket, bbb, com according to the parsing from the third domain name to the second domain name added by the management server of the object storage service OSS, thereby realizing the parsing from the first domain name example, aaa, com to the second domain name socket.
According to the technical scheme provided by the embodiment of the disclosure, the domain name binding request is firstly sent to be used for adding the resolution from the first domain name to the second domain name, then the third domain name is received, and the third domain name and the first domain name are sent to the domain name server so as to be added with the resolution from the first domain name to the third domain name. After successfully adding the resolution of the first domain name to the third domain name, the resolution from the first domain name to the second domain name is added. For example, after successfully adding the resolution of the first domain name to the third domain name, the management server of the OSS adds the resolution of the third domain name to the second domain name at the domain name server in such a way that the resolution of the first domain name to the third domain name is achieved. In the embodiment of the disclosure, because the resolution from the third domain name to the second domain name is added on the domain name server by the management server of the object storage service OSS, the user only needs to add the resolution from the first domain name to the third domain name on the domain name server, the operation is simpler, and the user experience is ensured. Meanwhile, because the first domain name of the user is resolved to the third domain name on the domain name server first and then is resolved to the second domain name from the third domain name, when the user deletes the socket corresponding to the second domain name, the management server of the OSS can delete the resolution from the third domain name to the second domain name, so that even if the user forgets to delete the resolution from the first domain name to the third domain name on the domain name server, the problem of taking over the subdomain name can be effectively avoided.
In an embodiment of the disclosure, an alternative implementation manner in which the resolution from the first domain name to the second domain name is added after the resolution from the first domain name to the third domain name is successfully added may be to send a notification to the management server after the resolution from the first domain name to the third domain name is successfully added; receiving the second domain name from the management server, wherein the management server sends the second domain name in response to receiving the notification; deleting the resolution from the first domain name to the third domain name from the domain name server, and adding the resolution from the first domain name to the second domain name at the domain name server.
In an embodiment of the present disclosure, when the first domain name can be resolved to the third domain name by the domain name server, an alternative implementation manner of adding resolution from the first domain name to the second domain name may be that, after the user client finishes adding resolution from the first domain name to the third domain name at the domain name server, the user client actively invokes an application program interface (Application Programming Interface, API) of the object storage service OSS to inform a management server of the object storage service OSS that adding of resolution from the first domain name to the third domain name is completed, and then verifies by the management server of the object storage service OSS whether the first domain name can be resolved to the third domain name by the domain name server. And when the verification is passed, the management server of the object storage service OSS sends the second domain name to the user client, wherein after receiving the second domain name, the user client deletes the resolution from the first domain name to the third domain name at the domain name server and adds the resolution from the first domain name to the second domain name.
According to the technical scheme provided by the embodiment of the disclosure, after the domain name server finishes the addition of the resolution from the first domain name to the second domain name, the user client actively calls the API of the OSS to inform the management server of the OSS that the addition is finished, and the management server of the OSS sends the second domain name to the user client after receiving the notification, so that the user client can automatically add the resolution from the first domain name to the second domain name at the domain name server, and therefore after the ownership verification of the user on the first domain name by using the third domain name is finished, the user client automatically adds the resolution from the first domain name to the second domain name, and the security of domain name management is improved.
Fig. 3A illustrates a schematic diagram of a specific application scenario of a domain name management method according to an embodiment of the present disclosure.
As shown in fig. 3A, the domain name management method may be applied to a scenario in which domain name management is performed in an object store service OSS. The method comprises the steps that a user client firstly sends a domain name binding request to an OSS management server, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name, the first domain name is a user domain name, and the second domain name is a domain name of a socket which can be used by a user in an object storage service OSS; after receiving the domain name binding request, the OSS management server generates a random third domain name and sends the third domain name to the user client; the user client adds the resolution of the first domain name and the received third domain name to a domain name server; after the OSS management server knows that the resolution from the first domain name to the third domain name is successfully added, the OSS management server adds the resolution from the third domain name to the second domain name to the domain name server. In this way, resolution of the user domain name to the socket domain name in the object store service OSS is securely achieved.
Fig. 3B illustrates a schematic diagram of a specific application scenario of another domain name management method according to an embodiment of the present disclosure.
As shown in fig. 3B, the domain name management method may be applied to a scenario in which domain name management is performed in an object store service OSS. The method comprises the steps that a client firstly sends a domain name binding request to an OSS management server, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name, the first domain name is a user domain name, and the second domain name is a domain name of a socket which can be used by a user in an object storage service OSS; after receiving the domain name binding request, the OSS management server generates a random third domain name and sends the third domain name to the client; the client adds the resolution of the first domain name and the received third domain name to a domain name server, and sends a notification to the OSS management server after successfully adding the resolution of the first domain name to the third domain name; the OSS management server sends a second domain name to the client after receiving the notification; the client deletes the resolution from the first domain name to the third domain name at the domain name server and adds the resolution from the third domain name to the second domain name. In this way, resolution of the user domain name to the socket domain name in the object store service OSS is securely achieved.
Fig. 4 shows a block diagram of a domain name management apparatus according to an embodiment of the present disclosure. The apparatus may be implemented as part or all of an electronic device by software, hardware, or a combination of both.
As shown in fig. 4, the domain name management apparatus 400 includes:
an obtaining module 401, configured to obtain a domain name binding request, where the domain name binding request is used to add resolution from a first domain name to a second domain name;
a first sending module 402, configured to send the third domain name;
a first adding module 403, configured to add resolution from the first domain name to the second domain name when the first domain name can be resolved into the third domain name by a domain name server.
In an embodiment of the present disclosure, the obtaining a domain name binding request includes obtaining the domain name binding request from a user client; the domain name binding request comprises information of legal users of the second domain name; transmitting a third different domain name for the first different domain name; and the sending the third domain name comprises sending the third domain name to the client.
In an embodiment of the disclosure, the third domain name includes a random domain name; the client sends the third domain name and the first domain name to the domain name server to add resolution from the first domain name to the third domain name
In an embodiment of the present disclosure, when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the first domain name to the second domain name includes: when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the third domain name to the second domain name at the domain name server.
According to the technical scheme provided by the embodiment of the disclosure, the domain name binding request is firstly obtained and used for adding the resolution from the first domain name to the second domain name, then the third domain name is sent, and when the first domain name can be resolved into the third domain name by the domain name server, the resolution from the first domain name to the second domain name is added, so that the security of domain name management is improved.
In an embodiment of the disclosure, the first adding module is further configured to delete resolution from the third domain name to the second domain name when the second domain name is deleted.
According to the technical scheme provided by the embodiment of the disclosure, when deleting the second domain name, the resolution from the third domain name to the second domain name is deleted, so that when a user forgets to delete the resolution from the first domain name to the third domain name in the domain name server due to deleting the second domain name, even if a malicious user creates a domain name with the same name as the second domain name and provides malicious service by using the domain name, the user is not led to the newly created domain name of the malicious user when accessing the first domain name, and the problem of taking over the subdomain name is effectively avoided.
In an embodiment of the present disclosure, when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the first domain name to the second domain name includes: and when the first domain name can be resolved into the third domain name by a domain name server, transmitting the second domain name to the client, wherein the client deletes resolution from the first domain name to the third domain name from the domain name server after receiving the second domain name, and adds resolution from the first domain name to the second domain name at the domain name server.
According to the technical scheme provided by the embodiment of the disclosure, after the ownership verification of the first domain name on the user by using the third domain name is completed, the user client side automatically adds the resolution from the first domain name to the second domain name, so that the security of domain name management is improved.
Fig. 5 shows a block diagram of another domain name management device according to an embodiment of the present disclosure. The apparatus may be implemented as part or all of an electronic device by software, hardware, or a combination of both.
As shown in fig. 5, the domain name management apparatus 500 includes:
A second sending module 501, configured to send a domain name binding request, where the domain name binding request is used to add resolution from a first domain name to a second domain name;
a receiving module 502, configured to receive a third domain name;
a second adding module 503, configured to send the third domain name and the first domain name to a domain name server, so as to add resolution from the first domain name to the third domain name; wherein a resolution from the first domain name to the second domain name is added after successfully adding the resolution of the first domain name to the third domain name.
In an embodiment of the present disclosure, the sending a domain name binding request includes sending the domain name binding request to a management server of the second domain name, and the receiving module is further configured to: after successfully adding the resolution of the first domain name to the third domain name, sending a notification to the management server; receiving the second domain name from the management server, wherein the management server sends the second domain name in response to receiving the notification; the second adding module is further configured to add resolution from the third domain name to the second domain name at the domain name server.
According to the technical scheme provided by the embodiment of the disclosure, the domain name binding request is firstly obtained and used for adding the resolution from the first domain name to the second domain name, then the third domain name is sent, when the first domain name can be resolved into the third domain name by the domain name server, the resolution from the first domain name to the second domain name is added, the fact that the user is a legal owner of the first domain name is verified, and the security of domain name management is improved.
The present disclosure also discloses an electronic device, and fig. 6 shows a block diagram of the electronic device according to an embodiment of the present disclosure.
As shown in fig. 6, the electronic device 600 comprises a memory 601 and a processor 602, wherein the memory 601 is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor 602 to implement a method according to an embodiment of the disclosure.
In the embodiment of the present disclosure, the computer instructions stored in the memory 601 are executed by the processor 602 to implement a domain name management method, the domain name management method comprising: obtaining a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name; transmitting a third domain name; when the first domain name can be resolved to the third domain name by a domain name server, resolution from the first domain name to the second domain name is added.
In an embodiment of the present disclosure, wherein: the obtaining the domain name binding request comprises obtaining the domain name binding request from a user client; the domain name binding request comprises information of legal users of the second domain name; transmitting a third different domain name for the first different domain name; and the sending the third domain name comprises sending the third domain name to the client.
In an embodiment of the present disclosure, wherein: the third domain name comprises a random domain name; the client sends the third domain name and the first domain name to the domain name server to add resolution from the first domain name to the third domain name.
In an embodiment of the present disclosure, when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the first domain name to the second domain name includes: when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the third domain name to the second domain name at the domain name server.
According to the technical scheme provided by the embodiment of the disclosure, the domain name binding request is firstly obtained and used for adding the resolution from the first domain name to the second domain name, then the third domain name is sent, and when the first domain name can be resolved into the third domain name by the domain name server, the resolution from the first domain name to the second domain name is added, so that the second domain name is prevented from being directly exposed to a query user on the premise of no additional operation of the user, the security of domain name management is improved, the attack of subdomain name taking over is avoided, and the user experience is ensured.
In an embodiment of the disclosure, the method further comprises: when the second domain name is deleted, resolution from the third domain name to the second domain name is deleted.
According to the technical scheme provided by the embodiment of the disclosure, when deleting the second domain name, the resolution from the third domain name to the second domain name is deleted, so that a malicious user cannot inquire the resolution from the third domain name to the second domain name in the domain name server, and the third domain name cannot directly correspond to the socket in the object storage service OSS, so that the malicious user cannot take over the first domain name by modifying the name of the socket in the object storage service OSS, the risk of taking over attack by the sub domain name is thoroughly avoided, and the security of domain name management is further improved.
In an embodiment of the present disclosure, when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the first domain name to the second domain name includes: and when the first domain name can be resolved into the third domain name by a domain name server, transmitting the second domain name to the client, wherein the client deletes resolution from the first domain name to the third domain name from the domain name server after receiving the second domain name, and adds resolution from the first domain name to the second domain name at the domain name server.
According to the technical scheme provided by the embodiment of the disclosure, the first domain name of the user is resolved to the third domain name corresponding to the first domain name one to one, and then the third domain name is resolved to the second domain name corresponding to the socket of the data actually stored by the user, so that the second domain name is prevented from being directly exposed to the inquiring user, the safety of domain name management is improved, the attack of sub domain name taking over is avoided, and the user experience is ensured.
In the embodiment of the present disclosure, the computer instructions stored in the memory 601 are executed by the processor 602 to implement a domain name management method, the domain name management method comprising: sending a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name; receiving a third domain name; transmitting the third domain name and the first domain name to a domain name server to add resolution from the first domain name to the third domain name; after successfully adding the resolution of the first domain name to the third domain name, the resolution from the first domain name to the second domain name is added.
According to the technical scheme provided by the embodiment of the disclosure, the domain name binding request is firstly obtained and used for adding the resolution from the first domain name to the second domain name, then the third domain name is sent, and when the first domain name can be resolved into the third domain name by the domain name server, the resolution from the first domain name to the second domain name is added, so that the second domain name is prevented from being directly exposed to a query user on the premise of no additional operation of the user, the security of domain name management is improved, the attack of subdomain name taking over is avoided, and the user experience is ensured.
In an embodiment of the present disclosure, the sending a domain name binding request includes sending the domain name binding request to a management server of the second domain name, and the method further includes: after successfully adding the resolution of the first domain name to the third domain name, sending a notification to the management server; receiving the second domain name from the management server, wherein the management server sends the second domain name in response to receiving the notification; deleting the resolution from the first domain name to the third domain name from the domain name server, and adding the resolution from the first domain name to the second domain name at the domain name server.
According to the technical scheme provided by the embodiment of the disclosure, the first domain name of the user is resolved to the third domain name corresponding to the first domain name one to one, and then the third domain name is resolved to the second domain name corresponding to the socket of the data actually stored by the user, so that the second domain name is prevented from being directly exposed to the inquiring user, the safety of domain name management is improved, the attack of sub domain name taking over is avoided, and the user experience is ensured.
Fig. 7 shows a schematic diagram of a computer system suitable for use in implementing methods according to embodiments of the present disclosure.
As shown in fig. 7, the computer system 700 includes a processing unit 701 that can execute various processes in the above-described embodiments in accordance with a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the system 700 are also stored. The processing unit 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, and the like; an output portion 707 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read therefrom is mounted into the storage section 708 as necessary. The processing unit 701 may be implemented as a processing unit such as CPU, GPU, TPU, FPGA, NPU.
In particular, according to embodiments of the present disclosure, the methods described above may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising computer instructions which, when executed by a processor, implement the method steps described above. In such embodiments, the computer program product may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable media 711.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules referred to in the embodiments of the present disclosure may be implemented in software or in programmable hardware. The units or modules described may also be provided in a processor, the names of which in some cases do not constitute a limitation of the unit or module itself.
As another aspect, the present disclosure also provides a computer-readable storage medium, which may be a computer-readable storage medium included in the electronic device or the computer system in the above-described embodiments; or may be a computer-readable storage medium, alone, that is not assembled into a device. The computer-readable storage medium stores one or more programs for use by one or more processors in performing the methods described in the present disclosure.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention referred to in this disclosure is not limited to the specific combination of features described above, but encompasses other embodiments in which any combination of features described above or their equivalents is contemplated without departing from the inventive concepts described. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).
Claims (13)
1. A domain name management method, comprising:
obtaining a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name, the first domain name comprises a user domain name of a user, the second domain name comprises a domain name of a socket created or authorized to be used by the user, and the first domain name can be resolved into the second domain name by a domain name server;
transmitting a third domain name, wherein the third domain name comprises a random domain name, the third domain name is randomly generated according to the second domain name, and the first domain name, the second domain name and the third domain name are in one-to-one correspondence;
when the first domain name can be resolved to the third domain name by the domain name server, resolution from the first domain name to the second domain name is added.
2. The method according to claim 1, wherein:
the obtaining the domain name binding request comprises obtaining the domain name binding request from a user client;
the domain name binding request comprises information of legal users of the second domain name;
transmitting a third different domain name for the first different domain name;
and the sending the third domain name comprises sending the third domain name to the client.
3. The method according to claim 2, wherein:
the client sends the third domain name and the first domain name to the domain name server to add resolution from the first domain name to the third domain name.
4. The method of claim 1, wherein the adding resolution from the first domain name to the second domain name when the first domain name is resolvable by a domain name server to the third domain name comprises:
when the first domain name can be resolved into the third domain name by a domain name server, adding resolution from the third domain name to the second domain name at the domain name server.
5. The method of claim 4, further comprising:
when the second domain name is deleted, resolution from the third domain name to the second domain name is deleted.
6. The method of claim 1, wherein the adding resolution from the first domain name to the second domain name when the first domain name is resolvable by a domain name server to the third domain name comprises:
and when the first domain name can be resolved into the third domain name by a domain name server, transmitting the second domain name to a client, wherein the client deletes resolution from the first domain name to the third domain name from the domain name server after receiving the second domain name, and adds resolution from the first domain name to the second domain name at the domain name server.
7. A domain name management method, comprising:
sending a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name, the first domain name comprises a user domain name of a user, the second domain name comprises a domain name of a socket created or authorized to be used by the user, and the first domain name can be resolved into the second domain name by a domain name server;
receiving a third domain name, wherein the third domain name comprises a random domain name, the third domain name is randomly generated according to the second domain name, and the first domain name, the second domain name and the third domain name are in one-to-one correspondence;
sending the third domain name and the first domain name to the domain name server to add resolution from the first domain name to the third domain name;
wherein a resolution from the first domain name to the second domain name is added after successfully adding the resolution of the first domain name to the third domain name.
8. The method of claim 7, wherein the sending a domain name binding request comprises sending the domain name binding request to a management server of the second domain name, the method further comprising:
after successfully adding the resolution of the first domain name to the third domain name, sending a notification to the management server;
Receiving the second domain name from the management server, wherein the management server sends the second domain name in response to receiving the notification;
deleting the resolution from the first domain name to the third domain name from the domain name server, and adding the resolution from the first domain name to the second domain name at the domain name server.
9. A domain name management apparatus comprising:
the system comprises an acquisition module, a domain name binding module and a domain name server, wherein the acquisition module is used for acquiring a domain name binding request, the domain name binding request is used for adding resolution from a first domain name to a second domain name, the first domain name comprises a user domain name of a user, the second domain name comprises a domain name of a socket created or authorized to be used by the user, and the first domain name can be resolved into the second domain name by the domain name server;
the first sending module is used for sending a third domain name, the third domain name comprises a random domain name, the third domain name is randomly generated according to the second domain name, and the first domain name, the second domain name and the third domain name are in one-to-one correspondence;
and the first adding module is used for adding resolution from the first domain name to the second domain name when the first domain name can be resolved into the third domain name by the domain name server.
10. The apparatus of claim 9, wherein:
the adding resolution from the first domain name to the second domain name when the first domain name is capable of being resolved to the third domain name by a domain name server includes: adding resolution from the third domain name to the second domain name at a domain name server when the first domain name is resolvable by the domain name server to the third domain name; the first adding module is further configured to delete resolution from the third domain name to the second domain name when the second domain name is deleted.
11. A domain name management apparatus comprising:
the second sending module is used for sending a domain name binding request, wherein the domain name binding request is used for adding resolution from a first domain name to a second domain name, the first domain name comprises a user domain name of a user, the second domain name comprises a domain name of a socket created or authorized to be used by the user, and the first domain name can be resolved into the second domain name by a domain name server;
the receiving module is used for receiving a third domain name, wherein the third domain name comprises a random domain name, the third domain name is randomly generated according to the second domain name, and the first domain name, the second domain name and the third domain name are in one-to-one correspondence;
A second adding module, configured to send the third domain name and the first domain name to the domain name server, so as to add resolution from the first domain name to the third domain name; wherein a resolution from the first domain name to the second domain name is added after successfully adding the resolution of the first domain name to the third domain name.
12. An electronic device includes a memory and a processor; wherein the memory is for storing one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method steps of any of claims 1-8.
13. A readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method steps of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210028841.8A CN114553826B (en) | 2022-01-11 | 2022-01-11 | Domain name management method, device, electronic equipment, medium and program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210028841.8A CN114553826B (en) | 2022-01-11 | 2022-01-11 | Domain name management method, device, electronic equipment, medium and program product |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114553826A CN114553826A (en) | 2022-05-27 |
| CN114553826B true CN114553826B (en) | 2023-10-17 |
Family
ID=81670029
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210028841.8A Active CN114553826B (en) | 2022-01-11 | 2022-01-11 | Domain name management method, device, electronic equipment, medium and program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114553826B (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101651720A (en) * | 2008-08-11 | 2010-02-17 | 上海可鲁系统软件有限公司 | Method for resolving domain names |
| US7970939B1 (en) * | 2007-12-31 | 2011-06-28 | Symantec Corporation | Methods and systems for addressing DNS rebinding |
| CN103581213A (en) * | 2012-07-19 | 2014-02-12 | 阿里巴巴集团控股有限公司 | Shared Hosts file application method, equipment and system |
| CN104378450A (en) * | 2013-08-12 | 2015-02-25 | 深圳市腾讯计算机系统有限公司 | Protection method and device for network attacks |
| CN106027295A (en) * | 2016-05-16 | 2016-10-12 | 乐视控股（北京）有限公司 | Hosting method and hosting system for static website |
| CN106332067A (en) * | 2015-06-19 | 2017-01-11 | 华为技术有限公司 | Method, device and system of preventing diameter signaling attacks in wireless network |
| CN106331216A (en) * | 2016-09-13 | 2017-01-11 | 腾讯科技（深圳）有限公司 | Domain name parsing method and domain name parsing device |
| CN106534141A (en) * | 2016-11-22 | 2017-03-22 | 汉柏科技有限公司 | Method and system for preventing domain name server from being attacked and firewall |
| WO2018112944A1 (en) * | 2016-12-23 | 2018-06-28 | 深圳前海达闼云端智能科技有限公司 | Domain name resolution method and apparatus |
| CN108259455A (en) * | 2016-12-29 | 2018-07-06 | 群晖科技股份有限公司 | Proxy server and cross-domain communication means |
| CN109257451A (en) * | 2017-07-14 | 2019-01-22 | 阿里巴巴集团控股有限公司 | Corresponding relationship analyzing method and device |
| CN111711716A (en) * | 2020-08-20 | 2020-09-25 | 苏州浪潮智能科技有限公司 | Domain name resolution method, device and equipment and readable storage medium |
| CN113301001A (en) * | 2020-04-07 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Attacker determination method, device, computing equipment and medium |
| CN113691489A (en) * | 2020-05-19 | 2021-11-23 | 北京观成科技有限公司 | Malicious domain name detection feature processing method and device and electronic equipment |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9258270B2 (en) * | 2013-05-23 | 2016-02-09 | International Business Machines Corporation | Selecting between domain name system servers of a plurality of networks |
| US10536425B2 (en) * | 2015-08-26 | 2020-01-14 | Pulsepoint, Inc. | Cross-domain HTTP requests using DNS rebinding |
| US10673805B2 (en) * | 2017-09-29 | 2020-06-02 | Level 3 Communications, Llc | Dynamic binding and load determination in a content delivery network (CDN) |
-
2022
- 2022-01-11 CN CN202210028841.8A patent/CN114553826B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7970939B1 (en) * | 2007-12-31 | 2011-06-28 | Symantec Corporation | Methods and systems for addressing DNS rebinding |
| CN101651720A (en) * | 2008-08-11 | 2010-02-17 | 上海可鲁系统软件有限公司 | Method for resolving domain names |
| CN103581213A (en) * | 2012-07-19 | 2014-02-12 | 阿里巴巴集团控股有限公司 | Shared Hosts file application method, equipment and system |
| CN104378450A (en) * | 2013-08-12 | 2015-02-25 | 深圳市腾讯计算机系统有限公司 | Protection method and device for network attacks |
| CN106332067A (en) * | 2015-06-19 | 2017-01-11 | 华为技术有限公司 | Method, device and system of preventing diameter signaling attacks in wireless network |
| CN106027295A (en) * | 2016-05-16 | 2016-10-12 | 乐视控股（北京）有限公司 | Hosting method and hosting system for static website |
| CN106331216A (en) * | 2016-09-13 | 2017-01-11 | 腾讯科技（深圳）有限公司 | Domain name parsing method and domain name parsing device |
| CN106534141A (en) * | 2016-11-22 | 2017-03-22 | 汉柏科技有限公司 | Method and system for preventing domain name server from being attacked and firewall |
| WO2018112944A1 (en) * | 2016-12-23 | 2018-06-28 | 深圳前海达闼云端智能科技有限公司 | Domain name resolution method and apparatus |
| CN108259455A (en) * | 2016-12-29 | 2018-07-06 | 群晖科技股份有限公司 | Proxy server and cross-domain communication means |
| CN109257451A (en) * | 2017-07-14 | 2019-01-22 | 阿里巴巴集团控股有限公司 | Corresponding relationship analyzing method and device |
| CN113301001A (en) * | 2020-04-07 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Attacker determination method, device, computing equipment and medium |
| CN113691489A (en) * | 2020-05-19 | 2021-11-23 | 北京观成科技有限公司 | Malicious domain name detection feature processing method and device and electronic equipment |
| CN111711716A (en) * | 2020-08-20 | 2020-09-25 | 苏州浪潮智能科技有限公司 | Domain name resolution method, device and equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114553826A (en) | 2022-05-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11695744B2 (en) | Using credentials stored in different directories to access a common endpoint | |
| KR101962156B1 (en) | Authorization processing method and apparatus | |
| US8572691B2 (en) | Selecting a web service from a service registry based on audit and compliance qualities | |
| CN103037312B (en) | Information push method and device | |
| US8046826B2 (en) | Resource server proxy method and system | |
| CN104954330B (en) | A kind of methods, devices and systems to be conducted interviews to data resource | |
| CN112261172B (en) | Service addressing access method, device, system, equipment and medium | |
| US20100077467A1 (en) | Authentication service for seamless application operation | |
| CN113381979B (en) | Access request proxy method and proxy server | |
| CN109474600B (en) | Account binding method, system, device and equipment | |
| CN107528865A (en) | The method for down loading and system of file | |
| CN102035815A (en) | Data acquisition method, access node and data acquisition system | |
| CN103428179A (en) | Method, system and device for logging into multi-domain-name website | |
| CN112306970B (en) | Processing method, device, equipment and storage medium of container mirror warehouse | |
| CN109558710B (en) | User login method, device, system and storage medium | |
| CN113886803A (en) | Object storage system of instant messaging, object storage request method and device | |
| CN103118025B (en) | Based on the single-point logging method of networking certification, device and certificate server | |
| CN117251837A (en) | System access method and device, electronic equipment and storage medium | |
| CN114553826B (en) | Domain name management method, device, electronic equipment, medium and program product | |
| WO2014070269A1 (en) | Methods and systems for managing directory information | |
| CN107343028B (en) | Communication method and system based on HTTP (hyper text transport protocol) | |
| JP2021117596A (en) | Information processing system, information processing method, and information processing program | |
| CN112134705A (en) | Data authentication method and device, storage medium and electronic device | |
| CN116055554B (en) | Notification engine based on message mechanism and applied to digital service | |
| CN113041624B (en) | Client secure storage method and device for game account password |
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 |