How to Manage IPv6 on a Vultr Bare Metal Instance

1. Navigate to Products and click Compute.
2. Click your target instance to open its management page.
3. Navigate to the Settings tab.
4. Click IPv6 on the left navigation menu to view your instance's public IPv6 network information.
5. Enter your IPv6 address in the IP field and a domain in the Reverse DNS field to enable reverse DNS on your instance.

1. Send a GET request to the List Bare Metal Instances endpoint and note the target instance's ID in your output.

   console Copy

   $ curl "https://api.vultr.com/v2/bare-metals" \
     -X GET \
     -H "Authorization: Bearer ${VULTR_API_KEY}"
   

2. Send a GET request to the Bare Metal IPv6 Addresses endpoint to view the instance's IPv6 information.

   console Copy

   $ curl "https://api.vultr.com/v2/bare-metals/{baremetal-id}/ipv6" \
     -X GET \
     -H "Authorization: Bearer ${VULTR_API_KEY}"
   

1. List all Bare Metal instances in your Vultr account and note the target instance's ID.

   console Copy

   $ vultr-cli bare-metal list
   

2. List the instance's IPv6 network information.

   console Copy

   $ vultr-cli bare-metal ipv6 <instance-id>
   

Terraform can enable or disable IPv6 for a Bare Metal instance at creation time. Managing existing IPv6 addresses or reverse DNS records after deployment is not supported directly in Terraform and must be done through the Vultr Customer Portal, API, or CLI.

1. Open your Terraform configuration for the existing Bare Metal instance.

2. Enable IPv6 on the instance and (optionally) set reverse DNS.

   terraform Copy

   # Enable IPv6 on the instance
   resource "vultr_bare_metal_server" "bm1" {
       # ...existing fields (region, plan, os_id, label, etc.)
       enable_ipv6 = true
   }
   
   # Optional: set reverse DNS for the instance's primary IPv6
   # (v6 address is known after the instance exists)
   resource "vultr_reverse_ipv6" "bm1_ptr" {
       ip      = vultr_bare_metal_server.bm1.v6_main_ip
       reverse = "host.example.com."
   }
   

3. Apply the configuration and observe the following output:

   Apply complete! Resources: 0 added, 1 changed, 0 destroyed.