Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion pages/vpc/reference-content/dns.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -82,4 +82,10 @@ If you experience problems with DNS, try the following steps:

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)

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).
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).

<Message type="important">
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.`

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.
</Message>