openstack
/
kolla-ansible
Code Issues Proposed changes

Add also_notifies to Infoblox backend for Designate 

Change-Id: Ia02f83dfaaba53f95e373b2b2be3f74cfb7ae578
Closes-Bug: #1855085
This commit is contained in:
Scott Solkhon 2019-12-04 10:54:09 +00:00
parent f52082abf7
commit 68b9224425
2 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ansible/roles/designate/templates/pools.yaml.j2
View File

@ -65,6 +65,11 @@
{% for host in designate_backend_infoblox_nameservers.replace(" ", "").split(',') %}
- host: {{ host }}
port: {{ designate_bind_port }}
{% endfor %}
also_notifies:
{% for host in designate_backend_infoblox_nameservers.replace(" ", "").split(',') %}
- host: {{ host }}
port: {{ designate_bind_port }}
{% endfor %}
targets:
- type: infoblox

11
releasenotes/notes/designate-infoblox-backend-also-notifies-0214cc1e51b838b8.yaml Normal file
View File

@ -0,0 +1,11 @@
---
fixes:
- |
Adds configuration to set `also_notifies` within the pools.yaml file
when using the Infoblox backend for Designate.
Pushing a DNS NOTIFY packet to the master does not cause the DNS update
to be propagated onto other nodes within the cluster. This means each node
needs a DNS NOTIFY packet otherwise users may be given a stale DNS record
if they query any worker node. For details please see
`bug 1855085 <https://bugs.launchpad.net/kolla-ansible/+bug/1855085>`__