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)
On 7/29/2021 12:34 AM, Matus UHLAR - fantomas wrote:
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?
On 29.07.21 12:18, Jim Garrison wrote:
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.
that is "local, configured hostname", not a "localhost" since localhost is
supposed to point to 127.0.0.1, as immediately next section says.
However it's OT here.
Postfix must not attempt to start until the network is completely up.
Agree. this seems to be resolved now.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I'm not interested in your website anymore.
If you need cookies, bake them yourself.
