On 08/12/2016 13:34, Mārtiņš Jakubovičs wrote: > Hello all, > > I have some confusion with integrating designate in to neutron. > I followed this documentation: > http://docs.openstack.org/draft/networking-guide/config-dns-int.html > > So, if I set dns_domain in neutron.conf, and create new port in tenant > network, which don't have dns_domain set, ports FQDN are hostname + > dns_domain from neutron.conf. This is correct. > > But if I set dns_domain in network, which are different from one I set > in neutron.conf, ports FQDN still use dns_domain from neutron.conf. > Should it work like that? I suppose, that ports FQDN should be hostname > + domain from network's dns_domain. > > For example: > neutron.conf > > [DEFAULT] > dns_domain = cloud.domain.com. > > In network without dns_domain, ports hostname are "test", so ports FQDN: > "test.cloud.domain.com." > In network with dns_domain: "svps.cloud.domain.com.", ports hostname are > same "test", but ports FQDN still creates: "test.cloud.domain.com." > Shouldn't it be "test.svps.cloud.domain.com."?
It should. Did you enable the dns ML2 plugin as well? > Thanks and best regards, > Martins > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack