mariux64: After a fileserver reboot, sometimes the filesystems are not exported to all clients

[donald]

We are not sure, why this happens. It is assumed, that the nameserver is overloaded and failing during exportfs -a. If the exportfs -a is repeated manually, the problem is usually fixed.

While the exports are stored with hostnames in the kernel (really?), exportfs tries to canonicalize the hostname. This might involve reverse mapping (really?), so the "in-addr.arpa" Domain has to be used. It might take some time to verify the DNSSEC trust chain, from the top level domain after unbound has been freshly started.

[donald]

• Schedule some more exportfs -a in intervals after boot?
• Distribute a /etc/hosts which includes the systems from the amd group?