You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -191,6 +195,10 @@ To attach access management tags to resources in this module, you need the follo
191
195
| <aname="input_dns_instance_name"></a> [dns\_instance\_name](#input\_dns\_instance\_name)| The name to give the provisioned DNS instance. If not set, the module generates a name based on the `prefix` and `name` variables. |`string`|`null`| no |
192
196
| <aname="input_dns_location"></a> [dns\_location](#input\_dns\_location)| The target location or environment for the DNS instance created to host the custom resolver in a hub-spoke DNS resolution topology. Only used if enable\_hub is true and skip\_custom\_resolver\_hub\_creation is false (defaults). |`string`|`"global"`| no |
193
197
| <aname="input_dns_plan"></a> [dns\_plan](#input\_dns\_plan)| The plan for the DNS resource instance created to host the custom resolver in a hub-spoke DNS resolution topology. Only used if enable\_hub is true and skip\_custom\_resolver\_hub\_creation is false (defaults). |`string`|`"standard-dns"`| no |
198
+
| <aname="input_dns_records"></a> [dns\_records](#input\_dns\_records)| List of DNS records to be created. | <pre>list(object({<br/> name = string<br/> type = string<br/> ttl = number<br/> rdata = string<br/> preference = optional(number, null)<br/> service = optional(string, null)<br/> protocol = optional(string, null)<br/> priority = optional(number, null)<br/> weight = optional(number, null)<br/> port = optional(number, null)<br/> }))</pre> |`[]`| no |
199
+
| <aname="input_dns_zone_description"></a> [dns\_zone\_description](#input\_dns\_zone\_description)| The description of the DNS zone. |`string`|`"Default DNS Zone"`| no |
200
+
| <aname="input_dns_zone_label"></a> [dns\_zone\_label](#input\_dns\_zone\_label)| Label associated with the DNS zone. |`string`|`"dns-zone"`| no |
201
+
| <aname="input_dns_zone_name"></a> [dns\_zone\_name](#input\_dns\_zone\_name)| The name of the DNS zone to be created. |`string`|`"slz.com"`| no |
194
202
| <aname="input_enable_hub"></a> [enable\_hub](#input\_enable\_hub)| Indicates whether this VPC is enabled as a DNS name resolution hub. |`bool`|`false`| no |
195
203
| <aname="input_enable_hub_vpc_crn"></a> [enable\_hub\_vpc\_crn](#input\_enable\_hub\_vpc\_crn)| Indicates whether Hub VPC CRN is passed. |`bool`|`false`| no |
196
204
| <aname="input_enable_hub_vpc_id"></a> [enable\_hub\_vpc\_id](#input\_enable\_hub\_vpc\_id)| Indicates whether Hub VPC ID is passed. |`bool`|`false`| no |
@@ -235,6 +243,10 @@ To attach access management tags to resources in this module, you need the follo
235
243
| <aname="output_dns_endpoint_gateways_by_crn"></a> [dns\_endpoint\_gateways\_by\_crn](#output\_dns\_endpoint\_gateways\_by\_crn)| The list of VPEs that are made available for DNS resolution in the created VPC. Only set if enable\_hub is false and enable\_hub\_vpc\_id are true. |
236
244
| <aname="output_dns_endpoint_gateways_by_id"></a> [dns\_endpoint\_gateways\_by\_id](#output\_dns\_endpoint\_gateways\_by\_id)| The list of VPEs that are made available for DNS resolution in the created VPC. Only set if enable\_hub is false and enable\_hub\_vpc\_id are true. |
237
245
| <aname="output_dns_instance_id"></a> [dns\_instance\_id](#output\_dns\_instance\_id)| The ID of the DNS instance. |
246
+
| <aname="output_dns_record_ids"></a> [dns\_record\_ids](#output\_dns\_record\_ids)| List of all the domain resource records. |
247
+
| <aname="output_dns_zone"></a> [dns\_zone](#output\_dns\_zone)| A map representing DNS zone information. |
248
+
| <aname="output_dns_zone_id"></a> [dns\_zone\_id](#output\_dns\_zone\_id)| The ID of the DNS zone. |
249
+
| <aname="output_dns_zone_state"></a> [dns\_zone\_state](#output\_dns\_zone\_state)| The state of the DNS zone. |
238
250
| <aname="output_network_acls"></a> [network\_acls](#output\_network\_acls)| List of shortnames and IDs of network ACLs |
239
251
| <aname="output_public_gateways"></a> [public\_gateways](#output\_public\_gateways)| Map of public gateways by zone |
240
252
| <aname="output_subnet_detail_list"></a> [subnet\_detail\_list](#output\_subnet\_detail\_list)| A list of subnets containing names, CIDR blocks, and zones. |
A simple example demonstrating the provisioning of a `Secure Landing Zone (SLZ) Virtual Private Cloud (VPC)` across two zones (`Zone 1` and `Zone 2`). This setup includes the creation of `Domain Name System (DNS) Zones and Records`, linking the provisioned VPC as a permitted network for DNS operations.
4
+
5
+
The following resources are provisioned by this example:
6
+
7
+
* A new `resource group`, if an existing one is not passed in.
8
+
9
+
* An IBM `Virtual Private Cloud (VPC)` with a publicly exposed subnet.
10
+
11
+
* Private `DNS zone` which can only be resolved from IBM Cloud's private network.
12
+
13
+
*`DNS permitted network` - [DNS Service](https://cloud.ibm.com/docs/dns-svcs/getting-started.html) is a global service, hence the permitted networks (for example, a `VPC`) should be added from any IBM Cloud region. This adds the network to the DNS zone, giving the network access to the zone. Maximum of 10 permitted networks can be added to a `DNS zone`. [Learn more](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-managing-permitted-networks&interface=ui)
14
+
15
+
*`DNS Records` - `DNS Records` make the connection between human-readable names and IP addresses.
16
+
17
+
> Note: To create a `PTR` type record, you must have an existing `A` or `AAAA` record that is not already associated with another `PTR` record. [Learn More](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-managing-dns-records&interface=ui#ptr-record)
0 commit comments