A network domain in Database Autonomy Service (DAS) identifies the third-party networks that are connected to DAS through DBGateway.
When DBGateway is deployed in centralized mode, you must select a network domain to identify the network environment of the instance that has DBGateway deployed. DBGateway instances in the same network domain support load balancing and disaster recovery.
How network domains affect connectivity
In centralized mode, assigning the correct network domain to each isolated network is required for successful database connections. The following table shows the impact of correct versus incorrect configuration:
| Configuration | What happens |
|---|---|
| Each isolated network has its own network domain | DBGateway routes traffic within the correct network. Instances connect successfully. |
| Two isolated networks share the same network domain | DBGateway deployed in one network routes requests to database instances in the other network. All affected database connections fail. |
Use cases
In most cases, when on-premises databases connect to DAS over the Internet using DBGateway, DAS automatically creates a default network domain. This covers the common single-site setup and requires no manual action.
Create a network domain manually when using Centralized DBGateway in either of these situations:
A newly connected on-premises database cannot communicate with an existing database already connected to DAS — the two databases reside in isolated networks and need separate network domains.
You need to segment the network by location, for example, to separate databases across different cities.