[jira] [Created] (CLOUDSTACK-6998) Integration with external DNS Provider (like Bind, PowerDNS)

["Silvano Buback (JIRA)" <ji...@apache.org>]

Silvano Buback created CLOUDSTACK-6998:
------------------------------------------

             Summary: Integration with external DNS Provider (like Bind, PowerDNS)
                 Key: CLOUDSTACK-6998
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6998
             Project: CloudStack
          Issue Type: New Feature
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.3.0
            Reporter: Silvano Buback
             Fix For: 4.5.0


When deploying Advanced Networks, Virtual Routers are used to isolate networks and provide DNS service for all machines inside each network. While this approach is better for keeping networks more secure and self-contained, it imposes a challenge when machines need to translate names that belong to machines from another network, i.e. machine in network A needs to find the IP address of a machine in network B.

A common solution for this problem is to make sure the Virtual Router from network B has its name translated from network A, but this does not scale to a corporate network, where you need to translate domain names of every machine from every network.

We tackled this problem by using a centralized DNS server, which is external to all networks in Cloudstack. That way, every machine is registered in that server and every other machine can translate its name by accessing that server as well. This server can run any known enterprise DNS server, such as Bind or PowerDNS, and provide its services through an external API.

This proposal includes both a DNS API to be run in a DNS server and a plugin designed for integrating virtual machines and virtual networks in Cloudstack with DNS API.

I put design document in wiki https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI.





--
This message was sent by Atlassian JIRA
(v6.2#6252)