Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
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
13 changes: 9 additions & 4 deletions pages/ipam/reference-content/ipv6.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ content:
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.
tags: ipv6 ipv4 support
dates:
validation: 2024-11-18
validation: 2025-05-27
posted: 2024-11-18
categories:
- network
Expand All @@ -27,7 +27,7 @@ This is where **IPv6** comes in, the most recent version of the IP protocol. Eac

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

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

## IPv6-compatible products

Expand All @@ -54,6 +54,7 @@ Go further with Instances and IPv6 in the following documentation:
- [Using routed IPs](/instances/api-cli/using-routed-ips/)
- 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/)
- [Fix DNS resolution with a routed IPv6-only setup on Debian Bullseye](/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye/)
- [Setting a reverse IPv6 DNS record via the IPAM API](/ipam/api-cli/set-ip-reverse/)

### Elastic Metal and IPv6

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

VPC and Private Networks are compatible with IPv6.

- Private Networks are dual-stack, meaning each Private Network necessarily has both an IPv4 and and an IPv6 CIDR blocks.
- Private Networks are dual-stack, meaning each Private Network necessarily has both IPv4 and and IPv6 CIDR blocks.
- 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.
- All IPv6-compatible resources will automatically receive an IPv6 address when they join a Private Network, in addition to an IPv4 address.
- This address can be auto-allocated from the pool, or specified by the user via a [reserved IP address](/ipam/how-to/reserve-ip/)
- 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.
- 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.

### InterLink and IPv6

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.

### Serverless Functions and Containers and IPv6

Expand Down
6 changes: 3 additions & 3 deletions pages/load-balancer/how-to/add-certificate.mdx
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
---
meta:
title: How to add a certificate to your Load Balancer
description: This page explains how to add a certificate to your Load Balancer
description: Learn how to add an SSL/TLS certificate to your Scaleway Load Balancer to enable secure HTTPS traffic for your services
content:
h1: How to add a certificate to your Load Balancer
paragraph: This page explains how to add a certificate to your Load Balancer
paragraph: Learn how to add an SSL/TLS certificate to your Scaleway Load Balancer to enable secure HTTPS traffic for your services
dates:
validation: 2024-11-18
validation: 2025-05-27
posted: 2022-10-20
---

Expand Down
33 changes: 23 additions & 10 deletions tutorials/bind-dns-server/index.mdx
Original file line number Diff line number Diff line change
@@ -1,44 +1,55 @@
---
meta:
title: Implementing a DNS server using BIND
description: In this tutorial you will learn How to implement a DNS server using BIND.
description: Learn how to install and configure a BIND DNS server on a Scaleway Instance to manage domain name resolution.
content:
h1: Implementing a DNS server using BIND
paragraph: In this tutorial you will learn How to implement a DNS server using BIND.
paragraph: Learn how to install and configure a BIND DNS server on a Scaleway Instance to manage domain name resolution.
tags: dns bind
categories:
- domains-and-dns
dates:
validation: 2024-11-18
validation: 2025-05-27
posted: 2018-12-05
---

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.

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

<Macro id="requirements" />

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

## Installing BIND

1. Install the latest version of BIND 9.20 and related tools:
1. Connect to the Instance that will act as the primary DNS server using [SSH](/instances/how-to/connect-to-instance/):
```
ssh root@<your_instance_ip>
```

2. Update the `apt` package manager and upgrade the software already installed on the Instance to the latest version, available in Ubuntu's repositories:
```
apt update && apt upgrade -y
3. Install the latest version of BIND 9.18 and related tools:
```
apt-get install bind9 bind9utils bind9-doc dnsutils
```
2. Verify the installed version:
4. Verify the installed version:
```
named -v
```
The expected output should be:
```
BIN 9.20.x
BIND 9.18.x
```

5. Repeat the above steps on the secondary DNS server Instance.
## Configuring the primary DNS server
Expand Down Expand Up @@ -138,6 +149,8 @@ DNS (Domain Name System) is a service that translates the IP address of computer
### Testing the Configuration
Carry out the following steps on a third machine, e.g. your local machine or another Instance.
1. Check the primary DNS server:
```bash
dig @192.0.2.1 www.example.com
Expand Down Expand Up @@ -169,6 +182,6 @@ DNS (Domain Name System) is a service that translates the IP address of computer

## Conclusion

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

For more advanced configurations and features, refer to the [official BIND 9.20 documentation](https://kb.isc.org/docs/isc-bind-9).
For more advanced configurations and features, refer to the [official BIND documentation](https://kb.isc.org/docs/isc-bind-9).
18 changes: 9 additions & 9 deletions tutorials/configure-nextcloud-ubuntu/index.mdx
Original file line number Diff line number Diff line change
@@ -1,19 +1,19 @@
---
meta:
title: Installing and configuring Nextcloud
description: This page shows how to install and configure Nextcloud on Ubuntu Jammy Jellyfish
description: Learn how to install and configure Nextcloud on Ubuntu Jammy Jellyfish using a Scaleway Instance to host your private cloud storage solution.
content:
h1: Installing and configuring Nextcloud
paragraph: This page shows how to install and configure Nextcloud on Ubuntu Jammy Jellyfish
paragraph: Learn how to install and configure Nextcloud on Ubuntu Jammy Jellyfish using a Scaleway Instance to host your private cloud storage solution.
categories:
- instances
tags: Nextcloud Ubuntu-Bionic-Beaver
tags: Nextcloud Ubuntu-Jammy-Jellyfish
dates:
validation: 2024-10-29
validation: 2025-05-27
posted: 2018-10-26
---

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

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.

Expand Down Expand Up @@ -78,7 +78,7 @@ By default, the Nextcloud installation via Snap provides a plain HTTP connection
```
nextcloud.enable-https lets-encrypt
```
2. The following message will appear, confirm it by pressing `y` on your keyboard:
3. The following message will appear, confirm it by pressing `y` on your keyboard:
```
In order for Let's Encrypt to verify that you actually own the
domain(s) for which you're requesting a certificate, there are a
Expand All @@ -102,15 +102,15 @@ By default, the Nextcloud installation via Snap provides a plain HTTP connection
Have you met these requirements? (y/n)
```
3. Enter your email address when asked to do so and confirm by pressing **Enter**:
4. Enter your email address when asked to do so and confirm by pressing **Enter**:
```
Please enter an email address (for urgent notices or key recovery): [email protected]
```
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**:
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**:
```
Please enter your domain name(s) (space-separated): your.domain.com
```
5. Your certificate is being requested and Apache will be restarted. The following messages will appear, once the certificate has been obtained:
6. Your certificate is being requested and Apache will be restarted. The following messages will appear, once the certificate has been obtained:
```
Attempting to obtain certificates... done
Restarting apache... done
Expand Down
2 changes: 1 addition & 1 deletion tutorials/configure-nodemcu-iot-hub/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ content:
categories:
- iot-hub
dates:
validation: 2024-11-18
validation: 2025-05-27
tags: iot iot-hub NodeMCU Arduino-IDE
hero: assets/scaleway_nodemcu.webp
---
Expand Down
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading