systemd-resolved

Tom H tomh0665 at gmail.com
Thu Dec 14 22:27:44 UTC 2017


On Thu, Dec 14, 2017 at 7:27 AM, M. Piscaer via ubuntu-users
<ubuntu-users at lists.ubuntu.com> wrote:
> On 14-12-17 13:15, Tom H wrote:
>> On Wed, Dec 13, 2017 at 8:00 AM, M. Piscaer via ubuntu-users
>> <ubuntu-users at lists.ubuntu.com> wrote:
>>>
>>> On an Ubuntu 17.04 system I try to surf to www.ziggogo.tv. In chrome I
>>> get the message:
>>>
>>> This site can’t be reached
>>> www.ziggogo.tv’s server DNS address could not be found.
>>>
>>> DNS_PROBE_FINISHED_NXDOMAIN
>>>
>>> Firefox has also the same issue. When I try to ping the addresses I
>>> get an error:
>>
>> What's the output of
>>
>> ls -l /etc/resolv.conf
>> cat /etc/resolv.conf
>> grep hosts /etc/nsswitch.conf
>> systemd-resolve --status
>> dig
>
> :~$ ls -l /etc/resolv.conf
> lrwxrwxrwx 1 root root 29 dec 13 13:17 /etc/resolv.conf ->
> ../run/resolvconf/resolv.conf
>
> :~$ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> # 127.0.0.53 is the systemd-resolved stub resolver.
> # run "systemd-resolve --status" to see details about the actual
> nameservers.
>
> nameserver 127.0.0.53
>
> :~$ grep hosts /etc/nsswitch.conf
> hosts:          mdns4_minimal resolve [!UNAVAIL=return] dns myhostname
>
> :~$ 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 7 (lxcbr0)
>       Current Scopes: none
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>
> Link 6 (virbr0-nic)
>       Current Scopes: none
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>
> Link 5 (virbr0)
>       Current Scopes: none
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>
> Link 4 (wlp2s0)
>       Current Scopes: none
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>
> Link 3 (wwp0s20f0u2i12)
>       Current Scopes: none
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>
> Link 2 (enp0s31f6)
>       Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>          DNS Servers: 172.17.24.21
>           DNS Domain: masterpe.nl
>
> :~$ dig
>
> ; <<>> DiG 9.10.3-P4-Ubuntu <<>>
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39021
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 65494
> ;; QUESTION SECTION:
> ;.                              IN      NS
>
> ;; ANSWER SECTION:
> .                       507806  IN      NS      a.root-servers.net.
> .                       507806  IN      NS      e.root-servers.net.
> .                       507806  IN      NS      d.root-servers.net.
> .                       507806  IN      NS      m.root-servers.net.
> .                       507806  IN      NS      b.root-servers.net.
> .                       507806  IN      NS      i.root-servers.net.
> .                       507806  IN      NS      h.root-servers.net.
> .                       507806  IN      NS      j.root-servers.net.
> .                       507806  IN      NS      c.root-servers.net.
> .                       507806  IN      NS      l.root-servers.net.
> .                       507806  IN      NS      k.root-servers.net.
> .                       507806  IN      NS      g.root-servers.net.
> .                       507806  IN      NS      f.root-servers.net.
>
> ;; Query time: 5 msec
> ;; SERVER: 127.0.0.53#53(127.0.0.53)
> ;; WHEN: Thu Dec 14 13:24:12 CET 2017
> ;; MSG SIZE  rcvd: 239

Everything looks OK. I've just read your other/previous email about
systemd-resolved failing when going from 25 to 26 records and it looks
like you've hit a bug.



More information about the ubuntu-users mailing list