On 7/29/2021 12:34 AM, Matus UHLAR - fantomas wrote:
On 28.07.21 12:54, Jim Garrison wrote:
This means that Postfix now starts up before the network is completely
up, and systemd's DNS resolution hack (systemd-resolved.service),
finding no interfaces up yet, resolves 'localhost' to 127.0.0.2.
(man systemd-resolved.service)
sorry, but this manpage says that localhost resolvs to 127.0.0.1
(as it always should).
according to systemd-resolved manpage, the local host name is resolved to
127.0.0.2 (not localhost)
maybe a just mistake in your description?
No, from man systemd-resolved.service:
systemd-resolved synthesizes DNS resource records (RRs) for the
following cases:
· The local, configured hostname is resolved to all locally
configured IP addresses ordered by their scope, or — if
none are configured — the IPv4 address 127.0.0.2 (which is
on the local loopback) and the IPv6 address ::1 (which is
the local host).
So if the network isn't actually up yet, DNS queries get resolved by
systemd-resolved. This explains how I could see the error message
about 127.0.0.2 without that IP address appearing anywhere.
Postfix must not attempt to start until the network is completely up.
--
Jim Garrison
j...@acm.org
