)]}'
{"deployment/experimental/designate/designate-mdns-container-puppet.yaml":[{"author":{"_account_id":6681,"name":"Brent Eagles","email":"beagles@redhat.com","username":"beagles"},"change_message_id":"c29ccca47bd3fb93c7807724c6619e511d1a1201","unresolved":false,"context_lines":[{"line_number":119,"context_line":"            - designate::mdns::workers: {get_param: DesignateWorkers}"},{"line_number":120,"context_line":"          - designate::mdns::listen:"},{"line_number":121,"context_line":"            - \u00270.0.0.0:5354\u0027"},{"line_number":122,"context_line":"            - \u0027[::]:5354\u0027"},{"line_number":123,"context_line":"      service_config_settings:"},{"line_number":124,"context_line":"        mysql:"},{"line_number":125,"context_line":"          designate::db::mysql::password: {get_param: DesignatePassword}"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f560f44_3e1dfabd","line":122,"updated":"2020-09-09 16:07:05.000000000","message":"This actually gave me pause because it seems a little weird to me that a component would listen on all IPs. However, going back to Michael J\u0027s presentation to confirm that this is meant to be accessible to \"customer facing DNS server\". So I wonder if:\n - the customer facing DNS server is considered \"in cloud\" and if so, it might be more appropriate that this be on the internal api network; or\n - the customer facing DNS server is \"external\" to the cloud and the mini DNS service is effectively a form of an api in which case this might belong on the external api network","commit_id":"5cfb038cf8980fcebc14447c409b82094d85c3f3"}]}