Submission type

• Bug report
• Request for enhancement (RFE)

NOTE: Do not submit anything other than bug reports or RFEs via the issue tracker!

systemd version the issue has been seen with

systemd 232

NOTE: Do not submit bug reports about anything but the two most recently released systemd versions upstream!

Used distribution

debian unstable

RFE

I'm using resolved on a server with 2 upstream tinydns servers that do not support anything but plain UDP.

resolved keeps switching between the two servers, attempting to use the full set of features (UDP+EDNS0+DO+LARGE), fails, switch to degraded mode (UDP), then after a grace period attempts again. I already disabled DNSSEC.

Feb 15 07:13:27 test systemd-resolved[13600]: Switching to system DNS server 80.68.80.24.
Feb 15 07:13:27 test systemd-resolved[13600]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 80.68.80.24.
Feb 15 07:13:27 test systemd-resolved[13600]: Using degraded feature set (UDP) for DNS server 80.68.80.24.

The upstream servers are not going to change on the server environment. These attempts make sense on a desktop system and/or with DHCP, but not when resolved is simply used as a caching resolver with fixed DNS entries.

I need a way to be able to force resolved to always use the degraded feature set, or tune the grace period to something reasonably large (months).