|
| 1 | +--- |
| 2 | +title: Azure VMware Solution - DNS forwarding from private cloud to on-premises |
| 3 | +description: Describes how to enable your CloudSimple Private Cloud DNS server to forward lookup of on-premises resources |
| 4 | +author: sharaths-cs |
| 5 | +ms.author: b-shsury |
| 6 | +ms.date: 02/29/2020 |
| 7 | +ms.topic: article |
| 8 | +ms.service: azure-vmware-cloudsimple |
| 9 | +ms.reviewer: cynthn |
| 10 | +manager: dikamath |
| 11 | +--- |
| 12 | + |
| 13 | +# Enable CloudSimple Private Cloud DNS servers to forward DNS lookup of on-premises resources to your DNS servers |
| 14 | + |
| 15 | +Private Cloud DNS servers can forward DNS lookup for any on-premises resources to your DNS servers. Enabling the lookup allows Private Cloud vSphere components to look up any services running in your on-premises environment and communicate with them using fully qualified domain names (FQDN). |
| 16 | + |
| 17 | +## Scenarios |
| 18 | + |
| 19 | +Forwarding DNS lookup for your on-premises DNS server allows you to use your Private Cloud for the following scenarios: |
| 20 | + |
| 21 | +1. Use Private Cloud as a disaster recovery setup for your on-premises VMware solution |
| 22 | +2. Use on-premises Active Directory as an identity source for your Private Cloud vSphere |
| 23 | +3. Use HCX for migrating virtual machines from on-premises to Private Cloud |
| 24 | + |
| 25 | +## Before you begin |
| 26 | + |
| 27 | +A network connection must be present from your Private Cloud network to your on-premises network for DNS forwarding to work. You can set up network connection using: |
| 28 | + |
| 29 | +* [Connect from on-premises to CloudSimple using ExpressRoute](on-premises-connection.md) |
| 30 | +* [Set up a Site-to-Site VPN gateway](https://docs.microsoft.com/azure/vmware-cloudsimple/vpn-gateway#set-up-a-site-to-site-vpn-gateway) |
| 31 | + |
| 32 | +Firewall ports must be opened on this connection for DNS forwarding to work. Ports used are TCP port 53 or UDP port 53. |
| 33 | + |
| 34 | +> [!NOTE] |
| 35 | +> If you are using Site-to-Site VPN, your on-premises DNS server subnet must be added as a part of on-premises prefixes. |
| 36 | +
|
| 37 | +## Request DNS forwarding from Private Cloud to on-premises |
| 38 | + |
| 39 | +To enable DNS forwarding from Private Cloud to on-premises, submit a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest), providing the following information. |
| 40 | + |
| 41 | +* Issue type: **Technical** |
| 42 | +* Subscription: **Subscription where CloudSimple service is deployed** |
| 43 | +* Service: **VMware Solution by CloudSimple** |
| 44 | +* Problem type: **Advisory or How do I...** |
| 45 | +* Problem subtype: **Need help with NW** |
| 46 | +* Provide the domain name of your on-premises domain in the details pane. |
| 47 | +* Provide the list of your on-premises DNS servers to which the lookup will be forwarded from your private cloud in the details pane. |
| 48 | + |
| 49 | +## Next steps |
| 50 | + |
| 51 | +* [Learn more about on-premises firewall configuration](on-premises-firewall-configuration.md) |
| 52 | +* [On-premises DNS server configuration](on-premises-dns-setup.md) |
0 commit comments