As I see it, the only reliable methods found to date are described in message #7 (https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/comments/7), message #17 (https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/comments/17), and message #19 (https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/comments/19).
I like the idea of using a standard resolv.conf unless a more specific one is found on Postfix startup, as proposed in #7, but that is a hack and might lead to problems for "non-standard" DNS configurations, or changes in the Ubuntu way of configuring DNS. A _reliable_ way of restarting on every change of /etc/resolv.conf to pick up the change would be the "right thing to do." AFAIU that should be done by placing a script in /etc/resolveconf/updated.d/. That script could possibly look just like that from message #19. I am going to try something like that, perhaps it works. I hope resolvconf still exists in the systemd world... Thanks, Erik -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
