Klaus Frank

``` Global LLMNR setting: yes MulticastDNS setting: yes DNSOverTLS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Fallback DNS Servers: 1.1.1.1 9.9.9.10 8.8.8.8 2606:4700:4700::1111 2620:fe::10 2001:4860:4860::8888 DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa...

I already left the train. Are there any other things I could do to help finding the root cause of this issue when I'm traveling again after holidays?

``` -- Logs begin at Sun 2018-11-18 21:58:42 CET, end at Wed 2018-12-26 18:11:50 CET. -- (...) Dec 26 18:07:32 archBook systemd-resolved[545]: Using degraded feature set (UDP+EDNS0+DO) for DNS server...

@norg The only workaround that I know is to disable systemd-resolved. just stopping it is not enough, as it will get restarted automatically.

@poettering Do you need something else? Or do you have all required information?

The error is dnssec related. Once you turn off dnssec within the config resolving queries again works. Since recently I also have this problem within another network (no captive portal),...

Ok, there seem to be network filtering (at least at universities eduroam) that drops DNSSEC dns queries, as cloudflare is returning DNSSEC at my home network just fine. Therefore using...

https://twitter.com/agowa338/status/1129481536175316992

!component systemd_service

!component lib/ansible/modules/systemd_service.py