CN105072211A - Domain name deployment system and domain name deployment method based on DNS (Domain Name Server) - Google Patents
Domain name deployment system and domain name deployment method based on DNS (Domain Name Server) Download PDFInfo
- Publication number
- CN105072211A CN105072211A CN201510492447.XA CN201510492447A CN105072211A CN 105072211 A CN105072211 A CN 105072211A CN 201510492447 A CN201510492447 A CN 201510492447A CN 105072211 A CN105072211 A CN 105072211A
- Authority
- CN
- China
- Prior art keywords
- dns
- configuration
- server
- cluster
- domain name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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/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]
Abstract
The invention provides a domain name deployment system and a domain name deployment method based on a DNS (Domain Name Server). The domain name deployment system comprises a configuration module, a cluster configuration database, an interface server, a central cluster and a DNS server cluster; the configuration module is used for managing configuration of the central cluster, the DNS server cluster and a mapping relationship between the central cluster and the DNS server cluster; the interface server is used for splitting DNS domain name configuration according to a DNS suffix; the central cluster is used for receiving and analyzing domain name related configurations and pushing the domain name related configurations to the DNS server cluster to deploy in a MDT (Mean Doubling Time) format after distributed storage; and the DNS server cluster is used for receiving a tar packet in the MDT format provided by the central cluster, combining tasks and providing DNS analysis services in a clustering manner. According to the invention, the problems of central storage bottleneck, low concurrency, high hardware requirements of an edge DNS server, wasted resources and the like when a single-centre deployment system responds to massive domain names can be effectively solved.
Description
Technical field
The present invention relates to the technical field that domain name is disposed, particularly relate to a kind of domain name deployment system based on domain name system (DomainNameSystem, DNS) and method.
Background technology
Dns resolution is as the Internet, the basis of the content distributing network particularly dispatched based on visiting IP and core link, real-time, accuracy, availability and fail safe that its domain name is disposed have a strong impact on the service quality that general upper network process and content distributing network provider provide.Along with the growth of content delivery network service provider business scale, and the quick increase of service node scale is to support more and more huge domain name system, for common single centre domain name deployment system, more show painstakingly difficult.
General single centre domain name deployment system comprises a deployment interface device, a center module and multiple dns server.Deployment interface device receives the deployment configuration xml of user, changes into the discernible configuration format of center module, and calls center module and complete deployment; Center module comprises central database and the deployment module being responsible for disposing that stores domain name configuration and machine information; Deployment module receives the deployment configuration from deployment interface device, disposes this and is configured to all dns servers, and be submitted to central database after completing deployment.
But there is following drawback in the single centre domain name deployment system of the type:
(1) storage concentrates on single-point, along with domain name data scale increases, must reach the single-point storage capacity upper limit, causes inquiry and storage efficiency to decline fast, serious reduction deployment performance;
(2) Command Line Parsing and dns server are disposed and are concentrated on single-point, have relatively independent different ZONE, and deployment needs order to perform, and has lower concurrency;
(3) dns server docked with single centre domain name deployment system need carry the deployment domain name of all ZONE, cannot flexible customization as required, requires higher, waste resource to hardware configuration.
Summary of the invention
The shortcoming of prior art in view of the above, the object of the present invention is to provide a kind of domain name deployment system based on DNS and method, adopt group scheme, effectively can solve the problem such as central store bottleneck, concurrency is not high and edge dns server hardware requirement is high, wasting of resources during single centre deployment system reply magnanimity domain name.
For achieving the above object and other relevant objects, the invention provides a kind of domain name deployment system based on DNS, comprise configuration module, cluster configuration data storehouse, interface server, center cluster and dns server cluster; Described cluster configuration data storehouse is used for storage center cluster, dns server cluster, and the configuration of mapping relations between two clusters; Described configuration module is connected with described cluster configuration data storehouse, for the configuration of the mapping relations between administrative center's cluster, dns server cluster and two clusters; Described interface server for receiving the DNS domain name configuration that external interface transmits, and presses the configuration of DNS suffix fractionation DNS domain name; Described center cluster is connected with described interface server with described configuration module, comprise one to multiple stage central server, for receiving and resolving the configuration that described configuration module and described interface server send, and after distributed store, the task agent of MDT form is pushed to described dns server cluster and disposes; Described dns server cluster is connected with described center cluster, comprises a dns server distributed to multiple stage, and for receiving the task agent of the MDT form provided from described center cluster, merging configuration deployment task also provides dns resolution service with trunking mode.
According to the above-mentioned domain name deployment system based on DNS, wherein: the configuration of described center cluster comprises the IP of all central servers in center cluster, account executive password, and the territory of the center calculation memory node that central server runs and its carrying; The configuration of dns server cluster comprises IP, the account executive password of all dns servers; The mapping relations configuration of center cluster and DNS service cluster comprises a center calculation memory node and has which dns server, and which center calculation memory node a dns server belongs to.
According to the above-mentioned domain name deployment system based on DNS, wherein: described configuration module can increase, deletes, starts and stop the center calculation memory node on central server newly; Can added central server and undercarriage central server.
According to the above-mentioned domain name deployment system based on DNS, wherein: the configuration that described center cluster receives comprises the configuration of domain name in the territory in DNS Protocol, the name server in DNS Protocol, DNS Protocol and center calculation memory node.
According to the above-mentioned domain name deployment system based on DNS, wherein: described central server comprises a center calculation memory node administration module and one or more center calculation memory node; Described center calculation memory node is used for all domain names of an independent bearing DNS suffix; Described center calculation memory node administration module is for managing the center calculation memory node on this central server.
Further, according to the above-mentioned domain name deployment system based on DNS, wherein: described center calculation memory node comprises data memory module, Command Line Parsing module and disposes control module; Described Command Line Parsing module is for receiving and resolving the configuration of DNS suffix; Described data memory module is used for stored configuration parsing module and resolves the configuration obtained; Described deployment control module for Command Line Parsing module being resolved the configuration deployment that obtains to the dns server cluster providing dns resolution to serve to described DNS suffix, and according to finally disposing result, to data memory module rollback or submit this secondary data to.
According to the above-mentioned domain name deployment system based on DNS, wherein: described dns server comprises task receiver and DNS authorization server; Described task receiver is used for arranging according to actual loading situation in operation process docking with the center calculation memory node of multiple not same area, receives the domain name configuration in multiple territory, in the DNS authorization server of self be deployed to after merging; Described DNS authorization server is for providing the domain name resolution service of DNS suffix.
Further, according to the above-mentioned domain name deployment system based on DNS, wherein: described task receiver comprises task receiver module, task deployment module and Queued tasks pond; Described task receiver module is used for docking with one or more center calculation memory nodes of each DNS suffix, and receive and merge task, in Queued tasks pond, the domain name data of the up-to-date full dose version of each DNS suffix safeguarded in suffix; Whether described task deployment module exists for regular check Queued tasks pond is treated deployment task, and when being in the state in non-deployment in DNS authorization server, disposes Queued tasks.
According to the above-mentioned domain name deployment system based on DNS, wherein: a dns server can carry multiple DNS suffix.
Meanwhile, the present invention also provides a kind of domain name dispositions method according to above-mentioned arbitrary described domain name deployment system based on DNS, wherein, comprises the following steps:
Configuration module manages and upgrades the configuration of the mapping relations between center cluster, dns server cluster and two clusters;
Interface server receives the DNS domain name configuration that external interface transmits, and presses the configuration of DNS suffix fractionation DNS domain name;
Center cluster receives and resolves the configuration that described configuration module and described interface server send, and after distributed store, the task agent of MDT form is pushed to described dns server cluster and disposes;
Dns server cluster receives the task agent of the MDT form provided from described center cluster, merges configuration deployment task and provides dns resolution service with trunking mode.
As mentioned above, the domain name deployment system based on DNS of the present invention and method, have following beneficial effect:
(1) center module of single centre deployment system is transformed into center cluster; This center cluster comprises multiple distribution central server on different physical machines, and supports to expand flexibly according to actual needs; If operation process business needs newly-increased ZONE, this ZONE comprises more domain name, if current certain central server service ability has more than needed, then can increase node thereon newly and carry this ZONE; If all central server service ability are saturated, then can increase newly central server on it newly-increased node carry this ZONE; Different center module concurrently can dispose managed ZONE, thus the storage solved when data scale increases and deployment performance bottleneck;
(2) dns server receives from the deployment task of different central server, can according to the multiple ZONE of active service horizontal load, and without the need to the whole ZONE of load, requires relative reduction to cpu performance and memory size, thus the hardware requirement of reduction DNS.
Accompanying drawing explanation
Fig. 1 is shown as the structural representation of the domain name deployment system based on DNS of the present invention;
Fig. 2 is shown as the deployment framework schematic diagram of the domain name deployment system based on DNS of the present invention;
Fig. 3 is shown as the structural representation of central server of the present invention;
Fig. 4 is shown as the schematic diagram that administrative center of the present invention calculates memory node;
Fig. 5 is shown as in an embodiment of the domain name deployment system based on DNS of the present invention and manages ZONE, the schematic diagram of ns and server;
Fig. 6 is shown as the schematic diagram managing different domain suffix in an embodiment of the domain name deployment system based on DNS of the present invention.
Element numbers explanation
1 configuration module
2 cluster configuration data storehouses
3 interface servers
4 center cluster
5DNS server cluster
Embodiment
Below by way of specific instantiation, embodiments of the present invention are described, those skilled in the art the content disclosed by this specification can understand other advantages of the present invention and effect easily.The present invention can also be implemented or be applied by embodiments different in addition, and the every details in this specification also can based on different viewpoints and application, carries out various modification or change not deviating under spirit of the present invention.
It should be noted that, the diagram provided in the present embodiment only illustrates basic conception of the present invention in a schematic way, then only the assembly relevant with the present invention is shown in graphic but not component count, shape and size when implementing according to reality is drawn, it is actual when implementing, and the kenel of each assembly, quantity and ratio can be a kind of change arbitrarily, and its assembly layout kenel also may be more complicated.
See figures.1.and.2, the domain name deployment system based on DNS of the present invention comprises configuration module 1, cluster configuration data storehouse 2, interface server 3, center cluster 4 and dns server cluster 5.
Cluster configuration data storehouse 2 is for storage center cluster 4 and dns server cluster 4, and the configuration of mapping relations between two clusters.The configuration of center cluster comprises the information such as the machine information such as IP, account executive password of all central servers in center cluster, and the territory (ZONE) of the center calculation memory node that central server runs and its carrying.The configuration of dns server cluster comprises the machine information such as IP, account executive password of all dns servers.The mapping relations configuration of center cluster and DNS service cluster comprises a center calculation memory node and has which dns server, and a dns server belongs to the relations such as which center calculation memory node.
Configuration module 1 is connected with cluster configuration data storehouse 2, for the configuration of the mapping relations between administrative center's cluster 4, dns server cluster 5 and two clusters.
Particularly, configuration module 1, by the central store computing node administration module on html operation interface operation calls central server, increases, deletes, starts and stops the center calculation memory node on this central server newly.
Interface server 3 supports that concurrent batch disposes domain name, for receiving the DNS domain name configuration that external interface transmits, and presses the configuration of DNS suffix fractionation DNS domain name.
Center cluster 4 is connected with interface server 3 with configuration module 1, for receiving and resolving the configuration that configuration module 1 and interface server 3 send, and after distributed store, the task agent (tar bag) of MDT form is pushed to dns server cluster 5 and carries out disposing to provide dns resolution service.
Wherein, configuration comprises the configuration of ZONEs, NSs, DNs and MAPERs etc.ZONEs is the plural number of ZONE, and ZONE represents in " territory " in DNS Protocol.NSs is the plural number of NS, and NS represents " nameserver (name server) " in DNS Protocol.DNs is the plural number of DN, and DN represents the domain name in DNS Protocol.MAPERs is the plural number of MAPER, and MAPER is " center calculation memory node ".
Particularly, center cluster is the cluster of easy expansion, distributed store, concurrent parsing deployment, comprises a central server of resolving to the responsible configuration store of multiple stage.As shown in Figure 3, each central server comprises a center calculation memory node administration module and one or more center calculation memory node.Central server has one or more center calculation memory node according to computing capability and plan of operation.Between the fail safe that whole center cluster is isolated in business for unit planning center calculation memory node with ZONE (territory) and concurrent deployment ability, there is good balance.
Center calculation memory node administration module, for managing the center calculation memory node on this central server, is supported to comprise management function that is newly-increased, that delete, inquire about.Each center calculation memory node comprises data memory module, Command Line Parsing module and disposes control module, (can be one-level suffix .com for independent bearing DNS suffix, .cn or suffix a.com, b.net etc. reaching or above grade two) all domain names.Wherein Command Line Parsing module is for receiving and resolving the configuration (ZONEs, NSs, DNs) in this DNS suffix.Data memory module is used for stored configuration parsing module and resolves the configuration obtained.Dispose control module to be used for Command Line Parsing module to resolve the configuration deployment of acquisition to the dns server cluster providing dns resolution to serve to this DNS suffix, and according to finally disposing result, to data memory module rollback or submit this secondary data to.
Wherein, the configuration code of ZONEs, NSs, DNs and MAPERs is as follows respectively:
BEGINdnsconfig1#1 is configuration version number
znaddzn＝deploydns.com.
nsaddns＝ns1.deploydns.com.
nsaddns＝ns2.deploydns.com.
#ZONEs configures
zcupdatezn＝deploydns.com.cv＝*
soa＝600,ns1.deploydns.com.,webmaster.deploydns.com.,1107011041,10800,3600,64800,60
ns＝all,600,ns1.deploydns.com.ns＝all,600,ns2.deploydns.com.
#NSs configures
ncupdatens＝ns1.deploydns.com.cv＝*nip＝all,600,1.1.1.1
ncupdatens＝ns2.deploydns.com.cv＝*nip＝all,600,2.2.2.2
#DNs configures
dnadddn＝www.deploydns.com.
dcupdatedn＝www.deploydns.com.cv＝*record＝600,IN,A,3.3.3.3record＝600,IN,A,4.4.4.4
ENDdnsconfig1
#MAPERs configures
BEGINdnsconfig1#1 is configuration version number
serveraddip＝192.168.0.1port＝10000password＝xxxx
centeraddcenter_server＝192.168.0.1mapper＝deploydns.com
ENDdnsconfig1
Dns server cluster 5 is connected with center cluster 4, comprises a dns server distributed to multiple stage, and for receiving the tar bag of the MDT form provided from center cluster 4, merging configuration deployment task also provides dns resolution service with trunking mode.
Particularly, dns server comprises task receiver and DNS authorization server.Task receiver is used for being docked from the center calculation memory node of multiple different ZONE by configuration module setting according to actual loading situation in operation process, receive the domain name configuration of multiple ZONE, in this DNS authorization server be deployed to after merging, thus provide the service of multiple ZONE.DNS authorization server is for providing the domain name resolution service of DNS suffix.
Wherein, task receiver comprises task receiver module, task deployment module and Queued tasks pond.Task receiver module is used for docking with one or more center calculation memory nodes of each DNS suffix, receives and merges task, safeguarding the domain name data (comprising ZONEs, DNs) of the up-to-date full dose version of each DNS suffix in Queued tasks pond.Whether task deployment module exists for regular check Queued tasks pond is treated deployment task, and when being in the state in non-deployment in DNS authorization server, disposes Queued tasks.
Wherein MDT form tar bag, after decompress(ion) content and form as shown in table 1.
Content and form after the tar bag decompress(ion) of table 1, MDT form
The form of #meta_file:
BEGIN1# data begin column, 1 represents versions of data number
ADDhosts_01# represents the hosts config directory of newly-increased hosts_01 configuration file to DNS software.
DELhosts_02# represents the hosts_02 under the hosts config directory deleting DNS software.
MODhosts_03# represents the hosts_03 configuration file under the hosts config directory of the hosts/hosts_03 file replacement DNS software in the tar bag of this MDT of use form.
END# ED is capable
The form of #ipdb/ipdb_file:
BEGIN1# data begin column, 1 represents versions of data number
View=view_01# defines view
Ips=192.168.0.0/24# definition is mapped to the ips section of view
END# ED is capable
#hosts/hosts_01
BEGIN1# data begin column, 1 represents versions of data number
dnsdeploy.comview_01600INSOAns1.dnsdeploy.comwebmaster.ns1.dnsdeploy.com11070110411080036006480060|600INNSns1.dnsdeploy.com|600INNSns2.dnsdeploy.com
ns1.dnsdeploy.comview_01600INA192.168.0.1
ns1.dnsdeploy.comview_01600INA192.168.0.2
www.dnsdeploy.comview_01600INA192.168.0.3
END# ED is capable
It should be noted that: the hosts file under ipdb/ipdb_file and hosts/ catalogue is the configuration file format of the proprietary use of native system DNS software, can named.conf and the named catalogue of analogy bind software.
With reference to Fig. 4, set forth the workflow of configuration module by specific embodiment.
(1) added central server
Allot a central server according to MRP, and mounting center calculates memory node administration module on newly-increased central server, then configures this newly-increased central server at html operation interface.
It is as follows that configuration module generates configuration order:
The added central server of # (192.168.0.1) and center calculation memory node (mapper_01)
BEGINdnsconfig1#1 is configuration version number
serveraddip＝192.168.0.1port＝10000password＝xxxx
centeraddcenter_server＝192.168.0.1mapper＝mapper_01
ENDdnsconfig1#1 is configuration version number
(2) undercarriage central server
According to MRP undercarriage central server, all center calculation memory nodes on this central server of migration backup, then at this central server of operation interface undercarriage.
It is as follows that configuration module generates configuration order:
# undercarriage central server (192.168.0.1)
BEGINdnsconfig1#1 is configuration version number
centerdelcenter_server＝192.168.0.1
ENDdnsconfig1#1 is configuration version number
(3) newly-increased center calculation memory node
By the newly-increased center calculation memory node interface add_node of the center calculation memory node administration module on html operation interface far call central server, create the center calculation memory node that name is called mapper_02.After center calculation memory node administration module receives add_node operational order, will automatically create and the relevant configuration of the data memory module of this center calculation memory node of initialization, Command Line Parsing module and deployment control module.
It is as follows that configuration module generates configuration order:
# is at the upper newly-increased center calculation memory node (02.deploydns.com) of existing central server (192.168.0.1)
BEGINdnsconfig1#1 is configuration version number
centeradd_nodecenter_server＝192.168.0.1mapper＝mapper_02
ENDdnsconfig1#1 is configuration version
(4) center calculation memory node is deleted
By the deletion center calculation memory node interface del_node of the center calculation memory node administration module on html operation interface far call central server, delete the center calculation memory node that name is called mpapper_02.After center calculation memory node administration module receives del_node operational order, will automatically delete the data memory module of this center calculation memory node, Command Line Parsing module and dispose the relevant configuration of control module.Center calculation memory node is only deleted in the lower just permission of the state status that quits work.
It is as follows that configuration module generates configuration order:
# is at existing central server (192.168.0.1) upper deletion center calculation memory node (02.deploydns.com)
BEGINdnsconfig1#1 is configuration version number
centerdel_nodecenter_server＝192.168.0.1mapper＝mapper_02
ENDdnsconfig1#1 is configuration version
(5) center calculation memory node is started
By the startup center calculation memory node interface start_node of the center calculation memory node administration module on html operation interface far call central server, start the center calculation memory node that name is called deploynode.com.Center calculation memory node administration module receives start_node operational order, by the service processes of log-on data memory module successively, and Command Line Parsing module and dispose the service processes of control module.
It is as follows that configuration module generates configuration order:
# is at existing central server (192.168.0.1) upper startup center calculation memory node (01.deploydns.com)
BEGINdnsconfig1#1 is configuration version number
centerstart_nodecenter_server＝192.168.0.1mapper＝mapper_01
ENDdnsconfig1#1 is configuration version
(6) center calculation memory node is stopped
By stop_node (stopping the calculating memory node) interface of the center calculation memory node administration module on html operation interface far call central server, name is stopped to be called the center calculation memory node of deploynode.com.After center calculation memory node administration module receives stop_node operational order, will Command Line Parsing module be stopped successively, dispose the service processes of control module and the service processes of data memory module.
It is as follows that configuration module generates configuration order:
# is at existing central server (192.168.0.1) upper stopping center calculation memory node (01.deploydns.com)
BEGINdnsconfig1#1 is configuration version number
centerstop_nodecenter_server＝192.168.0.1mapper＝mapper_01
ENDdnsconfig1#1 is configuration version
(7) ZONEs, NSs and SERVERs of management cluster
By the ZONEs of html operation interface management cluster, NSs and SERVERs.Html operation interface is by calling the operation-interface of the center calculation memory node on central server, and configuration belongs to ZONE, NS and the DNS authorization server SERVER of this center calculation memory node.A ZONE only belongs to a center calculation memory node, and a dns server can belong to different center calculation memory nodes, namely carries multiple DNS suffix.
Concrete management example is as follows:
71) newly-increased authorization message (ZONE and NS) process
Html operation interface operates authorization configuration, the ZONE of a newly-increased deploydns.com suffix, and NS record ns1.deploydns.com. ~ ns5.deploydns.com. that configuration is relevant.Operation is changed into the interface format of center calculation memory node by html operation interface, and all DNS authorization server that the center calculation memory node calling carrying .com suffix domain name docks self complete deployment.
It is as follows that configuration module generates configuration order:
# is at the upper newly-increased ZONE (deploydns.com.) of existing calculating memory node (mapper_01)
BEGINdnsconfig1#1 is configuration version
serveraddip＝1.1.1.1port＝10000password＝xxxx
serveraddip＝2.2.2.2port＝10000password＝xxxx
serveraddip＝3.3.3.3port＝10000password＝xxxx
serveraddip＝4.4.4.4port＝10000password＝xxxx
serveraddip＝5.5.5.5port＝10000password＝xxxx
znaddzn＝.deploydns.com.mapper＝mapper_01
nsaddns＝ns1.deploydns.com.
nsaddns＝ns2.deploydns.com.
nsaddns＝ns3.deploydns.com.
nsaddns＝ns4.deploydns.com.
nsaddns＝ns5.deploydns.com.
zcupdatezn＝deploydns.com.cv＝*
soa＝600,ns1.deploydns.com.,webmaster.deploydns.com.,1107011041,10800,3600,64800,60
ns＝all,600,ns1.deploydns.com.ns＝all,600,ns2.deploydns.com.ns＝all,600,ns3.deploydns.com.
ns＝all,600,ns4.deploydns.com.ns＝all,600,ns5.deploydns.com.
ncupdatens＝ns1.deploydns.com.cv＝*nip＝all,600,1.1.1.1
ncupdatens＝ns2.deploydns.com.cv＝*nip＝all,600,2.2.2.2
ncupdatens＝ns3.deploydns.com.cv＝*nip＝all,600,3.3.3.3
ncupdatens＝ns4.deploydns.com.cv＝*nip＝all,600,4.4.4.4
ncupdatens＝ns5.deploydns.com.cv＝*nip＝all,600,5.5.5.5
ENDdnsconfig1#1 is configuration version
72) newly-increased DNS authorization server process
Newly-increased .comDNS authorization server on html operation interface.Center calculation memory node receives the newly-increased DNS authorization server configuration from html operation interface, after DNS authorization server is increased to local data base, active push Fully Qualified Domain Name configuration (whole domain name configurations that namely in database, persistence is preserved) is to DNS authorization server.
It is as follows that configuration module generates configuration order:
# above increases DNS authorized machine (6.6.6.6) newly as ns6.deploydns.com. at existing ZONE (deploydns.com.)
BEGINdnsconfig1#1 is configuration version
serveraddip＝6.6.6.6port＝10000password＝xxxx
nsaddns＝ns6.deploydns.com.
zcupdatezn＝deploydns.com.cv＝*
soa＝600,ns1.deploydns.com.,webmaster.deploydns.com.,1107011041,10800,3600,64800,60
ns＝all,600,ns1.deploydns.com.ns＝all,600,ns2.deploydns.com.ns＝all,600,ns3.deploydns.com.
ns＝all,600,ns4.deploydns.com.ns＝all,600,ns5.deploydns.com.ns＝all,600,ns6.deploydns.com.
ncupdatens＝ns4.deploydns.com.cv＝*nip＝all,600,6.6.6.6
ENDdnsconfig1#1 is configuration version
73) DNS authorization server process is deleted
Html operation interface is deleted the DNS authorization server of .com.The deletion DNS authorization server that center calculation memory node receives from manager works node configures, and DNS authorization server is deleted from local data base, and suspends the follow-up domain name deployment to DNS authorization server.
It is as follows that configuration module generates configuration order:
# is at existing ZONE (deploydns.com.) upper deletion DNS authorized machine (5.5.5.5), and corresponding NS is ns6.deploydns.com.
BEGINdnsconfig1#1 is configuration version
zcupdatezn＝deploydns.com.cv＝*
soa＝600,ns1.deploydns.com.,webmaster.deploydns.com.,1107011041,10800,3600,64800,60
ns＝all,600,ns1.deploydns.com.ns＝all,600,ns2.deploydns.com.ns＝all,600,ns3.deploydns.com.
ns＝all,600,ns4.deploydns.com.
ncdelns＝ns4.deploydns.com.cv＝*nip＝all,600,5.5.5.5
serverdelip＝5.5.5.5port＝10000password＝xxxx
nsdelns＝ns5.deploydns.com.
ENDdnsconfig1#1 is configuration version
Meanwhile, based on the domain name deployment system of DNS of the present invention, the present invention also provides a kind of domain name dispositions method based on DNS, comprises the following steps:
Configuration module manages and upgrades the configuration of the mapping relations between center cluster, dns server cluster and two clusters;
Interface server receives the DNS domain name configuration that external interface transmits, and presses the configuration of DNS suffix fractionation DNS domain name;
Center cluster receives and resolves the configuration that described configuration module and described interface server send, and after distributed store, the tar of MDT form bag is pushed to described dns server cluster and disposes;
Dns server cluster receives the tar bag of the MDT form provided from described center cluster, merges configuration deployment task and provides dns resolution service with trunking mode.
Wherein, the specific implementation of the domain name dispositions method based on DNS of the present invention based on the aforesaid domain name deployment system based on DNS, therefore does not repeat them here.
The workflow of the brief description once domain name deployment system based on DNS of the present invention.
External interface upload comprise various DNS suffix (such as .com .cn .net etc.) original xml list to interface server.The DNS suffix that interface server carries according to each center calculation memory node, cutting original xml list becomes many parts (each DNS suffix is corresponding a), and changing into the soap form of center calculation memory node support, correspondence sends to each center calculation memory node to dispose.The waiting of this DNS suffix that the concurrent parsing of center calculation memory node of each DNS suffix receives disposes domain name list, be stored into this center calculation memory node data memory module this, and be sent on the task receiver associated by this DNS suffix and dispose.Task receiver, according to the deployment scenario of current DNS authorization server, merges or disposes separately the different suffix domain name list of the MDT form that new arrival is not disposed.
As shown in Figure 5 and Figure 6, in a preferred embodiment of the domain name deployment system based on DNS of the present invention, center cluster comprises central server 01 and central server 02.Central server 01 comprises the center calculation memory node 01 of a carrying .com suffix domain name, and central server 02 comprises the center calculation memory node 02 and center calculation node 03 that carry .cn and .net two domain suffix respectively.
Dns server cluster comprises dns server 01 ~ dns server 03.Wherein dns server 01 provides .comdns suffix domain name authorization service, dns server 02 provides .cn and .com suffix domain name authorization service, dns server 03 provides the DNS domain name authorization service of .cn and .net suffix, and dns server 04 provides the DNS domain name authorization service of .net suffix.
External interface submits to one to comprise .com, and the xml form deployment file of .cn and .net suffix domain name is to interface server.The deployment file of xml form is changed into the discernible com.deploy of center calculation memory node according to different domain suffix by interface server, cn.deploy, net.deploy tri-deployment files, and call center calculation memory node 01 ~ center calculation memory node 03 respectively and dispose.
Center calculation memory node 01 pair of com.deploy file checks, and changes into the tar bag of MDT form.Learn that the authorization server of .com suffix is dns server 01 and dns server 02 by inquiry local data storage module, thus be deployed to dns server 01 and dns server 02, and submit to or rollback local data storage module according to the feedback result of dns server 01 ~ dns server 02 finally whether deployment success or failure.
Center calculation memory node 02 pair of cn.deploy file checks, and changes into the tar bag of MDT form.Learn that the authorization server of .cn suffix is dns server 02 and dns server 03 by inquiry local data base, thus be deployed to dns server 02 and dns server 03, and submit to or rollback local data storage module according to the feedback result of dns server 02 ~ dns server 03 finally whether deployment success or failure.
Center calculation memory node 03 pair of net.deploy file checks, and changes into the tar bag of MDT form.Learn that the authorization server of .net suffix is dns server 03 and 04 by inquiry local data base, thus be deployed to dns server 03 and 04, and submit to or rollback local data storage module according to the feedback result of dns server 03 and dns server 04 finally whether deployment success or failure.
Interface server disposes result to external call according to the deployment result feedback of center calculation memory node 01 ~ center calculation memory node 03.
In sum, the center module of single centre deployment system is transformed into center cluster by the domain name deployment system based on DNS of the present invention and method; This center cluster comprises multiple distribution central server on different physical machines, and supports to expand flexibly according to actual needs; Dns server receives from the deployment task of different central server, can according to the multiple ZONE of active service horizontal load, and without the need to the whole ZONE of load, requires relative reduction to cpu performance and memory size, thus the hardware requirement of reduction DNS.So the present invention effectively overcomes various shortcoming of the prior art and tool high industrial utilization.
Above-described embodiment is illustrative principle of the present invention and effect thereof only, but not for limiting the present invention.Any person skilled in the art scholar all without prejudice under spirit of the present invention and category, can modify above-described embodiment or changes.Therefore, such as have in art usually know the knowledgeable do not depart from complete under disclosed spirit and technological thought all equivalence modify or change, must be contained by claim of the present invention.
Claims (10)
1. based on a domain name deployment system of DNS, it is characterized in that: comprise configuration module, cluster configuration data storehouse, interface server, center cluster and dns server cluster;
Described cluster configuration data storehouse is used for storage center cluster, dns server cluster, and the configuration of mapping relations between two clusters;
Described configuration module is connected with described cluster configuration data storehouse, for the configuration of the mapping relations between administrative center's cluster, dns server cluster and two clusters;
Described interface server for receiving the DNS domain name configuration that external interface transmits, and presses the configuration of DNS suffix fractionation DNS domain name;
Described center cluster is connected with described interface server with described configuration module, comprise one to multiple stage central server, for receiving and resolving the configuration that described configuration module and described interface server send, and after distributed store, the task agent of MDT form is pushed to described dns server cluster and disposes;
Described dns server cluster is connected with described center cluster, comprises a dns server distributed to multiple stage, and for receiving the task agent of the MDT form provided from described center cluster, merging configuration deployment task also provides dns resolution service with trunking mode.
2. the domain name deployment system based on DNS according to claim 1, it is characterized in that: the configuration of described center cluster comprises the IP of all central servers in center cluster, account executive password, and the territory of the center calculation memory node that central server runs and its carrying; The configuration of dns server cluster comprises IP, the account executive password of all dns servers; The mapping relations configuration of center cluster and DNS service cluster comprises a center calculation memory node and has which dns server, and which center calculation memory node a dns server belongs to.
3. the domain name deployment system based on DNS according to claim 1, is characterized in that: described configuration module can increase, deletes, starts and stop the center calculation memory node on central server newly; Can added central server and undercarriage central server.
4. the domain name deployment system based on DNS according to claim 1, is characterized in that: the configuration that described center cluster receives comprises the configuration of domain name in the territory in DNS Protocol, the name server in DNS Protocol, DNS Protocol and center calculation memory node.
5. the domain name deployment system based on DNS according to claim 1, is characterized in that: described central server comprises a center calculation memory node administration module and one or more center calculation memory node; Described center calculation memory node is used for all domain names of an independent bearing DNS suffix; Described center calculation memory node administration module is for managing the center calculation memory node on this central server.
6. the domain name deployment system based on DNS according to claim 5, is characterized in that: described center calculation memory node comprises data memory module, Command Line Parsing module and disposes control module; Described Command Line Parsing module is for receiving and resolving the configuration of DNS suffix; Described data memory module is used for stored configuration parsing module and resolves the configuration obtained; Described deployment control module for Command Line Parsing module being resolved the configuration deployment that obtains to the dns server cluster providing dns resolution to serve to described DNS suffix, and according to finally disposing result, to data memory module rollback or submit this secondary data to.
7. the domain name deployment system based on DNS according to claim 1, is characterized in that: described dns server comprises task receiver and DNS authorization server; Described task receiver is used for arranging according to actual loading situation in operation process docking with the center calculation memory node of multiple not same area, receives the domain name configuration in multiple territory, in the DNS authorization server of self be deployed to after merging; Described DNS authorization server is for providing the domain name resolution service of DNS suffix.
8. the domain name deployment system based on DNS according to claim 7, is characterized in that: described task receiver comprises task receiver module, task deployment module and Queued tasks pond; Described task receiver module is used for docking with one or more center calculation memory nodes of each DNS suffix, and receive and merge task, in Queued tasks pond, the domain name data of the up-to-date full dose version of each DNS suffix safeguarded in suffix; Whether described task deployment module exists for regular check Queued tasks pond is treated deployment task, and when being in the state in non-deployment in DNS authorization server, disposes Queued tasks.
9. the domain name deployment system based on DNS according to claim 1, is characterized in that: a dns server can carry multiple DNS suffix.
10., according to a domain name dispositions method for the domain name deployment system based on DNS one of claim 1-9 Suo Shu, it is characterized in that: comprise the following steps:
Configuration module manages and upgrades the configuration of the mapping relations between center cluster, dns server cluster and two clusters;
Interface server receives the DNS domain name configuration that external interface transmits, and presses the configuration of DNS suffix fractionation DNS domain name;
Center cluster receives and resolves the configuration that described configuration module and described interface server send, and after distributed store, the task agent of MDT form is pushed to described dns server cluster and disposes;
Dns server cluster receives the task agent of the MDT form provided from described center cluster, merges configuration deployment task and provides dns resolution service with trunking mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510492447.XA CN105072211B (en) | 2015-08-12 | 2015-08-12 | Domain name deployment system based on DNS and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510492447.XA CN105072211B (en) | 2015-08-12 | 2015-08-12 | Domain name deployment system based on DNS and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105072211A true CN105072211A (en) | 2015-11-18 |
| CN105072211B CN105072211B (en) | 2018-11-02 |
Family
ID=54501490
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510492447.XA Active CN105072211B (en) | 2015-08-12 | 2015-08-12 | Domain name deployment system based on DNS and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105072211B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105635342A (en) * | 2016-01-26 | 2016-06-01 | 华为技术有限公司 | Connection building method, domain name system and storage nodes |
| CN106020857A (en) * | 2016-04-06 | 2016-10-12 | 杭州沃趣科技股份有限公司 | Automatic disposition method used for Oracle Real Application Cluster database cluster |
| CN107046584A (en) * | 2017-03-15 | 2017-08-15 | 中国互联网络信息中心 | The DNS service dispositions method and system of a kind of overall coordination scheduling |
| CN108881501A (en) * | 2017-05-12 | 2018-11-23 | 阿里巴巴集团控股有限公司 | A kind of method and device realizing web application domain name and jumping |
| CN111314502A (en) * | 2020-03-09 | 2020-06-19 | 网宿科技股份有限公司 | Domain name deployment method and device based on domain name resolution system |
| CN112104680A (en) * | 2019-06-17 | 2020-12-18 | 中国移动通信有限公司研究院 | Method, device and equipment for determining edge application and storage medium |
| CN112631687A (en) * | 2020-12-31 | 2021-04-09 | 中国农业银行股份有限公司 | Configuration method, device and equipment of service cluster |
| CN115517009A (en) * | 2020-05-19 | 2022-12-23 | 深圳市欢太科技有限公司 | Cluster management method, cluster management device, storage medium and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103138961A (en) * | 2011-11-25 | 2013-06-05 | 阿里巴巴集团控股有限公司 | Server control method, controlled server and central control server |
| CN103179136A (en) * | 2013-04-22 | 2013-06-26 | 南京铱迅信息技术有限公司 | Saturation distribution type denial-of-service attack method and saturation distribution type denial-of-service attack system in defense dynamic website |
| CN104378452A (en) * | 2013-08-14 | 2015-02-25 | 阿里巴巴集团控股有限公司 | Method, device and system for domain name resolution |
| CN104461740A (en) * | 2014-12-12 | 2015-03-25 | 国家电网公司 | Cross-domain colony computing resource gathering and distributing method |
-
2015
- 2015-08-12 CN CN201510492447.XA patent/CN105072211B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103138961A (en) * | 2011-11-25 | 2013-06-05 | 阿里巴巴集团控股有限公司 | Server control method, controlled server and central control server |
| CN103179136A (en) * | 2013-04-22 | 2013-06-26 | 南京铱迅信息技术有限公司 | Saturation distribution type denial-of-service attack method and saturation distribution type denial-of-service attack system in defense dynamic website |
| CN104378452A (en) * | 2013-08-14 | 2015-02-25 | 阿里巴巴集团控股有限公司 | Method, device and system for domain name resolution |
| CN104461740A (en) * | 2014-12-12 | 2015-03-25 | 国家电网公司 | Cross-domain colony computing resource gathering and distributing method |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105635342A (en) * | 2016-01-26 | 2016-06-01 | 华为技术有限公司 | Connection building method, domain name system and storage nodes |
| CN105635342B (en) * | 2016-01-26 | 2019-04-19 | 华为技术有限公司 | Establish method, name server and the memory node of connection |
| CN106020857A (en) * | 2016-04-06 | 2016-10-12 | 杭州沃趣科技股份有限公司 | Automatic disposition method used for Oracle Real Application Cluster database cluster |
| CN107046584B (en) * | 2017-03-15 | 2020-08-14 | 中国互联网络信息中心 | DNS service deployment method and system for overall cooperative scheduling |
| CN107046584A (en) * | 2017-03-15 | 2017-08-15 | 中国互联网络信息中心 | The DNS service dispositions method and system of a kind of overall coordination scheduling |
| CN108881501A (en) * | 2017-05-12 | 2018-11-23 | 阿里巴巴集团控股有限公司 | A kind of method and device realizing web application domain name and jumping |
| CN112104680A (en) * | 2019-06-17 | 2020-12-18 | 中国移动通信有限公司研究院 | Method, device and equipment for determining edge application and storage medium |
| CN112104680B (en) * | 2019-06-17 | 2023-03-31 | 中国移动通信有限公司研究院 | Method, device and equipment for determining edge application and storage medium |
| CN111314502A (en) * | 2020-03-09 | 2020-06-19 | 网宿科技股份有限公司 | Domain name deployment method and device based on domain name resolution system |
| CN111314502B (en) * | 2020-03-09 | 2022-02-18 | 网宿科技股份有限公司 | Domain name deployment method and device based on domain name resolution system |
| CN115517009A (en) * | 2020-05-19 | 2022-12-23 | 深圳市欢太科技有限公司 | Cluster management method, cluster management device, storage medium and electronic equipment |
| CN115517009B (en) * | 2020-05-19 | 2023-10-13 | 深圳市欢太科技有限公司 | Cluster management method, cluster management device, storage medium and electronic equipment |
| CN112631687A (en) * | 2020-12-31 | 2021-04-09 | 中国农业银行股份有限公司 | Configuration method, device and equipment of service cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105072211B (en) | 2018-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105072211A (en) | Domain name deployment system and domain name deployment method based on DNS (Domain Name Server) | |
| CN105959138B (en) | The system and method for micro services Dynamical Deployment based on cloud computing | |
| US9338067B2 (en) | Network resource deployment for cloud-based services | |
| CN101408899B (en) | Method and apparatus for switching website multiple data sources | |
| TWI520062B (en) | Placing objects on hosts using hard and soft constraints | |
| CN105095317B (en) | Distributed data base service management system | |
| CN108347343B (en) | Policy management method, device and system | |
| CN103647849A (en) | Method and device for migrating businesses and disaster recovery system | |
| CN105245373A (en) | Construction and operation method of container cloud platform system | |
| US10754741B1 (en) | Event-driven replication for migrating computing resources | |
| CN105468720A (en) | Method for integrating distributed data processing systems, corresponding systems and data processing method | |
| US11588698B2 (en) | Pod migration across nodes of a cluster | |
| CN103077034B (en) | hybrid virtualization platform JAVA application migration method and system | |
| WO2017185484A1 (en) | Method and system for internationalized language administration | |
| CN104536805A (en) | Resource providing system and method of virtualization platform | |
| Luckow et al. | Migol: A fault-tolerant service framework for MPI applications in the grid | |
| CN104991826B (en) | A kind of virtual machine deployment method and device | |
| US10917292B2 (en) | Architectural design to enable bidirectional service registration and interaction among clusters | |
| Pachghare | Microservices architecture for cloud computing | |
| CN111294383B (en) | Internet of things service management system | |
| US10896077B2 (en) | Messaging abstraction layer for integration with message oriented middleware platforms | |
| CN111404980B (en) | Data storage method and object storage system | |
| US11522943B1 (en) | System and method for deferring data retrieval | |
| Dimitrov et al. | Low-cost Open Data As-a-Service in the Cloud. | |
| Hongyu et al. | Migrating from Monolithic Applications to Cloud Native Applications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |