DNS Service

From Tardis
Revision as of 15:10, 4 February 2015 by Skull (talk | contribs)
Jump to: navigation, search


Leela runs the standard Debian package of BIND 9.

The named daemon on leela is responsible for both dealing with and forwarding local requests, and answering authoritatively external requests for the tardis.ed.ac.uk domain.


This section is out of date and needs rewriting.
The content is likely to be incomplete or incorrect.

The DNS philosophy of tardis is to use the machines' own names for A records and have as many CNAME's as necessary as aliases for their functions, i.e. ssh.tardis.ed.ac.uk is a CNAME for vortis.

The addresses in the tardis domain are distributed thusly:

  • 1 Infrastructure
  • 2 Unused
  • 3 Services
  • 4 Cluster
  • 5 Gamesoc
  • 6 Unused


The forward and reverse lookup databases are controlled by RCS to ensure that nobody can completely mess up the config with a mistake. It is important to co -l before editing the files and ci -u when finished, or your changes will be lost (and you'll probably confuse and annoy whoever edits it next).

All servers should also have PTR records created in the corresponding database files (for Reverse DNS).

The files to edit are as follows:

  • db.tardis: The tardis.ed.ac.uk forward lookup database (IN/CNAME).
  • db.193.62.81: The tardis.ed.ac.uk reverse lookup database (PTR).

Once the files have been edited, run named-checkzone tardis db.tardis to verify the zone configuration has been correctly written.

Finally, reload bind with /etc/init.d/bind9 reload