systemd-resolved can not resolve .coop domain names

Bug #1682386 reported by Angel Aguilera
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I am using Ubuntu Gnome 17.04, systemd version 232-21ubuntu2.

I found that .coop domain nomes are not being resolved. If I switch to another DNS server (instead of 127.0.0.53, which is the current default in 17.04), then .coop domains are resolved:

$ nslookup
> www.somenergia.coop
Server: 127.0.0.53
Address: 127.0.0.53#53

** server can't find www.somenergia.coop: SERVFAIL
> server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
> www.somenergia.coop
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: www.somenergia.coop
Address: 164.132.200.9
>

Revision history for this message
Angel Aguilera (angel-aguilera) wrote :
Revision history for this message
Angel Aguilera (angel-aguilera) wrote :

This is the output of "systemd-resolve --status":

$ sudo systemd-resolve --status
Global
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 2 (wlp2s0)
      Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes
         DNS Servers: 87.216.1.65
                      87.216.1.66
          DNS Domain: Home

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Quentin Henriet (quentin-henriet) wrote :

Same problem after upgrading my two computers from Xubuntu 16.10 and from Kubuntu 16.10 to X/Kubuntu 17.04 today.

Revision history for this message
Jeffrey Blanchard (jeffreyblanchard) wrote :

I just updated to Zesty 17.04 and I am having trouble accessing .coop sites using Chromium and Firefox.

This site can’t be reached
www.gaiahost.coop’s server DNS address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN

I also use a .coop domain for my email server and can't access that either.

Everything still works fine on my other computer running 16.10

Revision history for this message
Quentin Henriet (quentin-henriet) wrote :

It seems to work again with systemd 232-1ubuntu3 which disable DNSSEC.

Revision history for this message
Jeffrey Blanchard (jeffreyblanchard) wrote :

I was just traveling and could access the coop domain, then got back home and used our house internet and no longer had access. Strange. I thought there had been a fix.

Revision history for this message
Jeffrey Blanchard (jeffreyblanchard) wrote :

Most places, including BWI airport, I can not access sites with the coop domain.

Revision history for this message
Jeffrey Blanchard (jeffreyblanchard) wrote :

I just ran the updater and the issue appears solved (for the moment anyway)

Dan Streetman (ddstreet)
Changed in systemd (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.