Ask Your Question

# Revision history [back]

### Designate: How is multitenancy achieved and how to use designate as nameserver in OpenStack VMs

I am running OpenStack Liberty and was able to get Designate running (I had no luck with the Designate's dashboard extension). I am using Bind9 as backend under Ubuntu 14.04.

I require automatic DNS resolution for VMs within each tenant and Designate's sink service seems to be a perfect candidate to solve the problem. I must admit, that I have many questions in my mind and maybe I got everything wrong with Designate.

1. Multitenancy: How is multitenancy achieved in Designate? Has each tenant its private Bind server? Is there a single central Bind server that is shared among the tenants? How is multitenancy working in the single case?
2. Designate in OpenStack VMs: How can I configure Neutron or Nova in that way that the VMs get their tenant-specific Nameserver for DNS resolution? Is this possible with the current implementation state of Designate? Are there any tutorials available?
3. Designate Sink: The configuration for the Designate Sink Service requires a domain_id. Does this mean,that all IPs and VMs' FQDN from all tenats are stored within this common domain or is this domain created for each tenant? In the central case, how is multitenancy achieved? Each tenant should only see its own IPs. Sharing Neutron's Floating IPs seems to be a nice way, but would that not cause name collisions? All VMs in each tenant get the same domain name. When the get the same hostname, we have one FQDN resolving to two different IPs.

I know, it's a lot... Maybe someone can help me in understanding Designate's principle. This service is really cool and I want to use it.

### Designate: How is multitenancy achieved and how to use designate as nameserver in OpenStack VMs

I am running OpenStack Liberty and was able to get Designate running (I had no luck with the Designate's dashboard extension). I am using Bind9 as backend under Ubuntu 14.04.

I require automatic DNS resolution for VMs within each tenant and Designate's sink service seems to be a perfect candidate to solve the problem. I must admit, that I have many questions in my mind and maybe I got everything wrong with Designate.

1. Multitenancy: How is multitenancy achieved in Designate? Has each tenant its private Bind server? Is there a single central Bind server that is shared among the tenants? How is multitenancy working in the single case?
2. Designate in OpenStack VMs: How can I configure Neutron or Nova in that way that the VMs get their tenant-specific Nameserver for DNS resolution? Is this possible with the current implementation state of Designate? Are there any tutorials available?
3. Designate Sink: The configuration for the Designate Sink Service requires a domain_id. Does this mean,that all IPs and VMs' FQDN from all tenats tenants are stored within this common domain or is this domain created for each tenant? In the central case, how is multitenancy achieved? Each tenant should only see its own IPs. Sharing Neutron's Floating IPs seems to be a nice way, but would that not cause name collisions? All VMs in each tenant get the same domain name. When the get the same hostname, we have one FQDN resolving to two different IPs.

I know, it's a lot... Maybe someone can help me in understanding Designate's principle. This service is really cool and I want to use it.

### Designate: How is multitenancy achieved and how to use designate as nameserver in OpenStack VMs

I am running OpenStack Liberty and was able to get Designate running (I had no luck with the Designate's dashboard extension). I am using Bind9 as backend under Ubuntu 14.04.

I require automatic DNS resolution for VMs within each tenant and Designate's sink service seems to be a perfect candidate to solve the problem. I must admit, that I have many questions in my mind and maybe I got everything wrong with Designate.

1. Multitenancy: How is multitenancy achieved in Designate? Has each tenant its private Bind server? Is there a single central Bind server that is shared among the tenants? How is multitenancy working in the single case?
2. Designate in OpenStack VMs: How can I configure Neutron or Nova in that way that the VMs get their tenant-specific Nameserver for DNS resolution? Is this possible with the current implementation state of Designate? Are there any tutorials available?
3. Designate Sink: The configuration for the Designate Sink Service requires a domain_id. Does this mean,that all IPs and VMs' FQDN from all tenants are stored within this common domain or is this domain created for each tenant? In the central case, how is multitenancy achieved? Each tenant should only see its own IPs. Sharing Neutron's Floating IPs seems to be a nice way, but would that not cause name collisions? All VMs in each tenant get the same domain name. When the they get the same hostname, we have one FQDN resolving to two different IPs.

I know, it's a lot... Maybe someone can help me in understanding Designate's principle. This service is really cool and I want to use it.