resolv.conf file is being overwritten by Plesk setup

Created:

2016-12-12 03:48:10 UTC

Modified:

2017-08-08 13:39:30 UTC

0

Was this article helpful?


Have more questions?

Submit a request

resolv.conf file is being overwritten by Plesk setup

Applicable to:

  • Plesk 12.5 for Linux

Symptoms

/etc/resolv.conf file is being overwritten by Plesk setup:

Initial resolv.conf configuration immediately after VM is built:

# cat /etc/resolv.conf
# Automatically generated by OnApp (4.0.0)
domain localdomain
nameserver 10.10.10.10
nameserver 10.10.10.20

When it Plesk initial set up is done in the interface by assigning an IP and the hostname, resolv.conf is changed:

# cat /etc/resolv.conf
# Generated by NetworkManager
# No nameservers found; try putting DNS servers into your
# ifcfg files in /etc/sysconfig/network-scripts like so:
# DNS1=xxx.xxx.xxx.xxx
# DNS2=xxx.xxx.xxx.xxx
# DOMAIN=lab.foo.com bar.foo.com

The following is logged to /var/log/plesk/panel.log :

NetworkManager[26684]: <debug> [1477442007.695588] [nm-properties-changed-signal.c:152] notify(): ignoring notification for prop hostname on type NMManager
[26684]: <debug> [1477442007.695747] [dns-manager/nm-dns-manager.c:595] update_dns(): updating resolv.conf
# Generated by NetworkManager

Cause

NetworkManager on a VM is configured to overwrite resolv.conf . Plesk does not write anything to resolv.conf .

Resolution

Adjust NetworkManager configuration so that it does not interfere with current resolv.conf using any method, for example, this one:

  1. open the nm conf file /etc/NetworkManager/NetworkManager.conf
  2. add the following line to the [main] section:
    dns=none

If this does not work, contact your network administrator to adjust NetworkManager configuration.

Alternatively, turn NetworkManager off on a VM.

Have more questions? Submit a request
Please sign in to leave a comment.