[Neutron] [Designate] Private / Internal DNS Zones with custom records for i.e. service discovery

Christian Rohmann christian.rohmann at inovex.de
Thu Mar 18 09:46:59 UTC 2021

Hey Openstack-Discuss,

apart from the standardized and auto-created records for ports / 
floating-ips and instances 
(https://docs.openstack.org/neutron/latest/admin/config-dns-int.html) - 
is there any way to allow users to add their own records which then only 
resolve internally?

The Neutron API (https://docs.openstack.org/api-ref/network/v2/#id52) 
seems to be all about the resources it manages, so no additional or 
custom records there. Looking at the Designate API 
is does not seem to be an option to mark a zone as "internal" or 
"private". But maybe there is another way to add records to the internal 

I am thinking of an only internally resolvable / valid DNS zone carrying 
records for i.e. service discovery / cluster forming.
There are more and more tools just looking up a DNS records to find 
cluster members ...

* ElasticSearch: 
* Hazelcast: 
* HiveMQ: 
* RabbitMQ: 

and with Kubernetes and the headless service concept there are more 
tools (ab)using DNS for this every week.
So having internal dns zones which only resolve within the project would 
be really helpful.

The hyperscalers call this feature

* AWS "Private hosted zones" 

* Azure "Private DNS" 
* GCP "Private zone" 
* Alibaba Cloud "DNS PrivateZone" 



More information about the openstack-discuss mailing list