cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6998) Integration with external DNS Provider (like Bind, PowerDNS)
Date Thu, 21 Aug 2014 10:21:11 GMT


ASF subversion and git services commented on CLOUDSTACK-6998:

Commit 233445ed68e3f903367e14a277ec2a5de9597b52 in cloudstack's branch refs/heads/master from
[;h=233445e ]

CLOUDSTACK-6998: GloboDNS, Integration with external DNS Provider

This is a feature to handle DNS entries by means of an external DNS Provider,
such as Bind. These entries include DNS domains and reverse domains, VM records
and reverse records.

For a complete description, please refer to the design document available at

For the discussion about this feature on the dev mailing list, please refer to

- new Network Service Provider called GloboDNS
- new Network Element to manage network domains and VM records (entries) on an external API
- new Network Resource to communicate with GloboDNS (open source)
- new API command to add DNS server
- new global option to determine if this provider should override VM entries on external DNS
- changes in UI to include GloboDNS in Providers list

Signed-off-by: Rohit Yadav <>

> Integration with external DNS Provider (like Bind, PowerDNS)
> ------------------------------------------------------------
>                 Key: CLOUDSTACK-6998
>                 URL:
>             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
>            Assignee: Rohit Yadav
>              Labels: dns, features
>             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

This message was sent by Atlassian JIRA

View raw message