WO2019237557A1 - 一种控制多cname流量比例的方法和装置 - Google Patents

一种控制多cname流量比例的方法和装置 Download PDF

Info

Publication number
WO2019237557A1
WO2019237557A1 PCT/CN2018/107475 CN2018107475W WO2019237557A1 WO 2019237557 A1 WO2019237557 A1 WO 2019237557A1 CN 2018107475 W CN2018107475 W CN 2018107475W WO 2019237557 A1 WO2019237557 A1 WO 2019237557A1
Authority
WO
WIPO (PCT)
Prior art keywords
dns server
domain name
cname
address
target
Prior art date
Application number
PCT/CN2018/107475
Other languages
English (en)
French (fr)
Inventor
陈单江
吴小英
Original Assignee
网宿科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 网宿科技股份有限公司 filed Critical 网宿科技股份有限公司
Priority to US16/485,549 priority Critical patent/US20210336920A1/en
Priority to EP18922730.9A priority patent/EP3800870A4/en
Publication of WO2019237557A1 publication Critical patent/WO2019237557A1/zh

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/45—Network directories; Name-to-address mapping
    • H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
    • 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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • 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
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/58—Caching of addresses or names

Definitions

  • the invention relates to the technical field of domain name resolution, in particular to a method and device for controlling the proportion of multiple CNAME traffic.
  • CDN service providers there are many CDN service providers, and there may be cases where multiple CDN service providers jointly provide a CDN acceleration service for a customer.
  • CDN acceleration service for a customer.
  • both customers and CDN service providers have a need to control the proportion of bandwidth carried by each CDN service provider.
  • the customer or CDN service provider can configure it in advance on the authoritative DNS server of the customer's domain name, using multiple CNAME (can be referred to as alias) records (the form of the CNAME record can be the correspondence between the customer's domain name and the CNAME domain name), and configure different traffic Pull ratio to drive traffic to customer domain names.
  • the authoritative DNS server has two CNAME records for the customer domain name www.XXX.com: M and N, and the corresponding traffic pull ratio is 4: 1.
  • the authoritative DNS server receives the A record of the local DNS server. After querying the request, you can select the CNAME record with a probability of 4: 1 and feed it back to the local DNS server. In this way, the local DNS server can then obtain the access IP of the CDN node that provides accelerated services for the customer's domain name from the authoritative DNS server pointed to by the CNAME record.
  • the local DNS server After the local DNS server obtains the access IP of the CDN node, it caches the access IP for a certain period of time. During the cache time, the local DNS server will pull all the access traffic for the customer's domain name in the service area to the CDN node, without any access traffic reaching the CDN nodes of other CDN service providers. Further, after the cache time has passed, if the authoritative DNS server feeds back the access IPs of the CDN nodes of different CDN service providers, the local DNS server will again pull all the access traffic of the customer domain name within its service scope to this CDN node. The access traffic on the CDN node will become zero. Therefore, the traffic load of the CDN node is high in a short time, and the traffic fluctuation of the CDN node is large in a long time.
  • embodiments of the present invention provide a method and device for controlling a multi-CNAME traffic ratio.
  • the technical solution is as follows:
  • a method for controlling the proportion of multiple CNAME traffic includes:
  • the target authoritative DNS server receives the A record query request of the target domain name sent by the local DNS server, and determines all CNAME domain names according to the stored CNAME records of the target domain name;
  • the target authoritative DNS server obtains an IP address corresponding to each CNAME domain name in all the CNAME domain names from the authoritative DNS servers corresponding to all the CNAME domain names;
  • the target authoritative DNS server combines at least one IP group corresponding to the CNAME domain name based on a preset traffic pull ratio of the target domain name to generate at least one IP group;
  • the target authoritative DNS server randomly feeds back one of the at least one IP group to the local DNS server.
  • the A record query request of the target domain name carries the IP address of the local DNS server or the IP address of the user terminal;
  • the obtaining, by the target authoritative DNS server from the authoritative DNS servers corresponding to all the CNAME domain names, an IP address corresponding to each of the CNAME domain names includes:
  • the target authoritative DNS server For each of the CNAME domain names, the target authoritative DNS server sends an A record query request of the CNAME domain name carrying the IP address of the local DNS server or the IP address of the user terminal to the authoritative DNS server corresponding to the CNAME domain name;
  • the target authoritative DNS server receives the IP address corresponding to the CNAME domain name determined and fed back by the authoritative DNS server corresponding to the CNAME domain name based on the IP address of the local DNS server or the IP address of the user terminal.
  • the A record query request of the target domain name carries the IP address of the local DNS server or the IP address of the user terminal;
  • the obtaining, by the target authoritative DNS server from the authoritative DNS servers corresponding to all the CNAME domain names, an IP address corresponding to each of the CNAME domain names includes:
  • the target authoritative DNS server For each of the CNAME domain names, the target authoritative DNS server sends an A record synchronization request to the authoritative DNS server corresponding to the CNAME domain name;
  • the target authoritative DNS server receives all A records sent by the authoritative DNS server corresponding to the CNAME domain name
  • the target authoritative DNS server determines the IP address corresponding to the CNAME domain name in all the A records based on the IP address of the local DNS server or the IP address of the user terminal.
  • the method further includes:
  • the target authoritative DNS server will randomly feedback One IP group among the at least one IP group.
  • the method further includes:
  • the target authoritative DNS server determines the authoritative DNS server corresponding to the CNAME domain name according to the authoritative DNS server record, otherwise recursively Iteratively query the authoritative DNS server corresponding to the CNAME domain name.
  • the ratio of the total probability that the IP address of the CDN node of each CDN service provider in all IP groups is selected satisfies the traffic pulling ratio of the target domain name.
  • an apparatus for controlling a proportion of multiple CNAME traffic includes:
  • a determining module configured to receive an A record query request of a target domain name sent by a local DNS server, and determine all CNAME domain names according to a stored CNAME record of the target domain name;
  • An obtaining module configured to obtain an IP address corresponding to each CNAME domain name in all the CNAME domain names from an authoritative DNS server corresponding to all the CNAME domain names;
  • a combination module configured to combine all IP addresses corresponding to the CNAME domain name based on a preset traffic traction ratio of the target domain name to generate at least one IP group;
  • a feedback module is configured to randomly feed back one IP group of the at least one IP group to the local DNS server.
  • the A record query request of the target domain name carries the IP address of the local DNS server or the IP address of the user terminal;
  • the obtaining module is specifically configured to:
  • the authoritative DNS server receiving the CNAME domain name determines and feeds back the IP address corresponding to the CNAME domain name based on the IP address of the local DNS server or the IP address of the user terminal.
  • the A record query request of the target domain name carries the IP address of the local DNS server or the IP address of the user terminal;
  • the obtaining module is specifically configured to:
  • the target authoritative DNS server For each of the CNAME domain names, the target authoritative DNS server sends an A record synchronization request to the authoritative DNS server corresponding to the CNAME domain name;
  • the target authoritative DNS server receives all A records sent by the authoritative DNS server corresponding to the CNAME domain name
  • the target authoritative DNS server determines the IP address corresponding to the CNAME domain name in all the A records based on the IP address of the local DNS server or the IP address of the user terminal.
  • the feedback module is further configured to:
  • the determining module is further configured to:
  • the ratio of the total probability that the IP address of the CDN node of each CDN service provider in all IP groups is selected satisfies the traffic pulling ratio of the target domain name.
  • an authoritative DNS server includes a processor and a memory.
  • the memory stores at least one instruction, at least one program, code set, or instruction set.
  • the at least one instruction, The at least one piece of program, the code set or the instruction set is loaded and executed by the processor to implement the method for controlling the proportion of multiple CNAME traffic as described in the first aspect.
  • a computer-readable storage medium stores at least one instruction, at least one program, code set, or instruction set, the at least one instruction, the at least one program, and the code.
  • the set or instruction set is loaded and executed by the processor to implement the method of controlling the proportion of multiple CNAME traffic as described in the first aspect.
  • the target authoritative DNS server receives the A record query request of the target domain name sent by the local DNS server, and determines all CNAME domain names according to the stored CNAME records of the target domain name.
  • the target authoritative DNS server obtains authoritative DNS from all CNAME domain names.
  • the server obtains the IP address corresponding to each CNAME domain name in all CNAME domain names;
  • the target authoritative DNS server combines the IP addresses corresponding to all CNAME domain names based on a preset traffic traction ratio of the target domain name to generate at least one IP group;
  • the target authoritative DNS The server randomly feeds back one of the at least one IP group to the local DNS server. In this way, the authoritative DNS server feeds back the IP group to the local DNS server.
  • the IP group can contain CDN nodes of multiple CDN service providers. No matter whether the local DNS server caches time or later, the access traffic to the domain name can be based on the traffic.
  • the traction ratio is more balanced to the CDN nodes of different CDN service providers, so it can effectively alleviate the problems of high traffic load of CDN nodes in the prior art and large fluctuations in traffic of CDN nodes in a long time.
  • FIG. 1 is a schematic diagram of a network framework for controlling a proportion of multiple CNAME traffic according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for controlling a multi-CNAME traffic ratio according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of an apparatus for controlling a proportion of multiple CNAME traffic according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of an authoritative DNS server according to an embodiment of the present invention.
  • An embodiment of the present invention provides a method for controlling the proportion of multiple CNAME traffic.
  • the execution subject of the method can be an authoritative DNS server, and is implemented by other DNS servers in the DNS server system.
  • the authoritative DNS server can store a large number of A records and CNAME records corresponding to the domain name.
  • the authoritative DNS server can retrieve the corresponding A record from the local database or from other
  • the corresponding A record is obtained from the database of the authoritative DNS server, and the A record is fed back to the local DNS server.
  • the local DNS server can be used to receive the domain name access request of the user terminal, and then feedback the corresponding IP address to the user terminal based on the A record fed back by the authoritative DNS server.
  • the authoritative DNS server may include a processor, a memory, and a transceiver.
  • the processor may be used to perform the processing of controlling the proportion of multiple CNAME traffic in the following processes.
  • the memory may be used to store the data required during the processing and the data generated, such as CNAME Record, A record, etc.
  • the transceiver can be used to receive and send relevant data during processing, such as receiving A record query requests, and feedback IP groups.
  • Step 201 The target authoritative DNS server receives the A record query request of the target domain name sent by the local DNS server, and determines all CNAME domain names according to the stored CNAME records of the target domain name.
  • the domain name holder wants to accelerate the access to its own domain name (using the target domain name as an example) through the CDN system, it can choose multiple CDN service providers to provide network acceleration services for the target domain name, or After the domain name holder selects a CDN service provider, the CDN service provider can also distribute the accelerated business of the target domain name to other CDN service providers. In this way, multiple CDN service providers can jointly provide CDN acceleration services for the target domain name. Before providing the CDN acceleration service, each CDN service provider can assign the target domain name CNAME to a preset domain name provided for the CDN acceleration service, which is bound to the IP address of the CDN node of the CDN service provider.
  • each CDN service provider can set its own CNAME record in the target authoritative DNS server corresponding to the target domain name.
  • the CNAME record consists of the customer domain name and the CNAME domain name.
  • the customer domain name is the target domain name, and the CNAME domain name is used for the above.
  • the user may enter the target domain name on the user terminal, and then the user terminal may send the access request of the target domain name to the corresponding local DNS server according to a preset DNS server proxy.
  • the local DNS server can query whether the A record of the target domain name is stored in the local database. If it is stored, it can directly feedback the IP address corresponding to the target domain name in the A record to the user terminal. If it is not stored, the local The DNS server can determine the target authoritative DNS server corresponding to the target domain name, and then send an A record query request for the target domain name to the target authoritative DNS server.
  • the target authoritative DNS server can query the CNAME records of all the target domain names that the machine has stored, and then determine all the CNAME domain names corresponding to the target domain names in the CNAME record.
  • Step 202 The target authoritative DNS server obtains an IP address corresponding to each CNAME domain name in all CNAME domain names from the authoritative DNS servers corresponding to all CNAME domain names.
  • the target authoritative DNS server can determine the authoritative DNS server corresponding to each CNAME domain name, and then obtain the IP address corresponding to each CNAME domain name from these authoritative DNS servers. It can be understood that different CNAME domain names are provided by different CDN service providers, and each CNAME domain name corresponds to the IP address of multiple CDN nodes provided by the CDN service provider to provide target domain name access acceleration.
  • the A record query request of the target domain name may carry the IP address of the local DNS server or the IP address of the user terminal.
  • the processing in step 202 may be specifically as follows: For each CNAME domain name, the target authoritative DNS server sends The authoritative DNS server corresponding to the CNAME domain name sends an A record query request carrying the IP address of the local DNS server or the IP address of the user terminal; the target authoritative DNS server receives the authoritative DNS server corresponding to the CNAME domain name based on the IP address of the local DNS server or The IP address of the user terminal determines and feeds back the IP address corresponding to the CNAME domain name.
  • the A record query request of the target domain name sent by the target DNS server of the local DNS server may carry the IP address of the local DNS server or the IP address of the user terminal.
  • the target authoritative DNS server can send the IP address carrying the local DNS server to the authoritative DNS server corresponding to the CNAME domain name.
  • a record query request for the CNAME domain name After receiving the A record query request, the authoritative DNS server corresponding to the CNAME domain name can query the A records corresponding to all the CNAME domain names stored on the local machine, and then determine the A record corresponding to the local DNS server in these A records.
  • the IP addresses belong to the same network segment or the IP addresses of the CDN nodes that are physically close to the local DNS server, and then these IP addresses are fed back to the target authoritative DNS server.
  • the target authoritative DNS server can send an A record query request for the CNAME domain name carrying the IP address of the user terminal to the authoritative DNS server corresponding to the CNAME domain name.
  • the authoritative DNS server corresponding to the CNAME domain name is receiving After querying A record query request, you can query all CNAME domain name pairs stored on this machine Corresponding A records, and then determine in these A records the IP addresses of the CDN nodes that belong to the same network segment as the user terminal or are physically close to the user terminal, and then return these IP addresses to the target authoritative DNS server. In this way, the target authoritative DNS server can receive the IP address corresponding to the CNAME domain name returned by the authoritative DNS server corresponding to the CNAME domain name.
  • the target authoritative DNS server can obtain the IP address corresponding to each CNAME domain name by synchronizing the A record database.
  • the processing in step 202 can be as follows: For each CNAME domain name, the target authoritative DNS server sends the CNAME to the CNAME. The authoritative DNS server corresponding to the domain name sends an A record synchronization request; the target authoritative DNS server receives all A records sent by the authoritative DNS server corresponding to the CNAME domain name; the target authoritative DNS server is based on the IP address of the local DNS server or the IP address of the user terminal in all A The IP address corresponding to the CNAME domain name is determined in the record.
  • the target authoritative DNS server may send an A record synchronization request to the authoritative DNS server corresponding to the CNAME domain name.
  • the authoritative DNS server corresponding to the CNAME domain name can return all A records in the A record database maintained by the machine to the target authoritative DNS server. In this way, after the target authoritative DNS server receives these A records, if the A record query request in step 201 carries the IP address of the local DNS server, it can be determined in all the above A records that the IP address of the local DNS server belongs to the same network.
  • step 202 it may further include the following processing: For each CNAME domain name, if the machine has stored the authoritative DNS server record of the CNAME domain name, the target authoritative DNS server determines the corresponding CNAME domain name according to the authoritative DNS server record. Authoritative DNS server, otherwise recursively / iteratively query the authoritative DNS server corresponding to the CNAME domain name.
  • the target authoritative DNS server determines all the CNAME domain names corresponding to the target domain name, for each CNAME domain name, it can find whether the machine has stored the authoritative DNS server records of the CNAME domain name. If it has been stored, the target authoritative DNS server The authoritative DNS server corresponding to the CNAME domain name can be determined according to the authoritative DNS server records. If it is not stored, the target authoritative DNS server can recursively / iteratively query the authoritative DNS server corresponding to the CNAME domain name.
  • Step 203 The target authoritative DNS server combines the IP addresses corresponding to all CNAME domain names based on a preset traffic pull ratio of the target domain name to generate at least one IP group.
  • each CDN service provider when each CDN service provider sets its own CNAME record in the target authoritative DNS server, it can also set the proportion of the traffic carried by the access traffic of the target domain name, which can be embodied by the proportion of traffic traction.
  • the target authoritative DNS server can call the preset traffic pull ratio of the target domain name, and then combine the IP addresses corresponding to all CNAME domain names according to the traffic pull ratio, thereby Generate at least one IP group, and each IP group may include IP addresses corresponding to different CNAME domain names.
  • the ratio of the total probability that the IP address of the CDN node of each CDN service provider in all IP groups is selected satisfies the traffic pulling ratio of the target domain name.
  • the authoritative DNS server can combine the IP addresses based on the following rules:
  • Each IP group contains the IP addresses of the CDN nodes of as many CDN service providers as possible;
  • the authoritative DNS server may cache the IP group for a period of time. Accordingly, after step 203, the following processing may be performed: within the preset A record cache duration of the target domain name, if it is carried again
  • the A record query request has the IP address of the local DNS server or the IP address of the user terminal, and the target authoritative DNS server randomly feeds back one of the at least one IP group.
  • the target authoritative DNS server may cache the IP group for a period of time (that is, the preset A record cache duration of the target domain name). During the cache time, if an A record query request carrying the IP address of the local DNS server or the IP address of the user terminal is received again, the target authoritative DNS server may randomly select an IP group from at least one IP group and send a request to A The sender of the record query request feeds back the IP group. It can be understood that the A record query request here may be sent by the above-mentioned local DNS server, or may be sent by other DNS servers.
  • Step 204 The target authoritative DNS server randomly feeds back one IP group of the at least one IP group to the local DNS server.
  • the target authoritative DNS server after the target authoritative DNS server generates at least one IP group, it can randomly select an IP group from the at least one IP group, and then feed back the IP group to the local DNS server. After that, the local DNS server can rearrange all the IPs in the IP group returned by the target authoritative DNS server in a random order, and then forward the rearranged IP group to the user terminal. In this way, after receiving the above-mentioned IP group, the user terminal can randomly select an IP address in the IP group, and then implement access to the target domain name based on the IP address.
  • steps 201 to 204 are described below by way of example:
  • the target domain name is www.XXX.com
  • two CDN service providers provide CDN acceleration services.
  • the CNAME domain names provided by the two CDN service providers are: www.a.com and www.b.com, of which www.a. The com and www.b.com traffic pull ratio is 4: 1;
  • the user terminal requests access to http://www.XXX.com/;
  • the local DNS server receives the access request and queries the A record of www.XXX.com locally. If there is, it returns the IP in the A record. If not, it queries the authoritative DNS server of XXX.com recursively / iteratively.
  • the local DNS server sends the A record query request of www.XXX.com to the authoritative DNS server of XXX.com;
  • XXX.com's authoritative DNS server receives the A record query request, finds the CNAME domain name: www.a.com and www.b.com, and the traffic pull ratio is 4: 1;
  • XXX.com's authoritative DNS server recursively / iteratively queries the a.com's NS and b.com's authoritative DNS server;
  • XXX.com's authoritative DNS server sends a request to a.com's authoritative DNS server to query the A record of www.a.com;
  • the authoritative DNS server of a.com After receiving the request, the authoritative DNS server of a.com responds with an A record (ip1, ip2, ip3, ip4);
  • XXX.com's authoritative DNS server initiates a request to b.com's authoritative DNS server to query the A record of www.b.com;
  • b.om's authoritative DNS server After receiving the request, b.om's authoritative DNS server responds with an A record (ip5, ip6);
  • XXX.com's authoritative DNS server receives (ip1, ip2, ip3, ip4) and (ip1, ip2, ip3, ip4) and presses 4: 1 to generate an IP group: (ip1, ip2, ip3, ip4, ip5) and (ip1, ip2, ip3, ip4, ip6);
  • the authoritative DNS server of XXX.com randomly selects an IP group to feed back the request to the local DNS server.
  • the target authoritative DNS server receives the A record query request of the target domain name sent by the local DNS server, and determines all CNAME domain names according to the stored CNAME records of the target domain name.
  • the target authoritative DNS server obtains the authoritative DNS from all CNAME domain names.
  • the server obtains the IP address corresponding to each CNAME domain name in all CNAME domain names;
  • the target authoritative DNS server combines the IP addresses corresponding to all CNAME domain names based on a preset traffic traction ratio of the target domain name to generate at least one IP group;
  • the target authoritative DNS The server randomly feeds back one of the at least one IP group to the local DNS server. In this way, the authoritative DNS server feeds back the IP group to the local DNS server.
  • the IP group can contain CDN nodes of multiple CDN service providers. No matter whether the local DNS server caches time or later, the access traffic to the domain name can be based on the traffic.
  • the traction ratio is more balanced to the CDN nodes of different CDN service providers, so it can effectively alleviate the problems of high traffic load of CDN nodes in the prior art and large fluctuations in traffic of CDN nodes in a long time.
  • an embodiment of the present invention further provides a device for controlling the proportion of multiple CNAME traffic. As shown in FIG. 3, the device includes
  • a determining module 301 configured to receive an A record query request of a target domain name sent by a local DNS server, and determine all CNAME domain names according to a stored CNAME record of the target domain name;
  • An obtaining module 302 configured to obtain an IP address corresponding to each CNAME domain name in all the CNAME domain names from an authoritative DNS server corresponding to the all CNAME domain names;
  • a combining module 303 configured to combine the IP addresses corresponding to all the CNAME domain names based on a preset traffic traction ratio of the target domain name to generate at least one IP group;
  • the feedback module 304 is configured to randomly feed back one IP group of the at least one IP group to the local DNS server.
  • the A record query request of the target domain name carries the IP address of the local DNS server or the IP address of the user terminal;
  • the obtaining module 302 is specifically configured to:
  • the authoritative DNS server receiving the CNAME domain name determines and feeds back the IP address corresponding to the CNAME domain name based on the IP address of the local DNS server or the IP address of the user terminal.
  • the A record query request of the target domain name carries the IP address of the local DNS server or the IP address of the user terminal;
  • the obtaining module 302 is specifically configured to:
  • the target authoritative DNS server For each of the CNAME domain names, the target authoritative DNS server sends an A record synchronization request to the authoritative DNS server corresponding to the CNAME domain name;
  • the target authoritative DNS server receives all A records sent by the authoritative DNS server corresponding to the CNAME domain name
  • the target authoritative DNS server determines the IP address corresponding to the CNAME domain name in all the A records based on the IP address of the local DNS server or the IP address of the user terminal.
  • the feedback module 304 is further configured to:
  • the determining module 301 is further configured to:
  • the ratio of the total probability that the IP address of the CDN node of each CDN service provider in all IP groups is selected satisfies the traffic pulling ratio of the target domain name.
  • the target authoritative DNS server receives the A record query request of the target domain name sent by the local DNS server, and determines all CNAME domain names according to the stored CNAME records of the target domain name.
  • the target authoritative DNS server obtains the authoritative DNS from all CNAME domain names.
  • the server obtains the IP address corresponding to each CNAME domain name in all CNAME domain names;
  • the target authoritative DNS server combines the IP addresses corresponding to all CNAME domain names based on a preset traffic traction ratio of the target domain name to generate at least one IP group;
  • the target authoritative DNS The server randomly feeds back one of the at least one IP group to the local DNS server. In this way, the authoritative DNS server feeds back the IP group to the local DNS server.
  • the IP group can contain CDN nodes of multiple CDN service providers. No matter whether the local DNS server caches time or later, the access traffic to the domain name can be based on the traffic.
  • the traction ratio is more balanced to the CDN nodes of different CDN service providers, so it can effectively alleviate the problems of high traffic load of CDN nodes in the prior art and large fluctuations in traffic of CDN nodes in a long time.
  • the device for controlling the proportion of multi-CNAME traffic when controlling the proportion of multi-CNAME traffic, is described by taking only the division of each functional module as an example. In actual applications, the above functions may be allocated according to needs. Different functional modules are completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the device for controlling the proportion of multiple CNAME traffic provided by the above embodiments and the method embodiment for controlling the proportion of multiple CNAME traffic belong to the same concept. For the detailed implementation process, see the method embodiment, which will not be repeated here.
  • FIG. 4 is a schematic structural diagram of an authoritative DNS server according to an embodiment of the present invention.
  • the authoritative DNS server 400 may have relatively large differences due to different configurations or performance, and may include one or more central processing units 422 (for example, one or more processors) and storage 432, and one or more storage applications 442. Or the storage medium 430 of the data 444 (for example, one or one storage device in Shanghai).
  • the memory 432 and the storage medium 430 may be transient storage or persistent storage.
  • the program stored in the storage medium 430 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the cache server.
  • the central processing unit 422 may be configured to communicate with the storage medium 430, and execute a series of instruction operations in the storage medium 430 on the authoritative DNS server 400.
  • the authoritative DNS server 400 may also include one or more power sources 426, one or more wired or wireless network interfaces 450, one or more input-output interfaces 458, one or more keyboards 456, and / or, one or more operations System 441, such as Windows Server, Mac OS XTM, Unix, Linux, FreeBSD, etc.
  • the authoritative DNS server 400 may include a memory, and one or more programs, one or more programs stored in the memory, and configured to be executed by one or more processors.
  • the one or more programs include Perform the above instructions to control the proportion of multiple CNAME traffic.
  • the program may be stored in a computer-readable storage medium.
  • the storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种控制多CNAME流量比例的方法和装置，属于域名解析技术领域。所述方法包括：目标权威DNS服务器接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的所述目标域名的CNAME记录确定所有CNAME域名；目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址；目标权威DNS服务器基于预设的所述目标域名的流量牵引比例对所有所述CNAME域名对应的IP地址进行组合，生成至少一个IP组；目标权威DNS服务器向所述本地DNS服务器随机反馈所述至少一个IP组中的一个IP组。

Description

一种控制多CNAME流量比例的方法和装置 技术领域
本发明涉及域名解析技术领域，特别涉及一种控制多CNAME流量比例的方法和装置。
背景技术
目前CDN服务商众多，可能存在多家CDN服务商共同为一个客户提供CDN加速服务的情况。从带宽承受上限及成本考虑，客户和CDN服务商都存在对各CDN服务商承载的带宽比例进行控制的需求。
客户或者CDN服务商可以预先在客户域名的权威DNS服务器处进行配置，使用多条CNAME(可称为别名)记录(CNAME记录的形式可以为客户域名和CNAME域名的对应关系)，配置不同的流量牵引比例来牵引对于客户域名的访问流量。例如，权威DNS服务器处存在针对客户域名www.XXX.com的两条CNAME记录：M和N，且对应的流量牵引比例为4:1，这样，权威DNS服务器在接到本地DNS服务器的A记录查询请求后，可以按照4:1的概率选取CNAME记录，并将其反馈给本地DNS服务器。这样，本地DNS服务器可以再从CNAME记录指向的权威DNS服务器处获取为客户域名提供加速服务的CDN节点的访问IP。
在实现本发明的过程中，发明人发现现有技术至少存在以下问题：
本地DNS服务器在获取到CDN节点的访问IP后，会对该访问IP缓存一定时间。在缓存时间内，本地DNS服务器会将其服务范围内对于客户域名的所有访问流量都牵引至CDN节点，而无任何访问流量到达其它CDN服务商的CDN节点。进一步，在缓存时间过后，如果权威DNS服务器反馈了不同CDN服务商的CDN节点的访问IP，本地DNS服务器又会将其服务范围内对于客户域名的所有访问流量都牵引至这个CDN节点，之前的CDN节点上的访问流量将变为0。故而，短时间内CDN节点的流量负载较高，长时间内CDN节点的流量波动较大。
发明内容
为了解决现有技术的问题，本发明实施例提供了一种控制多CNAME流量比例的方法和装置。所述技术方案如下：
第一方面，提供了一种控制多CNAME流量比例的方法，所述方法包括：
目标权威DNS服务器接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的所述目标域名的CNAME记录确定所有CNAME域名；
目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址；
目标权威DNS服务器基于预设的所述目标域名的流量牵引比例对所有所述CNAME域名对应的IP地址进行组合，生成至少一个IP组；
目标权威DNS服务器向所述本地DNS服务器随机反馈所述至少一个IP组中的一个IP组。
可选的，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
所述目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址，包括：
针对每个所述CNAME域名，目标权威DNS服务器向所述CNAME域名对应的权威DNS服务器发送携带有所述本地DNS服务器的IP地址或用户终端的IP地址的所述CNAME域名的A记录查询请求；
目标权威DNS服务器接收所述CNAME域名对应的权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址确定并反馈的所述CNAME域名对应的IP地址。
可选的，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
所述目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址，包括：
针对每个所述CNAME域名，目标权威DNS服务器向所述CNAME域名对应的权威DNS服务器发送A记录同步请求；
目标权威DNS服务器接收所述CNAME域名对应的权威DNS服务器发送 的所有A记录；
目标权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址在所述所有A记录中确定所述CNAME域名对应的IP地址。
可选的，所述生成至少一个IP组之后，还包括：
在预设的所述目标域名的A记录缓存时长内，如果再次接收到携带有所述本地DNS服务器的IP地址或所述用户终端的IP地址的A记录查询请求，目标权威DNS服务器则随机反馈所述至少一个IP组中的一个IP组。
可选的，所述目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址之前，还包括：
对于每个所述CNAME域名，如果本机已存储有所述CNAME域名的权威DNS服务器记录，目标权威DNS服务器则根据所述权威DNS服务器记录确定所述CNAME域名对应的权威DNS服务器，否则递归/迭代查询所述CNAME域名对应的权威DNS服务器。
可选的，所有IP组中各CDN服务商的CDN节点的IP地址被选总概率之比满足所述目标域名的流量牵引比例。
第二方面，提供了一种控制多CNAME流量比例的装置，所述装置包括：
确定模块，用于接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的所述目标域名的CNAME记录确定所有CNAME域名；
获取模块，用于从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址；
组合模块，用于基于预设的所述目标域名的流量牵引比例对所有所述CNAME域名对应的IP地址进行组合，生成至少一个IP组；
反馈模块，用于向所述本地DNS服务器随机反馈所述至少一个IP组中的一个IP组。
可选的，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
所述获取模块，具体用于：
针对每个所述CNAME域名，向所述CNAME域名对应的权威DNS服务器 发送携带有所述本地DNS服务器的IP地址或用户终端的IP地址的所述CNAME域名的A记录查询请求；
接收所述CNAME域名对应的权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址确定并反馈的所述CNAME域名对应的IP地址。
可选的，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
所述获取模块，具体用于：
针对每个所述CNAME域名，目标权威DNS服务器向所述CNAME域名对应的权威DNS服务器发送A记录同步请求；
目标权威DNS服务器接收所述CNAME域名对应的权威DNS服务器发送的所有A记录；
目标权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址在所述所有A记录中确定所述CNAME域名对应的IP地址。
可选的，所述反馈模块，还用于：
在预设的所述目标域名的A记录缓存时长内，如果再次接收到携带有所述本地DNS服务器的IP地址或所述用户终端的IP地址的A记录查询请求，则随机反馈所述至少一个IP组中的一个IP组。
可选的，所述确定模块，还用于：
对于每个所述CNAME域名，如果本机已存储有所述CNAME域名的权威DNS服务器记录，则根据所述权威DNS服务器记录确定所述CNAME域名对应的权威DNS服务器，否则递归/迭代查询所述CNAME域名对应的权威DNS服务器。
可选的，所有IP组中各CDN服务商的CDN节点的IP地址被选总概率之比满足所述目标域名的流量牵引比例。
第三方面，提供了一种权威DNS服务器，所述权威DNS服务器包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如第一方面所述的控制多CNAME流量比例的方法。
第四方面，提供了一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如第一方面所述的控制多CNAME流量比例的方法。
本发明实施例提供的技术方案带来的有益效果是：
本发明实施例中，目标权威DNS服务器接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的目标域名的CNAME记录确定所有CNAME域名；目标权威DNS服务器从所有CNAME域名对应的权威DNS服务器处获取所有CNAME域名中每个CNAME域名对应的IP地址；目标权威DNS服务器基于预设的目标域名的流量牵引比例对所有CNAME域名对应的IP地址进行组合，生成至少一个IP组；目标权威DNS服务器向本地DNS服务器随机反馈至少一个IP组中的一个IP组。这样，权威DNS服务器向本地DNS服务器反馈IP组，IP组中可以包含有多个CDN服务商的CDN节点，无论在本地DNS服务器的缓存时间之内还是之后，对于域名的访问流量都可以按照流量牵引比例较为均衡地牵引至不同的CDN服务商的CDN节点，故而可以有效缓解现有技术中短时间内CDN节点的流量负载较高，长时间内CDN节点的流量波动较大的问题。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例提供的一种控制多CNAME流量比例的网络框架示意图；
图2是本发明实施例提供的一种控制多CNAME流量比例的方法流程图；
图3是本发明实施例提供的一种控制多CNAME流量比例的装置结构示意图；
图4是本发明实施例提供的一种权威DNS服务器的结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
本发明实施例提供了一种控制多CNAME流量比例的方法，该方法的执行主体可以权威DNS服务器，并由DNS服务器***中的其它DNS服务器辅助实现。权威DNS服务器可以存储有大量域名对应的A记录和CNAME记录，在需要向本地DNS服务器反馈某个域名对应的A记录时，权威DNS服务器可以从本地数据库中调取相应的A记录，或者从其它权威DNS服务器的数据库中获取相应的A记录，再将A记录反馈给本地DNS服务器。本地DNS服务器可以用于接收用户终端的域名访问请求，然后基于权威DNS服务器反馈的A记录向用户终端反馈相应的IP地址。具体的网络框架可以如图1所示。权威DNS服务器可以包括处理器、存储器、收发器，处理器可以用于进行下述流程中对于控制多CNAME流量比例的处理，存储器可以用于存储处理过程中需要的数据以及产生的数据，如CNAME记录、A记录等，收发器可以用于接收和发送处理过程中的相关数据，如用于接收A记录查询请求，反馈IP组等。
下面将结合具体实施方式，对图2所示的处理流程进行详细的说明，内容可以如下：
步骤201，目标权威DNS服务器接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的目标域名的CNAME记录确定所有CNAME域名。
在实施中，域名持有者如果想要通过CDN***来实现对自身域名(以目标域名为例进行说明)的访问加速，可以选择多家CDN服务商来提供对于目标域名的网络加速服务，或者，域名持有者在选择了一家CDN服务商后，该CDN服务商也可以将目标域名的加速业务分给其他CDN服务商，这样，多家CDN服务商可以共同为目标域名提供CDN加速服务。在提供CDN加速服务之前，每家CDN服务商可以将目标域名CNAME至各自预设的、用于提供CDN加速服务的指定域名，该指定域名与CDN服务商的CDN节点的IP地址绑定。之后每家CDN服务商均可以在目标域名对应的目标权威DNS服务器中分别设置各自的CNAME记录，该CNAME记录由客户域名和CNAME域名构成，客户域名即为目标域名，CNAME域名即为上述用于提供CDN加速服务的指定域名。
这样，当用户想要访问上述目标域名时，可以在用户终端上输入目标域名，然后用户终端可以按照预设的DNS服务器代理将目标域名的访问请求发送到相应的本地DNS服务器处。本地DNS服务器在接收到该访问请求后，可以查询本地数据库中是否存储有目标域名的A记录，如果存储，则可以直接向用户终端反馈A记录中目标域名对应的IP地址，如果未存储，本地DNS服务器则可以确定目标域名对应的目标权威DNS服务器，然后向目标权威DNS服务器发送目标域名的A记录查询请求。目标权威DNS服务器在接收到上述A记录查询请求之后，可以查询本机已存储的所有目标域名的CNAME记录，然后确定CNAME记录中的目标域名对应的所有CNAME域名。
步骤202，目标权威DNS服务器从所有CNAME域名对应的权威DNS服务器处获取所有CNAME域名中每个CNAME域名对应的IP地址。
在实施中，目标权威DNS服务器在确定了目标域名对应的所有CNAME域名之后，可以确定每个CNAME域名对应的权威DNS服务器，然后从这些权威DNS服务器处获取每个CNAME域名对应的IP地址。可以理解，不同的CNAME域名均是由不同的CDN服务商提供的，每个CNAME域名均对应CDN服务商提供的用于提供目标域名访问加速的多个CDN节点的IP地址。
可选的，目标域名的A记录查询请求中可以携带有本地DNS服务器的IP地址或用户终端的IP地址，相应的，步骤202的处理可以具体如下：针对每个CNAME域名，目标权威DNS服务器向CNAME域名对应的权威DNS服务器发送携带有本地DNS服务器的IP地址或用户终端的IP地址CNAME域名的A记录查询请求；目标权威DNS服务器接收CNAME域名对应的权威DNS服务器基于本地DNS服务器的IP地址或用户终端的IP地址确定并反馈的CNAME域名对应的IP地址。
在实施中，基于本地DNS服务器的设置不同，本地DNS服务器目标权威DNS服务器发送的目标域名的A记录查询请求中可以携带有本地DNS服务器的IP地址或用户终端的IP地址。一种情况下，如果A记录查询请求携带的是本地DNS服务器的IP地址，则针对每个CNAME域名，目标权威DNS服务器可以向CNAME域名对应的权威DNS服务器发送携带有本地DNS服务器的IP地址的CNAME域名的A记录查询请求，CNAME域名对应的权威DNS服务器在接收到A记录查询请求后，可以查询本机存储的所有CNAME域名对应的A 记录，然后在这些A记录中确定与本地DNS服务器的IP地址属于同一网段或者与本地DNS服务器物理距离较近的CDN节点的IP地址，再将这些IP地址反馈给目标权威DNS服务器；另一种情况下，如果A记录查询请求携带的是用户终端的IP地址，则针对每个CNAME域名，目标权威DNS服务器可以向CNAME域名对应的权威DNS服务器发送携带有用户终端的IP地址的CNAME域名的A记录查询请求，CNAME域名对应的权威DNS服务器在接收到A记录查询请求后，可以查询本机存储的所有CNAME域名对应的A记录，然后在这些A记录中确定与用户终端的IP地址属于同一网段或者与用户终端物理距离较近的CDN节点的IP地址，再将这些IP地址反馈给目标权威DNS服务器。这样，目标权威DNS服务器可以接收CNAME域名对应的权威DNS服务器反馈的CNAME域名对应的IP地址。
可选的，目标权威DNS服务器可以通过同步A记录数据库的方式来获取每个CNAME域名对应的IP地址，相应的，步骤202的处理可以具体如下：针对每个CNAME域名，目标权威DNS服务器向CNAME域名对应的权威DNS服务器发送A记录同步请求；目标权威DNS服务器接收CNAME域名对应的权威DNS服务器发送的所有A记录；目标权威DNS服务器基于本地DNS服务器的IP地址或用户终端的IP地址在所有A记录中确定CNAME域名对应的IP地址。
在实施中，针对每个CNAME域名，目标权威DNS服务器可以向CNAME域名对应的权威DNS服务器发送A记录同步请求。CNAME域名对应的权威DNS服务器在接收到A记录同步请求后，可以将本机维护的A记录数据库中所有A记录反馈给目标权威DNS服务器。这样，目标权威DNS服务器接收这些A记录后，如果步骤201中的A记录查询请求携带的是本地DNS服务器的IP地址，则可以在上述所有A记录中确定与本地DNS服务器的IP地址属于同一网段或者与本地DNS服务器物理距离较近的CDN节点的IP地址；如果步骤201中的A记录查询请求携带的是用户终端的IP地址，则可以在上述所有A记录中确定与用户终端的IP地址属于同一网段或者与用户终端物理距离较近的CDN节点的IP地址。
可选的，在步骤202之前，还可以包括如下处理：对于每个CNAME域名，如果本机已存储有CNAME域名的权威DNS服务器记录，目标权威DNS服务器则根据权威DNS服务器记录确定CNAME域名对应的权威DNS服务器，否 则递归/迭代查询CNAME域名对应的权威DNS服务器。
在实施中，目标权威DNS服务器在确定了目标域名对应的所有CNAME域名之后，可以对于每个CNAME域名，查找本机是否已存储有CNAME域名的权威DNS服务器记录，如果已存储，目标权威DNS服务器则可以根据权威DNS服务器记录确定CNAME域名对应的权威DNS服务器，如果未存储，目标权威DNS服务器则可以递归/迭代查询CNAME域名对应的权威DNS服务器。
步骤203，目标权威DNS服务器基于预设的目标域名的流量牵引比例对所有CNAME域名对应的IP地址进行组合，生成至少一个IP组。
在实施中，每家CDN服务商在目标权威DNS服务器中分别设置各自的CNAME记录时，还可以设置有对于目标域名的访问流量各自承载的流量比例，具体可以通过流量牵引比例来体现。这样，目标权威DNS服务器在获取到所有CNAME域名对应的IP地址后，可以调取上述预设的目标域名的流量牵引比例，然后根据该流量牵引比例对所有CNAME域名对应的IP地址进行组合，从而生成至少一个IP组，每个IP组中可以包括不同CNAME域名对应的IP地址。
可选的，所有IP组中各CDN服务商的CDN节点的IP地址被选总概率之比满足目标域名的流量牵引比例。
在实施中，权威DNS服务器在获取到上述所有CNAME域名对应的IP地址后，可以基于以下几点规则对IP地址进行组合：
1.各IP组的被选概率完全一致；
2.每个IP组中各IP地址的被选概率完全一致；
3.每个IP组中不能存在相同的IP地址；
4.每个IP组中包含尽量多家CDN服务商的CDN节点的IP地址；
5.所有IP组中各CDN服务商的CDN节点的IP地址被选总概率之比满足
目标域名的流量牵引比例。
可选的，权威DNS服务器在生成IP组后，可以将IP组缓存一段时间，相应的，步骤203之后可以有如下处理：在预设的目标域名的A记录缓存时长内，如果再次接收到携带有本地DNS服务器的IP地址或用户终端的IP地址的A记录查询请求，目标权威DNS服务器则随机反馈至少一个IP组中的一个IP组。
在实施中，目标权威DNS服务器在生成至少一个IP组之后，可以将IP组缓存一段时间(即预设的目标域名的A记录缓存时长)。在缓存时间内，如果再 次接收到携带有本地DNS服务器的IP地址或用户终端的IP地址的A记录查询请求，目标权威DNS服务器则可以在至少一个IP组中随机选择一个IP组，并向A记录查询请求的发送端反馈该IP组。可以理解，此处的A记录查询请求可以是由上述本地DNS服务器发送的，也可以是由其它DNS服务器发送的。
步骤204，目标权威DNS服务器向本地DNS服务器随机反馈至少一个IP组中的一个IP组。
在实施中，目标权威DNS服务器在生成至少一个IP组之后，可以在至少一个IP组中随机挑选一个IP组，然后将该IP组反馈给本地DNS服务器。之后，本地DNS服务器可以将目标权威DNS服务器反馈的IP组内所有IP按照随机顺序进行重新排列，再将重新排列后的IP组转发给用户终端。这样，用户终端在接收到上述IP组后，可以在IP组内随机选择一个IP地址，然后基于该IP地址实现目标域名的访问。
为了便于理解，以下通过举例的方式对步骤201至步骤204的处理流程进行说明：
假设目标域名为www.XXX.com，由两家CDN服务商提供CDN加速服务，两家CDN服务商提供的CNAME域名分别为：www.a.com和www.b.com，其中www.a.com和www.b.com的流量牵引比例为4：1；
用户终端请求访问http://www.XXX.com/；
本地DNS服务器接收访问请求，在本机查询www.XXX.com的A记录，如果有，则反馈A记录中的IP，如果没有，则递归/迭代查询XXX.com的权威DNS服务器；
本地DNS服务器向XXX.com的权威DNS服务器发送www.XXX.com的A记录查询请求；
XXX.com的权威DNS服务器接收A记录查询请求，查找到CNAME域名：www.a.com和www.b.com，且流量牵引比例为4：1；
XXX.com的权威DNS服务器递归/迭代查询a.com的NS和b.com的权威DNS服务器；
XXX.com的权威DNS服务器向a.com的权威DNS服务器发送请求，查询www.a.com的A记录；
a.com的权威DNS服务器收到请求后，响应出A记录(ip1，ip2，ip3，ip4)；
XXX.com的权威DNS服务器向b.com的权威DNS服务器发起请求，查询www.b.com的A记录；
b.om的权威DNS服务器收到请求后，响应出A记录(ip5，ip6)；
XXX.com的权威DNS服务器收到(ip1，ip2，ip3，ip4)和(ip1，ip2，ip3，ip4)，按4：1，生成IP组：(ip1，ip2，ip3，ip4，ip5)和(ip1，ip2，ip3，ip4，ip6)；
XXX.com的权威DNS服务器随机挑选一个IP组反馈给本地DNS服务器的请求。
本发明实施例中，目标权威DNS服务器接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的目标域名的CNAME记录确定所有CNAME域名；目标权威DNS服务器从所有CNAME域名对应的权威DNS服务器处获取所有CNAME域名中每个CNAME域名对应的IP地址；目标权威DNS服务器基于预设的目标域名的流量牵引比例对所有CNAME域名对应的IP地址进行组合，生成至少一个IP组；目标权威DNS服务器向本地DNS服务器随机反馈至少一个IP组中的一个IP组。这样，权威DNS服务器向本地DNS服务器反馈IP组，IP组中可以包含有多个CDN服务商的CDN节点，无论在本地DNS服务器的缓存时间之内还是之后，对于域名的访问流量都可以按照流量牵引比例较为均衡地牵引至不同的CDN服务商的CDN节点，故而可以有效缓解现有技术中短时间内CDN节点的流量负载较高，长时间内CDN节点的流量波动较大的问题。
基于相同的技术构思，本发明实施例还提供了一种控制多CNAME流量比例的装置，如图3所示，所述装置包括
确定模块301，用于接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的所述目标域名的CNAME记录确定所有CNAME域名；
获取模块302，用于从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址；
组合模块303，用于基于预设的所述目标域名的流量牵引比例对所有所述CNAME域名对应的IP地址进行组合，生成至少一个IP组；
反馈模块304，用于向所述本地DNS服务器随机反馈所述至少一个IP组中的一个IP组。
可选的，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
所述获取模块302，具体用于：
针对每个所述CNAME域名，向所述CNAME域名对应的权威DNS服务器发送携带有所述本地DNS服务器的IP地址或用户终端的IP地址的所述CNAME域名的A记录查询请求；
接收所述CNAME域名对应的权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址确定并反馈的所述CNAME域名对应的IP地址。
可选的，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
所述获取模块302，具体用于：
针对每个所述CNAME域名，目标权威DNS服务器向所述CNAME域名对应的权威DNS服务器发送A记录同步请求；
目标权威DNS服务器接收所述CNAME域名对应的权威DNS服务器发送的所有A记录；
目标权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址在所述所有A记录中确定所述CNAME域名对应的IP地址。
可选的，所述反馈模块304，还用于：
在预设的所述目标域名的A记录缓存时长内，如果再次接收到携带有所述本地DNS服务器的IP地址或所述用户终端的IP地址的A记录查询请求，则随机反馈所述至少一个IP组中的一个IP组。
可选的，所述确定模块301，还用于：
对于每个所述CNAME域名，如果本机已存储有所述CNAME域名的权威DNS服务器记录，则根据所述权威DNS服务器记录确定所述CNAME域名对应的权威DNS服务器，否则递归/迭代查询所述CNAME域名对应的权威DNS服务器。
可选的，所有IP组中各CDN服务商的CDN节点的IP地址被选总概率之比满足所述目标域名的流量牵引比例。
本发明实施例中，目标权威DNS服务器接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的目标域名的CNAME记录确定所有CNAME域名；目标权威DNS服务器从所有CNAME域名对应的权威DNS服务器处获取所有CNAME域名中每个CNAME域名对应的IP地址；目标权威DNS服务器基于预设的目标域名的流量牵引比例对所有CNAME域名对应的IP地址进行组合，生成至少一个IP组；目标权威DNS服务器向本地DNS服务器随机反馈至少一个IP组中的一个IP组。这样，权威DNS服务器向本地DNS服务器反馈IP组，IP组中可以包含有多个CDN服务商的CDN节点，无论在本地DNS服务器的缓存时间之内还是之后，对于域名的访问流量都可以按照流量牵引比例较为均衡地牵引至不同的CDN服务商的CDN节点，故而可以有效缓解现有技术中短时间内CDN节点的流量负载较高，长时间内CDN节点的流量波动较大的问题。
需要说明的是：上述实施例提供的控制多CNAME流量比例的装置在控制多CNAME流量比例时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的控制多CNAME流量比例的装置与控制多CNAME流量比例的方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图4是本发明实施例提供的权威DNS服务器的结构示意图。该权威DNS服务器400可因配置或性能不同而产生比较大的差异，可以包括一个或一个以***处理器422(例如，一个或一个以上处理器)和存储器432，一个或一个以上存储应用程序442或数据444的存储介质430(例如一个或一个以上海量存储设备)。其中，存储器432和存储介质430可以是短暂存储或持久存储。存储在存储介质430的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对缓存服务器中的一系列指令操作。更进一步地，中央处理器422可以设置为与存储介质430通信，在权威DNS服务器400上执行存储介质430中的一系列指令操作。
权威DNS服务器400还可以包括一个或一个以上电源426，一个或一个以 上有线或无线网络接口450，一个或一个以上输入输出接口458，一个或一个以上键盘456，和/或，一个或一个以上操作***441，例如Windows Server，Mac OS XTM，Unix，Linux，FreeBSD等等。
权威DNS服务器400可以包括有存储器，以及一个或者一个以上的程序，其中一个或者一个以上程序存储于存储器中，且经配置以由一个或者一个以上处理器执行所述一个或者一个以上程序包含用于进行上述控制多CNAME流量比例的指令。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (14)

  1. 一种控制多CNAME流量比例的方法，其特征在于，所述方法包括：
    目标权威DNS服务器接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的所述目标域名的CNAME记录确定所有CNAME域名；
    目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址；
    目标权威DNS服务器基于预设的所述目标域名的流量牵引比例对所有所述CNAME域名对应的IP地址进行组合，生成至少一个IP组；
    目标权威DNS服务器向所述本地DNS服务器随机反馈所述至少一个IP组中的一个IP组。
  2. 根据权利要求1所述的方法，其特征在于，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
    所述目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址，包括：
    针对每个所述CNAME域名，目标权威DNS服务器向所述CNAME域名对应的权威DNS服务器发送携带有所述本地DNS服务器的IP地址或用户终端的IP地址的所述CNAME域名的A记录查询请求；
    目标权威DNS服务器接收所述CNAME域名对应的权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址确定并反馈的所述CNAME域名对应的IP地址。
  3. 根据权利要求1所述的方法，其特征在于，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
    所述目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址，包括：
    针对每个所述CNAME域名，目标权威DNS服务器向所述CNAME域名对应的权威DNS服务器发送A记录同步请求；
    目标权威DNS服务器接收所述CNAME域名对应的权威DNS服务器发送 的所有A记录；
    目标权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址在所述所有A记录中确定所述CNAME域名对应的IP地址。
  4. 根据权利要求2或3所述的方法，其特征在于，所述生成至少一个IP组之后，还包括：
    在预设的所述目标域名的A记录缓存时长内，如果再次接收到携带有所述本地DNS服务器的IP地址或所述用户终端的IP地址的A记录查询请求，目标权威DNS服务器则随机反馈所述至少一个IP组中的一个IP组。
  5. 根据权利要求1所述的方法，其特征在于，所述目标权威DNS服务器从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址之前，还包括：
    对于每个所述CNAME域名，如果本机已存储有所述CNAME域名的权威DNS服务器记录，目标权威DNS服务器则根据所述权威DNS服务器记录确定所述CNAME域名对应的权威DNS服务器，否则递归/迭代查询所述CNAME域名对应的权威DNS服务器。
  6. 根据权利要求1所述的方法，其特征在于，所有IP组中各CDN服务商的CDN节点的IP地址被选总概率之比满足所述目标域名的流量牵引比例。
  7. 一种控制多CNAME流量比例的装置，其特征在于，所述装置包括：
    确定模块，用于接收本地DNS服务器发送的目标域名的A记录查询请求，根据已存储的所述目标域名的CNAME记录确定所有CNAME域名；
    获取模块，用于从所述所有CNAME域名对应的权威DNS服务器处获取所述所有CNAME域名中每个CNAME域名对应的IP地址；
    组合模块，用于基于预设的所述目标域名的流量牵引比例对所有所述CNAME域名对应的IP地址进行组合，生成至少一个IP组；
    反馈模块，用于向所述本地DNS服务器随机反馈所述至少一个IP组中的一个IP组。
  8. 根据权利要求7所述的装置，其特征在于，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
    所述获取模块，具体用于：
    针对每个所述CNAME域名，向所述CNAME域名对应的权威DNS服务器发送携带有所述本地DNS服务器的IP地址或用户终端的IP地址的所述CNAME域名的A记录查询请求；
    接收所述CNAME域名对应的权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址确定并反馈的所述CNAME域名对应的IP地址。
  9. 根据权利要求7或8所述的装置，其特征在于，所述目标域名的A记录查询请求中携带有所述本地DNS服务器的IP地址或用户终端的IP地址；
    所述获取模块，具体用于：
    针对每个所述CNAME域名，目标权威DNS服务器向所述CNAME域名对应的权威DNS服务器发送A记录同步请求；
    目标权威DNS服务器接收所述CNAME域名对应的权威DNS服务器发送的所有A记录；
    目标权威DNS服务器基于所述本地DNS服务器的IP地址或用户终端的IP地址在所述所有A记录中确定所述CNAME域名对应的IP地址。
  10. 根据权利要求8所述的装置，其特征在于，所述反馈模块，还用于：
    在预设的所述目标域名的A记录缓存时长内，如果再次接收到携带有所述本地DNS服务器的IP地址或所述用户终端的IP地址的A记录查询请求，则随机反馈所述至少一个IP组中的一个IP组。
  11. 根据权利要求7所述的装置，其特征在于，所述确定模块，还用于：
    对于每个所述CNAME域名，如果本机已存储有所述CNAME域名的权威DNS服务器记录，则根据所述权威DNS服务器记录确定所述CNAME域名对应的权威DNS服务器，否则递归/迭代查询所述CNAME域名对应的权威DNS服务器。
  12. 根据权利要求7所述的装置，其特征在于，所有IP组中各CDN服务商的CDN节点的IP地址被选总概率之比满足所述目标域名的流量牵引比例。
  13. 一种权威DNS服务器，所述权威DNS服务器包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如权利要求1至6任一项所述的控制多CNAME流量比例的方法。
  14. 一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如权利要求1至6任一项所述的控制多CNAME流量比例的方法。
PCT/CN2018/107475 2018-06-13 2018-09-26 一种控制多cname流量比例的方法和装置 WO2019237557A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/485,549 US20210336920A1 (en) 2018-06-13 2018-09-26 Method and device for controlling ratio of multi-cname traffic
EP18922730.9A EP3800870A4 (en) 2018-06-13 2018-09-26 MULTI-CNAME TRAFFIC REPORT CONTROL PROCESS AND DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810610126.9A CN108900648B (zh) 2018-06-13 2018-06-13 一种控制多cname流量比例的方法和装置
CN201810610126.9 2018-06-13

Publications (1)

Publication Number Publication Date
WO2019237557A1 true WO2019237557A1 (zh) 2019-12-19

Family

ID=64344625

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107475 WO2019237557A1 (zh) 2018-06-13 2018-09-26 一种控制多cname流量比例的方法和装置

Country Status (4)

Country Link
US (1) US20210336920A1 (zh)
EP (1) EP3800870A4 (zh)
CN (1) CN108900648B (zh)
WO (1) WO2019237557A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111625359A (zh) * 2020-05-25 2020-09-04 北京金山云网络技术有限公司 用户的cdn用量的确定方法、装置和终端设备
CN111885216A (zh) * 2020-07-15 2020-11-03 北京青云科技股份有限公司 Dns查询方法、装置、设备和存储介质
CN112291343A (zh) * 2020-10-28 2021-01-29 成都知道创宇信息技术有限公司 信息获取方法、装置及电子设备
CN112738271A (zh) * 2021-01-08 2021-04-30 网宿科技股份有限公司 一种cdn质量的探测方法、***及域名服务器
CN115208766A (zh) * 2022-07-29 2022-10-18 天翼云科技有限公司 一种cdn带宽调度方法及相关装置
CN115442330A (zh) * 2022-08-05 2022-12-06 天翼云科技有限公司 一种域名解析***、方法及设备

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108900648B (zh) * 2018-06-13 2020-11-06 网宿科技股份有限公司 一种控制多cname流量比例的方法和装置
CN109818946B (zh) * 2019-01-11 2022-07-26 网宿科技股份有限公司 Ca证书申请和部署的方法和***
CN109936632B (zh) * 2019-03-07 2021-12-21 杭州又拍云科技有限公司 一种应用于dns权威服务器的cname加速方法
CN109889626A (zh) * 2019-03-20 2019-06-14 湖南快乐阳光互动娱乐传媒有限公司 获取ip地址和dns地址的对应关系的方法及装置、***
CN110557464A (zh) * 2019-09-05 2019-12-10 网宿科技股份有限公司 Dns解析方法、权威dns服务器和dns解析***
CN111478984B (zh) * 2020-03-17 2022-09-09 平安科技（深圳）有限公司 服务器ip地址获取方法、装置及计算机可读存储介质
CN111953802A (zh) * 2020-07-06 2020-11-17 网宿科技股份有限公司 一种域名的解析方法、***、设备及存储介质
CN112073409A (zh) * 2020-09-04 2020-12-11 杭州安恒信息技术股份有限公司 攻击流量清洗方法、装置、设备及计算机可读存储介质
CN112100477A (zh) * 2020-09-07 2020-12-18 北京视界云天科技有限公司 多云调度方法、装置、计算机设备和存储介质
CN112291339B (zh) * 2020-10-28 2022-09-23 平安科技（深圳）有限公司 基于云解析的全局负载均衡方法及***
CN112671866B (zh) * 2020-12-15 2022-11-25 牙木科技股份有限公司 Dns分流解析方法、dns服务器及计算机可读存储介质
CN114168945A (zh) * 2021-12-09 2022-03-11 绿盟科技集团股份有限公司 一种检测子域名潜在风险的方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100011120A1 (en) * 2002-08-07 2010-01-14 Foundry Networks, Inc. Canonical name (cname) handling for global server load balancing
CN105681491A (zh) * 2016-04-08 2016-06-15 网宿科技股份有限公司 一种域名解析加速方法、***和装置
CN106027695A (zh) * 2016-07-13 2016-10-12 成都知道创宇信息技术有限公司 一种获取递归dns所用ip的方法
CN106301966A (zh) * 2016-10-25 2017-01-04 北京云端智度科技有限公司 一种基于域名的按比例分配流量的方法
CN108900648A (zh) * 2018-06-13 2018-11-27 网宿科技股份有限公司 一种控制多cname流量比例的方法和装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6205489B1 (en) * 1999-01-05 2001-03-20 Whowhere, Inc. Method for providing an internet protocol address with a domain name server
US7860964B2 (en) * 2001-09-28 2010-12-28 Level 3 Communications, Llc Policy-based content delivery network selection
CN102014044B (zh) * 2009-09-04 2013-01-02 技嘉科技股份有限公司 一种网域冲突避免方法及运用该方法的路由器
US9992159B2 (en) * 2012-06-11 2018-06-05 Nec Corporation Communication information detecting device and communication information detecting method
CN104144222B (zh) * 2014-08-20 2015-08-19 北京阅联信息技术有限公司 Dns授权***中基于别名记录的负载均衡方法及***
CN107071078B (zh) * 2017-02-19 2019-05-10 网宿科技股份有限公司 域名解析***、域名解析服务器和域名解析方法
CN106790704B (zh) * 2017-02-27 2019-09-13 网宿科技股份有限公司 一种访问云存储文件的方法及***
CN107566279B (zh) * 2017-08-30 2020-06-02 四川易诚智讯科技有限公司 一种基于路由信息和Traceroute信息的路由器别名解析方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100011120A1 (en) * 2002-08-07 2010-01-14 Foundry Networks, Inc. Canonical name (cname) handling for global server load balancing
CN105681491A (zh) * 2016-04-08 2016-06-15 网宿科技股份有限公司 一种域名解析加速方法、***和装置
CN106027695A (zh) * 2016-07-13 2016-10-12 成都知道创宇信息技术有限公司 一种获取递归dns所用ip的方法
CN106301966A (zh) * 2016-10-25 2017-01-04 北京云端智度科技有限公司 一种基于域名的按比例分配流量的方法
CN108900648A (zh) * 2018-06-13 2018-11-27 网宿科技股份有限公司 一种控制多cname流量比例的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3800870A4 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111625359A (zh) * 2020-05-25 2020-09-04 北京金山云网络技术有限公司 用户的cdn用量的确定方法、装置和终端设备
CN111625359B (zh) * 2020-05-25 2023-04-18 北京金山云网络技术有限公司 用户的cdn用量的确定方法、装置和终端设备
CN111885216A (zh) * 2020-07-15 2020-11-03 北京青云科技股份有限公司 Dns查询方法、装置、设备和存储介质
CN112291343A (zh) * 2020-10-28 2021-01-29 成都知道创宇信息技术有限公司 信息获取方法、装置及电子设备
CN112291343B (zh) * 2020-10-28 2022-11-22 成都知道创宇信息技术有限公司 信息获取方法、装置及电子设备
CN112738271A (zh) * 2021-01-08 2021-04-30 网宿科技股份有限公司 一种cdn质量的探测方法、***及域名服务器
CN115208766A (zh) * 2022-07-29 2022-10-18 天翼云科技有限公司 一种cdn带宽调度方法及相关装置
CN115208766B (zh) * 2022-07-29 2023-11-03 天翼云科技有限公司 一种cdn带宽调度方法及相关装置
CN115442330A (zh) * 2022-08-05 2022-12-06 天翼云科技有限公司 一种域名解析***、方法及设备
CN115442330B (zh) * 2022-08-05 2023-08-08 天翼云科技有限公司 一种域名解析***、方法及设备

Also Published As

Publication number Publication date
EP3800870A4 (en) 2021-07-28
CN108900648A (zh) 2018-11-27
US20210336920A1 (en) 2021-10-28
CN108900648B (zh) 2020-11-06
EP3800870A1 (en) 2021-04-07

Similar Documents

Publication Publication Date Title
WO2019237557A1 (zh) 一种控制多cname流量比例的方法和装置
US7548945B2 (en) System, network device, method, and computer program product for active load balancing using clustered nodes as authoritative domain name servers
US9319315B2 (en) Distributing transmission of requests across multiple IP addresses of a proxy server in a cloud-based proxy service
WO2017084274A1 (zh) 选择回源服务器的方法及装置
EP2692095B1 (en) Method, apparatus and computer program product for updating load balancer configuration data
WO2019061522A1 (zh) 域名解析方法、客户端、边缘节点及域名解析***
CN105681491A (zh) 一种域名解析加速方法、***和装置
US20200382465A1 (en) Client subnet efficiency by equivalence class aggregation
CN109587290B (zh) 一种域名解析的方法及相关装置
EP3726786B1 (en) Method and apparatus for transmitting application programming interface (api) request
WO2021042673A1 (zh) Dns解析方法、权威dns服务器和dns解析***
US8868756B1 (en) Sticky routing
CN108881516A (zh) 一种调度多cdn服务***的方法和装置
CN109067936A (zh) 一种域名解析的方法及装置
CN112738288A (zh) Dns域名解析方法、dns服务器、gslb***及域名解析***
WO2021057369A1 (zh) HttpDNS调度方法、装置、介质及设备
CN110213349A (zh) 一种http调度方法及装置
US9565276B2 (en) Transparent redirection of clients to a surrogate payload server through the use of a proxy location server
CN105493462B (zh) 一种内容分发方法、装置和***
US7711780B1 (en) Method for distributed end-to-end dynamic horizontal scalability
US20070130322A1 (en) System and method for bulk network data collection
CN115242882A (zh) 一种基于传输层路由访问k8s容器环境的方法及装置
CN106254576B (zh) 一种报文转发方法及装置
CN111447297B (zh) IPv4、IPv6的DNS统一接入的管理方法及***
CN114844670B (zh) 一种基于命名网络的ip地址隐藏的方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18922730

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018922730

Country of ref document: EP

Effective date: 20201231