Update: LITE DNS Deployment (#1753)

Co-authored-by: Sacha Narinx <Springstone@users.noreply.github.com>
Co-authored-by: Jack Tracey <41163455+jtracey93@users.noreply.github.com>

docs/wiki/Whats-new.md

@@ -63,6 +63,8 @@ Here's what's changed in Enterprise Scale/Azure Landing Zones:
 - Updated Microsoft Sentinel onboarding (enablement) using the new mechanism that fixes issues after 1 July 2024. Microsoft Sentinel is enabled by default through the portal accelerator as a best practice - we do not however configure any data connectors, we only enable the service. Should you wish to remove this, you can delete the association from the Azure Portal after deployment from the "Sentinel" feature blade.
 - Fixed a bug that would result in a failed deployment if deploying an Express Route Gateway and Basic Firewall SKU through the portal accelerator.
 - Fixed a bug that would result in a failed deployment for some multi-region Virtual WAN scenarios with identity networks and gateways.
+- Fixed a bug that had ALZ-LITE deployments try to connect DNS zones twice for single regions deployment.
+
 
 ### July 2024
 

eslzArm/eslzArm.json

@@ -7776,7 +7776,7 @@
                         "value": "[parameters('enablePrivateDnsZonesSecondary')]"
                     },
                     "enableHubSecondary": {
-                        "value": "[parameters('enableHubSecondary')]"
+                        "value": "[parameters('enableSecondaryRegion')]"
                     }
                 }
             }