Nameservers and DNS Records

Use of Gandi's nameservers (our “LiveDNS” as we call the new ones designed to integrate with v5) is free for all domains registered or transferred to Gandi. In order to use Gandi's nameservers, however, your domain must be at Gandi. Gandi does not allow managing DNS records of domains not registered with us.

If you are currently using our classic DNS (a.dns.gandi.net, b.dns.gandi.net, c.dns.gandi.net) you will not be able to manage your DNS records on our new website. When you go to edit your records, we will ask if you want to switch to LiveDNS - you will need to accept this switch in order to proceed.

The below instructions requires that your domain name uses Gandi's LiveDNS:

These are the DNS that we use with Gandi v5 that allows for using the “services” features, as well as automatic updating by our website for simple hosting, ssl, mail, and web forwarding.

While our classic DNS service pushed zone file changes once every 20 minutes, the LiveDNS service does so immediately after each change. One word of warning, though: if you choose to change a domain’s DNS to LiveDNS, once you do so, zonefile records can no longer be managed on the v4 interface.

If you have your own primary nameserver, but you need a secondary DNS, Gandi can provide this service to you, with no extra charge if the domain is registered with us.

Gandi's secondary DNS is ns6.gandi.net. Its IP is 217.70.177.40.

Our secondary nameserver can be useful if you only have one nameserver, but need another, and don't have the resources or time to set up your own.

How to add

On the Nameserver page in your domain's admin, enter the following in one of the blank fields:

ns6.gandi.net

How it works

ns6.gandi.net copies the zone file from the primary DNS whenever it detects that a change has been made in the primary DNS. Therefore, you must first have the possibility of including ns6.gandi.net in the zone, as it will be requesting zone transfers from the primary nameserver.

In order for this to work and to use our secondary server:

  • the administrator of the primary nameserver must authorize the AxFr conection to ns6.gandi.net
  • the administrator of the primary nameserver must increment the serial number of the SOA.

To find the serial number type the command:

dig SOA @ns6.gandi.net example.com

And you will see a line like this:

;; ANSWER SECTION:
net4france.com.         604800  IN      SOA     s1.net4france.com. kermit.s1.net4france.com. 2007110919 86400 21600 604800 60

In this line, the SOA is :“2007110919”, which can be compared to the primary nameserver:

dig SOA @server1.webhost.com example.com 
For extensions like .de that perform a zonecheck, you will not be able to use our secondary nameserver if you have not correctly authorized the zone transfer to it as described above. Also, due to the provisioning delay, please allow for at least 30 minutes to an hour for the operation to be attempted before checking on your interface to see if it was updated (and therefore, accepted by the registry)