wido commented on issue #9958: URL: https://github.com/apache/cloudstack/issues/9958#issuecomment-3777787494
> > > [@wido](https://github.com/wido), is it ok to change this to an idea-discussion-item? it will remain a valid feature but as of yet seems largely an idea for a distant future improvement and not a direct issue that can be picked up for implementation. > > > > > > Yes and No. I discussed with [@weizhouapache](https://github.com/weizhouapache) in Milan and if I am not mistaken he wants to start working on this in Q1 2026. > > Yes, I've written a draft of design, can you review ? https://cwiki.apache.org/confluence/display/CLOUDSTACK/DNS+Framework+and+Plugins > > [@wido](https://github.com/wido) [@alexandremattioli](https://github.com/alexandremattioli) [@DaanHoogland](https://github.com/DaanHoogland) [@rohityadavcloud](https://github.com/rohityadavcloud) [@sudo87](https://github.com/sudo87) Thank you! This has landed somewhere below in my mailbox, but I have taken a look at your proposal and I think overall it's solid. I do have a few remarks: - Should we store the record contents locally? How do we sync this? Or should we just use the DNS API to fetch all the records and show the zone contents? What if somebody makes a change on the DNS server's end without telling CS? The zone will get out of sync - Maybe we should just store the zone name and an external reference, this could be an ID, UUID, Zone name, etc - Shouldn't zones be unique per DNS server? The DNS server is the Authoritative one here, so should we re-invent the wheel? We could always cache the response locally, but for consistency sake depend on the DNS server. -- 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]
