.. your system is not ready for use by Virtualmin.

I have a clean O/S (CentOS6) install with Virtualmin loaded for management performed by a NOC engineer where my server is co-located. This was done on his advice to make life easy for me due to I am a Network Engineer / Consultant with other duties. I am new to Virtualmin. The problem is many fold in my mind based on what I have read from Virtualmin's configuration screens. Currently I only want to have one web site up and running but I think my main problem is due to the statement returned after re-check of configuration files function within Virtualmin. Supporting screen text is as follows: The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active ..

Your system has 1.83 GB of memory, which is at or above the Virtualmin recommended minimum of 256 MB.

Virtualmin is configured to setup DNS zones, but this system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers, or turn off the BIND feature on the module config page. It appears that DHCP is being used to dynamically configure your network interfaces, which can cause the DNS servers to be set based on settings provided by the DHCP server. Using a static IP address is strongly recommended with Virtualmin.

.. your system is not ready for use by Virtualmin.

Status: 
Closed (fixed)

Comments

Your system has 1.83 GB of memory, which is at or above the Virtualmin recommended minimum of 256 MB.

Virtualmin is configured to setup DNS zones, but this system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers, or turn off the BIND feature on the module config page. It appears that DHCP is being used to dynamically configure your network interfaces, which can cause the DNS servers to be set based on settings provided by the DHCP server. Using a static IP address is strongly recommended with Virtualmin

Howdy -- the error you're seeing there is just suggesting that the /etc/resolv.conf file is missing a "nameserver 127.0.0.1" line. If you add that, it should resolve the issue you're seeing.

As described above, while Virtualmin does add that line for you during the installation process, if your server uses DHCP, that can cause that line to be removed after rebooting.

If you had any followup questions, it looks like you're using Virtualmin GPL there... and the best place to ask questions in that case would be in the Forums, which you can access using the "Forums" link above. We monitor the Forums, along with lots of wonderful folks in the community. Thanks!

Thank you for your timely response. I have just edited the /etc/resolv.conf file and rebooted the server. I do have follow up questions but will have to wait for the server to come back online. I will attempt to work through the other issues and questions I have by asking questions in the forum.

Again thank you very much!