<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Lucky,<div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">The backend is going to determine what can be done and I am not seeing that below. There are many option depending on how complex the changes are in that zone in the DR site. If you have a similar IP subnet scheme in a /23 or /24 with the same 4th octet and the backend is a database, then a script could easily zap the A records in that zone. If the number of hosts at the DR site is relatively small, then a script could create/update /etc/hosts entries on the PDNS server and then serve that via "etc-hosts-file=/etc/hosts”.</div></div></blockquote><br class=""></div><div>What you could do as well, is put a dnsdist instance in front of your NS. You could then have two pdns instances, one hosting the “main version” of the domains, one hosting the DR version. Define both as a separate pool in dnsdist, sending all traffic by default to main one.</div><div><br class=""></div><div>Then, when a domain needs to be moved to the DR, you could then change the dnsdist config to use the “DR” pool for that domain.</div><div><br class=""></div><div>Regards,</div><div><br class=""></div><div>Frank Louwers</div><div>PowerDNS Consultant @ Kiwazo</div><br class=""></div><div class=""></div></body></html>