Comment 9 for bug 1672099

I just found that I can reproduce this loop state by reconnecting to my Wi-Fi access point. The storm starts right after this line, 5 seconds after the link comes up:

systemd-resolved[1188]: Server 127.0.0.1 does not support DNSSEC, downgrading to non-DNSSEC mode.

The (much shorter this time) syslog extract is attached.

The only reference I can find to 127.0.0.53 in the settings (other than comment lines) is in /run/resolvconf/interface/systemd-resolved:

nameserver 127.0.0.53

So I also don't know how dnsmasq gets that address unless it reads that config file for some reason (no mention of it in source), derives it from an incoming request, or gets it via D-Bus.