This feature should provide a framework for synchronizing data to and from PowerDNS servers through the use of task queuing. This framework should be designed with a future goal in mind of handling not just data related to authoritative DNS zones, but also server metrics and configuration for all three servers available in the PowerDNS suite.
Furthermore, where applicable, the synchronized entity schema should allow for the storage of synchronization flags to indicate what directions are allowed to produce updates to data mismatch scenarios. For example, the ability to flag most records of a zone as outgoing updates only meaning that only changes in this application will be pushed to PowerDNS servers but changes on the server will not be pulled into this application. Conversely, a small sub-set of records could be flagged to allow for both ingress and egress updates which would support the use of the RFC 2136 implementation for DNS updates.
This system should also include a Go binary that can act as a Celery scheduling proxy for incoming DNS messages on UDP/53.
This feature should provide a framework for synchronizing data to and from PowerDNS servers through the use of task queuing. This framework should be designed with a future goal in mind of handling not just data related to authoritative DNS zones, but also server metrics and configuration for all three servers available in the PowerDNS suite.
Furthermore, where applicable, the synchronized entity schema should allow for the storage of synchronization flags to indicate what directions are allowed to produce updates to data mismatch scenarios. For example, the ability to flag most records of a zone as outgoing updates only meaning that only changes in this application will be pushed to PowerDNS servers but changes on the server will not be pulled into this application. Conversely, a small sub-set of records could be flagged to allow for both ingress and egress updates which would support the use of the RFC 2136 implementation for DNS updates.
This system should also include a Go binary that can act as a Celery scheduling proxy for incoming DNS messages on UDP/53.