CN110213398B - Alias management method, device, server and storage medium - Google Patents
Alias management method, device, server and storage medium Download PDFInfo
- Publication number
- CN110213398B CN110213398B CN201910465487.3A CN201910465487A CN110213398B CN 110213398 B CN110213398 B CN 110213398B CN 201910465487 A CN201910465487 A CN 201910465487A CN 110213398 B CN110213398 B CN 110213398B
- Authority
- CN
- China
- Prior art keywords
- alias
- address
- bound
- aliases
- primary
- 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
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/30—Managing network names, e.g. use of aliases or nicknames
-
- 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/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- 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/50—Address allocation
- H04L61/5076—Update or notification mechanisms, e.g. DynDNS
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses an alias management method, device, server and storage medium, and belongs to the technical field of networks. The invention provides a management method of a secondary alias, which binds a plurality of domain names with a plurality of primary aliases respectively, binds the plurality of primary aliases with a common secondary alias, binds the secondary aliases with an IP address, and can quickly find the corresponding secondary aliases through a user identifier when the IP addresses bound by the plurality of domain names corresponding to the user identifier are to be updated, and change the binding relationship on the secondary aliases, thereby realizing the function of updating the IP addresses bound by the plurality of domain names without updating the binding relationship for each primary alias one by one, thereby accelerating the speed of updating the IP address and improving the efficiency of managing the aliases. And an IP address does not need to be respectively allocated to each primary alias, so that the number of the IP addresses allocated to a plurality of primary aliases in total is saved, and the resource utilization rate of the IP addresses is improved.
Description
Technical Field
The present invention relates to the field of network technologies, and in particular, to a method and an apparatus for alias management, a server, and a storage medium.
Background
With the development of network technology, domain names registered in the internet are increasing day by day, and in order to improve the speed of domain name resolution and avoid exposing Internet Protocol (IP) addresses of websites, domain names are usually associated with alias names (CNAME), so that the domain names point to the alias names and the alias names point to the IP addresses. When domain name resolution is required, the corresponding alias is firstly resolved through the domain name, and then the corresponding IP address is resolved through the alias.
Taking the example that a user has N domain names, the alias is currently managed by the following method: each domain name in the N domain names is respectively bound with an alias, and each alias in the N alias is respectively bound with an IP address, so that the N individual names correspond to the N IP addresses one by one, wherein N is a positive integer.
When the alias is managed by adopting the method, when the IP addresses corresponding to the N domain names are to be updated, the IP addresses bound to each alias in the N alias are required to be updated one by one, namely, the step of updating the IP addresses for N times is required to be executed, so that the visible steps are complicated, and the efficiency is low.
Disclosure of Invention
The embodiment of the invention provides an alias management method, device, server and storage medium, which can solve the technical problems of complicated steps and low efficiency in updating an IP address in the related art. The technical scheme is as follows:
in one aspect, a method for alias management is provided, the method including:
receiving an updating request, wherein the updating request is used for requesting to update the Internet protocol IP addresses bound by a plurality of domain names corresponding to the user identification;
inquiring alias management information according to the user identifier to obtain a secondary alias corresponding to the user identifier, wherein the alias management information comprises a corresponding relation between the user identifier and the secondary alias, the secondary alias is bound with a plurality of primary aliases, and the primary aliases are respectively bound with the domain names;
and updating the IP address bound by the secondary alias.
In another aspect, there is provided an alias management apparatus, the apparatus including:
the device comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an updating request which is used for requesting to update the Internet protocol IP addresses bound by a plurality of domain names corresponding to user identifications;
the query module is used for querying alias management information according to the user identifier to obtain a secondary alias corresponding to the user identifier, wherein the alias management information comprises a corresponding relation between the user identifier and the secondary alias, the secondary alias is bound with a plurality of primary aliases, and the primary aliases are respectively bound with the domain names;
and the updating module is used for updating the IP address bound by the secondary alias.
In one possible implementation, the alias management information includes a second binding relationship between the domain name and the primary alias, and a third binding relationship between the primary alias and the secondary alias, and after updating the IP address to which the secondary alias is bound,
the receiving module is further configured to receive a domain name resolution request, where the domain name resolution request is used to request to acquire an IP address corresponding to a target domain name in the plurality of domain names;
the query module is further configured to query the second binding relationship according to the target domain name to obtain a target primary alias bound to the target domain name;
the query module is further configured to query the third binding relationship according to the target primary alias to obtain the secondary alias bound to the target primary alias;
the query module is further configured to query the first binding relationship according to the secondary alias to obtain the updated IP address bound to the secondary alias.
In one possible implementation, the apparatus further comprises:
the establishing module is used for establishing the second binding relationship according to the domain names and the primary aliases; establishing the third binding relationship according to the plurality of primary aliases and the secondary aliases; and establishing the first binding relationship according to the secondary alias and the IP address.
In another aspect, a server is provided and includes one or more processors and one or more memories, where at least one instruction is stored in the one or more memories, and the instruction is loaded and executed by the one or more processors to implement the operations performed by the alias management method.
In another aspect, a computer-readable storage medium is provided, in which at least one instruction is stored, and the instruction is loaded and executed by a processor to implement the operations performed by the alias management method.
The technical scheme provided by the embodiment of the invention has the beneficial effects that at least:
the method and the device provided by the embodiment of the invention provide a management method of a secondary alias, a plurality of domain names are respectively bound with a plurality of primary aliases, the plurality of primary aliases are bound with a common secondary alias, the secondary alias is bound with an IP address, when the IP addresses bound by the plurality of domain names corresponding to a user identifier are to be updated, the corresponding secondary aliases can be quickly found through the user identifier, the binding relationship is changed on the secondary aliases, the function of updating the IP addresses bound by the plurality of domain names can be realized, the binding relationship does not need to be updated one by one aiming at each primary alias, the speed of updating the IP address is accelerated, and the efficiency of managing the aliases can be improved. In addition, a plurality of primary aliases and a common secondary alias are bound together, and one IP address is allocated to the secondary alias, so that the plurality of primary aliases can share one IP address, and each primary alias does not need to be allocated with one IP address, so that the number of the total allocated IP addresses for the plurality of primary aliases is saved, and the resource utilization rate of the IP addresses is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a diagram illustrating the relationship between a user identifier, a domain name, a primary alias, a secondary alias, and an IP address provided by an embodiment of the present invention;
fig. 2 is a block diagram of an alias management system according to an embodiment of the present invention;
fig. 3 is a flowchart of an alias management method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an alias management apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Some key terms to which the present invention relates are described below.
Domain Name (Domain Name): is a string of names separated by points, which is the name of a computer device or a group of computer devices in an ethernet network. The domain name can be understood as a computer identification formed by characters, and compared with an IP address formed by numbers, the domain name has the characteristic of convenient memory, so that people can access a computer pointed by the IP address through the domain name without memorizing the IP address by registering the domain name and mapping the domain name and the IP address. Illustratively, referring to fig. 1, the domain names may be "a.qq.com", "b.wx.com".
Domain name resolution: refers to the process of converting a domain name to an IP address.
Alias (CNAME, also known as canonical name): for mapping multiple names to the same computer or group of computer devices. In the process of domain name resolution, the domain name is firstly resolved into a corresponding alias, and then the alias is resolved into a corresponding IP address. In the embodiment, the management mode of the aliases is improved, and a mechanism of two-level aliases is designed.
Primary alias: refers to an alias that is directly bound to a domain name. Each domain name of the same user identification can be respectively bound with a primary alias. Illustratively, referring to fig. 1, the primary alias may be "a.com-l 1. waf.com", "b.com-l 1. waf.com", and as can be seen from fig. 1, the domain name "a.qq.com" is bound with the primary alias "a.com-l 1. waf.com", and the domain name "b.wx.com" is bound with the primary alias "b.com-l 1. waf.com".
Secondary alias: refers to aliases bound to the primary alias. All the domain name bound primary aliases of the same user identifier can be bound with a common secondary alias, the secondary aliases can be bound with an IP address, and the IP address can correspond to a specific server or a plurality of servers. Illustratively, referring to fig. 1, the secondary alias may be "l 2. waf.com", and as can be seen from fig. 1, the primary alias "a.com-l 1. waf.com" and the primary alias "b.com-l 1. waf.com" are both bound to this secondary alias "l 2. waf.com", i.e., the domain name "a.qq.com" and the domain name "b.wx.com" of the user identification are both bound to this secondary alias "l 2. waf.com".
Website application level intrusion prevention system (web application firewall, WAF for short): the method is a product for providing protection service for World Wide Web (Web) application by executing a series of security policies aiming at Hypertext Transfer Protocol (HTTP)/Hypertext Transfer security Protocol (HTTPs).
Fig. 2 is a block diagram of an alias management system according to an embodiment of the present invention. The alias management system includes: a first terminal 210, an alias management platform 220, and a second terminal 230.
The first terminal 210 is connected to the alias management platform 220 through a wireless network or a wired network. The first terminal 210 may be at least one of a smartphone, a game console, a desktop computer, a tablet computer, an e-book reader, an MP3 player (a player for playing music), an MP4 player (a player for playing audio, video, or browsing pictures), and a laptop portable computer. The first terminal 210 installs and runs an application program, which may be a program for managing a website. Illustratively, the first terminal 210 is a terminal used by a first user, which may be an owner, a builder, or an administrator of a website, and a user identifier of the first user is logged into an application running in the first terminal 210. The first terminal 210 may be generally referred to as one of a plurality of terminals, and the embodiment is only illustrated by the first terminal 210. Those skilled in the art will appreciate that the number of first terminals may be greater or less. For example, the number of the first terminals may be only one, or several tens or hundreds of the first terminals, or a larger number, and in this case, the alias management system further includes other first terminals. The number and the device type of the first terminals are not limited in the embodiment of the invention.
The alias management platform 220 includes at least one of a server, a plurality of servers, a cloud computing platform, and a virtualization center. The alias management platform 220 is used to provide background services for applications installed by the first terminal 210. For example, the alias management platform 220 may be provided as a WAF, which may provide protection services to applications installed in the first terminal 210 by enforcing the security policies of HTTP/HTTPs. The alias management platform 220 may include an alias management Server, a Domain Name Server (DNS), and a database. The alias management server is used for managing aliases, the DNS is used for domain name resolution, and a database can store a large number of domain names and alias management information. The alias management server may be one or more. When there are multiple alias management servers, there are at least two alias management servers for providing different services, and/or there are at least two alias management servers for providing the same service, for example, providing the same service in a load balancing manner, which is not limited in this embodiment. Alias management information may be generated and maintained in the alias management server.
The second terminal 230 is connected to the alias management platform 220 through a wireless network or a wired network. The second terminal 230 may be at least one of a smartphone, a game console, a desktop computer, a tablet computer, an e-book reader, an MP3 player, an MP4 player, and a laptop portable computer. The second terminal 230 installs and runs an application, which may be a Web application, for example, any one of an audio playing application, a video playing application, a social contact application, an instant messaging application, a translation application, a shopping application, and a browser application. Illustratively, the second terminal 230 is a terminal used by a second user, the first user may be a user of a website, and a user account of the second user is logged in an application running in the second terminal 230, and the user account may be an account registered in the website. The second terminal 230 may be generally referred to as one of a plurality of terminals, and the embodiment is only illustrated by the second terminal 230. Those skilled in the art will appreciate that the number of the second terminals 230 may be greater or less. For example, the number of the second terminals 230 may be only one, or the number of the second terminals 230 may be several tens or several hundreds, or more, in which case the alias management system further includes other second terminals 230. The number and the device type of the second terminals 230 are not limited in the embodiment of the present invention.
Fig. 3 is a flowchart of an alias management method according to an embodiment of the present invention. The execution main body of the embodiment of the invention comprises a first terminal, a server and a second terminal, and referring to fig. 3, the method comprises the following steps:
301. the server generates alias management information.
The alias management information is used for managing the alias, and includes a user identifier, a plurality of domain names, a plurality of primary aliases, a secondary alias and an IP address, and may include a correspondence between the user identifier and the secondary alias, a first binding relationship between the secondary alias and the IP address, a second binding relationship between the domain name and the primary alias, and a third binding relationship between the primary alias and the secondary alias.
Specifically, the user identifier corresponds to a secondary alias, the secondary aliases corresponding to different user identifiers may be different, and the secondary alias corresponding to the user identifier may be determined according to any user identifier and a corresponding relationship between the user identifier and the secondary alias. The second-level aliases are bound with the plurality of first-level aliases, that is, the plurality of first-level aliases all point to the second-level aliases, and the second-level aliases can be determined according to each first-level alias in the plurality of first-level aliases and the third binding relation. The plurality of first-level aliases are respectively bound with the plurality of domain names, each first-level alias can be bound with one domain name, the domain names bound by different first-level aliases can be different, and the first-level aliases bound by the domain names can be determined according to any one of the plurality of domain names and the second binding relation. Illustratively, referring to fig. 1, the plurality of domain names may be domain name a and domain name B, the plurality of primary aliases may be alias L1-a and alias L1-B, the secondary alias may be alias L2, domain name a is bound to alias L1-a, domain name B is bound to alias L1-B, and alias L1-a and alias L1-B are both bound to alias L2.
As can be seen from fig. 1, in the present embodiment, a plurality of primary aliases (e.g., alias L1-a and alias L1-B) point to a common secondary alias (e.g., alias L2), and the secondary alias (e.g., alias L2) is bound to an IP address, so that a plurality of domain names (e.g., domain name a and domain name B) can share the same IP address, and if the IP address bound by a plurality of domain names (e.g., domain name a and domain name B) needs to be changed, only operation is performed on the secondary alias (e.g., alias L2), and there is no need to perform operation on each primary alias one by one.
In some possible embodiments, the generation process of the alias management information may include the following steps one to seven.
Step one, a first terminal sends a user identification and a plurality of domain names to a server.
The first terminal may send the user identifier registered by the user and all domain names corresponding to the user identifier to the server, so that the server allocates an IP address to the domain name corresponding to the user identifier. The user identification is used for uniquely identifying the corresponding user, and the user identifications of different users are different. For example, the user identifier may be a user identification number (identification, ID).
And step two, the server receives the user identification and the plurality of domain names from the first terminal, and for each domain name in the plurality of domain names, the server generates a primary alias according to the domain name.
The server may generate a corresponding primary alias for each domain name, resulting in multiple primary aliases. For example, if a user has N domain names, N primary aliases may be generated for the N domain names, where N is a positive integer. In addition, the server may send the primary alias corresponding to each domain name to the first terminal, so that the user can know the first alias corresponding to the domain name.
And step three, the server establishes the second binding relationship according to the domain names and the primary aliases.
The second binding relationship may include a plurality of domain names and a plurality of primary aliases, and each domain name in the second binding relationship may bind one primary alias.
And fourthly, carrying out hash operation on the user identification by the server to obtain the secondary alias.
And generating a secondary alias by taking the user identifier as granularity, wherein all domain names corresponding to the same user identifier correspond to the same secondary alias. Moreover, because the user identification has uniqueness, the user identifications of different users cannot be repeated, and the hash operation has uniqueness, the secondary aliases corresponding to different user identifications are different, so that the repetition of the secondary aliases corresponding to different users is avoided.
And step five, the server establishes the third binding relationship according to the plurality of primary aliases and the secondary aliases.
The third binding relationship may include a plurality of primary aliases and a secondary alias, and the primary alias and the secondary alias may be in a many-to-one relationship, that is, the plurality of primary aliases may bind a common secondary alias, and any one of the plurality of primary aliases may resolve to the secondary alias.
And step six, the server establishes the first binding relationship according to the secondary alias and the IP address.
The first binding relationship may include a secondary alias and at least one IP address, and the secondary alias and the IP address may be in a one-to-one relationship or a one-to-many relationship. Generally, if an IP address is assigned to a user, all domain names corresponding to the IP address may share the same secondary alias, and the secondary alias and the IP address may be in a one-to-one relationship.
And step seven, the server generates the alias management information.
The server may write the correspondence between the user identifier and the secondary alias, or may write the first binding relationship, the second binding relationship, and the third binding relationship into the alias management information, and then, the server may store the alias management information so as to manage the domain name, the primary alias, the secondary alias, and the IP address corresponding to the user identifier.
302. The first terminal sends an update request to the server.
The update request is used for requesting to update the internet protocol IP addresses bound by the domain names corresponding to the user identifiers, and the update request can be triggered by an input operation of the first user on the first terminal. The update request may carry a user identifier of the first user.
The update request includes, but is not limited to, the following two types.
Type one (modify), update request may be used to request a modification to the IP address of the secondary alias binding in the first binding relationship. For example, the update request may be used to request that the IP addresses corresponding to the plurality of domain names be modified to the updated IP address, so that the plurality of domain names are rebinding with the updated IP address.
Illustratively, a modification type of update request may be applied in a scenario of a regional change. Specifically, the update request may be used to request that the IP addresses corresponding to the domain names be modified from the IP address of the first region to the IP address of the second region, so that the domain names can be resolved to the IP address of the second region, and the terminal may change from a server accessing the first region to a server accessing the second region. Wherein the first region and the second region may be any two different regions. The update request may carry an identifier of the second region, where the identifier of the second region is used to indicate the second region, and may be, for example, a name, a number, and the like of the second region.
Type two (add), the update request is to request that an updated IP address be added to the IP address of the second level alias binding in the first binding relationship.
Illustratively, the increased type of update request may be applied in a multi-access scenario. Specifically, the update request may be used to request that an IP address of the third domain is added to the IP address bound to the second-level alias in the first binding relationship, so that the domain names can be resolved to the IP address of the third domain, and the terminal may access the server of the third domain. The update request may carry an identifier of the third region, where the identifier of the third region is used to indicate the third region, and may be, for example, a name, a number, and the like of the third region.
303. The server receives an update request of the first terminal.
304. And the server queries alias management information according to the user identifier to obtain a secondary alias corresponding to the user identifier.
The server can analyze the update request to obtain the user identifier carried by the update request, and query the corresponding relation between the user identifier and the second-level alias in the alias management information by taking the user identifier as an index to obtain the second-level alias.
305. The server updates the IP address of the secondary alias binding.
The domain names are respectively bound with the primary aliases, the primary aliases are bound with the secondary aliases, the secondary aliases are bound with the IP addresses, the server updates the IP addresses bound by the secondary aliases, the IP addresses corresponding to the primary aliases can be updated, and the IP addresses corresponding to the domain names are updated.
Illustratively, if the IP addresses corresponding to the N primary aliases are to be updated, only one step of updating the IP addresses bound by the secondary aliases needs to be executed, and the IP addresses bound by each primary alias do not need to be updated respectively, so that the step of updating the IP addresses can be reduced from N times to 1 time, and by reducing the step of updating the IP addresses (N-1) times, the speed and efficiency of updating the IP addresses can be greatly improved, and the function of quickly and conveniently managing the IP addresses is realized.
In addition, because N primary aliases are bound with the same secondary alias, and the secondary alias is bound with an IP address, namely, the N primary aliases are only bound with one IP address, but are not required to be bound with the N IP addresses respectively, the IP addresses required to be bound by the N primary aliases can be saved from N to 1, and the resource utilization rate of the IP addresses can be greatly improved by saving (N-1) IP addresses.
Corresponding to the update request of type one, the server may modify the IP address bound by the secondary alias in the first binding relationship into an updated IP address in response to the update request. Illustratively, in a scenario of region change, the server may allocate an IP address of the second region to the user identifier; and modifying the IP address pointed by the secondary alias from the IP address of the first region to the IP address of the second region.
In response to the update request of type two, the server may add the IP addresses corresponding to the domain names. Illustratively, in a scenario of multi-place access, the server may allocate an IP address of the third area to the user identifier; and adding the updated IP address to the IP address bound by the second-level alias in the first binding relationship.
306. And the second terminal sends a domain name resolution request to the server.
The domain name resolution request is used for requesting to acquire an IP address corresponding to a target domain name in the plurality of domain names, wherein the target domain name is a domain name to be resolved.
307. The server receives a domain name resolution request.
308. And the server acquires the updated IP address according to the alias management information.
Since the IP address bound to the secondary alias is updated in the above steps 302 to 305, the server can obtain the updated IP address when performing domain name resolution.
In some possible embodiments, step 308 may specifically include the following steps one to three:
step one, the server inquires the second binding relation according to the target domain name to obtain a target primary alias bound with the target domain name. The target primary alias is a primary alias bound with the target domain name in the multiple primary aliases.
And step two, the server queries the third binding relation according to the target primary alias to obtain the secondary alias bound with the target primary alias.
And step three, the server queries the first binding relation according to the secondary alias to obtain the updated IP address bound with the secondary alias.
309. And the server sends the updated IP address to the second terminal.
The second terminal may receive the updated IP address and send an access request to the updated IP address.
Illustratively, in a scenario applied to a region change, before the region change, the server may send the IP address of the first region to the second terminal, and then the second terminal may send an access request to the server corresponding to the IP address of the first region, after the region change, the server may send the IP address of the second region to the second terminal by performing the above steps, and then the second terminal may access the server of the second region according to the IP address of the second region, thereby ensuring that the server may still normally access the second terminal after the region is changed from the first region to the second region, and in this scenario, the operation of updating the IP address is simplified.
In the scenario of multi-place access, after a server is deployed in a new region (a third region), the server sends an IP address of the third region to the second terminal, and then the second terminal accesses the server in the third region according to the IP address of the third region, so that the terminal can access the new server after the server is deployed in the new region, and in the scenario, the operation of updating the IP address is simplified.
The embodiment can be applied to a scene of managing aliases in the WAF, and can quickly and conveniently perform certain transparent operations on the background of the Web application by executing the steps, so that the domain name and the aliases of the Web application are more conveniently managed, and the utilization rate of IP resources is effectively improved.
It should be noted that, in this embodiment, each step executed by the server may be executed by being dispersed on different servers, or may be executed by being integrated on the same server, which is not limited in this embodiment. Illustratively, the above steps 301, 303, 304, 305, 307, 309 may be performed by the alias management server, and the step 308 may be performed by the alias management server interacting with the DNS.
The embodiment provides a management method of a secondary alias, which binds a plurality of domain names with a plurality of primary aliases respectively, binds a plurality of primary aliases with a common secondary alias, binds a secondary alias with an IP address, and when an IP address bound by a plurality of domain names corresponding to a user identifier is to be updated, the corresponding secondary alias can be quickly found through the user identifier, and the binding relationship is changed on the secondary alias, so that the function of updating the IP addresses bound by a plurality of domain names can be realized, and the binding relationship does not need to be updated one by one for each primary alias, thereby accelerating the speed of updating the IP address and improving the efficiency of managing the aliases. In addition, a plurality of primary aliases and a common secondary alias are bound together, and one IP address is allocated to the secondary alias, so that the plurality of primary aliases can share one IP address, and each primary alias does not need to be allocated with one IP address, so that the number of the total allocated IP addresses for the plurality of primary aliases is saved, and the resource utilization rate of the IP addresses is improved.
Fig. 4 is a schematic structural diagram of an alias management apparatus according to an embodiment of the present invention. Referring to fig. 4, the apparatus includes: a receiving module 401, a query module 402, and an update module 403.
A receiving module 401, configured to receive an update request, where the update request is used to request to update internet protocol IP addresses bound to multiple domain names corresponding to user identifiers;
a query module 402, configured to query alias management information according to the user identifier to obtain a second-level alias corresponding to the user identifier, where the alias management information includes a correspondence between the user identifier and the second-level alias, the second-level alias is bound to multiple first-level aliases, and the multiple first-level aliases are bound to the multiple domain names respectively;
and an updating module 403, configured to update the IP address bound to the second-level alias.
In one possible implementation, the apparatus further comprises:
the hash operation module is used for carrying out hash operation on the user identification to obtain the secondary alias;
and the generating module is used for generating the alias management information according to the user identifier and the secondary alias.
In one possible implementation, the alias management information includes a first binding relationship between a secondary alias and an IP address, and the updating module 403 is configured to perform any one of:
modifying the IP address bound by the secondary alias in the first binding relationship into an updated IP address;
and adding the updated IP address to the IP address bound by the second-level alias in the first binding relationship.
In one possible implementation, the alias management information includes a second binding between the domain name and the primary alias, and a third binding between the primary alias and the secondary alias, and the update of the IP address bound to the secondary alias,
the receiving module 401 is further configured to receive a domain name resolution request, where the domain name resolution request is used to request to obtain an IP address corresponding to a target domain name in the multiple domain names;
the query module 402 is further configured to query the second binding relationship according to the target domain name, so as to obtain a target primary alias bound to the target domain name;
the query module 402 is further configured to query the third binding relationship according to the target primary alias to obtain the secondary alias bound to the target primary alias;
the query module 402 is further configured to query the first binding relationship according to the secondary alias, so as to obtain the updated IP address bound to the secondary alias.
In one possible implementation, the apparatus further comprises:
the establishing module is used for establishing the second binding relationship according to the domain names and the primary aliases; establishing the third binding relationship according to the plurality of primary aliases and the secondary aliases; and establishing the first binding relationship according to the secondary alias and the IP address.
The device provided by the embodiment of the invention provides a management device of a secondary alias, a plurality of domain names are respectively bound with a plurality of primary aliases, the plurality of primary aliases are bound with a common secondary alias, the secondary alias is bound with an IP address, when the IP addresses bound by the plurality of domain names corresponding to a user identifier are to be updated, the corresponding secondary aliases can be quickly found through the user identifier, the binding relationship is changed on the secondary aliases, the function of updating the IP addresses bound by the plurality of domain names can be realized, the binding relationship does not need to be updated for each primary alias one by one, the speed of updating the IP address is accelerated, and the efficiency of managing the aliases can be improved. In addition, a plurality of primary aliases and a common secondary alias are bound together, and one IP address is allocated to the secondary alias, so that the plurality of primary aliases can share one IP address, and each primary alias does not need to be allocated with one IP address, so that the number of the total allocated IP addresses for the plurality of primary aliases is saved, and the resource utilization rate of the IP addresses is improved.
All the above-mentioned optional technical solutions can be combined arbitrarily to form the optional embodiments of the present invention, and are not described herein again.
It should be noted that: in the alias management apparatus provided in the above embodiment, when managing aliases, only the division of the above functional modules is illustrated, and in practical applications, the above function assignment may be performed by different functional modules according to needs, that is, the internal structure of the server is divided into different functional modules to perform all or part of the above described functions. In addition, the alias management apparatus and the alias management method provided in the above embodiments belong to the same concept, and specific implementation processes thereof are described in detail in the method embodiments and are not described herein again.
Fig. 5 is a schematic structural diagram of a server according to an embodiment of the present invention, where the server 500 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 501 and one or more memories 502, where the memory 502 stores at least one instruction, and the at least one instruction is loaded and executed by the processor 501 to implement the alias management method provided by each method embodiment. Of course, the server may also have a wired or wireless network interface, an input/output interface, and other components to facilitate input and output, and the server may also include other components for implementing the functions of the device, which are not described herein again.
In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one instruction is stored, and the instruction is loaded and executed by a processor to implement the operation performed by the alias management method. For example, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (6)
1. A method for alias management, the method comprising:
carrying out Hash operation on the user identification to obtain a secondary alias;
generating alias management information according to the user identifier and the secondary alias, wherein the alias management information comprises a first binding relationship between the secondary alias and an Internet Protocol (IP) address, and the IP address is an IP address bound by a plurality of domain names corresponding to the user identifier;
receiving an update request, wherein the update request is used for requesting to update the IP address;
inquiring the alias management information according to the user identifier to obtain the second-level alias corresponding to the user identifier, wherein the alias management information comprises the corresponding relation between the user identifier and the second-level alias, the second-level alias is bound with a plurality of first-level aliases, and the plurality of first-level aliases are respectively bound with the plurality of domain names;
when the update request is of a modification type, modifying the IP address bound by the secondary alias in the first binding relationship into an updated IP address;
and when the update request is an update request of an increased type, adding an updated IP address to the IP address bound by the secondary alias in the first binding relationship.
2. The method of claim 1, wherein the alias management information comprises a second binding between the domain name and the primary alias and a third binding between the primary alias and the secondary alias, the method further comprising:
receiving a domain name resolution request, wherein the domain name resolution request is used for requesting to acquire an IP address corresponding to a target domain name in the plurality of domain names;
inquiring the second binding relation according to the target domain name to obtain a target primary alias bound with the target domain name;
inquiring the third binding relation according to the target primary alias to obtain a secondary alias bound with the target primary alias;
and inquiring the first binding relation according to the secondary alias to obtain the updated IP address bound with the secondary alias.
3. The method of claim 2, wherein prior to receiving the update request, the method further comprises:
establishing the second binding relationship according to the domain names and the primary aliases;
establishing the third binding relationship according to the plurality of primary aliases and the secondary aliases;
and establishing the first binding relationship according to the secondary alias and the IP address.
4. An alias management apparatus, comprising:
the hash operation module is used for carrying out hash operation on the user identification to obtain a secondary alias;
a generating module, configured to generate alias management information according to the user identifier and the secondary alias, where the alias management information includes a first binding relationship between the secondary alias and an internet protocol IP address, and the IP address is an IP address bound by multiple domain names corresponding to the user identifier;
a receiving module, configured to receive an update request, where the update request is used to request to update the IP address;
the query module is used for querying the alias management information according to the user identifier to obtain the second-level alias corresponding to the user identifier, wherein the alias management information comprises a corresponding relation between the user identifier and the second-level alias, the second-level alias is bound with a plurality of first-level aliases, and the plurality of first-level aliases are respectively bound with the plurality of domain names;
the updating module is used for modifying the IP address bound by the secondary alias in the first binding relationship into an updated IP address when the updating request is a modification type updating request; and when the update request is an update request of an increased type, adding an updated IP address to the IP address bound by the secondary alias in the first binding relationship.
5. A server, comprising one or more processors and one or more memories having stored therein at least one instruction, the instruction being loaded and executed by the one or more processors to perform operations performed by the alias management method as recited in any of claims 1 to 3.
6. A computer-readable storage medium having stored therein at least one instruction which is loaded and executed by a processor to perform operations performed by the alias management method as claimed in any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910465487.3A CN110213398B (en) | 2019-05-30 | 2019-05-30 | Alias management method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910465487.3A CN110213398B (en) | 2019-05-30 | 2019-05-30 | Alias management method, device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110213398A CN110213398A (en) | 2019-09-06 |
| CN110213398B true CN110213398B (en) | 2021-10-08 |
Family
ID=67789694
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910465487.3A Active CN110213398B (en) | 2019-05-30 | 2019-05-30 | Alias management method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110213398B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111770063B (en) * | 2020-02-18 | 2022-09-16 | 支付宝(杭州)信息技术有限公司 | Derivation and verification method, device and equipment for digital identity information |
| CN111935327B (en) * | 2020-02-24 | 2023-07-25 | 北京豆萌信息技术有限公司 | Domain name assignment method, device, equipment and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004312609A (en) * | 2003-04-10 | 2004-11-04 | Hitachi Ltd | Dynamic dns registration method, domain name solution method, proxy server, and address translation instrument |
| CN105516391A (en) * | 2015-12-25 | 2016-04-20 | 互联网域名系统北京市工程研究中心有限公司 | CNAME-based DNS (domain name system) domain name resolution method |
| CN106817437A (en) * | 2017-01-11 | 2017-06-09 | 腾讯科技（深圳）有限公司 | The querying method and device of address record |
| CN107071078A (en) * | 2017-02-19 | 2017-08-18 | 网宿科技股份有限公司 | Domain name analysis system, domain name resolution server and domain name analytic method |
| CN109561101A (en) * | 2018-12-25 | 2019-04-02 | 上海点融信息科技有限责任公司 | For the treating method and apparatus of Denial of Service attack |
-
2019
- 2019-05-30 CN CN201910465487.3A patent/CN110213398B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004312609A (en) * | 2003-04-10 | 2004-11-04 | Hitachi Ltd | Dynamic dns registration method, domain name solution method, proxy server, and address translation instrument |
| CN105516391A (en) * | 2015-12-25 | 2016-04-20 | 互联网域名系统北京市工程研究中心有限公司 | CNAME-based DNS (domain name system) domain name resolution method |
| CN106817437A (en) * | 2017-01-11 | 2017-06-09 | 腾讯科技（深圳）有限公司 | The querying method and device of address record |
| CN107071078A (en) * | 2017-02-19 | 2017-08-18 | 网宿科技股份有限公司 | Domain name analysis system, domain name resolution server and domain name analytic method |
| CN109561101A (en) * | 2018-12-25 | 2019-04-02 | 上海点融信息科技有限责任公司 | For the treating method and apparatus of Denial of Service attack |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110213398A (en) | 2019-09-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108370391B (en) | Shared multi-tenant Domain Name System (DNS) server for virtual networks | |
| WO2019165665A1 (en) | Domain name resolution method, server and system | |
| CN107181808B (en) | Private cloud system and operation method | |
| CN105959433B (en) | A kind of domain name analytic method and its domain name analysis system | |
| CN107786621B (en) | User information management method, access processing method, device and system | |
| US20110119306A1 (en) | User-Based DNS Server Access Control | |
| WO2022111313A1 (en) | Request processing method and micro-service system | |
| US10609060B2 (en) | Clustering network addresses | |
| KR20140021602A (en) | Global traffic management using modified hostname | |
| CN204695386U (en) | Towards the management information system of many tenants | |
| CN110213398B (en) | Alias management method, device, server and storage medium | |
| CN112035244A (en) | Deployment of virtual node clusters in a multi-tenant environment | |
| CN114338682B (en) | Flow identity identification transmission method and device, electronic equipment and storage medium | |
| CN108737591A (en) | A kind of method and device of service configuration | |
| US10944714B1 (en) | Multi-factor domain name resolution | |
| US11861386B1 (en) | Application gateways in an on-demand network code execution system | |
| CN108141704B (en) | Location identification of previous network message processors | |
| CN113965543A (en) | Access method and device of application server and storage medium | |
| KR102131083B1 (en) | System and method for cloud based hosting service | |
| US10819775B2 (en) | Systems and methods for server failover and load balancing | |
| US10791088B1 (en) | Methods for disaggregating subscribers via DHCP address translation and devices thereof | |
| US11652746B1 (en) | Resilient consistent hashing for a distributed cache | |
| WO2021232860A1 (en) | Communication method, apparatus and system | |
| US10958580B2 (en) | System and method of performing load balancing over an overlay network | |
| US11941543B2 (en) | Inferencing endpoint discovery in computing systems |
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 |