On 6/18/14, 12:51 PM, "O'CONNELL, MATT" <mo1...@att.com> wrote:
>I think the thinking was the AT&T DNS backend was more desirable >(hardened, load balanced, global, configurable, >non-prototype, 30 second updates), so the idea was to go around the >Designate DNS function and >call the ATT DNS API and use the Designate for customer and other non DNS >function points. I think that is the plan for CORA. I definitely agree that is a plausible approach and Designate should be able to accommodate customers with a running set of authoritative name servers (assuming supported makes/versions of name servers) as you describe. OP’s challenge is greater than keeping their current backend, they have a "database of record” to manage. > In AT&T, we already have a ³DNS bind provisioner and a database of > record² that keeps our DNS authoritative servers updated. My feeling is that eliminating that database would be a better long term solution as it minimizes upgrade complexity. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
