Today, to create a record in Designate through the integration with Neutron, we don't use the dns_domain entry in neutron.conf. For the integration with Designate to create a record, the following conditions must be met:
1) The port's network has to have a non blank value in it dns_domain attribute
2) The port has to have a non blank value in it dns_name attribute
3) The zone that corresponds to the network's dns_domain value must exist already in designate under the tenant
What you are proposing is to create the records under <tenantid>.defaultzone.com., where defaultzone is the value of the dns_domain config option in neutron.conf. Am I understanding correctly?
If that is what you are proposing, who is going to create the zone is Designate?
Hi Gregoire,
Today, to create a record in Designate through the integration with Neutron, we don't use the dns_domain entry in neutron.conf. For the integration with Designate to create a record, the following conditions must be met:
1) The port's network has to have a non blank value in it dns_domain attribute
2) The port has to have a non blank value in it dns_name attribute
3) The zone that corresponds to the network's dns_domain value must exist already in designate under the tenant
What you are proposing is to create the records under <tenantid> .defaultzone. com., where defaultzone is the value of the dns_domain config option in neutron.conf. Am I understanding correctly?
If that is what you are proposing, who is going to create the zone is Designate?