CN114553826A - Domain name management method, domain name management device, electronic apparatus, domain name management medium, and program product - Google Patents
Domain name management method, domain name management device, electronic apparatus, domain name management medium, and program product Download PDFInfo
- Publication number
- CN114553826A CN114553826A CN202210028841.8A CN202210028841A CN114553826A CN 114553826 A CN114553826 A CN 114553826A CN 202210028841 A CN202210028841 A CN 202210028841A CN 114553826 A CN114553826 A CN 114553826A
- Authority
- CN
- China
- Prior art keywords
- domain name
- resolution
- server
- sending
- 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.)
- Granted
Links
Images
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 domain name management device, electronic equipment, a medium and a program product, wherein the domain name management method comprises the following steps: acquiring 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; sending a third domain name; 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.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a domain name management method, apparatus, electronic device, medium, and program product.
Background
Currently, accessing a bucket domain name based on a user domain name can be realized by adding an analysis mode for the user domain name and the bucket domain name of a logical space bucket used by the user in an Object Storage Service (OSS) in a domain name server, so that the user can conveniently access the bucket domain name by using a user domain name defined by the user without recording the bucket domain name of the bucket where the user actually stores data. However, the operation mode does not perform security verification on the user domain name, and a large potential safety hazard exists.
Disclosure of Invention
In order to solve the problems in the related art, embodiments of the present disclosure provide a domain name management method, device, 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:
acquiring 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;
sending a third domain name;
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.
With reference to the first aspect, the present disclosure is in a first implementation manner of the first aspect, wherein:
the obtaining of the domain name binding request comprises obtaining the domain name binding request from a user client;
the domain name binding request comprises information of a legal user of the second domain name;
sending a different third domain name for the different first 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, the present disclosure is in a second implementation manner of the first aspect, 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 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 by a domain name server to be the third 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.
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:
deleting resolution from the third domain name to the second domain name when 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 by a domain name server to be the third domain name includes:
sending the second domain name to the client when the first domain name is resolvable by a domain name server to the third domain name, 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;
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;
after successfully adding the resolution of the first domain name to the third domain name, a resolution from the first domain name to the second domain name is added.
With reference to the second aspect, the present disclosure is in a first implementation manner of the second aspect, where the sending the 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 the resolution of the first domain name to the third domain name is successfully added, 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;
removing resolution from the first domain name to the third domain name from the domain name server and adding resolution from the first domain name to the second domain name at the domain name server.
In a third aspect, an embodiment of the present disclosure provides a domain name management apparatus.
Specifically, the domain name management apparatus includes:
an obtaining module, 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;
the first sending module is used for sending the third domain name;
a first adding module, configured to add resolution from the first domain name to the second domain name when the first domain name can be resolved by a domain name server into the third domain name.
With reference to the third aspect, the present disclosure is in a first implementation manner of the third aspect, wherein:
the obtaining of the domain name binding request comprises obtaining the domain name binding request from a user client;
the first domain name comprises information of a legal user of the second domain name;
sending a different third domain name for the different first 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, the present disclosure is in a second implementation manner of the third aspect, 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 as 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, in the present 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.
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 to the third domain name by a domain name server includes:
sending the second domain name to the client when the first domain name is resolvable by a domain name server to the third domain name, 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, an embodiment of the present disclosure provides a domain name management apparatus.
Specifically, the domain name management apparatus includes: a second sending module, configured to send a domain name binding request, where the domain name binding request is used to add resolution from the first domain name to the second domain name;
a receiving module, configured to receive a third domain name;
a second adding module for 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; wherein resolution from the first domain name to the second domain name is added after successful addition of 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 the 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 the resolution of the first domain name to the third domain name is successfully added, 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 a resolution from the first domain name to the third domain name from the domain name server and add a resolution from the first domain name to the second domain name at the domain name server.
In a fifth aspect, the present disclosure provides an electronic device, including a memory and a processor, where the memory is configured to store one or more computer instructions, where the one or more computer instructions are executed by the processor to implement the method according to any one of the first implementation manners of the first aspect to the second aspect.
In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having stored thereon computer instructions, which, when executed by a processor, implement the method according to any one of the first implementation manners of the first aspect to the second aspect.
In a seventh aspect, this disclosed embodiment provides a computer program product comprising computer instructions that, when executed by a processor, implement the method steps as described in any one of the first implementation manners of the first aspect to the second aspect.
According to the technical scheme provided by the embodiment of the disclosure, a domain name binding request is firstly obtained, the domain name binding request is used for adding the resolution from a first domain name to a second domain name, then a third domain name is sent, when the first domain name can be resolved into the third domain name by a 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 safety 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 when taken in conjunction with the accompanying drawings. In the drawings:
fig. 1 illustrates a flow diagram of a domain name management method according to an embodiment of the present disclosure;
fig. 2 shows a flow diagram 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 illustrating 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 shows a block diagram of another domain name management apparatus according to an embodiment of the present disclosure;
FIG. 6 shows a block diagram of an electronic device according to an embodiment of the present disclosure;
FIG. 7 shows a schematic block diagram of a computer system suitable for use in implementing a method according to an embodiment 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. Also, for the sake of clarity, parts not relevant to the description of the exemplary embodiments are omitted in the drawings.
In the present disclosure, it is to be understood that terms such as "including" or "having," etc., are intended to indicate the presence of the disclosed features, numbers, steps, behaviors, components, parts, or combinations thereof, and are not intended to preclude the possibility that one or more other features, numbers, steps, behaviors, components, parts, or combinations thereof may be present or added.
It should be further noted that the embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict. 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 the user information or the user data is an operation that is authorized, confirmed, or actively selected by the user.
First, noun terms to which one or more embodiments of the present disclosure relate are explained.
Object Storage Service (OSS): the cloud storage service is high in mass, safety, low in cost and reliability, and is suitable for storing any type of files.
bucket: the logical space for storing the user files in the OSS can be understood as a folder, and theoretically, an unlimited number of files can be stored under one bucket.
bucket Domain name: each bucket has a unique domain name, and the domain name can be accessed by a hypertext Transfer Protocol (HTTP) request to access the file under the bucket.
DNS: all known as Domain Name servers (Domain Name services) for resolving Domain names to Internet Protocol (IP) addresses or other Domain names.
As mentioned above, currently, accessing a bucket domain name based on a user domain name can be realized by adding an analysis mode to the user domain name and the bucket domain name of a logical space bucket used by the user in an Object Storage Service (OSS) in a domain name server, so that the user can conveniently access the bucket domain name by using a user domain name defined by the user without recording the bucket domain name of the bucket where the user actually stores data. However, the operation mode does not perform security verification on the validity of the user domain name, and a large potential safety hazard exists.
In view of this, the present disclosure provides a domain name management method, which includes first obtaining 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, 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 performing validity verification on a user domain name through the third domain name before adding resolution from the first domain name to the second domain name, thereby improving security of domain name management.
Fig. 1 shows a flowchart 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 for adding resolution from a first domain name to a second domain name is obtained;
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, a 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 for providing services based on domain names, for example, scenarios for performing domain name management in an object storage service OSS, and the like. For convenience of description, the following explanation and explanation are given taking as an example the implementation of the domain name management method in the management server scenario of the object storage service OSS.
In this embodiment of the present disclosure, the obtaining of the domain name binding request means that the management server of the object storage service OSS obtains the domain name binding request from the user client, where the domain name binding request is used to add resolution from the first domain name to the second domain name. The first domain name may be a user domain name of the user, for example, aaa.com, and the second domain name may be a domain name of a bucket in the object storage service OSS, for example, bucket.bbb.com, where the bucket is a bucket that can be used by the user, for example, a bucket created by the user or a bucket that the user is authorized to use. Further, the domain name binding request may include information of a valid user of the second domain name, such as an account number and password information, so that the management server of the OSS determines whether a bucket corresponding to the second domain name can be used by the user. And after the addition is completed from the resolution of the first domain name to the second domain name, the first domain name can be resolved into the second domain name by the domain name server. Specifically, after the addition is completed, the domain name server resolves the first domain name to a second domain name after the user inputs the first domain name in the address bar, so that the user can access the IP address or the storage space corresponding to the second domain name. For example, after the resolution of the first domain name example.
In this embodiment of the present disclosure, the sending the third domain name refers to sending the third domain name to the user client by the management server of the object storage service OSS, where the third domain name may include a random domain name. And aiming at different first domain names, the management server of the object storage service OSS sends different third domain names 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 randomly generating a third domain name according to the second domain name information may be generating the third domain name according to the second domain name and additional information, or generating the third domain name according to bucket information and additional information corresponding to the second domain name, or generating the third domain name according to the second domain name and bucket information and additional information corresponding to the second domain name. The additional information may include current time and/or a random number, and the packet information corresponding to the second domain name may include a name and/or an IP address of the packet information corresponding to the second domain name.
In this disclosure, the third domain name corresponds to the first domain name one to one, and specifically, the third domain name may be constrained by using a unique index in a database to generate the third domain name corresponding to the first domain name one to one. In the embodiment of the present disclosure, in order to improve the resource utilization efficiency and further improve the security, an expiration time may be set for the third domain name.
In this embodiment of the disclosure, when the first domain name can be resolved into the third domain name by the domain name server, the management server of the object storage service OSS may add, by the user, the first domain name to the resolution of the third domain name at the domain name server after sending the third domain name to the user client. And the management server of the object storage service OSS queries the domain name server periodically or in response to a received query instruction, and determines whether the first domain name can be resolved to the third domain name. For example, after the management server of the object storage service OSS sends a 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 valid, the management server of the object storage service OSS may query the domain name server, and the first domain name example. If the first domain name example.aa.com can be resolved by the domain name server into the third domain name random.bbb.com, it indicates that the user successfully adds resolution from the first domain name to the third domain name in the domain name server, and further indicates that the user is a legal owner of the first domain name. By adopting the method for adding the first domain name of the user and the third domain name corresponding to the first domain name one by one in the domain name server, the verification of whether the user has the ownership of the first domain name can be realized. After the user is verified to be the legal owner of the first domain name, resolution from the first domain name to the second domain name is added, and therefore safety of domain name management is improved.
In this embodiment of the present disclosure, when the first domain name can be resolved as 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 the addition of resolution from the first domain name to the second domain name. Specifically, when the management server of the object storage service OSS determines that the first domain name can be resolved to the third domain name, the management server of the object storage service OSS adds a resolution from the third domain name to the second domain name at the domain name server, so that the first domain name can be resolved to the second domain name. For example, when the management server of the object storage service OSS determines that the first domain name example. At this time, if the user inputs the first domain name example. aaa.com in the address column, the domain name server firstly resolves the first domain name to the third domain name random.bbb.com according to the resolution of the first domain name to the third domain name added by the user, and then resolves the third domain name random.bbb.com to the second domain name bucket.bbb.com according to the resolution of the third domain name to the second domain name added by the management server of the object storage service OSS, thereby realizing the resolution bucket.bbb.com from the first domain name example. aaa.com to the second domain name.
By analyzing the first domain name to the third domain name and then analyzing the third domain name to the second domain name, the attack of taking over the sub-domain names can be effectively avoided. Sub-domain takeover refers to the following situation. For example, if the user a has added the user domain name owned by the user a to the resolution of the first bucket domain name of the first bucket 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 bucket domain name in the domain name server when deleting the first bucket, and at this time, the user B may create a second bucket with the same name as the first bucket in the OSS, that is, the user domain name left in the domain name server may be used to resolve the first bucket domain name, which leads the user accessing the user domain name to be guided to the second bucket, and further fails to obtain a desired result. If a virus is contained in the second packet, the user may be attacked by the virus.
In the embodiment of the present disclosure, since the resolution from the third domain name to the second domain name is added to 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 to the domain name server, the operation is simple, and the user experience is ensured. Meanwhile, the first domain name of the user is firstly resolved to the third domain name on the domain name server and then resolved to the second domain name from the third domain name, so that when the user deletes the bucket 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, and therefore, 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 of the sub-domain names can be effectively avoided.
Specifically, in this embodiment of the present disclosure, the domain name management method may further include: deleting resolution from the third domain name to the second domain name when the second domain name is deleted. Specifically, in a scenario of performing domain name management in an object storage service OSS, when the second domain name is deleted, deleting an analysis operation from the third domain name to the second domain name may be that, when a bucket corresponding to the second domain name in the object storage service OSS is deleted, a management server of the OSS deletes an analysis from the third domain name to the second domain name in a domain name server. In other application scenarios of providing a service based on a domain name, the operation of deleting the resolution from the third domain name to the second domain name when the second domain name is deleted may be that, when the second domain name is deleted in a server providing a service based on a second domain name, the server deletes the resolution from the third domain name to the second domain name in a domain name server.
According to the technical scheme provided by the embodiment of the disclosure, when the second domain name is deleted, the resolution from the third domain name to the second domain name is deleted, so that when a user deletes the second domain name and forgets to delete the resolution from the first domain name to the third domain name in the domain name server, the resolution from the third domain name to the second domain name is deleted, and therefore, even if a malicious user creates a domain name the same as the second domain name and provides malicious service by using the domain name, the user cannot be guided to the domain name newly created by the malicious user when accessing the first domain name, and the problem of taking over sub-domain names is effectively avoided.
In this embodiment, an alternative implementation manner of adding the 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 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 the domain name server, where the client deletes the resolution from the first domain name to the third domain name from the domain name server after receiving the second domain name, and adds the resolution from the first domain name to the second domain name at the domain name server.
In this disclosure, when the first domain name can be resolved into the third domain name by the domain name server, an alternative implementation manner of adding the resolution from the first domain name to the second domain name may be that, after the user client completes the addition of the resolution from the first domain name to the third domain name at the domain name server, the user client actively calls an Application Programming Interface (API) of the object storage service OSS to notify the management server of the object storage service OSS that the addition of the resolution from the first domain name to the third domain name is completed, and then the management server of the object storage service OSS verifies whether the first domain name can be resolved into 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 the user client receives the second domain name, the resolution from the first domain name to the third domain name is deleted at the domain name server, and 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, after the domain name server completes 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 completed, and after receiving the notification, the management server of the OSS sends the second domain name to the user client, so that the user client can automatically add the resolution from the first domain name to the second domain name in the domain name server, and then the user client automatically adds the resolution from the first domain name to the second domain name after the ownership verification of whether the user has the first domain name or not by using the third domain name is completed, thereby improving the safety of domain name management.
Fig. 2 shows a flow diagram 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, sending 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;
in step S202, a third domain name is received;
in step S203, 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;
in step S204, 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.
In the embodiment of the present disclosure, the domain name management method may be applied to various scenarios for providing services based on domain names, for example, scenarios for performing domain name management in an object storage service OSS, and the like. For convenience of description, the following explanation and explanation are given taking as an example the implementation of the domain name management method in a user client that needs to access an object storage service OSS.
In this embodiment, the sending of the 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. The first domain name may be a user domain name of the user, for example, aaa.com, and the second domain name may be a domain name of a bucket in the object storage service OSS, for example, bucket.bbb.com, where the bucket is a bucket that can be used by the user, for example, a bucket created by the user or a bucket that the user is authorized to use. Further, the domain name binding request may include information about a valid user of the second domain name, such as account and password information, so that the management server of the OSS determines whether a bucket corresponding to the second domain name can be used by the user. And after the addition is completed from the resolution of the first domain name to the second domain name, the first domain name can be resolved into the second domain name by the domain name server. Specifically, after the addition is completed, the domain name server resolves the first domain name to a second domain name after the user inputs the first domain name in the address bar, so that the user can access the IP address or the storage space corresponding to the second domain name. For example, after the resolution of the first domain name example.
In this embodiment of the disclosure, the receiving the third domain name means that the user client receives 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. And aiming at different first domain names, the management server of the object storage service OSS sends different third domain names 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 randomly generating a third domain name according to the second domain name information may be generating the third domain name according to the second domain name and additional information, or generating the third domain name according to bucket information and additional information corresponding to the second domain name, or generating the third domain name according to the second domain name and bucket information and additional information corresponding to the second domain name. The additional information may include current time and/or a random number, and the packet information corresponding to the second domain name may include a name and/or an IP address of the packet information corresponding to the second domain name.
In this embodiment, the third domain name corresponds to the first domain name one to one. The third domain name may be constrained in the database using the 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 be set for the third domain name.
In this embodiment of the present 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 refers to sending the received third domain name and the first domain name to the domain name server by the user client to add resolution from the first domain name to the third domain name. For example, after receiving the third domain name random.bbb.com sent by the management server of the object storage service OSS, the user client 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 this embodiment of the present disclosure, after the resolution of successfully adding the first domain name to the third domain name is added, the resolution from the first domain name to the second domain name may be added, where the user client sends a notification to a management server of an object storage service OSS after a domain name server successfully adds the resolution from the first domain name to the third domain name; the management server of the object storage service OSS, after 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. At this time, if the user inputs the first domain name example. aaa.com in the address column, the domain name server firstly resolves the first domain name to the third domain name random.bbb.com according to the resolution of the first domain name to the third domain name added by the user, and then resolves the third domain name random.bbb.com to the second domain name bucket.bbb.com according to the resolution of the third domain name to the second domain name added by the management server of the object storage service OSS, thereby realizing the resolution bucket.bbb.com from the first domain name example. aaa.com to the second domain name.
According to the technical scheme provided by the embodiment of the disclosure, a domain name binding request is sent first, the domain name binding request is used for adding resolution from a first domain name to a second domain name, then a third domain name is received, and the third domain name and the first domain name are sent to a domain name server so as 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, a 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 from the third domain name to the second domain name at the domain name server, in this way, the resolution from the first domain name to the third domain name is achieved. In the embodiment of the present disclosure, since the resolution from the third domain name to the second domain name is added to 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 to the domain name server, the operation is simple, and the user experience is ensured. Meanwhile, the first domain name of the user is firstly resolved to the third domain name on the domain name server and then resolved to the second domain name from the third domain name, so that when the user deletes the bucket 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, and therefore, 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 of the sub-domain names can be effectively avoided.
In this embodiment of the present disclosure, an alternative implementation manner in which, after the resolution of the first domain name to the third domain name is successfully added, the resolution of the first domain name to the second domain name is added may be that, after the resolution of the first domain name to the third domain name is successfully added, a notification is sent 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; removing resolution from the first domain name to the third domain name from the domain name server and adding resolution from the first domain name to the second domain name at the domain name server.
In this disclosure, when the first domain name can be resolved into the third domain name by the domain name server, an alternative implementation manner of adding the resolution from the first domain name to the second domain name may be that, after the user client completes the addition of the resolution from the first domain name to the third domain name at the domain name server, the user client actively calls an Application Programming Interface (API) of the object storage service OSS to notify the management server of the object storage service OSS that the addition of the resolution from the first domain name to the third domain name is completed, and then the management server of the object storage service OSS verifies whether the first domain name can be resolved into 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 the user client receives the second domain name, the resolution from the first domain name to the third domain name is deleted at the domain name server, and 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, after the domain name server completes the addition of the resolution from the first domain name to the second domain name, the user client actively calls an API of the OSS to inform the management server of the OSS that the addition is completed, and after receiving the notice, the management server of the OSS sends the second domain name to the user client, so that the user client can automatically add the resolution from the first domain name to the second domain name in the domain name server, and therefore, after the ownership verification whether the user has the first domain name by using the third domain name is completed, 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. 3A is a schematic diagram illustrating 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 of domain name management in an object storage service OSS. 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 bucket domain name 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 random 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; and after the OSS management server learns that the analysis addition from the first domain name to the third domain name is successful, adding the analysis from the third domain name to the second domain name to the domain name server. By adopting the method, the resolution from the user domain name to the bucket domain name in the object storage service OSS is safely realized.
Fig. 3B is a schematic diagram illustrating 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 of domain name management in an object storage service OSS. 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 bucket domain name 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 random 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 the resolution of the first domain name to the third domain name is successfully added; after receiving the notification, the OSS management server sends a second domain name to the client; and the client deletes the resolution from the first domain name to the third domain name in the domain name server and adds the resolution from the third domain name to the second domain name. By adopting the method, the resolution from the user domain name to the bucket domain name in the object storage service OSS is safely realized.
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 through 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 a 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 the domain name server.
In the embodiment of the present disclosure, the obtaining of the domain name binding request includes obtaining the domain name binding request from a user client; the domain name binding request comprises information of a legal user of the second domain name; sending a different third domain name for the different first 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, the third domain name comprises a random domain name; the client 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
In this 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, a domain name binding request is firstly obtained, the domain name binding request is used for adding resolution from a first domain name to a second domain name, then a third domain name is sent, and 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, so that the safety of domain name management is improved.
In this embodiment of the present disclosure, the first adding module is further configured to delete the 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 the second domain name is deleted, the resolution from the third domain name to the second domain name is deleted, so that when a user deletes the second domain name and forgets to delete the resolution from the first domain name to the third domain name in the domain name server, the resolution from the third domain name to the second domain name is deleted, and therefore, 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 cannot be guided to the domain name newly created by the malicious user when accessing the first domain name, and the problem of taking over sub-domain names is effectively avoided.
In this 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: sending the second domain name to the client when the first domain name is resolvable by a domain name server to the third domain name, wherein the client deletes the resolution from the first domain name to the third domain name from the domain name server after receiving the second domain name and adds 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, after the ownership verification of the first domain name of the user by using the third domain name is completed, the resolution from the first domain name to the second domain name is added by the user client, so that the safety of domain name management is improved.
Fig. 5 shows a block diagram of another 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 through 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 resolution from the first domain name to the second domain name is added after successful addition of resolution of the first domain name to the third domain name.
In this embodiment of the disclosure, the sending the 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 the resolution of the first domain name to the third domain name is successfully added, 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, a domain name binding request is firstly obtained and used for adding the resolution from a first domain name to a second domain name, then a third domain name is sent, and when the first domain name can be resolved into the third domain name by a domain name server, the resolution from the first domain name to the second domain name is added, so that the user is verified to be a legal owner of the first domain name, and the safety 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 includes 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 disclosed embodiment, the computer instructions stored in the memory 601 are executed by the processor 602 to implement a domain name management method, which includes: acquiring 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; sending a third domain name; when the first domain name is resolvable by a domain name server to the third domain name, adding resolution from the first domain name to the second domain name.
In an embodiment of the present disclosure, wherein: the obtaining of the domain name binding request comprises obtaining the domain name binding request from a user client; the domain name binding request comprises information of a legal user of the second domain name; sending a different third domain name for the different first 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 this embodiment of the present disclosure, adding resolution from the first domain name to the second domain name when the first domain name can be resolved by a domain name server to be the third 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, a domain name binding request is firstly obtained, the domain name binding request is used for adding the resolution from a first domain name to a second domain name, then a third domain name is sent, and when the first domain name can be resolved into the third domain name by a 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 safety of domain name management is improved, the sub-domain name takeover attack is avoided, and the user experience is ensured.
In an embodiment of the disclosure, the method further comprises: deleting 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 the second domain name is deleted, 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 a domain name server, and because the third domain name cannot directly correspond to a bucket in an object storage service OSS, the malicious user cannot take over the first domain name by modifying the name of the bucket in the object storage service OSS, thereby thoroughly avoiding the risk of taking over an attack by a sub-domain name, and further improving the safety of domain name management.
In an embodiment of the present disclosure, the adding resolution from the first domain name to the second domain name when the first domain name can be resolved as the third domain name by a domain name server includes: sending the second domain name to the client when the first domain name is resolvable by a domain name server to the third domain name, 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 which is in one-to-one correspondence with the first domain name, and then the third domain name is resolved to the second domain name which corresponds to the bucket for actually storing data 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 taking over by sub-domain names is avoided, and the user experience is ensured.
In the disclosed embodiment, the computer instructions stored in the memory 601 are executed by the processor 602 to implement a domain name management method, which 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; 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; after successfully adding the resolution of the first domain name to the third domain name, a 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, a domain name binding request is firstly obtained, the domain name binding request is used for adding the resolution from a first domain name to a second domain name, then a third domain name is sent, and when the first domain name can be resolved into the third domain name by a 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 safety of domain name management is improved, the sub-domain name takeover attack is avoided, and the user experience is ensured.
In this embodiment of the present disclosure, the sending the 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 the resolution of the first domain name to the third domain name is successfully added, 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; removing resolution from the first domain name to the third domain name from the domain name server and adding 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 which is in one-to-one correspondence with the first domain name, and then the third domain name is resolved to the second domain name which corresponds to the bucket for actually storing data 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 taking over sub-domain names is avoided, and the user experience is ensured.
FIG. 7 shows a schematic block diagram of a computer system suitable for use in implementing a method according to an embodiment 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 according to 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 necessary 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 by 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 portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and 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. A 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 out therefrom is mounted into the storage section 708 as necessary. The processing unit 701 may be implemented as a CPU, a GPU, a TPU, an FPGA, an NPU, or other processing units.
In particular, the above described methods may be implemented as computer software programs according to embodiments of the present disclosure. 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 an embodiment, the computer program product may be downloaded and installed from a network via the communication section 709, and/or installed from the removable medium 711.
The flowchart 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 described in the embodiments of the present disclosure may be implemented by software or by programmable hardware. The units or modules described may also be provided in a processor, and the names of the units or modules do not in some cases constitute a limitation of the units or modules themselves.
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 embodiments; or it may be a separate computer readable storage medium not incorporated into the 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 exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is possible without departing from the inventive concept. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Claims (14)
1. A domain name management method, comprising:
acquiring 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;
sending a third domain name;
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.
2. The method of claim 1, wherein:
the obtaining of the domain name binding request comprises obtaining the domain name binding request from a user client;
the domain name binding request comprises information of a legal user of the second domain name;
sending a different third domain name for the different first domain name;
and the sending the third domain name comprises sending the third domain name to the client.
3. The method of claim 2, 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.
4. The method of claim 1, wherein adding a 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:
deleting resolution from the third domain name to the second domain name when the second domain name is deleted.
6. The method of claim 1, wherein adding a 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:
sending the second domain name to the client when the first domain name is resolvable by a domain name server to the third domain name, 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;
receiving a third domain name;
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;
wherein resolution from the first domain name to the second domain name is added after successful addition of 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 for the second domain name, the method further comprising:
after the resolution of the first domain name to the third domain name is successfully added, 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;
removing resolution from the first domain name to the third domain name from the domain name server and adding resolution from the first domain name to the second domain name at the domain name server.
9. A domain name management apparatus comprising:
the device comprises an acquisition module, a sending module and a receiving module, wherein the acquisition module is used for acquiring a domain name binding request which 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;
a first adding module, configured to add resolution from the first domain name to the second domain name when the first domain name can be resolved by a domain name server into the third domain name.
10. The apparatus of claim 9, wherein:
when the first domain name can be resolved to 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; 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:
a second sending module, configured to send a domain name binding request, where the domain name binding request is used to add resolution from the first domain name to the second domain name;
a receiving module, configured to receive a third domain name;
a second adding module, 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 resolution from the first domain name to the second domain name is added after successful addition of resolution of the first domain name to the third domain name.
12. 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 steps of any of claims 1-8.
13. A readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the method steps of any of claims 1-8.
14. A computer program product comprising computer instructions which, when executed by a processor, carry out the method steps of any of claims 1 to 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 true CN114553826A (en) | 2022-05-27 |
| CN114553826B 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 (17)
| 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 |
| US20140351413A1 (en) * | 2013-05-23 | 2014-11-27 | International Business Machines Corporation | Selecting between domain name system servers of a plurality of networks |
| 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 |
| CN106331216A (en) * | 2016-09-13 | 2017-01-11 | 腾讯科技（深圳）有限公司 | Domain name parsing method and domain name parsing device |
| CN106332067A (en) * | 2015-06-19 | 2017-01-11 | 华为技术有限公司 | Method, device and system of preventing diameter signaling attacks in wireless network |
| US20170063778A1 (en) * | 2015-08-26 | 2017-03-02 | Pulsepoint, Inc. | Cross-Domain HTTP Requests Using DNS Rebinding |
| 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 |
| US20190104103A1 (en) * | 2017-09-29 | 2019-04-04 | Level 3 Communications, Llc | Dynamic binding and load determination in a content delivery network (cdn) |
| 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 |
-
2022
- 2022-01-11 CN CN202210028841.8A patent/CN114553826B/en active Active
Patent Citations (17)
| 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 |
| US20140351413A1 (en) * | 2013-05-23 | 2014-11-27 | International Business Machines Corporation | Selecting between domain name system servers of a plurality of networks |
| 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 |
| US20170063778A1 (en) * | 2015-08-26 | 2017-03-02 | Pulsepoint, Inc. | Cross-Domain HTTP Requests Using DNS Rebinding |
| 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 |
| US20190104103A1 (en) * | 2017-09-29 | 2019-04-04 | Level 3 Communications, Llc | Dynamic binding and load determination in a content delivery network (cdn) |
| 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 |
|---|---|
| CN114553826B (en) | 2023-10-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103037312B (en) | Information push method and device | |
| KR101962156B1 (en) | Authorization processing method and apparatus | |
| CN112261172B (en) | Service addressing access method, device, system, equipment and medium | |
| CN108540433B (en) | User identity verification method and device | |
| CN103428179B (en) | A kind of log in the method for many domain names website, system and device | |
| CN111030812A (en) | Token verification method, device, storage medium and server | |
| US20100077467A1 (en) | Authentication service for seamless application operation | |
| CN110247894B (en) | Method and device for identifying fake handle server | |
| JP2017509936A (en) | Facilitating third-party execution of batch processing of requests that require authorization from resource owners for repeated access to resources | |
| CN112235423B (en) | Cross-chain transaction processing method and device, electronic equipment and storage medium | |
| CN110601832A (en) | Data access method and device | |
| CN109558710B (en) | User login method, device, system and storage medium | |
| CN109995775B (en) | Block chain verification code application method, equipment and storage medium | |
| CN113886803A (en) | Object storage system of instant messaging, object storage request method and device | |
| CN109977126A (en) | Replacing options, device, electronic equipment and the storage medium of identity | |
| CN111538566A (en) | Mirror image file processing method, device and system, electronic equipment and storage medium | |
| CN114553826B (en) | Domain name management method, device, electronic equipment, medium and program product | |
| CN111988298B (en) | Data processing method, device and equipment | |
| CN114338060B (en) | Authority verification method, device, system, equipment and storage medium | |
| CN113420241A (en) | Page access method and device, electronic equipment and storage medium | |
| CN112330366A (en) | Redemption code redemption request verification method, apparatus, device and computer readable medium | |
| JP2021117596A (en) | Information processing system, information processing method, and information processing program | |
| CN113301176B (en) | Domain name resolution method and device for content distribution network, electronic equipment and medium | |
| CN114584556B (en) | File transmission method and device | |
| US11882171B2 (en) | Instanced web servers for displaying custom content in a secure context |
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 |