Linux with Db2 cluster on Azure Stack Limitation

%3CLINGO-SUB%20id%3D%22lingo-sub-2659974%22%20slang%3D%22en-US%22%3ELinux%20with%20Db2%20cluster%20on%20Azure%20Stack%20Limitation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2659974%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20Linux%20based%20IAAS%20compute%20service%20with%202%20or%20more%20Db2%20and%20GPFS%20nodes%20setup%20in%26nbsp%3B%20Active%20%2F%20Standby%20mode.%20Here%20the%20cluster%20fail-over%20mechanism%20needs%20a%20VIP%20which%20I%20assume%20is%20not%20available%20on%20Azure%20Stack%20Hub.%20In%20the%20Azure%20public%20cloud%2C%20the%20backend%20cluster%20uses%20the%20automatic%20script%20via%20Azure%20CLI%20to%20update%20private%20DNS%20zone%20and%26nbsp%3B%20A%20record%20with%20CNAME%20to%20promote%20the%20Master%20%2F%20Active%20node%20during%20the%20fail-over%20process.%20Is%20that%20correct%20that%20the%20Private%20DNS%20zone%20services%20unavailable%20on%20Azure%20Stack%20Hub%20hence%20we%20can't%20form%20a%20cluster%20like%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20read%20on%20the%20Azure%20Stack%20Hub%20DNS%20article%20that%20we%20have%20an%20internal%20zone%20that's%20used%20for%20infrastructure%20services%20in%20Azure%20Stack%20Hub.%20It's%20Directory%20Service-integrated%20and%20private%20(not%20reachable%20from%20outside%20the%20Azure%20Stack%20Hub%20deployment).%20Can%20this%20be%20used%20as%20private%20DNS%20zone.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20workaround%20or%20solution%20to%20resolve%20this%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2659974%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Stack%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Stack%20Hub%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELInux%20db2%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

We are using Linux based IAAS compute service with 2 or more Db2 and GPFS nodes setup in  Active / Standby mode. Here the cluster fail-over mechanism needs a VIP which I assume is not available on Azure Stack Hub. In the Azure public cloud, the backend cluster uses the automatic script via Azure CLI to update private DNS zone and  A record with CNAME to promote the Master / Active node during the fail-over process. Is that correct that the Private DNS zone services unavailable on Azure Stack Hub hence we can't form a cluster like this.

 

I read on the Azure Stack Hub DNS article that we have an internal zone as azurestack.local that's used for infrastructure services in Azure Stack Hub. It's Directory Service-integrated and private (not reachable from outside the Azure Stack Hub deployment). But this recursive server is used to resolve names of everything except for the "internal private zone" and the external public DNS zone for that Azure Stack Hub deployment.

 

What is the workaround or solution to resolve our issue for private DNS zone.

0 Replies