Skip to content

Commit 329964d

Browse files
committed
fix(docs): review
1 parent db79c55 commit 329964d

File tree

9 files changed

+63
-137
lines changed

9 files changed

+63
-137
lines changed

pages/ipam/reference-content/ipv6.mdx

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ content:
77
paragraph: Learn about IPv6 at Scaleway - configuration, routing, security, and best practices for seamless integration and scalability. Transition smoothly with our step-by-step guide.
88
tags: ipv6 ipv4 support
99
dates:
10-
validation: 2024-11-18
10+
validation: 2025-05-27
1111
posted: 2024-11-18
1212
categories:
1313
- network
@@ -27,7 +27,7 @@ This is where **IPv6** comes in, the most recent version of the IP protocol. Eac
2727

2828
Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. This can also be notated as `2001:DB8::3:0:1FF:0:2E`.
2929

30-
As well as providing a much bigger address space, IPv6 also includes a built-in network security layer (IPsec), as well as improved features for reliability and efficiency, like autoconfiguration, streamlined headers and improved Quality of Service (QoS). All leading to a more robust and secure protocol, that can potentially offer lower latency and faster data transfer.
30+
As well as providing a much bigger address space, IPv6 also includes a built-in network security layer (IPsec), as well as improved features for reliability and efficiency, like auto-configuration, streamlined headers and improved Quality of Service (QoS). All leading to a more robust and secure protocol, that can potentially offer lower latency and faster data transfer.
3131

3232
## IPv6-compatible products
3333

@@ -54,6 +54,7 @@ Go further with Instances and IPv6 in the following documentation:
5454
- [Using routed IPs](/instances/api-cli/using-routed-ips/)
5555
- Fix lost IPv6 connectivity when migrating to routed IP for old [Debian Buster images](/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster/) or [RHEL images](/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance/)
5656
- [Fix DNS resolution with a routed IPv6-only setup on Debian Bullseye](/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye/)
57+
- [Setting a reverse IPv6 DNS record via the IPAM API](/ipam/api-cli/set-ip-reverse/)
5758

5859
### Elastic Metal and IPv6
5960

@@ -113,11 +114,15 @@ Go further with IPv6 and Load Balancers with the following documentation:
113114

114115
VPC and Private Networks are compatible with IPv6.
115116

116-
- Private Networks are dual-stack, meaning each Private Network necessarily has both an IPv4 and and an IPv6 CIDR blocks.
117+
- Private Networks are dual-stack, meaning each Private Network necessarily has both IPv4 and and IPv6 CIDR blocks.
117118
- For IPv6, this is a `/64` block, automatically created by Scaleway, guaranteed to be unique within the VPC and not overlapping with any of your other Private Networks.
118119
- All IPv6-compatible resources will automatically receive an IPv6 address when they join a Private Network, in addition to an IPv4 address.
119120
- This address can be auto-allocated from the pool, or specified by the user via a [reserved IP address](/ipam/how-to/reserve-ip/)
120-
- Scaleway VPC routing supports both IPv4 and IPv6 protocols. [Managed routes](/vpc/how-to/manage-routing/#how-to-generate-a-managed-route) to Private Networks are simultaneously generated for both IPV4 and IPV6, and both are added to the VPC's route table. Note that auto-generated managed routes to Public Gateways are only created in IPv4, since Public Gateways are not yet IPv6-compatible. [Custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) are only created for the IP type specified during the creation process.
121+
- Scaleway VPC routing supports both IPv4 and IPv6 protocols. [Managed routes](/vpc/how-to/manage-routing/#how-to-generate-a-managed-route) to Private Networks are simultaneously generated for both IPv4 and IPv6, and both are added to the VPC's route table. Note that auto-generated managed routes to Public Gateways are only created in IPv4, since Public Gateways are not yet IPv6-compatible. [Custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) are only created for the IP type specified during the creation process.
122+
123+
### InterLink and IPv6
124+
125+
InterLink supports both IPv4 and IPv6 traffic. Each InterLink entails two BGP sessions: one for IPv4 and one of IPv6, whereby routing information is dynamically exchanged between the external router and the Scaleway VPC vRouter. When creating a [routing policy](/interlink/concepts/#routing-policy) for your InterLink, you must separately specify the IPv4 and IPv6 routes to propagate.
121126

122127
### Serverless Functions and Containers and IPv6
123128

pages/load-balancer/how-to/add-certificate.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
meta:
33
title: How to add a certificate to your Load Balancer
4-
description: This page explains how to add a certificate to your Load Balancer
4+
description: Learn how to add an SSL/TLS certificate to your Scaleway Load Balancer to enable secure HTTPS traffic for your services
55
content:
66
h1: How to add a certificate to your Load Balancer
7-
paragraph: This page explains how to add a certificate to your Load Balancer
7+
paragraph: Learn how to add an SSL/TLS certificate to your Scaleway Load Balancer to enable secure HTTPS traffic for your services
88
dates:
9-
validation: 2024-11-18
9+
validation: 2025-05-27
1010
posted: 2022-10-20
1111
---
1212

tutorials/bind-dns-server/index.mdx

Lines changed: 23 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,55 @@
11
---
22
meta:
33
title: Implementing a DNS server using BIND
4-
description: In this tutorial you will learn How to implement a DNS server using BIND.
4+
description: Learn how to install and configure a BIND DNS server on a Scaleway Instance to manage domain name resolution.
55
content:
66
h1: Implementing a DNS server using BIND
7-
paragraph: In this tutorial you will learn How to implement a DNS server using BIND.
7+
paragraph: Learn how to install and configure a BIND DNS server on a Scaleway Instance to manage domain name resolution.
88
tags: dns bind
99
categories:
1010
- domains-and-dns
1111
dates:
12-
validation: 2024-11-18
12+
validation: 2025-05-27
1313
posted: 2018-12-05
1414
---
1515

1616
DNS (Domain Name System) is a service that translates the IP address of computers connected to the internet into human-readable domain names, and vice versa. In an environment with a limited amount of Linux machines, it is possible to use the `/etc/hosts` file for associating an IP address to a DNS name. But when you have a large infrastructure with lots of systems/resources, `/etc/hosts` may quickly become cumbersome.
1717

18-
[BIND](https://www.isc.org/bind/) or Berkeley Internet Name Domain is open-source software that implements DNS protocols for the internet. In this tutorial, we need a DNS server machine & a client machine for testing.
18+
[BIND](https://www.isc.org/bind/) or Berkeley Internet Name Domain is open-source software that implements DNS protocols for the internet. In this tutorial, we need primary and secondary DNS server machines, in accordance with best practice to ensure redundancy. We also need a third machine (e.g. your local machine) for testing.
1919

2020
<Macro id="requirements" />
2121

2222
- A Scaleway account logged into the [console](https://console.scaleway.com)
2323
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
24+
- Two [Instances](/instances/how-to/create-an-instance/) running Ubuntu, to act as the primary and secondary DNS server machines.
25+
- A local machine, or a third Instance, to test from.
2426
- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
2527
- `sudo` privileges or access to the root user
2628

2729
## Installing BIND
2830

29-
1. Install the latest version of BIND 9.20 and related tools:
31+
1. Connect to the Instance that will act as the primary DNS server using [SSH](/instances/how-to/connect-to-instance/):
32+
```
33+
ssh root@<your_instance_ip>
34+
```
35+
36+
2. Update the `apt` package manager and upgrade the software already installed on the Instance to the latest version, available in Ubuntu's repositories:
37+
```
38+
apt update && apt upgrade -y
39+
40+
3. Install the latest version of BIND 9.18 and related tools:
3041
```
3142
apt-get install bind9 bind9utils bind9-doc dnsutils
3243
```
33-
2. Verify the installed version:
44+
4. Verify the installed version:
3445
```
3546
named -v
3647
```
3748
The expected output should be:
3849
```
39-
BIN 9.20.x
50+
BIND 9.18.x
4051
```
41-
52+
5. Repeat the above steps on the secondary DNS server Instance.
4253
4354
## Configuring the primary DNS server
4455
@@ -138,6 +149,8 @@ DNS (Domain Name System) is a service that translates the IP address of computer
138149
139150
### Testing the Configuration
140151
152+
Carry out the following steps on a third machine, e.g. your local machine or another Instance.
153+
141154
1. Check the primary DNS server:
142155
```bash
143156
dig @192.0.2.1 www.example.com
@@ -169,6 +182,6 @@ DNS (Domain Name System) is a service that translates the IP address of computer
169182

170183
## Conclusion
171184

172-
You have successfully configured a DNS server using BIND 9.20. You can now resolve domain names within your infrastructure or serve DNS queries to external clients.
185+
You have successfully configured a redundant DNS server using BIND 9.18. You can now resolve domain names within your infrastructure or serve DNS queries to external clients.
173186

174-
For more advanced configurations and features, refer to the [official BIND 9.20 documentation](https://kb.isc.org/docs/isc-bind-9).
187+
For more advanced configurations and features, refer to the [official BIND documentation](https://kb.isc.org/docs/isc-bind-9).

tutorials/configure-nextcloud-ubuntu/index.mdx

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
---
22
meta:
33
title: Installing and configuring Nextcloud
4-
description: This page shows how to install and configure Nextcloud on Ubuntu Jammy Jellyfish
4+
description: Learn how to install and configure Nextcloud on Ubuntu Jammy Jellyfish using a Scaleway Instance to host your private cloud storage solution.
55
content:
66
h1: Installing and configuring Nextcloud
7-
paragraph: This page shows how to install and configure Nextcloud on Ubuntu Jammy Jellyfish
7+
paragraph: Learn how to install and configure Nextcloud on Ubuntu Jammy Jellyfish using a Scaleway Instance to host your private cloud storage solution.
88
categories:
99
- instances
10-
tags: Nextcloud Ubuntu-Bionic-Beaver
10+
tags: Nextcloud Ubuntu-Jammy-Jellyfish
1111
dates:
12-
validation: 2024-10-29
12+
validation: 2025-05-27
1313
posted: 2018-10-26
1414
---
1515

16-
Nextcloud is an open-source, self-hosted file share, and communication platform.
16+
Nextcloud is an open-source, self-hosted file-share, and communication platform.
1717

1818
It provides a large portfolio of [different applications](https://nextcloud.com/install/#install-clients) to access your cloud storage from your PC, Mac, or mobile device.
1919

@@ -78,7 +78,7 @@ By default, the Nextcloud installation via Snap provides a plain HTTP connection
7878
```
7979
nextcloud.enable-https lets-encrypt
8080
```
81-
2. The following message will appear, confirm it by pressing `y` on your keyboard:
81+
3. The following message will appear, confirm it by pressing `y` on your keyboard:
8282
```
8383
In order for Let's Encrypt to verify that you actually own the
8484
domain(s) for which you're requesting a certificate, there are a
@@ -102,15 +102,15 @@ By default, the Nextcloud installation via Snap provides a plain HTTP connection
102102
103103
Have you met these requirements? (y/n)
104104
```
105-
3. Enter your email address when asked to do so and confirm by pressing **Enter**:
105+
4. Enter your email address when asked to do so and confirm by pressing **Enter**:
106106
```
107107
Please enter an email address (for urgent notices or key recovery): [email protected]
108108
```
109-
4. Enter the domain name that you have configured in a previous step for your Instance (`your.domain.com` in our case), then confirm by pressing **Enter**:
109+
5. Enter the domain name that you have configured in a previous step for your Instance (`your.domain.com` in our case), then confirm by pressing **Enter**:
110110
```
111111
Please enter your domain name(s) (space-separated): your.domain.com
112112
```
113-
5. Your certificate is being requested and Apache will be restarted. The following messages will appear, once the certificate has been obtained:
113+
6. Your certificate is being requested and Apache will be restarted. The following messages will appear, once the certificate has been obtained:
114114
```
115115
Attempting to obtain certificates... done
116116
Restarting apache... done

tutorials/configure-nodemcu-iot-hub/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ content:
88
categories:
99
- iot-hub
1010
dates:
11-
validation: 2024-11-18
11+
validation: 2025-05-27
1212
tags: iot iot-hub NodeMCU Arduino-IDE
1313
hero: assets/scaleway_nodemcu.webp
1414
---
Binary file not shown.
Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)