I am looking at building in some multi-cloud resilience to a deployment, was considering my options and would appreciate any thoughts !
So far, my ideas are: 1) Run both clouds completely independently and have some middleware that pushes the same API command to both PowerDNS instances. I know this is popular in some circles and indeed there are one or two middleware tools already out there, e.g. DNSControl. Clearly this probably has the best resilience options given the complete independence of both sides. But it does require the middleware bit to be bulletproof. 2) My existing PowerDNS is simple, two region backed by PostgreSQL which replicates to standby Postgres in the other region. So theoretically this should be robust for 99.9% of issues apart from complete cloud failure. I am therefore thinking perhaps on the second cloud I should use the PowerDNS Lighning Stream backend (to keep costs down and also to provide resilience against any possible issues with Postgres by using a different backend at the different cloud). And so the question here is if there is an easy way to pull the data in ? Clearly I can give the PowerDNS server read-only permissions to the PostgreSQL backend in the other cloud, but can then automagically pull that data across into Lighning Stream ? Clearly I could build some API scripts but I'm looking for a more "built-in" way, since home-made scripts mean maintenance and debugging. :) 3) Other option I might have missed ? Thanks in advance ! Laura _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
