systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary

Bug #1650877 reported by Fred on 2016-12-18
This bug report is a duplicate of:  Bug #1682499: Disable DNSSEC by default. Edit Remove
This bug affects 16 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)

Bug Description

After I boot Ubuntu 17.04 "Zesty Zapus" (dev)

$ systemd-resolve resolve call failed: DNSSEC validation failed: failed-auxiliary

But after I have started Mozilla Firefox, and I try again it correctly resolves.

$ systemd-resolve

-- Information acquired via protocol DNS in 3.6ms.
-- Data is authenticated: no

This does not only apply to the above mentioned domain.
This seems to be related to a GitHub issue:

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed

I am having real trouble with this error on my 17.04 machine (nightly).

systemd-resolve --service
Resolve call failed: DNSSEC validation failed: failed-auxiliary

Then from one moment to the next suddenly everything works again.

Interstingly I sometimes experience the same as the OP. Starting Firefox seems to "fix" the issue. Chromium does not!

Malte Cornils (malte) wrote :

/etc/systemd/resolv.conf entry DNSSEC=no and enacting a sudo service systemd-resolved restart works around the problem for me. However, DNSSEC with the default (i.e. fallback) should still work.

Starting Firefox does not "fix" the problem for me, though.

humble_coffee (humblecoffee) wrote :

I'm getting this after upgrading to 17.04. Setting DNSSEC=no in /etc/systemd/resolv.conf seems to fix the issue.

Paul Natsuo Kishimoto (khaeru) wrote :

I think this is a consequence of — if so, please mark (also those others listed in #7) as duplicate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers