Installing and configuring Bind
You may follow:
Install the bind9 server package on
your first “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.
If you are a member of e.g. group 7 then
sdi04a.mi.hdm-stuttgart.de will host your DNS server. Create a complete new zone
g7.sdi.mi.hdm-stuttgart.de containing both your machines
sdia.g7.sdi.mi.hdm-stuttgart.de and
sdib.g7.sdi.mi.hdm-stuttgart.de address records. Your DNS server should provide at least the following
data:
- Your g7.sdi.mi.hdm-stuttgart.de domain's primary nameserver
-
Primary name server for domain
g7.sdi.mi.hdm-stuttgart.de. - vm1.g7.sdi.mi.hdm-stuttgart.de
-
Your first machine's host name.
- vm2.g7.sdi.mi.hdm-stuttgart.de
-
Your second machine's host name.
- www.g7.sdi.mi.hdm-stuttgart.de and cloud.g7.sdi.mi.hdm-stuttgart.de
-
(
CNAME) aliases tovm1.g7.sdi.mi.hdm-stuttgart.deorvm2.g7.sdi.mi.hdm-stuttgart.de.
All host names (albeit not yet existing) should point to your virtual machines' IP. This requires setting up a forward zone file.
Tip
-
The named-checkzone command helps you to check for your two zone files' correctness
-
The named-checkconf command checks for your configuration's overall correctness.
-
You may use the nslookup command to query your DNS server. The
set type=nsoption allows to query for the domain's primary name server.
-
ns(Nameserver) -
www(Future webserver, see the section called “Apache web server”).
Test your configuration using dig @<your
host-IP> ... . You should be able to
resolve e.g. www.g7.sdi.mi.hdm-stuttgart.de to your local
host's IP address.
