From 6c221d560ebecb8b01e49d0cc6a155e27d6f6880 Mon Sep 17 00:00:00 2001
From: Martin Goik <goik@hdm-stuttgart.de>
Date: Mon, 3 Apr 2023 13:38:54 +0200
Subject: [PATCH] Link supplements,
---
Doc/Sdi/Dns/dns.xml | 82 ++++++++++++++++++++++++++++-----------------
1 file changed, 51 insertions(+), 31 deletions(-)
diff --git a/Doc/Sdi/Dns/dns.xml b/Doc/Sdi/Dns/dns.xml
index 113e66e8c..54d063dc2 100644
--- a/Doc/Sdi/Dns/dns.xml
+++ b/Doc/Sdi/Dns/dns.xml
@@ -190,13 +190,6 @@ hdm-stuttgart.de. 3600 IN NS iz-net-2.hdm-stuttgart.de.</screen>
<section xml:id="sdiDnsExercises">
<title>Exercises</title>
- <para>You may follow <quote
- xlink:href="https://www.linuxbabe.com/debian/authoritative-dns-server-debian-10-buster-bind9">Set
- Up BIND Authoritative DNS Server on Debian 10 Buster</quote> implementing
- the subsequent steps. You may want to read <link
- xlink:href="https://www.zytrax.com/books/dns/ch8/soa.html">Start of
- Authority Resource Record</link> in particular.</para>
-
<section xml:id="sdiDnsUseDig">
<title>Querying <xref linkend="glo_DNS"/> data.</title>
@@ -209,6 +202,28 @@ hdm-stuttgart.de. 3600 IN NS iz-net-2.hdm-stuttgart.de.</screen>
<section xml:id="sdiBindInstall">
<title>Installing <xref linkend="glo_Soft_Bind"/></title>
+ <para>You may follow:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><link
+ xlink:href="https://www.linuxbabe.com/debian/authoritative-dns-server-debian-10-buster-bind9">Set
+ Up BIND Authoritative DNS Server on Debian</link></para>
+ </listitem>
+
+ <listitem>
+ <para><link
+ xlink:href="https://cloudinfrastructureservices.co.uk/how-to-install-bind-dns-on-debian-11-server-setup-configure">How
+ to Install Bind DNS on Debian 11 Server</link></para>
+ </listitem>
+
+ <listitem>
+ <para><link
+ xlink:href="https://www.zytrax.com/books/dns/ch8/soa.html">Start of
+ Authority Resource Record</link></para>
+ </listitem>
+ </itemizedlist>
+
<para>Install the <productname>bind9</productname> server package on
your <quote>a</quote> virtual machine. The MI department has already set
up a <xref linkend="glo_DNS"/> service for
@@ -216,34 +231,48 @@ hdm-stuttgart.de. 3600 IN NS iz-net-2.hdm-stuttgart.de.</screen>
want to be able configuring private host aliases.</para>
<para>Consider the example virtual machine
- <code>sdi4a.mi.hdm-stuttgart.de / 141.62.75.104</code> hosting a <xref
- linkend="glo_DNS"/> server. It should provide at least the following
+ <code>sdi04a.mi.hdm-stuttgart.de / 141.62.75.104</code> hosting a <xref
+ linkend="glo_DNS"/> server. Create a complete new zone describing a
+ domain sdi4<code>.mi.hdm-stuttgart.de</code> containing both your
+ machine's <code>sdi04a.sdi4mi.hdm-stuttgart.de</code> and
+ <code>sdi04b.sdi4mi.hdm-stuttgart.de</code> address records. Your <xref
+ linkend="glo_DNS"/> server should provide at least the following
data:</para>
<glosslist>
<glossentry>
- <glossterm>ns4.mi.hdm-stuttgart.de</glossterm>
+ <glossterm>Your sdi4.mi.hdm-stuttgart.de domain's primary
+ nameserver</glossterm>
<glossdef>
<para>Primary name server for domain
- <code>sdi4a.mi.hdm-stuttgart.de</code>.</para>
+ <code>sdi4.mi.hdm-stuttgart.de</code>. </para>
</glossdef>
</glossentry>
<glossentry>
- <glossterm>sdi4a.mi.hdm-stuttgart.de</glossterm>
+ <glossterm>sdi04a.sdi4.mi.hdm-stuttgart.de</glossterm>
<glossdef>
- <para>Host name.</para>
+ <para>Your first machine's host name.</para>
</glossdef>
</glossentry>
<glossentry>
- <glossterm>www4-1.mi.hdm-stuttgart.de and
+ <glossterm>sdi04b.sdi4.mi.hdm-stuttgart.de</glossterm>
+
+ <glossdef>
+ <para>Your first machine's host name.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>www4.sdi4.mi.hdm-stuttgart.de and
www4-2.mi.hdm-stuttgart.de</glossterm>
<glossdef>
- <para><code>CNAME</code> aliases.</para>
+ <para>An (<code>CNAME</code>) alias to
+ sdi04a.sdi4.mi.hdm-stuttgart.de.</para>
</glossdef>
</glossentry>
</glosslist>
@@ -279,19 +308,15 @@ hdm-stuttgart.de. 3600 IN NS iz-net-2.hdm-stuttgart.de.</screen>
</listitem>
<listitem>
- <para><code>www</code> (Future Webserver, see <xref
+ <para><code>www</code>4 (Future webserver, see <xref
linkend="sdiApache"/>).</para>
</listitem>
</itemizedlist>
<para>Test your configuration using <code>dig</code> <option>@<your
host-IP></option> <option>...</option> . You should be able to
- resolve e.g. <code>www.mi.hdm-stuttgart.de</code> to your local host's
- IP address.</para>
-
- <para>Define an alternate name (alias) <code>info</code> to
- <code>www</code> serving as <code>info.mi.hdm-stuttgart.de</code> and
- check this address as well.</para>
+ resolve e.g. <code>www4.sdi4.mi.hdm-stuttgart.de</code> to your local
+ host's IP address.</para>
</section>
<section xml:id="sdiDnsReverse">
@@ -300,7 +325,7 @@ hdm-stuttgart.de. 3600 IN NS iz-net-2.hdm-stuttgart.de.</screen>
<para>Define a reverse zone file to answer queries asking for an IP
address' machine name <abbrev>i.e.</abbrev> resolving
<code>141.62.75.104</code> to
- <code>sdi4a.mi.hdm-stuttgart.de</code>.</para>
+ <code>sdi04a.mi.hdm-stuttgart.de</code>.</para>
</section>
<section xml:id="sdiDnsForwarder">
@@ -323,14 +348,9 @@ hdm-stuttgart.de. 3600 IN NS iz-net-2.hdm-stuttgart.de.</screen>
Test this configuration using dig accordingly.</para>
<para>Caveat: Configuring a client machine using your name server and
- sending a mail to <code>xy123@mi.hdm-stuttgart.de</code> won't work
- since the HdM's mail filters will deliver these mails to the MI mail
- server <code>mail.mi.hdm-stuttgart.de</code> rather than to
- <code>mail.hdm-stuttgart.de</code> (and you probably have no account on
- this particular machine). In addition both servers will reject mails
- having destination addresses differing from
- <code>...@hdm-stuttgart.de</code> or
- <code>...@mi.hdm-stuttgart.de</code> respectively.</para>
+ sending a mail to <code>xy123@sdi04.mi.hdm-stuttgart.de</code> won't
+ work since <code>mail.hdm-stuttgart.de</code> will reject mails being
+ sent to any domain other than <code>hdm-stuttgart.de</code>.</para>
</section>
<section xml:id="sdiDnsProjectNameServer">
--
GitLab