If I go to Host Systems > KVM Host Settings, then the window doesn't open for long time. Monitoring /var/log/messages at the same time gives lots of messages like:
Apr 16 05:10:28 vps2 named[11539]: error (network unreachable) resolving 'guestsystem.vps2.mysite.net.mysite.net/A/IN': 2001:504:c27::2:30#53
Apr 16 05:10:28 vps2 named[11539]: error (network unreachable) resolving './NS/IN': 2001:504:c27::2:30#53
This list is long repeating the same error for all the guest systems we host. I am afraid the problem is that our KVM host automatically generates and assigns hostnames for guest systems like:
guestsystem.vps2.mysite.net.mysite.net
But then, for convenience and aesthetic purposes, we login to every newly created guest system and re-configure its hostname in the form of 'ns1.clientdomain.tld'. It is shorter and more desirable for and by our clients. After that we go to Cloudmin and put 'ns1.clientdomain.tld' for 'Internet hostname' option in "Edit System".
Aren't we allowed to do so? To use custom hostnames using client domain names instead of automatically generated one by Cloudmin? If we are then why the system still is seeking for old hostnames? Clearing DNS records from Cloudmin DNS doesn't also help.
I just wonder if Internet Hostname should always be left the same? Initially it is assigned something like:
Internet hostname: guestname.vps2.mysite.netBut then, after we update hostname within the guest system, then "Unix hostname on system" values changes to:
Unix hostname on system: ns1.guestname.comand then we copy this value to "Internet hostname" field too. Is this screwing up out host system?