global availability
2 TopicsDNS (GTM) best practice for DR
Hi, I need to set DR based on DNS module. After reading few posts and docs all I know that there is plenty approaches that can be implemented. I have little experience with DNS module so I will appreciate any advice what will be optimum solution. Scenario: Two Data Centers: DC1 (main), DR1 (used only when resources in DC not available) Each DC uses non overlapping subnet ranges DCs connected via internal private L2/L3 link All DNS queries will only come from devices inside DCs In each Data Center single BIG-IP DNS device In each DC one host (let's call it Main) requiring DNS resolution for resources it has to access In each DS eight hosts (let's call them Slaves) with separate IP and FQDN - those are not LTMs but standard servers - Generic Host type (monitoring via HTTP monitor) DNS device should perform DNS resolution for FQDNs for Main host DR rules: If any Slave in DC1 is down, DNS request should be resolved to IP of any working Slave If all Slaves in DC1 are down, DNS request should be resolved to IP of any Slave in DR1 What would be best approach? As far as I understand Global Availability method should be used, but at what level: Pool Wide IP Is that better to create on Pool with members from both DSs or separate Pool - one per DC - each containing members from respective DC? Now how to handle condition to return IP of active Slave inside one DC? I guess I need to create as many WideIPs as Slaves (8), or rather one wildcard IP: slave1.vip.site.com, slave2.vip.site.com,...,slave8.vip.site.com or .vip.site.com Then how to perform returning IP of another active Slave when Slave for which DNS request was made is down - inside DC HA? Piotr497Views0likes3CommentsDeclaring disaster when using a BIG-IP DNS Controller driven disaster recovery data center transition
I'm re-asking this question, because we still don't have a solution, and I'm hoping that potential answers may have been missed on the first ask - and it just "feels" to me like someone who is more experienced with Big-IP DNS Controllers (GTMs) would know a way to do this. The original posting is here. In our organization, we're planning on using our GTMs to control disaster recovery - that is, we have a backup data center, which is cold, but we want to spin it up in case of a disaster, and only after it's ready, "flip a switch" to declare a disaster, and at that point have all GTM-managed names start returning the alternate data center's IPs. Up until that switch-flip, all wide IPs should continue to return their original data center IP values (or, potentially, return nothing at all, failing to resolve). My question is, what are the general recommendations for implementation of this manual "switch"? What have people done in terms of creating a construct that is manually controlled, in order to control the GTM's logic for declaring disaster, and affecting a broad array of wide IPs, etc. managed by the GTMs? (sorry, "BIG-IP DNS") It was suggested to simply use global availability - but that doesn't quite fit, because we don't want the alternate data center's IPs returned by the wide IPs until after this "switch" is thrown. Is there some capability at the data center construct level to effect this behavior? Via distributed applications? I'm hoping for some built-in configurable capability, without having to do significant iRule coding or iControl scripting. At that point, it may simply be easier to manage it all via short TTLs and manual imports to our primary DNS servers (which are not GTMs). Thank you for any help!337Views0likes1Comment