Difference between revisions of "DNS Service"

From Tardis
Jump to: navigation, search
m (Text replace - "^" to "<div style="width:55%;margin:0 auto;border:2px solid;border-left:20px solid;border-color:#d9534f;text-align:center;padding:5px;font-weight:bold;">This page is out of date and needs rewriting.<br /> The content is likely to be incomp)
m (Text replace - "<div style="width:55%;margin:0 auto;border:2px solid;border-left:20px solid;border-color:#d9534f;text-align:center;padding:5px;font-weight:bold;">This page is out of date and needs rewriting.<br /> The content is likely to be incomplete or)
Line 1: Line 1:
 
{{OODNotice}}
 
{{OODNotice}}
[[Category:OutOfDate]]== Daemon ==
+
[[Category:OutOfDate]]
 +
== Daemon ==
 
Leela runs the standard Debian package of BIND 9.
 
Leela runs the standard Debian package of BIND 9.
  

Revision as of 21:03, 12 October 2013

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

Daemon

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.

Configuration

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 192.168.1.0/24
  • 2 Unused 192.168.0.0/24
  • 3 Services 193.62.81.0/27
  • 4 Cluster 193.62.81.32/28
  • 5 Gamesoc 193.62.81.48/29
  • 6 Unused 193.62.81.56/29

Editing

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).