---
title: How to add a DNS delegation to a Scaleway Dedibox IP address block
description: This page explains how to add a DNS delegation to IPv6 and IPv4 on Scaleway Dedibox.
tags: dns dedibox delegation IPv6 IPv4
dates:
  validation: 2025-08-28
  posted: 2021-05-26
---
import Requirements from '@macros/iam/requirements.mdx'

import image from './assets/scaleway-dedibox-server-list.webp'
import image2 from './assets/scaleway-edit-delegation.webp'

You cannot directly edit reverse DNS for IPv4 /27 blocks or IPv6 blocks (/48, /56, /64) in the Dedibox console.
Instead, you must delegate these subnets to your nameservers, which will handle the propagation of reverse DNS records on the internet. For redundancy, you need at least two DNS servers, and you can delegate subnets directly from your account.

<Requirements />

- A Dedibox account logged into the [console](https://console.online.net)
- Created a corresponding **A record** for your reverse DNS at least 24 hours ago

## How to add a DNS delegation in the console

1. From the [console](https://console.online.net), click **Server** in the top menu, then select **Network configuration**.
    <Lightbox image={image} alt="" />
2. Click the settings icon (cogwheel) next to the relevant IP block, then select **Edit nameserver delegation**. The **Edit nameserver delegation** page displays.
    <Lightbox image={image2} alt="" />
3. Enter details for the two name servers, and click **Update delegation**.
    <Message type="tip">
      - You can have a minimum of two and a maximum of five name servers. To add more name servers, use the **Add nameserver** button.
      - Ensure that your DNS configuration complies with [RFC 4183](https://datatracker.ietf.org/doc/html/rfc4183).
    </Message>

      You will need to repeat this for all your /27 IPv4 blocks. For IPv6, once you delegate your /48 all subnets will be automatically configured to the same name servers.

## Example BIND configurations

### IPv4

Here is an example BIND configuration for the block `62.4.10.0/27`:

```
0-27.10.4.62.in-addr.arpa.     86400   IN      SOA     ns1.mydns.net. hostmaster.mydns.net. (
                                      2013121407     ; Serial
                                      10800   ; Refresh
                                      1800    ; Retry
                                      604800  ; Expire
                                      86400 ) ; Minimum TTL
0-27.10.4.62.in-addr.arpa.     86400   IN      NS      ns1.mydns.net.
0-27.10.4.62.in-addr.arpa.     86400   IN      NS      ns2.mydns.net.
1.0-27.10.4.62.in-addr.arpa.   86400   IN      PTR     toto.domaine.com.
```

- The line **SOA** indicates the authoritative server for the IP block,
- The lines **NS** indicate the propagating DNS servers for the concerned IP block.
- The lines **PTR** indicate the reverse of the indicated IP, here 62.4.10.1.

<Message type="note">
  If your IP block is a size other than /27, you will need to adapt your configuration accordingly.
</Message>

### IPv6

Here is an example BIND configuration for the zone `001:bc8::3398::/48`:

```
;
; 2001:bc8:3398::/48
;
;
$TTL 1h ; Default TTL
8.9.3.3.8.c.b.0.1.0.0.2.ip6.arpa.       IN      SOA     ns1.domain.fr  webmaster.domain.fr (
        2016071503      ; serial
        1h              ; secondary refresh interval
        15m             ; secondary retry interval
        1w              ; secondary copy expire time
        1h              ; NXDOMAIN cache time
        )

;
; domain name servers
;
@       IN      NS      ns1.domain.fr.
@       IN      NS      ns2.domain.fr.


; IPv6 PTR entries
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.9.3.3.8.c.b.0.1.0.0.2.ip6.arpa.    IN    PTR    toto.domain.fr.
```

<Message type="tip">
  You can use the utilities available at [whatsmydns.net](https://www.whatsmydns.net/reverse-dns-generator) to facilitate the generation of your zones.
</Message>