From time to time when I'm switching from
wlan0 (or vice versa) interface domain name resolving breaks and
/etc/NetworkManager/NetworkManager.conf and restarted network manager with
restart network-manager. But this didn't help.
Then I found that
dnsmasq process is not a child of NetworkManager
# pstree -spu $(pidof dnsmasq) init(1)───dnsmasq(3015,libvirt-dnsmasq)
I'm not sure why it is running. Can it be related to VirtualBox?
I don't want it to touch
resolve.conf. How to disable it?
My system is Linux Mint 17 Qiana.
dnsmasqis a good software and it knows why it overwrites
nameserver 127.0.1.1value. So why it doesn't do its job then?
/etc/resolv.confshould always contain
nameserver 127.0.0.1, because it handles all DNS requests. With NetworkManager+dnsmasq, what normally happens is that NM sends messages to dnsmasq over dbus to tell it when connections change. Why isn't it doing it? That's a question you could ask on this site — with all necessary explanations about your network setup.
127.0.0.1) and where it is configured?
127.points to the local machine. I don't know why 127.0.1.1 is used here. Anyway, if you want help with dnsmasq, you need to ask a new question where you explain your setup, including why VirtualBox is involved at all (is your system running in a VM? Or is it a VM host? What kind of VM configurations have you made? etc.).