Site-to-site VPN connectivity
PREREQUISITES: The site-to-site VPN connectivity is available in Sitefinity Cloud with a Dedicated Compute add-on and can be used for projects provisioned on the unified infrastructure. To purchase the Dedicated Compute add-on, contact your Account Manager.
Overview
Websites often depend on services that are not exposed to the internet, for example, internal APIs, identity providers, or line-of-business systems hosted on premises or in another cloud. With the Dedicated Compute add-on, the applications of your Sitefinity Cloud project connect to these services over an encrypted site-to-site VPN connection, without exposing the services publicly.
The Dedicated Compute add-on includes:
- One or more IPsec site-to-site connections between Sitefinity Cloud and the VPN devices in your networks.
- Dedicated compute resources and a dedicated network address range for the applications of your project.
- Network isolation, so that only your project can reach your networks.
- Optional DNS forwarding, so that your applications can call private services by hostname instead of by IP address.
How site-to-site VPN connectivity works
Progress manages an Azure VPN Gateway in the region where your project is hosted. For each of your networks, the Progress Sitefinity team configures a route-based IPsec/IKEv2 connection between this gateway and your VPN device.
The connection carries traffic that originates from Sitefinity Cloud:
- Sitefinity CMS and decoupled Renderer applications of your project run on dedicated compute resources and use a dedicated network address range that Progress assigns to your project.
- Traffic from your applications to the private address ranges of your network is routed through the VPN connection. All other traffic - for example, calls to public APIs - is not affected.
- Requests to your network originate from the address range of your project. Allow this range in your firewall rules.
All environments of your project, for example, Staging and Production, share the same address range, VPN connections, and DNS forwarding rules.
Network isolation
The VPN connections of your project are available only to your project:
- Only the address range of your project has routes to your networks. Other Sitefinity Cloud projects and shared platform services have no route to your networks.
- The private domains that are forwarded to your DNS servers resolve only for your project. Other projects cannot resolve these domains.
Limitations
- The connection is for traffic from your Sitefinity Cloud applications to your network. It does not provide access from your network into Sitefinity Cloud. Your website remains available to visitors through its public domains.
- The connection is not a remote-access VPN. Developer machines and other networks, including other VPNs, cannot connect to your private services through Sitefinity Cloud. To test integrations with private services, deploy your code to one of your Sitefinity Cloud environments. For more information, see Deploy code changes.
- Sitefinity Cloud does not support dynamic routing with Border Gateway Protocol (BGP) or active-active VPN connections.
Requirements for your network
To set up a VPN connection, your network team must provide:
- The public, static IPv4 address of your VPN device.
- The private address ranges in your network that your applications need to reach, in CIDR notation. These ranges must not overlap with the address range of your project.
Your VPN device must support route-based IPsec/IKEv2 VPN connections. Progress provides the following information to your network team:
- The public IP address of the Azure VPN Gateway.
- The address range of your project.
- The pre-shared key of the connection, over a secure channel.
- The IPsec and IKE parameters of the connection.
Your firewall must allow traffic from the address range of your project to the services that your applications call.
DNS forwarding
Private services often have hostnames that only your internal DNS servers can resolve. The IP addresses behind those hostnames can change, for example, when a load balancer is replaced. With DNS forwarding, your applications use the private hostnames directly, the same way they use public ones.
NOTE: DNS forwarding is optional. Without it, your applications can still reach your private services by IP address.
How DNS forwarding works
You specify the private domains to forward and the DNS servers in your network that answer for them. When your applications look up a hostname in one of these domains, or in one of their subdomains, Sitefinity Cloud forwards the query to your DNS servers over the VPN connection:
- Your DNS servers remain the only source of the records. Progress does not host any DNS zones or records for your domains. When you change a record on your DNS servers, the change becomes visible to your applications without a request to Progress.
- Answers are cached for up to 30 seconds.
- All other hostnames, including public domains, resolve the same way as without DNS forwarding.
- Your DNS servers are queried in the order that you specify. The next server is used if the previous one does not respond.
Requirements for your DNS servers
- The DNS servers must have IP addresses inside the private address ranges of your VPN connections.
- Your firewall must allow DNS queries over UDP and TCP port 53 from the address range of your project to your DNS servers. If your DNS servers listen on a different port, specify it in your request.
- The DNS servers must answer queries that arrive over the VPN connection. Some built-in cloud resolvers answer only to clients inside their own virtual network. For example, in Amazon Web Services, if the built-in resolver of the VPC does not answer over the VPN connection, create a Route 53 Resolver inbound endpoint and use its IP addresses.
DNS forwarding limits
| Item | Limit |
|---|---|
| Forwarded domains per project | Up to 20 |
| DNS servers per domain | 1 to 6 |
| Domain format | A fully qualified domain name with at least two labels, for example, corp.example.com. Wildcards are not supported. |
| Reserved domains | Domains used by Sitefinity Cloud platform cannot be forwarded, for example, Microsoft and Azure domains, sitefinity.cloud, and reverse lookup zones. |
Request a VPN connection or a change
To set up a VPN connection, add DNS forwarding, or change an existing configuration:
- Log a support case.
- Specify the Sitefinity Cloud project.
- Provide the details for the change:
- For a new VPN connection, provide the public IP address of your VPN device and your private address ranges.
- For DNS forwarding, provide the private domains and the IP addresses of the DNS servers for each domain, in the order in which they should be queried.
The Progress Sitefinity team configures the change and confirms when it is active. Progress monitors the status of each VPN connection and of the forwarded domains.
RECOMMENDATION: To test connectivity to a private service, use a TCP or HTTPS request to the service, for example, to its health endpoint. Do not rely on
ping. Many networks and load balancers do not respond to ICMP requests, sopingcan fail even when the service is reachable.