CN106790744B

CN106790744B - IP scheduling method and system

Info

Publication number: CN106790744B
Application number: CN201611087234.XA
Authority: CN
Inventors: 王晓旭
Original assignee: Shanghai Yundun Information Technology Co ltd
Current assignee: Shanghai Yundun Information Technology Co ltd
Priority date: 2016-12-01
Filing date: 2016-12-01
Publication date: 2020-09-15
Anticipated expiration: 2036-12-01
Also published as: CN106790744A

Abstract

The application aims to provide an automatic IP scheduling scheme, in the scheduling process, the attribute information of a domain name and the attribute information of an IP node pool can be respectively obtained, matching analysis is carried out based on the domain name and the attribute information of the IP node pool, and a proper IP node is automatically allocated to the domain name, so that the resolution line and speed of the domain name are optimal, the response is quicker, the use experience of a user is improved, and in addition, the problem of risk centralization is avoided because the domain name does not need to be grouped before scheduling. Furthermore, after the first scheduling is completed, the health condition of the IP node is monitored in real time, and when the IP node is detected to be abnormal, the IP scheduling is carried out again, so that the IP nodes distributed for the domain name are all in a normal state.

Description

IP scheduling method and system

Technical Field

The present application relates to the field of information technology, and in particular, to an IP scheduling method and system.

Background

Domain Name (Domain Name), which is the Name of a certain computer or group of computers on the internet composed of a string of names separated by dots, is used to identify the computer or group of computers during data transmission. An IP (Internet Protocol) address is a uniform address format provided by an IP Protocol, and is a logical address of each computer or group of computers on the Internet. Each domain name needs to correspond to an IP address, and therefore, IP address allocation for the domain name needs to be realized through IP scheduling. In the prior art, the IP scheduling scheme specifically includes: and manually grouping the accessed domain names, wherein each group of domain names shares the IP nodes in the appointed IP node pool, thereby realizing IP scheduling. The above scheme has the following disadvantages:

1. the user experience is poor. The domain name grouping needs manual operation, which causes slow domain name access speed, i.e. slow domain name enabling service, and causes impaired user experience.

2. And (4) risk centralization. The domain names of the same group share the IP nodes in the designated IP node pool, and if any domain name in a certain group of domain names is attacked, all the domain names in the group are subjected to the attack risk.

3. The response speed of fault handling is slow. When the node is detected to be abnormal, the abnormal condition needs to be manually processed, and the fault processing is possibly not timely.

Content of application

An object of the present application is to provide an IP scheduling method and system, so as to solve the problems of slow response speed and concentrated risk in the prior art.

In order to achieve the above object, the present application provides an IP scheduling method, including:

acquiring attribute information of a domain name and attribute information of an IP node pool, wherein the IP node pool comprises at least one IP node;

and allocating the IP nodes in the IP node pool for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool.

Further, allocating an IP node to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool, including:

determining a first label of the domain name based on the attribute information of the domain name, and determining a second label of the IP node pool based on the attribute information of the IP node pool;

and when the first label is determined to be matched with the second label, allocating the IP nodes in the IP node pool for the domain name.

Further, when it is determined that the first label matches the second label, allocating an IP node in the IP node pool to the domain name includes:

upon determining that the first label matches the second label, detecting a health of the IP node;

and allocating the IP nodes with normal health conditions in the IP node pool to the domain name.

Further, the method further comprises:

when the domain name is allocated with the IP node in the IP node pool for the first time or the domain name is detected to be abnormal, the domain name is put into an observation pool, and if the domain name is not abnormal during observation, the domain name is put into a normal pool.

Further, before allocating the IP node in the IP node pool to the domain name, the method further includes:

and auditing the domain name according to the attribute information of the domain name.

Further, after allocating the IP node in the IP node pool to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool, the method further includes:

detecting health conditions of IP nodes in the IP node pool allocated for the domain name;

and if the health condition of the IP node is abnormal, reallocating the IP node with the normal health condition for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool.

Based on another aspect of the present application, there is also provided an IP scheduling system, including:

the device comprises a first device, a second device and a third device, wherein the first device is used for acquiring attribute information of a domain name and attribute information of an IP node pool, and the IP node pool comprises at least one IP node;

and the second device is used for distributing the IP nodes in the IP node pool for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool.

Further, the second apparatus is configured to determine a first label of the domain name based on the attribute information of the domain name, and determine a second label of the IP node pool based on the attribute information of the IP node pool; and when the first label is determined to be matched with the second label, allocating the IP nodes in the IP node pool to the domain name.

Further, the second device is configured to, when an IP node in the IP node pool is allocated to the domain name for the first time or when the domain name is detected to be abnormal, allocate an IP node in the observation scheduling pool to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool; and if the domain name is not abnormal during the observation period, reallocating the IP node in the normal scheduling pool for the domain name.

Further, the system further comprises:

and the fifth device is used for placing the domain name into an observation pool when the IP node in the IP node pool is allocated for the domain name for the first time or the domain name is detected to be abnormal, and placing the domain name into a normal pool if the domain name is not abnormal during observation.

Further, the system further comprises:

and the third device is used for auditing the domain name according to the attribute information of the domain name before the IP nodes in the IP node pool are allocated to the domain name.

Further, the system further comprises:

a fourth device, configured to detect a health condition of the IP node in the IP node pool allocated for the domain name after allocating the IP node in the IP node pool to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool; and if the health condition of the IP node is abnormal, reallocating the IP node with the normal health condition for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool.

Compared with the prior art, the automatic IP scheduling scheme is provided, in the scheduling process, the attribute information of the domain name and the attribute information of the IP node pool are respectively obtained, matching analysis is carried out based on the domain name and the attribute information of the IP node pool, and the appropriate IP node is automatically allocated to the domain name, so that the resolution line and speed of the domain name are optimal, the response is quicker, the use experience of a user is improved, and in addition, the problem of risk centralization is avoided because the domain name does not need to be grouped before scheduling.

Furthermore, after the first scheduling is completed, the health condition of the IP node is monitored in real time, and when the IP node is detected to be abnormal, the IP scheduling is carried out again, so that the IP nodes distributed for the domain name are all in a normal state.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:

fig. 1 is a schematic overall functional diagram of an IP scheduling scheme provided in an embodiment of the present application;

fig. 2 is a processing flow chart of an IP scheduling method according to an embodiment of the present application;

fig. 3 is a flowchart of processing performed in an intelligent IP scheduling method according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram illustrating IP node pool distribution in an embodiment of the present application;

fig. 5 is a processing flow chart when an IP node is allocated in the IP scheduling method according to the embodiment of the present application;

FIG. 6 is an overall service flow diagram of an IP scheduling scheme provided by an embodiment of the application;

fig. 7 is a schematic structural diagram of an IP scheduling system according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a preferred IP scheduling system according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of another preferred IP scheduling system provided in an embodiment of the present application;

fig. 10 is an overall processing architecture diagram of an IP scheduling scheme provided by an embodiment of the present application;

the same or similar reference numbers in the drawings identify the same or similar elements.

Detailed Description

The present application is described in further detail below with reference to the attached figures.

In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.

The embodiment of the present application provides a scheme for IP scheduling, which can be generally split into three major parts as shown in fig. 1: domain name information collection 1, IP node pool information collection 2, and intelligent IP scheduling 3.

Based on the above, an embodiment of the present application provides an IP scheduling method, where a specific processing flow of the method is shown in fig. 2, and the method includes:

step S101, obtaining attribute information of a domain name and attribute information of an IP node pool, wherein the IP node pool comprises at least one IP node. The main functions realized in this step include: collecting domain name information and collecting IP node pool information.

Step S102, distributing the IP nodes in the IP node pool for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool. And after the dispatching system finishes the collection work of the domain name and the attribute information of the IP node pool, starting to carry out intelligent IP dispatching, matching based on a preset matching rule according to the domain name and the attribute information of the IP node pool, finally finishing the distribution of the IP nodes and updating DNS records.

Wherein, the attribute information of the domain name includes but is not limited to: the domain name belongs to the account type, domain name record information, domain name affiliated package, domain name scheduling type, etc.

The types of accounts to which the domain name belongs are as follows: individuals, government enterprises, agents and the like, different rules can be set respectively for different account types during scheduling, for example, better IP nodes are preferentially allocated to domain names of specific types.

The domain name registration information includes: filed and not filed. The domain name is recorded or not, which may be directly embodied in the IP node allocated to the domain name in the scheduling process, for example, a specific IP node may be allocated to only the recorded domain name.

The package to which the domain name belongs comprises: free edition, standard edition, professional edition, advanced edition and fixed edition. The attribute information is used for carrying out more precise region division and node pool positioning on the IP nodes distributed by the domain name, and the distribution of the IP nodes in the IP node pool is more balanced and reasonable on the premise of isolating the IP risk grades distributed among users with different grades.

The domain name scheduling types include: observation scheduling and normal scheduling. When the domain name is subjected to IP scheduling for the first time or is observed to be abnormal, the domain name can be subjected to observation scheduling, and when the domain name is not abnormal during observation, the domain name can be switched to normal scheduling. Specifically, when an IP node in the IP node pool is allocated to the domain name for the first time, or when the domain name is detected to be abnormal, the domain name is placed into an observation pool, and if the domain name is not abnormal during observation, the domain name is placed into a normal pool.

The distinction between the observation scheduling and the normal scheduling is to isolate risks, facilitate monitoring and ensure that the IP scheduling of the normal domain name is not influenced to the maximum extent. In general, the observation of an anomaly in a domain name means that some large-scale attacks (DDoS, CC, WAF, and the like) exist on a normally accessed domain name, so that a website corresponding to the domain name cannot be accessed, and the service performance and stability of a normal IP node are affected. In an actual scene, a preset standard can be set to determine whether the domain name is abnormal, such as DDoS attack bandwidth peak, CC attack frequency, WAF attack interception times, and the like. The observation period can be generally set according to actual scenes and can be generally set to be less than one day.

In an actual scenario, the attribute information of the Domain Name may be obtained in a record scanning manner, and mainly, a currently used DNS (Domain Name System) record is scanned. The DNS records with the existing domain names are automatically imported after being scanned, and the attribute information of the domain names is automatically acquired, so that the operation cost of a user is reduced, and the user experience is improved.

As a preferred embodiment, step S102 may specifically include the processing flow shown in fig. 3:

step S201, determining a first label of the domain name based on the attribute information of the domain name, and determining a second label of the IP node pool based on the attribute information of the IP node pool. Thus, matching may be performed based on the first tag and the second tag.

Step S202, when the first label is determined to be matched with the second label, allocating the IP node in the IP node pool to the domain name.

In order to implement the above scheme, before performing IP scheduling, corresponding settings need to be completed, which mainly includes the following settings: the method comprises the steps of planning configuration of an IP node pool and IP nodes, second label setting of the IP node pool and first label setting of a domain name.

Specifically, the planning configuration of the IP node pool and the IP nodes is mainly the division of the IP node pool and the IP nodes. As a feasible implementation manner, in this embodiment, the IP node pool node pools are set step by step according to the size of the limited range, first, two large node pools of "record" and "no record" are set in the system according to the difference between record and no record, and under the directory with record, different area node pools are divided according to areas; under the regional node pool, the IP node pools of individuals, government and enterprises and agents are divided according to the domain name types, and the rest can be done in the same way, and the IP node pool distribution diagram is shown in FIG. 4. In an actual scenario, an editing function may be provided, and when the mouse moves to the IP node pool, an operation icon of the IP node pool is displayed, operations such as adding, editing, deleting, and dissolving IP occupation are supported for the IP nodes in the IP node pool, and the IP nodes are supported to be moved to their peer IP node pool, upper IP node pool, or lower IP node pool. When the IP node is deleted, the domain name associated with the IP node is also unbound; when the IP occupation is solved, only the domain name associated with the IP node is unbound, and the IP node is not deleted. And carrying out IP scheduling again on the unbound domain names, and allocating IP nodes to the domain names. Further, a minimum allocated IP number and a minimum remaining IP number of the IP node pool may also be set, where the minimum allocated IP number refers to the number of at least allocated IP nodes for all domain names using the node pool, and when performing IP scheduling, if the number of allocated IP nodes is less than the number, allocation failure will be caused, that is, no IP node allocation will be performed on the domain name, and the current state of the domain name is retained. The minimum remaining IP number refers to the minimum number of the IP nodes remaining in the current IP node pool, and if the number of the IP nodes in the IP node pool is less than or equal to the minimum number, the IP nodes in the IP node pool cannot be deleted.

The second label setting of the IP node pool specifically includes: after the division of the IP node pool is completed, in order to implement convenient classification and distribution of domain names of different types and the same characteristics during IP scheduling, a specific label may be added to the IP node pool. The specific content of the tag can be set according to the actual application scenario.

The first label setting of the domain name specifically comprises the following steps: in order to make the IP scheduling result of the domain name meet the expectation, labels may be added to the domain name based on the attribute information of the domain name, and the labels may reflect the type or the characteristics of the domain name to some extent. In the actual matching process, the labels of the IP node pool and the domain name can become important bases for matching in the scheduling process.

After the first label setting of the domain name and the second label setting of the IP node pool are completed, intelligent IP scheduling can be directly realized through matching labels, and the efficiency of IP scheduling is improved.

Further, to ensure availability of the IP assigned to the domain name, the health of the IP node may be checked when performing IP scheduling. Specifically, step S202 may be specifically divided into steps as shown in fig. 5:

step S2021, detecting a health condition of the IP node when it is determined that the first tag matches the second tag. The health condition check of the IP node mainly comprises two aspects: health check of IP node pool to which IP node belongs, and health check of each IP node itself.

In a practical scenario, the health of the IP node pool may be checked first. That is, before allocating the IP node, whether the IP node pool is normal (e.g., whether the number of available IP nodes in the node pool is sufficient, etc.) is detected. If the number of the domain names allowed to be simultaneously accessed by the IP node is within the normal service division range (for example, whether the number of the domain names allowed to be simultaneously accessed by the IP node reaches the maximum value) and the like, the IP node in the IP node pool is continuously checked, for example, whether a machine room network where the IP node is located is normal, whether a server corresponding to the IP node normally responds, whether the IP node is down and the like are checked, and whether the use of the IP node is within the normal service.

If the check results are still normal, the subsequent processing flow is performed, that is, step S2022, to assign the IP node with normal health condition in the IP node pool to the domain name. And if the IP nodes are abnormal, switching to a repairing process to repair the corresponding IP nodes in the IP node pool. In the process of allocating the IP nodes, according to different service requirements, part of the IP nodes are allowed to be allocated to a plurality of domain names for simultaneous use, wherein the number of the domain names using a certain IP node at the same time is different according to subdivision services. In addition, some IP nodes belong to exclusive IP nodes and can only be allocated to one domain name for use, for example, a domain name for starting SSL (Secure socket layer), and the specific allocation principle can be set according to an actual application scenario.

Furthermore, the scheme of the application can also ensure the automatic switching function of the abnormal IP node so as to ensure that the domain name is always online. In order to implement the above functions, after the step S102, the method further includes:

step S103, detecting the health condition of the IP nodes in the IP node pool allocated for the domain name;

and step S104, if the health condition of the IP node is abnormal, reallocating the IP node with the normal health condition for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool.

Automatic switching is realized by reallocating the IP nodes so as to complete IP rescheduling. In an actual scenario, the switching rule includes source returning, pausing, non-processing and the like besides rescheduling, and the switching rule can be set according to different application scenarios respectively to ensure the efficiency of the scheme. Com, for example, when an IP node used by a certain website is down, the scheduling system starts to make a priority judgment: if the switching rule is set to reschedule, a new IP node with normal health condition is allocated to the domain name for rescheduling, and if the switching rule is set to one of returning to the source, suspending and not processing, the corresponding processing is carried out according to the rule.

In addition, before allocating the IP node in the IP node pool to the domain name, the method further includes: and auditing the domain name according to the attribute information of the domain name. The domain name auditing method mainly comprises the following steps: and checking whether the domain name meets the specifications of related legal requirements and company business requirements. Such as whether the domain name is recorded, whether the website of the domain name is normally accessed, whether the content is legal, whether the domain name has DNS resolution, etc. The auditing mode comprises automatic auditing and manual auditing of the system. The domain name access under normal conditions can realize the automatic audit of the system; for some domain names and users with specific requirements, manual review can be performed. Thus, the business flow of the scheme is shown in fig. 6.

Based on the same inventive concept, the embodiment of the application also provides an IP scheduling system, and the corresponding method of the system is the IP scheduling method in the foregoing embodiment, and the principle of solving the problem is similar to the method.

Fig. 7 illustrates an IP scheduling system provided in an embodiment of the present application, which includes a first apparatus 710 and a second apparatus 720. The first apparatus 710 is configured to obtain attribute information of a domain name and attribute information of an IP node pool, where the IP node pool includes at least one IP node. The main functions of its realization include: collecting domain name information and collecting IP node pool information.

The second device 720 is configured to allocate an IP node in the IP node pool to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool. And after the dispatching system finishes the collection work of the domain name and the attribute information of the IP node pool, starting to carry out intelligent IP dispatching, matching based on a preset matching rule according to the domain name and the attribute information of the IP node pool, finally finishing the distribution of the IP nodes and updating DNS records.

The domain name scheduling types include: observation scheduling and normal scheduling. When the domain name is subjected to IP scheduling for the first time or is observed to be abnormal, the domain name can be subjected to observation scheduling, and when the domain name is not abnormal during observation, the domain name can be switched to normal scheduling. Specifically, the system further includes a fifth device, where the fifth device is configured to place the domain name into an observation pool when the IP node in the IP node pool is allocated for the domain name for the first time or when the domain name is detected to be abnormal, and place the domain name into a normal pool if the domain name is not abnormal during observation.

As a preferred embodiment, the second means 720 is specifically configured to determine the first label of the domain name based on the attribute information of the domain name, and determine the second label of the IP node pool based on the attribute information of the IP node pool. Thus, matching may be performed based on the first tag and the second tag. And when the first label is determined to be matched with the second label, allocating the IP nodes in the IP node pool to the domain name.

Further, to ensure availability of the IP assigned to the domain name, the health of the IP node may be checked when performing IP scheduling. Specifically, the second device 720 first detects the health condition of the IP node when allocating the IP node in the IP node pool for the domain name when determining that the first label matches the second label. The health condition check of the IP node mainly comprises two aspects: health check of IP node pool to which IP node belongs, and health check of each IP node itself.

If the check results are still normal, the second device 720 performs subsequent processing procedures to allocate an IP node with a normal health status in the IP node pool to the domain name. And if the IP nodes are abnormal, switching to a repairing process to repair the corresponding IP nodes in the IP node pool. In the process of allocating the IP nodes, according to different service requirements, part of the IP nodes are allowed to be allocated to a plurality of domain names for simultaneous use, wherein the number of the domain names using a certain IP node at the same time is different according to subdivision services. In addition, some IP nodes belong to exclusive IP nodes and can only be allocated to one domain name for use, for example, a domain name for starting SSL (secure sockets Layer), and the specific allocation principle can be set according to an actual application scenario.

Furthermore, the scheme of the application can also ensure the automatic switching function of the abnormal IP node so as to ensure that the domain name is always online. To achieve the above functions, the system may further include a fourth device 740, as shown in fig. 8. Specifically, the fourth device 740 detects the health condition of the IP nodes in the IP node pool allocated for the domain name after allocating the IP nodes in the IP node pool to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool; and if the health condition of the IP node is abnormal, reallocating the IP node with the normal health condition for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool.

In addition, as another preferred embodiment, the system may further include a third device 730, as shown in fig. 9. The third device 730 is configured to, before allocating an IP node in the IP node pool to the domain name, audit the domain name according to the attribute information of the domain name. The domain name auditing method mainly comprises the following steps: and checking whether the domain name meets the specifications of related legal requirements and company business requirements. Such as whether the domain name is recorded, whether the website of the domain name is normally accessed, whether the content is legal, whether the domain name has DNS resolution, etc. The auditing mode comprises automatic auditing and manual auditing of the system. The domain name access under normal conditions can realize the automatic audit of the system; for some domain names and users with specific requirements, manual review can be performed. Thus, the business flow of the scheme is shown in fig. 6.

To sum up, the application provides an automatic IP scheduling scheme, and an overall processing framework of the scheme is as shown in fig. 10, in a scheduling process, attribute information of a domain name and attribute information of an IP node pool are respectively obtained, matching analysis is performed based on the domain name and the attribute information of the IP node pool, and a proper IP node is automatically allocated to the domain name, so that an analysis line and speed of the domain name are optimal, response is faster, user experience is improved, and in addition, the domain name does not need to be grouped before scheduling, so that the problem of risk centralization is avoided.

It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In one embodiment, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.

In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Program instructions which invoke the methods of the present application may be stored on a fixed or removable recording medium and/or transmitted via a data stream on a broadcast or other signal-bearing medium and/or stored within a working memory of a computer device operating in accordance with the program instructions. An embodiment according to the present application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or a solution according to the aforementioned embodiments of the present application.

It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware.

Claims

1. An IP scheduling method, wherein the method comprises:

allocating the IP nodes in the IP node pool to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool;

the method further comprises the following steps:

when the domain name is allocated with the IP node in the IP node pool for the first time or the domain name is detected to be abnormal, putting the domain name into an observation pool, and if the domain name is not abnormal during observation, putting the domain name into a normal pool;

allocating an IP node for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool, comprising:

when the first label is determined to be matched with the second label, allocating an IP node in the IP node pool to the domain name;

the DNS record is updated.

2. The method of claim 1, wherein assigning an IP node of the pool of IP nodes to the domain name upon determining that the first label matches the second label comprises:

3. The method of claim 1, wherein prior to assigning the domain name to an IP node in the pool of IP nodes, further comprising:

4. The method according to any one of claims 1 to 3, wherein, after allocating an IP node in the IP node pool to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool, the method further comprises:

5. An IP scheduling system, wherein the system comprises:

a second device, configured to allocate an IP node in the IP node pool to the domain name according to the attribute information of the domain name and the attribute information of the IP node pool;

the system further comprises:

a fifth device, configured to, when an IP node in the IP node pool is allocated for the domain name for the first time, or when the domain name is detected to be abnormal, place the domain name into an observation pool, and if the domain name is not abnormal during observation, place the domain name into a normal pool;

the second device is configured to determine a first label of the domain name based on the attribute information of the domain name, and determine a second label of the IP node pool based on the attribute information of the IP node pool; when the first label is determined to be matched with the second label, allocating the IP nodes in the IP node pool to the domain name; the DNS record is updated.

6. The system according to claim 5, wherein the second apparatus is configured to, when an IP node in the IP node pool is allocated for the domain name for the first time, or when the domain name is detected to be abnormal, allocate an IP node in the observation scheduling pool for the domain name according to the attribute information of the domain name and the attribute information of the IP node pool; and if the domain name is not abnormal during the observation period, reallocating the IP node in the normal scheduling pool for the domain name.

7. The system of claim 5, wherein the system further comprises:

8. The system of any one of claims 5 to 7, wherein the system further comprises: