Help Center/ VPC Endpoint/ User Guide (Kuala Lumpur Region)/ Getting Started/ Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks/ Step 1: Create a VPC Endpoint for Connecting to DNS
Updated on 2023-12-20 GMT+08:00
View PDF
Share

Step 1: Create a VPC Endpoint for Connecting to DNS

Scenarios

This section describes how to create a VPC endpoint for accessing a DNS server, in order to forward requests of resolving OBS domain names.

Prerequisites

The required VPC endpoint service is available.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Click Service List and choose Networking > VPC Endpoint.
  1. On the VPC Endpoints page, click Create VPC Endpoint.

    The Create VPC Endpoint page is displayed.

  2. Configure VPC endpoint parameters.
    Table 1 VPC endpoint parameters

    Parameter

    Description

    Region

    Specifies the region where the VPC endpoint is to be located.

    Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.

    Service Category

    There are two options:

    • Cloud services: Select this value if the target VPC endpoint service is a cloud service.
    • Find a service by name: Select this value if the target VPC endpoint service is a private service of your own.

    In this example, select Cloud services.

    Service List

    This parameter is available only when you select Cloud services for Service Category.

    The VPC endpoint service has been created by the O&M personnel and you can directly use it.

    Select the VPC endpoint service for DNS.

    Create a Private Domain Name

    If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name.

    This parameter is mandatory when the VPC endpoint will be used to access an interface VPC endpoint service.

    VPC

    Specifies the VPC where the VPC endpoint is to be deployed.

    Subnet

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    Specifies the subnet where the VPC endpoint is to be deployed.

    Tag

    This parameter is optional.

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 10 tags to each VPC endpoint.

    Tag keys and values must meet requirements listed in Table 2.
    Table 2 Tag requirements for VPC endpoints

    Parameter

    Requirement

    Tag key
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 characters.
    • Cannot start or end with a space or contain special characters =*<>\,|/

    Tag value
    • Cannot be left blank.
    • Can contain a maximum of 43 characters.
    • Cannot start or end with a space or contain special characters =*<>\,|/
  3. Confirm the specifications and click Create Now.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
  4. Click Back to VPC Endpoint List after the task is submitted.

    If the status of the VPC endpoint changes to Accepted, the VPC endpoint for connecting to the VPC endpoint service for DNS is created.

  5. In the VPC endpoint list, click before the target VPC endpoint to view its details.

    After a VPC endpoint for accessing interface VPC endpoint services is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name during creation.