Skip to content

Commit bbb3b94

Browse files
authored
fix(vpc): add info about cli dns (#4984)
1 parent 0b962dc commit bbb3b94

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

pages/vpc/reference-content/dns.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,4 +82,10 @@ If you experience problems with DNS, try the following steps:
8282

8383
4. **Check whether you are using Network Manager**: DNS does not work out of the box for Linux distributions using Network Managed, such as **RockyLinux**. Find out how to resolve this problem [on our troubleshooting page](/vpc/troubleshooting/private-dns-dhcp-not-working/#distributions-running-network-manager)
8484

85-
If you are still having problems reaching a resource attached to a Private Network via its hostname, [open a support ticket](https://console.scaleway.com/support).
85+
If you are still having problems reaching a resource attached to a Private Network via its hostname, [open a support ticket](https://console.scaleway.com/support).
86+
87+
<Message type="important">
88+
It is possible to use the [Scaleway CLI's Domains and DNS commands](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/dns.md) to read and edit DNS zones for VPC Private Networks. The format for these zones is `<Private_Network_ID>.<VPC_ID>.privatedns.`. For example to list the records of a Private Network's DNS zone, use `scw dns record list <Private_Network_ID>.<VPC_ID>.privatedns.`
89+
90+
However, using the CLI to view and manage your VPC's DNS records is **not officially supported by Scaleway**. It should only be attempted by advanced users, at their own risk. VPC DNS is designed to be fully managed by Scaleway: using the CLI to manually remove or modify records that have been auto-created may result in a broken DNS service on your VPC.
91+
</Message>

0 commit comments

Comments
 (0)