---
title: 'Video: Use CloudConnexa To Create a Site-to-Site Network With Application Domain-Based Routing'
canonical: https://openvpn.net/cloud-docs/videos/use-cases/video--use-cloudconnexa-to-create-a-site-to-site-network-with-application-domain-based-routing/
product: CloudConnexa Docs
description: This video shows application domain-based routing working between two connected sites. CloudConnexa connects an HQ network and a Branch network, allowing the computers in each site to access authorized applications from the other.
keywords: S2S
---

# Video: Use CloudConnexa To Create a Site-to-Site Network With Application Domain-Based Routing

This video demonstrates application domain-based routing in action between two connected sites. CloudConnexa connects an HQ network and a Branch network, allowing the computers in each site to access authorized applications from the other.

|  |  |
| --- | --- |
| **Date published:** | 06/23/2023 |
| **Functionality covered:** | Adding Networks, Deploy Connector on Linux (Ubuntu), enable NAT, enable routing (IP forwarding), application domain-based routing, access groups, adding DNS records, |
| **Description** | Two networks are connected to CloudConnexa. Connector software is installed on a Linux computer running Ubuntu on each network. The Ubuntu computer is set up as a router, allowing for the traffic generated from computers on the network to be routed to CloudConnexa. As application domain-routing is being used, two things need to be ensured: A static route for the CloudConnexa domain routing subnet 100.80/12 and 100.96/11 as the destination and the private IP address of the Linux computer as the target (next hop) needs to be setup in the network's router. > **Note** > > This static route is all that is required. Unlike traditional routing, static routes for each connected network's IP address subnet are unnecessary. All the computers on the network should use the Connector as the DNS Server. The IP address of the DNS server is one before the tunnel IP address of the Connector. For example, if the tunnel IP address of the Connector is 100.96.1.18, then the DNS server IP address is 100.96.1.17. Access Groups can be setup for each Network/Site so that only authorized applications can be accessed between sites. |
| **Length** | 13:48 |

## Related Resources

[Tutorial: Assign DNS servers using DHCP for AWS VPC](https://openvpn.net/cloud-docs/tutorials/configuration-tutorials/connectors/iaas/tutorial--assign-dns-servers-using-dhcp-for-aws-vpc.md)

---

Prev: [Video: Use CloudConnexa for Zero Trust Network Access to a Public SaaS Application](https://openvpn.net/cloud-docs/videos/use-cases/video--use-cloudconnexa-for-zero-trust-network-access-to-a-public-saas-application.md)
Next: [Video: Use CloudConnexa To Create a Site-to-Site Network With IP subnet Routing](https://openvpn.net/cloud-docs/videos/use-cases/video--use-cloudconnexa-to-create-a-site-to-site-network-with-ip-subnet-routing.md)
Index: https://openvpn.net/cloud-docs/llms.txt