Hi,

my database backup process for a web app reaches the IPv6 only database
server via IPv6. I would love to modify the corresponding service that
is started from a timer to not have AF_INET in RestrictAddressFamilies.

But since systemd-resolved listens on IPv4 only and the stub-resolv.conf
that my /etc/resolv.conf is linked to only consider IPv4, I need to
allow AF_INET for the host to resolve.

Please consider adding the possibility of using systemd-resolved
IPv4-less in a future version of your package.

Greetings
Marc

Already possible:

Add
DNSStubListenerExtra=::1
in the resolved config file.

This could be made default too upstream or in Debian.

Sadly that is only half the way since one needs to point
/etc/resolv.conf to the IPv6 resolved address as well. And
/run/systemd/resolve/stub-resolv.conf seems to be hardwired to
127.0.0.53:

|  systemd-resolved maintains the /run/systemd/resolve/stub-resolv.conf file for
|  compatibility with traditional Linux programs. This file lists the 127.0.0.53
|  DNS stub (see above) as the only DNS server.

Greetings
Marc