Oh - Nice, I've not seen these repositories before.

I'll add them to our related links docs section for easier discovery.

Also - Slightly Off Topic - At the Summit in Paris, I was speaking with one of the Neutron developers who has some pretty solid Neutron + Designate integration, I'm hoping to catch him on IRC during the week to see how we can move it forward :)

Thanks,
Kiall

On 2014-11-08 19:22, Yuriy Brodskiy wrote:
For our use-case we only add fip records into external DNS.
Whenever a floating ip(fip) is created via neutron, a DNS domain for
the tenant will be created if doesnt exist and a DNS A record will be
created in the tenant dns domain. 

https://github.com/Symantec/neutron-designate-fip-plugin [4]

To make sure that VMs have correct domain information, we populate
metadata with designate information of the tenant and that is used via
cloud-init.

https://github.com/Symantec/nova-designate-dns-plugin [5]

On Sat, Nov 8, 2014 at 10:25 AM, mad Engineer
<[email protected] [6]> wrote:

Hi,
    Is there any way to use external dns server for instances?
All instances are currently getting instance name as hostname and
with in openstack network its working and i manually add entries in
corporate BIND to make it work for outside openstack.

Is it possible to use an an external DNS server as nameserver for
all instance and automatically add hostnames to that server.

Thanks
_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]
Post to     : [email protected] [2]
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [3]


_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to