From Sugar Labs
< Service
Revision as of 17:16, 5 December 2017 by Bernie (talk | contribs)
Jump to navigation Jump to search

Administrative contact

To request changes to DNS records, contact <hostmaster AT sugarlabs DOT org>


Current hostmasters are:

(please use preferably the administrative address)

Registered nameservers

The following nameservers are currently registered in whois records for our domains:

hostname aka location IPv4 IPv6 lightwave MIT Media Lab, Cambridge, USA 2002:1255:2c40::1 sunjammer FSF, Boston, USA 2001:4830:134:7::11 trinity Develer, Firenze, Italy 2002:5395:9ed2::1

Editing zone data

We use distributed version control and admin scripts to arbitrate edits to the zone files and nameserver configurations. DO NOT EDIT THESE FILES DIRECTLY ON THE MASTER NAMESERVER, ANY CHANGES WILL BE OVERWRITTEN.

Checkout nameserver config

Checkout the git repository containing the DNS zone data:

git clone ns

Do not checkout the repository as root. Your user on Machine/lightwave needs to be in group hostmaster.

In order to make changes, you will also need the private keys for your domain. For security reasons, these are not kept on the master DNS itself. Ask one of the other hostmasters for a copy and put it in the keys/ directory alongside the public keys.

Edit zone data

Guidelines for editing zones:

  • Please keep the zone files tidy, by following indentation style
  • Add comments as needed to describe obscure records in the zone files
  • Remember to keep reverse zones always up to date
  • Bump the serials after each update! (this is done automatically by our update-zone script)

Push changes back to master nameserver

After you edited the zone, execute this script to re-sign the zone and push your changes to the master DNS:


The script does:

  • bump the serial number
  • re-sign the zone with the DNSSEC private keys (which you must copy to keys/)
  • commit your changes
  • push the commit to the remote repository

The post-receive hook automates the rest of the procedure:

  • send a notification email to systems-logs@
  • checkout your changes to the bind configuration directory
  • make BIND reload its configuration
  • watch BIND's log file to ensure there are no errors and slaves are actually transferring the changed zones

For other domains hosted on Sugar Labs infrastructure (such as eg. use:


This will check the zone before pushing.

GIT repository implementation details

We use a detached working directory to allow the automatic checkout to work (see post-receive hook below). The git repository is in /var/lib/bind/etc/bind.git and the working directory lives in /var/lib/bind/etc/bind. /etc/bind is a symlink to the working directory (/var/lib/bind/etc/bind).

See Sysadmin/Autocheckout repositories for all the implementation details.

DNSSEC details

How to create keys for a new domain

cd keys
dnssec-keygen -r/dev/random -a RSASHA1 -b 1024 -n ZONE
dnssec-keygen -r/dev/random -f KSK -a RSASHA1 -b 1280 -n ZONE

(the above commands take a very long time!)

How to manually sign a zone

dnssec-signzone -o -K keys masters/
/etc/init.d/bind9 restart

How to publish DLV records

Go to and upload the two DNSKEY records for each zone, then follow the instructions to validate them. This is the end result:

Add DS records to TLD

This step must be done by the registrar.

I've opened a support ticket on Joker asking to add support for DS records. If they can't do it, we need to transfer to another registrar. At this time, the only decent choice for a DNSSEC enabled registrar is

How to validate zone data

  • Validate zone data with dig:
dig +dnssec +multiline -t ns @localhost | grep ad
  • Validate zone data against domain DNSKEY:
unbound-host -y ' IN DNSKEY 256 3 5 AwEAAa3dS5/3fkGXuqXft2dN/UPUivGqiYzZF+jWcow8LTAnlsoYaJFB VMAlJWbC6FFI7AMjoJYpmoeDMgHd4BtVqZO2ikx5zc48CtOUHUdXs7nw fMSQoVOnplpTKH2AgyRfDqYhtosP0euyJQNZI+NiYneZb1o1Ys7PE87Y 7FamjXwV' -v
  • Validate zone data against domain DS key:
unbound-host  -y ' IN DS 58126 5 2 96BF1964F3EA9885F5DE83DA14419F55F579A42BC18759C1B79BDE64 7587CFA8' -v 
  • Validate zone data against root DNSKEY:
unbound-host  -y '. DNSKEY 257 3 8 AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF FVQUTf6v58fLjwBd0YI0EzrAcQqBGCzh/RStIoO8g0NfnfL2MTJRkxoX bfDaUeVPQuYEhg37NZWAJQ9VnMVDxP/VHL496M/QZxkjf5/Efucp2gaD X6RS6CXpoY68LsvPVjR0ZSwzz1apAzvN9dlzEheX7ICJBBtuA6G3LQpz W5hOA2hzCTMjJPJ8LbqF6dsV6DoBQzgul0sGIcGOYl7OyQdXfZ57relS Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq QxA+Uk1ihz0=' -v
  • Validate zone data online:

DNSSEC tutorial