scaleway · bene2k1 · Jan 30, 2025 · Jan 30, 2025 · Jan 30, 2025 · Jan 30, 2025
diff --git a/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx b/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to access a Mac mini using remote desktop clients on macOS, Windows, and Linux.
 tags: apple-silicon, connection, mac-mini, mac-mini
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-05-26
 categories:
   - bare-metal

diff --git a/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx b/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to connect to a Scaleway Mac mini using SSH, providing step-by-step instructions and necessary requirements.
 tags: apple-silicon, connection, mac-mini, mac-mini-m1
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-05-26
 categories:
   - bare-metal

diff --git a/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx b/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to install the Homebrew package manager to a Scaleway Mac mini.
 tags: apple-silicon, connection, mac-mini, mac-mini-m1
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-05-26
 categories:
   - bare-metal

diff --git a/pages/apple-silicon/how-to/shutdown-mac-mini.mdx b/pages/apple-silicon/how-to/shutdown-mac-mini.mdx
@@ -8,7 +8,7 @@ content:
   paragraph: This guide provides instructions on how to properly shutdown a Scaleway Mac mini.
 tags: mac-mini, mac-mini-m1, apple-silicon, shutdown
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-05-26
 categories:
   - bare-metal

diff --git a/pages/apple-silicon/how-to/update-os-mac-mini.mdx b/pages/apple-silicon/how-to/update-os-mac-mini.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to update the operating system of a Scaleway Mac mini.
 tags: apple-silicon, connection, mac-mini, mac-mini-m1
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-05-26
 categories:
   - bare-metal

diff --git a/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx b/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to upgrade the macOS of a Scaleway Mac mini to a beta version.
 tags: apple-silicon mac-mini beta macos
 dates:
-  validation: 2024-07-30
+  validation: 2025-01-30
   posted: 2024-07-30
 categories:
   - bare-metal

diff --git a/pages/apple-silicon/quickstart.mdx b/pages/apple-silicon/quickstart.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page shows you how to get started with Scaleway's Apple silicon.
 tags: apple-silicon mac-mini- mac mini mac-mini ios
 dates:
-  validation: 2024-07-25
+  validation: 2025-01-30
   posted: 2021-05-26
 categories:
   - bare-metal

diff --git a/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx b/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to assign a failover IP for Scaleway Dedibox servers.
 tags: dedibox failover failover-ip
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-07-29
 categories:
   - dedibox-network

diff --git a/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx b/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to configure a Dedibox failover IP on Debian or Ubuntu Linux.
 tags: failover-failover IP ip debian ubuntu dedibox linux
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-07-29
 categories:
   - dedibox-network

diff --git a/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx b/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to configure network settings for virtual machines on various operating systems, including Ubuntu, Debian, CentOS, and Windows Server.
 tags: dedibox network virtual-machine virtual machine ubuntu debian centOS windows-server
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-07-29
 categories:
   - dedibox-network
@@ -36,74 +36,75 @@ Find below examples of network interface configurations on different distributio
 
 Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for configuring network interfaces. For older releases, refer to the Debian configuration.
 
-1. Log into your virtual machine and open the network configuration file `/etc/netplan/01-netcfg.yaml` in a text editor of your choice, for example `nano`:
-    ```
+1. Log into your virtual machine and open the network configuration file `/etc/netplan/01-netcfg.yaml` in a text editor of your choice:
+    ```sh
     sudo nano /etc/netplan/01-netcfg.yaml
     ```
-2. Create a network configuration as follows. Replace `fail.over.ip.address` with your failover IP address:
+2. Create a network configuration as follows. Replace `<failover_IP>` with your failover IP address:
     ```yaml
     network:
-    ethernets:
+      version: 2
+      ethernets:
         ens18:
-            addresses:
-            - [ "fail.over.ip.address/32" ]
-            nameservers:
-              addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers)
-            routes:
-            -   to: default
-                via: 62.210.0.1
-            -   to: 62.210.0.1/32
-                via: fail.over.ip.address
-                scope: link
-    version: 2
+          addresses:
+            - <failover_IP>/32
+          nameservers:
+            addresses: [ "51.159.47.28", "51.159.47.26" ]
+          routes:
+            - to: default
+              via: 62.210.0.1
+            - to: 62.210.0.1/32
+              via: <failover_IP>
+              scope: link
     ```
 3. Save the file and exit the text editor.
 4. Apply the new configuration:
-    ```
+    ```sh
     sudo netplan apply
     ```
 
 ## Debian
 
-1. Log into the virtual machine and edit the file `/etc/network/interfaces` with a text editor of your choice, for example, `nano`:
-    ```
+1. Log into the virtual machine and edit the network configuration file:
+    ```sh
     sudo nano /etc/network/interfaces
     ```
-2. Configure the network interface as follows. Replace `fail.over.ip.address` with your failover IP address:
-    ```
+2. Configure the network interface as follows. Replace `<failover_IP>` with your failover IP address:
+    ```ini
     auto eth0
-        iface eth0 inet static
-        address fail.over.ip.address
+    iface eth0 inet static
+        address <failover_IP>
         netmask 255.255.255.255
         pointopoint 62.210.0.1
         gateway 62.210.0.1
     ```
 3. Save the file and exit the text editor.
-4. Set the DNS server information by editing the file `/etc/resolv.conf`:
-    ```
+4. Set the DNS server information:
+    ```sh
     sudo nano /etc/resolv.conf
     ```
-5. Set the DNS resolver by adding the following lines to the file. Then save it and exit the text editor:
-    ```
+5. Add the following DNS resolvers:
+    ```plaintext
     nameserver 51.159.47.28
     nameserver 51.159.47.26
     ```
-    <Message type="tip">
-      Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers)
-    </Message>
-6. Activate the network on your virtual machine by running:
-    ```
+6. Activate the network on your virtual machine:
+    ```sh
     sudo ifup eth0
     ```
+    *Alternatively, you can restart networking with:*
+    ```sh
+    sudo systemctl restart networking
+    ```
 
 ## CentOS
 
-1. Log into the virtual machine and edit the file `/etc/sysconfig/network-scripts/ifcfg-eth0` with a text editor of your choice, for example, `nano`:
-    ```
+1. Log into the virtual machine and edit the network configuration file:
+    ```sh
     sudo nano /etc/sysconfig/network-scripts/ifcfg-eth0
     ```
-2. Configure the network interface as follows. Replace `fail.over.ip.address` with your failover IP address and `virtual:mac:address` with the virtual MAC of the VM:
-    ```
+2. Configure the network interface as follows. Replace `<failover_IP>` with your failover IP address and `<virtual_MAC>` with the virtual MAC of the VM:
+    ```ini
     DEVICE=eth0
     BOOTPROTO=none
     ONBOOT=yes
@@ -112,34 +113,41 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for
     PEERDNS=yes
     TYPE=Ethernet
     NETMASK=255.255.255.255
-    IPADDR=fail.over.ip.address
+    IPADDR=<failover_IP>
     GATEWAY=62.210.0.1
-    DNS1=51.159.47.28 # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers)
+    DNS1=51.159.47.28
     DNS2=51.159.47.26
     ARP=yes
-    HWADDR=virtual:mac:address
+    HWADDR=<virtual_MAC>
     ```
-3. Save the file and close the text editor.
-4. Edit the file `/etc/sysconfig/network-scripts/route-eth0` as follows, then save and exit the text editor:
+3. Save and close the text editor.
+4. Create or edit the routing configuration file:
+    ```sh
+    sudo nano /etc/sysconfig/network-scripts/route-eth0
     ```
+    Add the following lines:
+    ```ini
     62.210.0.1 dev eth0
     default via 62.210.0.1 dev eth0
     ```
-5. Run the following command to bring the network interface up:
-    ```
+5. Activate the network interface:
+    ```sh
     sudo ifup eth0
     ```
 
 ## Windows Server
 
-1. Connect to the desktop of your VM in the virtual console, then open the network settings of your server.
-2. Enter the following information in the network adapter configuration:
-    * Address: failover IP
-    * Subnetmask: `255.255.255.255`
-    * Gateway: `62.210.0.1`
-    * DNS 1: `51.159.47.28`
-    * DNS 2: `51.159.47.26`
-
-    <Message type="tip">
-      Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers)
-    </Message>
+1. Open the network settings on your VM by navigating to:
+    ```
+    Control Panel → Network & Internet → Change Adapter Options
+    ```
+2. Select your network adapter and enter the following details:
+    - **IP Address**: `<failover_IP>`
+    - **Subnet Mask**: `255.255.255.255`
+    - **Gateway**: `62.210.0.1`
+    - **DNS 1**: `51.159.47.28`
+    - **DNS 2**: `51.159.47.26`
+
+<Message type="tip">
+  Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers)
+</Message>
diff --git a/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx b/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx
@@ -1,37 +1,51 @@
 ---
 meta:
   title: How to configure the reverse DNS of a Dedibox failover IP
-  description: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Online.net consle.
+  description: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Scaleway Dedibox console.
 content:
-  h1: How to configure the reverse DNS of a Dediboxfailover IP
-  paragraph: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Online.net consle.
+  h1: How to configure the reverse DNS of a Dedibox failover IP
+  paragraph: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Scaleway Dedibox console.
 tags: dedibox dns failover-ip failover
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-07-29
 categories:
   - dedibox-network
 ---
 
-Failover IP addresses allow you to have several IP addresses with your server. This allows you to assign IP addresses to different websites or to virtual machines.
+Failover IP addresses allow you to assign multiple IP addresses to your server. This enables you to allocate different IPs to websites, virtual machines, or services.
 
-Your failover IP can be routed at any time to your servers in just a few minutes by using our Account Management console or through our API. By switching your failover IP addresses from one server to another, the hosted services remain available without reconfiguring the IP address.
+Your failover IP can be routed at any time to your servers within a few minutes using the Scaleway Account Management console or API. By transferring failover IP addresses between servers, hosted services remain available without requiring IP reconfiguration.
 
-You can add a failover IP address(es) for each server according to the offer and your service level.
+You can add failover IP addresses to each server based on your offer and service level.
 
 <Macro id="requirements" />
 
 - A Dedibox account logged into the [console](https://console.online.net)
 - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
 
-1. From your Scaleway console, click **Server** > **Network configuration**. The list of your failover IPs and IP blocks displays.
-    <Lightbox src="scaleway_edit_reverse.webp" alt="" />
-2. Click **Edit reverses**. The list of your reverse DNS settings displays.
-3. Enter the new reverse DNS record and click **Update**.
-    <Lightbox src="scaleway_update_reverse.webp" alt="" />
-
-    <Message type="tip">
-      Make sure to have a valid **[A record](/dedibox-dns/concepts/#dns-record)** for forwarding DNS configured and pointing to your IP address before changing the reverse DNS of it.
-    </Message>
+## Configuring Reverse DNS
 
+1. From your Scaleway console, navigate to **Server** > **Network Configuration**. The list of your failover IPs and IP blocks is displayed.
+    <Lightbox src="scaleway_edit_reverse.webp" alt="Scaleway network configuration interface" />
+2. Click **Edit Reverse DNS**. The list of your current reverse DNS records appears.
+3. Enter the new reverse DNS record and click **Update**.
+    <Lightbox src="scaleway_update_reverse.webp" alt="Scaleway reverse DNS update interface" />
+
+<Message type="tip">
+  Ensure that a valid **[A record](/dedibox-dns/concepts/#dns-record)** is configured and pointing to your IP address before updating the reverse DNS.
+</Message>
+
+<Message type="note">
+  Reverse DNS updates may take some time to propagate. You can verify changes using the following commands:
+
+  - Linux/macOS:
+    ```sh
+    dig -x <failover_IP>
+    ```
+  - Windows:
+    ```sh
+    nslookup <failover_IP>
+    ```
+</Message>
 
diff --git a/pages/dedibox-ip-failover/how-to/configure-windows.mdx b/pages/dedibox-ip-failover/how-to/configure-windows.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to configure a Scaleway Dedibox failover IP on Windows Server 2019.
 tags: dedibox failover-ip windows server windows-server-2019
 dates:
-  validation: 2024-07-22
+  validation: 2025-01-30
   posted: 2021-07-29
 categories:
   - dedibox-network