Comment 4 for bug 1567957

It's because of NetworkManager. It reset /etc/resolv.conf. We've been pushing toward disabling it from the very beginning of deployment. I will investigate how to block it from updating /etc/resolv.conf and again about disabling it. To work around, just add the IP of your Fuel Master as the first nameserver