Installation_Guide/en-US

Jeroen van Meeuwen vanmeeuwen at kolabsys.com
Sun Aug 5 15:55:04 CEST 2012


 Installation_Guide/en-US/Preparing_the_System.xml |   37 ++++++++++++++++++++++
 1 file changed, 37 insertions(+)

New commits:
commit 7333b5d0902508595f2ec7505ba5e4c11bf9e1a8
Author: Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>
Date:   Sun Aug 5 14:54:43 2012 +0100

    Add verbiage about the System Hostname and FQDN to Preparing the System

diff --git a/Installation_Guide/en-US/Preparing_the_System.xml b/Installation_Guide/en-US/Preparing_the_System.xml
index ddabdeb..a4f34c9 100644
--- a/Installation_Guide/en-US/Preparing_the_System.xml
+++ b/Installation_Guide/en-US/Preparing_the_System.xml
@@ -304,6 +304,43 @@ COMMIT</screen>
 
     </section>
 
+    <section id="sect-Community_Installation_Guide-Preparing_the_System-The_System_Hostname_and_FQDN">
+        <title>The System Hostname and FQDN</title>
+        <para>
+            The setup procedure of Kolab Groupware also requires that the Fully Qualified Domain Name (FQDN) for the system resolves back to the system. If the FQDN does not resolve back to the system itself, the Kolab Groupware server components will refer to the system by the configured or detected FQDN, but will fail to communicate with one another.
+        </para>
+        <para>
+            Should the FQDN of the system (found with <command>hostname -f</command>) be, for example, <emphasis>kolab.example.org</emphasis>, then <emphasis>kolab.example.org</emphasis> should resolve to the IP address configured on one of the network interfaces not the loopback interface, and the IP address configured on said network interface should have a reverse DNS entry resulting in at least <emphasis>kolab.example.org</emphasis>
+        </para>
+        <example id="exam-Community_Installation_Guide-The_System_Hostname_and_FQDN-Example_Network_and_DNS_Configuration">
+            <title>Example Network and DNS Configuration</title>
+            <para>
+                The following lists an example network and DNS configuration for a Kolab Groupware server.
+            </para>
+            <para>
+
+<screen># <userinput>hostname -f</userinput>
+kolab.example.org
+# <userinput>ping -c 1 kolab.example.org</userinput>
+PING kolab.example.org (192.168.122.40) 56(84) bytes of data.
+64 bytes from kolab.example.org (192.168.122.40): icmp_seq=1 ttl=64 time=0.014 ms
+
+--- kolab.example.org ping statistics ---
+1 packets transmitted, 1 received, 0% packet loss, time 0ms
+rtt min/avg/max/mdev = 0.014/0.014/0.014/0.000 ms
+# <userinput>ip addr sh eth0</userinput>
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
+    link/ether 52:54:00:72:10:83 brd ff:ff:ff:ff:ff:ff
+    inet 192.168.122.40/24 brd 192.168.122.255 scope global eth0
+    inet6 fe80::5054:ff:fe72:1083/64 scope link
+    valid_lft forever preferred_lft forever</screen>
+
+            </para>
+
+        </example>
+
+    </section>
+
 
 </chapter>
 





More information about the commits mailing list