I experience this on Zesty, on an always-on machine, that however relies on DHCP for network configuration.
I would argue that this is an upstream bug, or if you want a design flaw. It is perfectly normal for resolv.conf to change at arbitrary moments. Examples are VPN and alternative redundant connectivity for a host. It seems wrong for a server to rely on a static snapshot of network configuration, because that configuration may change with time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519331 Title: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
