Note: this is conditional upon the results of a design/implementation review. This also requires that the designate network attachment be used for zone transfers and rndc requests. This is not relevant for bring your own bind or related to access to these pods from outside the cluster.

The miniDNS and bind9 services are referenced by IP in designate's bind pool and by the worker in rndc requests. As they are part of the running configuration, they need to:

• be consistent and predictable
• in the case of bind, not shift amongst the pods.

Furthermore there isn't an assumption about the deployment type at the moment, so we may not be able to rely on the worker's name or podname to select from the pool of IPs.