| 2015-09-12 15:48:24 |
Filip Pytloun |
description |
External flag cannot be set during creation or update of virtual DNS via UI. Therefore zone can't be visible outside of assigned IPAM - it seems that virtual DNS zones were external by default before R2.20.
It's possible to set external flag when using add_virtual_dns.py tool:
https://github.com/Juniper/contrail-controller/blob/master/src/dns/scripts/add_virtual_dns.py
But when virtual DNS is updated in UI (eg. IPAMs assigned), external flag is set back to false and zone is no longer visible from outside.
Quick and dirty workaround is to comment out condition in named_config.cc to have all zones as external to keep R2.1 behavior:
https://github.com/Juniper/contrail-controller/blob/master/src/dns/bind/named_config.cc#L264 |
External flag cannot be set during creation or update of virtual DNS via UI. Therefore zone can't be visible outside of assigned IPAM - it seems that virtual DNS zones were external by default before R2.20.
It's possible to set external flag when using add_virtual_dns.py tool:
https://github.com/Juniper/contrail-controller/blob/master/src/dns/scripts/add_virtual_dns.py
But when virtual DNS is updated in UI (eg. IPAMs assigned), external flag is set back to false and zone is no longer visible from outside.
Quick and dirty workaround is to comment out condition in named_config.cc to have all zones as external to keep R2.1 behavior:
https://github.com/Juniper/contrail-controller/blob/master/src/dns/bind/named_config.cc#L264
Bug appears in latest build of OpenContrail R2.20 (built on 2015-09-11). |
|
