Skip to content

Commit d280b1d

Browse files
fix(rdb): review bastien
1 parent 5c5e6e0 commit d280b1d

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -80,12 +80,8 @@ You can create new Database Instances to attach to your Private Network, or atta
8080
</Message>
8181

8282
<Message type="note">
83-
Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform/OpenTofu.
84-
85-
There are also internal DNS entries that point to the allocated IP address, which can be used to connect to the database. You can use the following formats:
86-
- `<rdb_instance_name>.<private_network_name>.internal`
87-
- `<rdb_instance_uuid>.<private_network_name>.internal`
88-
- `<rdb_instance_uuid>.<private_network_uuid>.internal`
83+
- Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform/OpenTofu.
84+
- You can also use internal DNS entries that point to the allocated IP address, which can be used to connect to the database. Refer to the [DNS resolution details](/vpc/reference-content/dns/#dns-resolution-details) section of the **Understanding Scaleway DNS for VPC and Private Networks** documentation page for a list of the formats resolved by the DNS service.
8985
</Message>
9086
7. Click **Attach to Private Network** to conclude.
9187

0 commit comments

Comments
 (0)