DNS APIv2beta1

The DNS API allows you to manage your DNS zones and records.

• Manage your domain with one or more zones
• Use Dynamic Records to optimize and ease your Infra As Code

A domain name is an identification string that defines a realm of administrative autonomy, authority or control within the Internet. Domain names are formed by the rules and procedures of the Domain Name System (DNS). Any name registered in the DNS is a domain name.

Domains are further divided into sub-domains, each becoming a DNS zone itself with its own set of administrators and DNS servers.

The term domain is used in the business functions of the entity assigned to it and the term zone is usually used for configuration of DNS services.

example.com is the domain and has only one owner who can manage it.

By default, the domain only has a root zone (no sub domain).

example.com zone allows the configuration of records such as:

If we add a DNS zone to the sub domain dev.example.com, we get:

• Only the owner of the domain can use the domain services
• Each zone supports the creation of sub-zones, which inherit the parent's projectID

In the simplest case you will only need the root zone.

But multiple zones (i.e. sub-domains) allow:

• access delegation to zone(s) (preventing access to the root zone)
• (future) features based on templates
• performance tuning (for example if you have 10k records, it will be better to divide them into x zones / sub-domains)

Remark: to be RFC compliant, each zone will automatically have NS records added.

An internationalized domain name (IDN) is an Internet domain name that contains at least one label that is displayed in software applications, which is in whole or in part in a language-specific script or alphabet, such as Arabic, Chinese, Cyrillic, Tamil, Hebrew or the Latin alphabet-based characters with diacritics or ligatures, such as French. These writing systems are encoded by computers in multi-byte Unicode. Internationalized domain names are stored in the Domain Name System as ASCII strings using Punycode transcription.

Example: allélua.com converted in IDN is xn--alllua-dva.com.

To simplify its use, the DNS API uses unicode (UTF-8) for name and data fields.

Login to your Scaleway account and create a token from the credentials page. A secret_key and an access_key will be displayed on your screen, the secret_key will be used as X-Auth-Token.

Reference: https://www.scaleway.com/docs/generate-an-api-token/

The organization id is required to get the permissions. You will need to query:

To get your organization id:

Reference: https://www.scaleway.com/docs/retrieve-my-organization-id-throught-the-api/

To use Scaleway DNS to manage your Domain, you need to register your Domain with:

You will then have 48h to set up a TXT record to confirm the ownership of the Domain:

• name: _scaleway-challenge
• content: the validation token

Upon validation you will receive a confirmation email and the Domain will be available on the API. You will then have to update your DNS nameservers to Scaleway DNS servers: ns0.dom.scw.cloud and ns1.dom.scw.cloud.

• for a Domain: at your registrar to point your Domain to Scaleway DNS servers
• for a sub Domain: at your parent DNS server to point your sub Domain to Scaleway DNS servers

DNSSEC

Your domain's DNSSEC needs to be set up on the registry by your registrar and on the DNS server with the same information. If need: remove your DNSSEC settings on your registrar before migrating to our service. You will be able to re-setup if after.

To set up the DNSSEC:

• use the Registrar API EnableDomainDNSSEC to generate the setup on the DNS servers
• if your domain is not registered on Scaleway but on another Registrar, use the DS or public key information to configure the DNSSEC on your registrar

• record name format is always in "short" format not FQDN.
• for zone example.com, name test.example.com. will be converted to test
• for data value, if not in RFC format, it will be corrected if possible:
  • for TXT, quotes will be added
  • for CNAME, if not in FQDN, the zone will be added
  • etc.

Remarks:

• The clear operation clears all the records (thus allows to restart from scratch)
• The operation works the same as PowerDns patch
• If the zone does not exist but is included in a managed zone, the API will create the new (sub) zone

For external domain:

You have not DNSSEC set at your registrar

You will have to set in your registrar the DS returned in the result:

You have DNSSEC already set at your registrar

Call the API with the right settings:

We provide the classic record types (A, AAAA, CNAME...) along with some dynamic records. At the moment the following dynamic records are supported: http(s) health checks and views.

Service up

This will test if a (http/https) service is up on a provided list of IPs.

An IP is considered healthy if the query response contains the text specified in must_contain.

The Record Type can be one of:

• A
• AAAA

View

View will give responses depending on the requester (or resolver) IP.

Record Type can be:

• A
• AAAA
• CNAME
• TXT

Delete the zone AND all the records, NS included:

Returns a list of manageable DNS zones. You can filter the DNS zones by domain name.

Create a new DNS zone.

Update the name and/or the organizations for a DNS zone.

Delete a DNS zone and all it's records.

Clone an existed DNS zone with all its records into a new one.

Refresh SOA DNS zone. You can recreate the given DNS zone and its sub DNS zone if needed.

Get the DNS zone TSIG Key to allow AXFR request.

Returns a list of Nameservers and their optional glue records for a DNS zone.

Update DNS zone nameservers and set optional glue records.

Returns a list of DNS records of a DNS zone with default NS. You can filter the records by type and name.

Only available with default NS.
Send a list of actions and records.

Action can be:

• add:
• Add new record
• Can be more specific and add a new IP to an existing A record for example
• set:
• Edit a record
• Can be more specific and edit an IP from an existing A record for example
• delete:
• Delete a record
• Can be more specific and delete an IP from an existing A record for example
• clear:
• Delete all records from a DNS zone

All edits will be versioned.

Only available with default NS.
Delete all the records from a DNS zone. All edits will be versioned.

Get a list of DNS zone versions.
The maximum version count is 100.
If the count reaches this limit, the oldest version will be deleted after each new modification.

Get a list of records from a previous DNS zone version.

Get all differences from a previous DNS zone version.

Restore and activate a previous DNS zone version.

Import and replace records from a given provider format with default NS.

Get a DNS zone in a given format with default NS.

Import and replace records from a given provider format with default NS.