Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
resolved stub resolver doesn't provide RRSIG data in replies when DO/CD queries are sent to it #4621
systemd version the issue has been seen with
In case of bug report: Expected behaviour you didn't see
In case of bug report: Unexpected behaviour you saw
In case of bug report: Steps to reproduce the problem
Well, resolved is not supposed to be a DNS server, it's supposed to be exactly good enough so that libc-like DNS clients can resolve their stuff, and we carry enough info for the AD bit to be set. That's by design really. See the commit msg of b30bf55.
If we don't set AD properly for negative replies, that'd be a bug however, indeed.
Op 12-11-16 om 05:37 schreef Lennart Poettering:
Thanks Lennart. I understand systemd-resolved is not a fully fledged
ldns and getdns can do this for example.
Perhaps this could be a enhancement request then?
Also, I have to admit that I cannot find it specified in the RFCs right
changed the title
resolved doesn't set AD properly for negative replies on stub listener
Nov 14, 2016
Hi, I'm not sure if I'm seeing the same issue, or at least a variant of the same issue.
I configured my system (ubuntu 16.10) to use systemd as the dns resolver, and that broke lookups of RRSIG records.
If i try to use dig i get this result:
and by using systemd-resolve directly i get this result:
referenced this issue
May 9, 2017
Please, help! Or in other words, I would like to have an answer to Anders’ question above. My very own app which does DANE, broke on Ubuntu 18.04 LTS. It worked great in Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. This is a software bug for sure. Now, I have to report this somewhere, even if it is to myself.
$ dig @127.0.0.1 www.nlnetlabs.nl. A +dnssec
$ dig @18.104.22.168 www.nlnetlabs.nl. A +dnssec
Yet another example
There must be a totally easy answer, which I do not see. My app does not work on default in Ubuntu 18.04 LTS at all, because the DNS result is even ‘bogus’. Please, help!
I cross-posted this on the Unbound mailing-list…
referenced this issue
Jun 8, 2018
@traud I don't know the official answer, but I did (A). https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782679
According to the BIND docs, the tool
I stumbled over this issue here because I was wondering and debugging why
Of course, one can always manually tell