Hi Erik, At Globo, network domain always have exclusive names, based on zone name and vlan number, so there is no conflict.
At the point of view of plugin, if domain exists it will be used. If a record exists, it will be overwritten. When you delete a network, dns domain will be deleted too, doesn't matter if it exists before network creation or not. Records in this domain will be removed too. []'s, Silvano Buback On Fri, Jun 13, 2014 at 3:52 AM, Erik Weber <terbol...@gmail.com> wrote: > On Fri, Jun 13, 2014 at 7:21 AM, Silvano Nogueira Buback < > silv...@corp.globo.com> wrote: > > > Hi there, > > > > > > I work at Globo.com, a media company in Brazil. Here we use a cloudstack > > private network with an advanced zone setup (isolated vlans). > > > > For some couple of reasons, the name of virtual machine needs to be > > available not only on virtual router network context, but on our internal > > DNS servers. > > > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind > server) > > thru an open source API written by globo.com called DNSAPI. More info at > > https://github.com/globocom/Dns-Api. > > > > To make this implementation of DNS provider, we based our plugin on > > "dns-notifier", but we had to add more classes for our implementation. > > > > * DnsAPINetworkDAO to manage the networkDomain for each network. > > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > > * DnsAPIElement, this class implements the provider itself. > > * DnsAPIResource, implements all communications with DNSAPI > > (ServerResource). > > > > Besides this classes, another one was necessary to the call to > > DnsAPIResource and return the answer, and one API command was created to > > configure the provider in Zone. > > > > Above a video that show you how everything was integrated. > > > > https://www.youtube.com/watch?v=fAB53T_NZMI > > > > We really appreciate all your comments about our implementation, > > > > > replying in the right thread this time :-) > > I like the idea and the fact that the backend is available as open source. > That should make it pretty straight forward to convert it to other DNS > solutions (PowerDNS for me). > > - What happens if there is a conflict? > - Does it require / assume that the domain is non-existant on the DNS > servers? > - How does cleanup handle additional records added outside of CloudStack? > > -- > Erik Weber >
