This section describes how to access OBS using a VPN or Direct Connect connection.
For details about how to create a VPN connection, see Creating a VPN in the Virtual Private Network User Guide.
For details about how to enable Direct Connect, see Getting Started in the Direct Connect User Guide.
The methods of configuring DNS forwarding rules vary depending on OSs. For details, see the DNS software operation guides.
This step uses Bind, a common DNS software, as an example to configure forwarding rules in the UNIX.
In file /etc/named.conf, add the DNS forwarder configuration and set forwarders to the private IP address of the VPC endpoint for accessing DNS.
options { forward only; forwarders{ xx.xx.xx.xx;}; };
To access DNS over a VPN or Direct Connect connection, ensure that traffic from your on-premises data center to DNS is directed to the VPN gateway or Direct Connect gateway.
Configure a permanent route at your on-premises data center and specify the IP address of the Direct Connect or VPN gateway as the next hop for accessing DNS. The following is the example command for configuring such a route:
route -p add xx.xx.xx.xx mask 255.255.255.255 xxx.xxx.xxx.xxx
The CIDR block of the VPC endpoint for accessing OBS is 100.125.0.0/16. To access OBS over a VPN or Direct Connect connection, ensure that traffic from your on-premises data center to OBS is directed to the VPN gateway or Direct Connect gateway.
Configure a permanent route at your on-premises data center and specify the Direct Connect or VPN gateway as the next hop for accessing OBS. The following is the example command for configuring such a route:
route -p add 100.125.0.0 mask 255.255.0.0 xxx.xxx.xxx.xxx
telnet bucket.endpoint
In the command:
Example: telnet bucket.obs.eu-de.otc.t-systems.com