Eduardo Gonzalez fae046ece8 Fixes bind9 restarting when no designate_forwarders_addresses ...

When deploying designate if no designate_forwarders_addresses
is provided, bind9 container keeps restarting due an invalid(empty)
forwarder addresses is set in named.conf

Change-Id: I7d309eb077243435dd2038629074251abec7d3e1
Closes-Bug: #1787092

2018-08-15 08:24:48 +02:00

..

designate-api.json.j2

Support policy.yaml file [part 4]

2018-01-22 01:57:02 +00:00

designate-backend-bind9.json.j2

Ansible-ize OpenStack Designate

2017-01-05 14:34:15 +00:00

designate-central.json.j2

Support policy.yaml file [part 4]

2018-01-22 01:57:02 +00:00

designate-mdns.json.j2

Support policy.yaml file [part 4]

2018-01-22 01:57:02 +00:00

designate-producer.json.j2

Support policy.yaml file [part 4]

2018-01-22 01:57:02 +00:00

designate-sink.json.j2

Support policy.yaml file [part 4]

2018-01-22 01:57:02 +00:00

designate-worker.json.j2

Support policy.yaml file [part 4]

2018-01-22 01:57:02 +00:00

designate.conf.j2

Deprecate auth_uri option

2018-08-07 11:58:23 +05:30

named.conf.j2

Fixes bind9 restarting when no designate_forwarders_addresses

2018-08-15 08:24:48 +02:00

pools.yaml.j2

Change listen for mdns

2017-11-21 15:04:24 +00:00

rndc.conf.j2

Ansible-ize OpenStack Designate

2017-01-05 14:34:15 +00:00

rndc.key.j2

Ansible-ize OpenStack Designate

2017-01-05 14:34:15 +00:00