Skip to content
Snippets Groups Projects
Commit 68b92244 authored by Scott Solkhon's avatar Scott Solkhon
Browse files

Add also_notifies to Infoblox backend for Designate

Change-Id: Ia02f83dfaaba53f95e373b2b2be3f74cfb7ae578
Closes-Bug: #1855085
parent f52082ab
No related branches found
No related tags found
No related merge requests found
......@@ -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
......
---
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>`__
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment