Enabling a VPC as a DNS hub

Enabling a VPC as a DNS hub in the UI

To enable a VPC as a DNS hub in the IBM Cloud console, follow these steps:

1. From your browser, open the IBM Cloud console and log in to your account.

2. Select the Navigation Menu , then click Infrastructure > Network > VPCs.

3. Click the link of the Virtual Private Cloud that you want to designate as the DNS hub VPC. The Overview page displays.

4. Scroll to the Optional DNS settings section at the end of the page, then expand the DNS hub section and enable the DNS hub switch.

   The Virtual private clouds table now show a DNS-hub tag next to the name of the designated hub VPC.

Enabling a VPC as a DNS hub from the CLI

To enable a VPC as a DNS hub with the CLI, follow these steps:

1. Set up your CLI environment.

2. Log in to your account with the CLI. After you enter the password, the system asks which account and region that you want to use:

   ibmcloud login --sso
   

3. Enable the following feature flag:

   export IBMCLOUD_IS_FEATURE_VPC_DNS_SHARING=true
   

4. Enable a DNS hub for the VPC and specify the resolver type:

   ibmcloud is vpc-create my-cli-vpc [--dns-enable-hub true] [--dns-resolver-type manual] [--dns-resolver-manual-servers  MANUAL_SERVERS | @MANUAL_SERVERS]
   

   Where:

   --dns-enable-hub

   Indicates whether this VPC is enabled as a DNS name resolution hub. One of: false, true.

   --dns-resolver-type

   Indicates the type of the DNS resolver to use. One of: system (default), manual.

   --dns-resolver-manual-servers

   Valid when the resolver type is manual. Configure manual DNS server addresses for the VPC. MANUAL_SERVERS|@MANUAL_SERVERS manual servers in JSON or a JSON file.

Enabling a VPC as a DNS hub with the API

To enable a VPC as a DNS hub with the API, follow these steps:

1. Set up your API environment.

2. To enable an existing VPC as a DNS hub, enter the following command:

   curl -X PATCH -sH "Authorization:${iam_token}" "${vpc_api_endpoint}/v1/vpcs/${vpc_id}?version=${api_version}&generation=2" -d '{"dns": {"enable_hub": true}}'
   

3. To create a hub VPC with default DNS servers, enter the following command:

   curl -X POST -sH "Authorization:${iam_token}" "${vpc_api_endpoint}/v1/vpcs?version=$api_version&generation=2" -d '{"name": "test-hub", "dns": {"enable_hub": true} ,"resource_group": {"id": "'$ResourceGroupId'"}}'
   

For more information, reference the Create a VPC API.

Sample output:

  "classic_access": false,
  "created_at": "2019-01-27T14:39:40Z",
  "crn": "crn:[...]",
  "default_network_acl": {
    "crn": "crn:[...]",
    "href": "https://us-south.iaas.cloud.ibm.com/v1/network_acls/dcfd9b64-9119-48ea-8697-23f9f5fb6bd6",
    "id": "dcfd9b64-9119-48ea-8697-23f9f5fb6bd6",
    "name": "my-network-acl"
  },
  "default_routing_table": {
    "href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/2a842e76-1302-45ad-8b1f-cc7eb0f3868b/routing_tables/f4e65793-1b51-4548-b0c5-769e18d64775",
    "id": "f4e65793-1b51-4548-b0c5-769e18d64775",
    "name": "my-routing-table",
    "resource_type": "routing_table"
  },
  "default_security_group": {
    "crn": "crn:[...]",
    "href": "https://us-south.iaas.cloud.ibm.com/v1/security_groups/95770f87-81f3-4164-8f6d-9f54a3f3a459",
    "id": "95770f87-81f3-4164-8f6d-9f54a3f3a459",
    "name": "my-security-group"
  },
  "href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/f64efe74-a5a2-45c7-b37d-5071d2dd6339",
  "id": "2a842e76-1302-45ad-8b1f-cc7eb0f3868b",
  "name": "my-vpc-2",
  "resource_group": {
    "href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/4bbce614c13444cd8fc5e7e878ef8e21",
    "id": "4bbce614c13444cd8fc5e7e878ef8e21",
    "name": "Default"
  },
  "resource_type": "vpc",
  "status": "available"
}

Enabling a VPC as a DNS hub with Terraform

You can use Terraform to enable a VPC as a DNS hub.

To use Terraform, download the Terraform CLI and configure the IBM Cloud Provider plug-in. For more information, see Getting started with Terraform.

VPC infrastructure services use a regional specific endpoint, which targets us-south by default. If your VPC is created in another region, make sure to target the appropriate region in the provider block of the provider.tf file.

The following example details targeting a region other than the default us-south:

provider "ibm" {
  region = "eu-de"
}

To enable a VPC as a DNS hub:

resource "ibm_is_vpc" "example" {
  name = "example-vpc"
  dns {
		enable_hub = true
		resolver {
			manual_servers {
				type = "manual"
				address = "192.168.3.4"
			}
		}
	}
}