Jump to: navigation, search

DNSaaS

Revision as of 20:35, 24 October 2012 by Jcmartin (talk)

Dumping ground for content around OpenStack and DNS-as-a-Service

Comparison of nova-dns and moniker

Google Doc document

Discussion topics

Scope

  • Internal use case : A and PTR records for Fixed IPs and Floating IPs.
  • per instance CNAME ?

Notifications

Today the nova-dns implementation is querying the nova database to detect ip allocation. We should not rely of the nova database for this and should instead add notification in nova to notify of fixed_ips allocation (for example in the place where the current dns code resides)

Zones

nova-dns is creating one zone per tenant, using the tenant id as the name. What zone for floating IP ? Should users be able to specify zone parameters (SOA) ? Suggestion is to use templates and not allow tenant specification.

Records

Today, A record is created for both the instance uuid and instance name or, in the case of nova-dns, just for instance name. What is the right model ?

  • A for uuid and instance name
  • A for uuid, CNAME for instance name (can be changed later by user)

What about PTR ?