Deploy DNS Proxy

DNS Proxy is available through an Azure app hosted by TitanHQ on its Azure Directory. The current version of DNS Proxy is 3.01.

To deploy DNS Proxy:

Prerequisites for Deploying DNS Proxy into your Resource Group

The following are prerequisites you should consider before deploying DNS proxy into your Resource Group. For further information, you can read Manage Azure resource groups by using the Azure portal .

  • DNS Proxy must be launched into an existing resource group with an existing Azure Virtual Network (VNet) and Network Security Group (NSG).

  • The subnet that DNS Proxy is launched into must have an NSG associated with it.

  • To access the UI, HTTPS or HTTP ports must be open on the VNet.

  • By default, ports 80, 443 and 7780 are open on the NSG. Ports 80 and 443 are required to access the DNS Proxy UI. Port 7780 Is needed to communicate with other DNS Proxies in your Azure estate.

  • Azure Command-Line Interface (CLI) must be installed on the machine that runs the DNS Proxy installer. See https://docs.microsoft.com/en-us/cli/azure/install-azure-cli .

  • You must have a default ssh key in your ~/.ssh folder (C:\Users[username].ssh). If you do not have one, it can be generated in PowerShell with the following command: "ssh-keygen -m PEM -t rsa -b 4096".

Make the Azure App Available on the Target Tenant

Follow the steps below to make the app available on the target tenant:

  1. Go to your Microsoft Azure Portal > Azure Active Directory. This link will take you directly there: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview .

  2. Copy your Tenant ID from the Tenant information panel:

  3. Replace [TENANT-ID] in the URL below with your Tenant ID copied in Step 2 above.

    https://login.microsoftonline.com/[TENANT-ID]/oauth2/authorize?client_id=a248315f-7d19-41c2-8acb-2619857956c9&response_type=code&redirect_uri=https%3A%2F%2Fwww.microsoft.com%2F

  4. Open a new browser tab, paste the modified URL from the previous step and navigate to the page.

  5. If the following Permissions requested window displays, check Consent on behalf of your organization and click Accept. You may be redirected to a generic Microsoft page that you can close.

    Important

    This makes the DNSProxy-Distribution-Prod app available to your tenant.

  6. From the portal menu in the top left, select Resource groups and navigate to the resource group into which you want to launch DNS Proxy.

  7. Open the Role assignments tab and click Add role assignment.

    • From the Role menu, select Contributor.

    • From the Assign access to menu, select User, group or service principal.

    • From the Select menu, select DNSProxy-Distribution-Prod.

    • Click Save.

  8. Click Save.

Deploy DNS Proxy into your Resource Group

Please make sure that you have read the prerequisites before deploying DNS proxy into your resource group.

  1. Download the Azure DNS Proxy installer here (DnsProxy-AzureInstaller.exe). The current version of DNS Proxy is 3.01.

    Important

    As a best practice, delete the DnsProxy-AzureInstaller.exe install file after deployment.

  2. Run the DnsProxy-AzureInstaller.exe install file.

  3. A command line interface opens and you will be prompted to enter the following:

    • Your Tenant ID.

    • A number to append to the virtual machine name. For example, if the virtual machine name is TitanHQ-DNSProxy-VM and you enter 1, the virtual machine name will be TitanHQ-DNSProxy-VM-1.

      Note

      If you are deploying more than one server, you can enter 2 for the second one, and so on. The servers will be created with the number appended at the end.

    • The name of the (existing) target resource group DNS Proxy will be launched into.

    • The name of the target VNet.

    • The name of the (existing) target Subnet.

Once the details above have been supplied, the application will deploy DNS Proxy. It normally takes 5 - 7 minutes for the deployment to complete. When the provisioning process is complete, you will see the following resources in the target resource group:

DNS Proxy deployment is now complete.

As a best practice, delete the DnsProxy-AzureInstaller.exe install file after deployment.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article