Comment 7 for bug 1671606

It looks like the resolvconf package was updated on my machine on 3/2/2017 also. Isn't resolvconf responsible for updating DNS info when something like a DNS lease is obtained?

I'm pretty sure I didn't see the problem until after the network-manager package was updated around 3/8/2017, but maybe there was cached information that allowed it to continue to work for a while. I'm not sure how all of this plays together.