Installing Bind

You may follow:

Install the bind9 server package on your a virtual machine. The MI department has already set up a DNS service for mi.hdm-stuttgart.de. But regarding upcoming exercises we want to be able configuring private host aliases.

Consider the example virtual machine sdi04a.mi.hdm-stuttgart.de / 141.62.75.104 hosting a DNS server. Create a complete new zone describing a domain sdi4.mi.hdm-stuttgart.de containing both your machine's sdi04a.sdi4.mi.hdm-stuttgart.de and sdi04b.sdi4.mi.hdm-stuttgart.de address records. Your DNS server should provide at least the following data:

Your sdi4.mi.hdm-stuttgart.de domain's primary nameserver

Primary name server for domain sdi4.mi.hdm-stuttgart.de.

sdi04a.sdi4.mi.hdm-stuttgart.de

Your first machine's host name.

sdi04b.sdi4.mi.hdm-stuttgart.de

Your second machine's host name.

www4.sdi4.mi.hdm-stuttgart.de and www4-2.sdi4.mi.hdm-stuttgart.de

An (CNAME) alias to sdi04a.sdi4.mi.hdm-stuttgart.de.

All host names (albeit not yet existing) should point to your virtual machine's IP. This requires setting up a forward zone file.

Tip

  1. The named-checkzone command helps you to check for your two zone files' correctness

  2. The named-checkconf command checks for your configuration's overall correctness.

  3. You may use the nslookup command to query your DNS server. The set type=ns option allows to query for the domain's primary name server.

Test your configuration using dig @<your host-IP> ... . You should be able to resolve e.g. www4.sdi4.mi.hdm-stuttgart.de to your local host's IP address.