I tried manually to add in
/etc/resolv.conf
nameserver 127.0.0.1 and now is working!
But after I Restarted the server the /etc/resolv.conf is Generated by NetworkManager and again the problem is here!
???
THE SOLUTION:
https://wiki.debian.org/NetworkConfiguration#Using_DHCP_to_automatically_configure_the_interface
The resolv.conf configuration file
The configuration file resolv.conf at /etc/resolv.conf contains information that allows a computer connected to a network to resolve names into addresses. (Note: Do not confuse this configuration file with the program resolvconf, which unfortunately has a nearly identical name.)
The resolv.conf file typically contains the IP addresses of nameservers (DNS name resolvers) that will attempt to translate names into addresses for any node available on the network. There will be a line or lines that look like this:
nameserver 12.34.56.78
nameserver 12.34.56.79
In this example, the system is using nameservers at the IP addresses 12.34.56.78 and 12.34.56.79. Simply edit the file and enter the IP addresses of the nameservers you need to use after each nameserver. Add more nameserver lines if you have more nameservers. Don’t use this method if you have the resolvconf program installed.
The resolv.conf configuration file has many other options for defining how resolver looks up names. See man resolv.conf for details.
The resolvconf program
The resolvconf program keeps track of system information about the currently available nameservers. It should not be confused with the configuration file resolv.conf, which unfortunately has a nearly identical name. The resolvconf program is optional on a Debian system.
The configuration file resolv.conf contains information about the nameservers to be used by the system. However, when multiple programs need to dynamically modify the resolv.conf configuration file they can step on each other and the file can become out-of-sync. The resolvconf program addresses this problem. It acts as an intermediary between programs that supply nameserver information (e.g. dhcp clients) and programs that use nameserver information (e.g. resolver).
When resolvconf is properly installed, the resolv.conf configuration file at /etc/resolv.conf is replaced by a symbolic link to /etc/resolvconf/run/resolv.conf and the resolver instead uses the configuration file that is dynamically generated by resolvconf at /etc/resolvconf/run/resolv.conf.
The resolvconf program is generally only necessary when a system has multiple programs that need to dynamically modify the nameserver information. In a simple system where the nameservers do not change often or are only changed by one program, the resolv.conf configuration file is adequate.
If the resolvconf program is installed, you should not edit the resolv.conf configuration file manually as it will be dynamically changed by programs in the system. If you need to manually define the nameservers (as with a static interface), add a line something like the following to the interfaces configuration file at /etc/network/interfaces:
dns-nameservers 12.34.56.78 12.34.56.79
Place the line indented within an iface stanza, e.g., right after the gateway line. Enter the IP addresses of the nameservers you need to use after dns-nameservers. Put all of them on one line separated by spaces. Don’t forget the “s” on the end of dns-nameservers.
The resolvconf program is a fairly new addition to Debian and many older programs need to be updated or reconfigured to work properly with it. If you have problems, see /usr/share/doc/resolvconf/README. It has lots of information on making other programs get along with resolvconf.
I addeded in at /etc/network/interfaces:
search 77.xx.xx.55 mydomain.com
dns-nameservers 127.0.0.1 99.XX.66.0 192.168.0.1 192.168.0.165
dns-domain 77.xx.xx.55 mydomain.com
Hope this will help!
Did you do a minimal install of Debian? You really don’t need NetworkManager on a server. Personally, I’d ditch it in this case as it’s getting in the way of your configuration.
Seems like you’re using DHCP to set your IP and network configuration. That’s not really suitable for servers (Virtualmin will work with it, but it’s a bad idea on a bunch of other fronts). You can configure NetworkManager to include 127.0.0.1 as a DNS server on the system, even if you don’t switch to a statically configured network.
Also note this warning is about a few optional features of Virtualmin; it is not strictly mandatory, it just allows the Virtualmin Preview Website feature to work even before DNS propagates, among other things.
for anyone who cannot wait and want to try it, install debian jessie, then install virtualmin and then do distro upgrade…or if you sit on jessie, just do distro upgrade, reboot couple of times and you should be on debian9. I’ve done this accidentally but it all works. Normally I would wait for couple of months with upgrade like this or do fresh install but its done now.
Hello all;
Any news about new script to install Virtualmin on debian 9 ?
If you are keen to get started, you could try the beta installer from this thread --> https://www.virtualmin.com/node/52613
It works pretty well, and the more people that try it and report their results, the faster everything will be ready.