systemd-resolved can not resolve .coop domain names
Bug #1682386 reported by
Angel Aguilera
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.
> 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
>
Changed in systemd (Ubuntu): | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
This is the output of "systemd-resolve --status":
$ sudo systemd-resolve --status
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
Global
DNSSEC NTA: 10.in-addr.arpa
Link 2 (wlp2s0)
87.216. 1.66
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
DNS Domain: Home