Service/Nameservers

< Service
Revision as of 18:56, 18 February 2010 by Bernie (talk | contribs)

Hostmasters

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

Current hostmasters are:

  • Bernie Innocenti <bernie@codewiz.org>
  • (others to be added when this documentation is finished)


Registered nameservers

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

(FIXME: this is what it should look like after the current transitional mess)

hostname aka location IPv4 IPv6
ns1.sugarlabs.org lightwave FSF, Boston, USA 140.186.70.102 2002:8cba:4666::1
ns2.sugarlabs.net sunjammer FSF, Boston 140.186.70.53 2002:8cba:4635::1
ns1.codewiz.org trinity Develer, Firenze, Italy 83.149.158.210 2002:5395:9ed2::1
ns2.auth.osuosl.org - OSU-OSL, Seattle, USA 140.211.166.141 -

Note that ns2.auth.osuosl.org is not under our control and does not serve all our domains.

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 LOCALLY, ANY CHANGES WILL BE OVERWRITTEN.

Checkout nameserver config

To simplify merging, each hostmaster pushes to a separate branch:

git clone root@lightwave.sugarlabs.org:/var/lib/bind/etc/bind ns
git config --add remote.origin.push '+refs/heads/*:refs/remotes/USERNAME/*'

FIXME: use an unprivileged group "hostmaster" rather than root.

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!

Push changes back to master nameserver

We have a handy script to automate everything:

./
  • You should see the slaves transfering the new zones you have modified

TODO: document what to do for changes to slaves config.