My environment is following, all cabled with gigalan, all latest Debian 9, vm with virtualbox on 2 different physical hosts.

  • A mikrotik internet router which acts as DHCPD
    • I configured it setting the domain (myCompany.local)
    • To give always the same IP to following machines
  • A virtualmachine (Debian BIND9) in my environment (physical host 1)
  • Have different client virtual machines lets say vm1, vm2 (Physical host 1)
  • My workstation which the only difference I know is it has a wlan0 interface

My ultimate goal is not having to configure the workstations and let the DHCP Server give the domain (myCompany.local) and the IP Address of DNS Server. I read that there are some practices that don't seem to do like that. So I don't know if

  • my approach is wrong
  • my configuration is wrong
  • I'm wrong
  • There is a computer world conspiracy ;-)
  • In some machines the network-manager from plasma takes the hand over the other network manager (which I understood is the network service which takes dhclient with /etc/dhcp/dhclient.conf as config file to give requests to the server??!!
  • I'm really wrong about all that

Here is my configuration:

/etc/hosts       localhost.localdomain   localhost       localhost myLptp        myLptp.myCompany.local

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
**strong text**


source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

auto wlan0

allow-hotplug eth0
iface eth0 inet dhcp

on myLptp /etc/resolv.conf automatically configured by dhclient


on vms /etc/resolv.conf automatically configured by dhclient

# Generated by NetworkManager
search myDomain.local
  • You should make sure your interfaces are either being managed by static configuration or NetworkManager only. – CameronNemo Aug 3 '18 at 2:15
  • @CameronNemo how do I do that? – Philippe Gachoud Aug 3 '18 at 11:32
  • maybe part of the answer is that, on my not working machine /etc/resolv.conf is a static file and on the other workings, it is a symlink /var/run/NetworkManager/resolv.conf – Philippe Gachoud Aug 3 '18 at 13:05

Seems that part of the answer of my problem was following. I don't know why, but the attributes of the file were changed so that it was immutable.

~$ lsattr /etc/resolv.conf
----i---------e---- /etc/resolv.conf

When I sudo chattr -i /etc/resolv.conf everything came to normal and I could get the first domain and nameserver from DHCP Client

~$ lsattr /etc/resolv.conf
--------------e---- /etc/resolv.conf

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.