weizhouapache commented on issue #9958: URL: https://github.com/apache/cloudstack/issues/9958#issuecomment-3784630694
> It will add latency. If this really becomes a problem we can potentially cache, but I wouldn't do that for now. Usually these APIs are rather fast. let's not cache them then. > > Does the "account" suffix make it any clearer? Because it's a generic DNS server. Usually these have a single API key/secret and you manage all the zones. CloudStack will then do the logic of accounting and authorization for it's internal users. > > * dns_server > * dns_provider > > Both would work for me. for internal cloud platform, if all vms use the same DNS provider with same credential, it is simple. if we consider a multi-tenant platform where each domain or project represents a customer, it might be useful if each customer manages multiple accounts on various DNS providers/servers. Each account manages multiple DNS zone/domains. > > > the `dns_zone` table stores the information of DNS zones/domains, as well as some cloudstack information, for example ownership or dedication. I added a column `external_reference` to store the additional information of the dns zone on external dns servers. > > The "external_reference" column would have to be populated by the driver. The driver would return this reference once the zone is created. That's what we then use to look up the zone again in that driver. The driver might return the zone name, an ID (integer) or a UUID. That's up to the driver. Yes, make sense. that's what I intend to do: save necessary information in database to speed up operations afterwards. > > I would also make sure that from the start there is DNSSEC support. That you can enable/disable DNSSEC by asking this and the provider can return the KSK and ZSK from the zone. we will consider the use case. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
