fix(vpc): add info

Author: RoRoJ

menu/navigation.json

@@ -2923,17 +2923,21 @@
               },
               {
                 "items": [
-                  {
-                    "label": "Understanding VPC GA and migration",
-                    "slug": "vpc-migration"
-                  },
                   {
                     "label": "Understanding routing",
                     "slug": "understanding-routing"
                   },
+                  {
+                    "label": "Understanding DNS",
+                    "slug": "dns"
+                  },
                   {
                     "label": "Getting the most from Private Networks",
                     "slug": "getting-most-private-networks"
+                  },
+                  {
+                    "label": "Understanding VPC GA and migration",
+                    "slug": "vpc-migration"
                   }
                 ],
                 "label": "Additional Content",

network/vpc/reference-content/getting-most-private-networks.mdx

@@ -69,6 +69,10 @@ Further, when you attach a resource to a Private Network and specify a reserved
 
 Using reserved IP addresses is ideal to ensure that certain IP addresses are never released into the general pool and kept for certain critical resources with fixed IP requirements, even when that resource is detached from the Private Network, or when migrating between resources. Reserved IP addresses may also be useful where your Private Network is extending or integrating with external networks, or to assign addresses to virtual machines hosted on Elastic Metal servers via Proxmox.
 
+### DNS and hostnames
+
+Scaleway Private Networks benefit from managed internal DNS. This allows the resolution of resources' **hostnames** on the Private Network, into their private IP addresses. See our documentation on [Understanding Scaleway DNS](/network/vpc/reference-content/dns/) for full details of how to effectively use hostname addressing and the capabilities of Private Networks' DNS resolver service.
+
 ## Removing public IPs from resources
 
 We strongly recommend that you disable public connectivity on all of your Scaleway resources, unless it is absolutely required. It is preferable to attach resources to Private Networks wherever possible, and direct all traffic to the resource's private IP address on that network. This ensures optimal security, reduced cost and enhanced latency. Find out more in our documentation about [public connectivity best practices](/network/ipam/reference-content/public-connectivity-best-practices).