ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
SUMMARY
My idea is as follows:
- A new framework is addedd: Authorative DNS
- This allows for admins and end-users to manage DNS zones
- Different providers implement different APIs, examples:
These drivers will support various functionality and advertise their capabilities or limitations:
- Create and delete zones
- Manage records in these zones
- Advertise which record types are supported
- Limit the amount of records in a zone (if any)
- Set a limitation on how low the TTL can be
Per account and domain we can then set limits:
- Amount of zones to create
- Amount of creates per zone
This would allow for a couple of things:
- End-users can manage their DNS via the same API as they manage their cloud resources
- End-users can manage DNS via the CloudStack UI
- We can directly create public DNS records for newly created instances
- You assign a DNS zone to a CloudStack zone
- Upon VM creation a record is created
i-xx-yy-vm.myzone.tld A 1.2.3.4
i-xx-yy-vm.myzone.tld AAAA 2001:db8:af31::61
- When the VM is removed the DNS records are removed
- Console Proxy and Secondary Storage VMs can point to a working hostname instead of IP-address
- We can then also support IPv6 for the CP and SS
- We can set the PTR (Reverse DNS) record for a VM after boot
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
SUMMARY
My idea is as follows:
These drivers will support various functionality and advertise their capabilities or limitations:
Per account and domain we can then set limits:
This would allow for a couple of things:
i-xx-yy-vm.myzone.tld A 1.2.3.4
i-xx-yy-vm.myzone.tld AAAA 2001:db8:af31::61