19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Safeguard Catalogue - Hardware & Software Remarks<br />

____________________________________________________________________ .........................................<br />

S 4.108 Simplified and secure network management<br />

with DNS services under Novell NetWare 4.11<br />

Initiation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security Management<br />

Implementation responsibility: Administrator<br />

A unique address must be assigned to every <strong>IT</strong> system in a TCP/IP network.<br />

<strong>The</strong> Internet Protocol (IP) specifies this address as four decimal numbers<br />

separated by a dot, each with a value range of between 0 and 255. As many<br />

numeric addresses are difficult to remember, meaningful host names can be<br />

assigned to the <strong>IT</strong> systems as well, e.g. www.bsi.bund.de. Resolution of host<br />

names into IP addresses can be performed using two different mechanisms.<br />

Under the first, an ASCII text file called HOSTS, which is stored in the<br />

SYS:ETC directory, can be manually created. From a security and<br />

administrative viewpoint this method should only be used in small networks<br />

as the HOSTS file has to be stored individually on each server and each<br />

workstation to enable local resolution. Special routines (e.g. login scripts) can<br />

be used to automate distribution of the HOSTS file.<br />

<strong>The</strong> second mechanism entails using a DNS server. Some of the aspects of<br />

setting up and configuring a DNS server under Novell NetWare 4.11 which<br />

require especial consideration in relation to system security are considered<br />

below.<br />

Function of the DNS components<br />

<strong>The</strong> two main components of DNS are the name server and the resolver,<br />

which is loaded on the client and queries the name server.<br />

- Primary name server<br />

<strong>The</strong> primary name server obtains the DNS entries for the zones for which it<br />

is authorised from a file on its hard disk. "Authorised" here means that the<br />

primary name server does not need to cross-check the DNS information<br />

with any other name server for a given zone. At the same time the primary<br />

name server is also the single point of administration for the domain. Only<br />

one primary name server exists for each zone.<br />

- Secondary name server<br />

<strong>The</strong> secondary name server possesses a write-protected copy of the DNS<br />

database of the primary name server. This copy is updated within a set<br />

period of time which is specified in the record type SOA (Start of<br />

Authority). Record types define the resource records which form the<br />

entries in the DNS database. <strong>The</strong> copy operation is known as "zone<br />

transfer" and forms the basis for updating the distributed DNS database of<br />

a domain. Secondary name servers take on load distribution tasks, enable<br />

the DNS database to be made available close to the resolver and create<br />

redundancy of the DNS domain information. To ensure that the system is<br />

fail-safe, at least one secondary name server should be configured for each<br />

zone.<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

Link between IP<br />

addresses and host<br />

names<br />

One primary name<br />

server per zone<br />

Load distribution,<br />

reduction of network<br />

traffic and redundancy

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!