systemd-resolved

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

systemd-resolved

ubuntu-users mailing list
Hi,

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:

:~$ ping www.ziggogo.tv
ping: www.ziggogo.tv: Temporary failure in name resolution

When I try to ping with version number specified all words OK.

:~$ ping -4 www.ziggogo.tv
PING wp-a49d720000000000.id.cdn.upcbroadband.com (212.142.30.150) 56(84)
bytes of data.
^C64 bytes from 212.142.30.150: icmp_seq=1 ttl=55 time=7.28 ms

--- wp-a49d720000000000.id.cdn.upcbroadband.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.286/7.286/7.286/0.000 ms

:~$ ping -6 www.ziggogo.tv
PING www.ziggogo.tv(2001:730:3400:8000::16 (2001:730:3400:8000::16)) 56
data bytes
64 bytes from 2001:730:3400:8000::16 (2001:730:3400:8000::16):
icmp_seq=1 ttl=55 time=5.87 ms
^C
--- www.ziggogo.tv ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 5.875/5.875/5.875/0.000 ms

If i do a host lookup I get the following result:

:~$ host www.ziggogo.tv
www.ziggogo.tv is an alias for wp-a49d720000000000.id.cdn.upcbroadband.com.
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.150
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.180
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.144
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.166
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.148
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.170
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.138
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.136
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.182
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.142
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.164
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.134
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.168
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.132
wp-a49d720000000000.id.cdn.upcbroadband.com has address 212.142.30.140
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::16
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8001::14
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::10
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8001::6
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::14
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8001::a
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::a
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::8
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8001::16
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::e
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8001::4
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::6
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8001::8
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::4
wp-a49d720000000000.id.cdn.upcbroadband.com has IPv6 address
2001:730:3400:8000::c

The config of /etc/systemd/resolved.conf is default:
[Resolve]
#DNS=
#FallbackDNS=
#Domains=
#LLMNR=yes
#DNSSEC=no
#Cache=yes
#DNSStubListener=udp


Probably I has to do with the massive records. Both zones ziggogo.tv and
upcbroadband.com doesn't have any DNSSec enabled.

Kinds regards,

Michiel Piscaer

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: systemd-resolved

Liam Proven
On 13 December 2017 at 14:00, M. Piscaer via ubuntu-users
<[hidden email]> wrote:

> Hi,
>
> 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:

I have no idea if this is relevant, I'm afraid, but just in case it is
helpful, I had the problem described in this link and the steps given
sorted it for me:

https://askubuntu.com/questions/965527/dns-problems-after-upgrading-from-16-04-to-17-10-how-to-reset-the-dns-settings


--
Liam Proven • Profile: https://about.me/liamproven
Email: [hidden email] • Google Mail/Talk/Plus: [hidden email]
Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven
UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: systemd-resolved

ubuntu-users mailing list
Hi,


On 13-12-17 15:39, Liam Proven wrote:

> On 13 December 2017 at 14:00, M. Piscaer via ubuntu-users
> <[hidden email]> wrote:
>> Hi,
>>
>> 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:
>

I did an little test with test-size.masterpe.nl. If I put 13 A records
and 12 AAAA records, with an total of 25 all works fine. And I can ping
to that record.

If I add one record to A or AAAA so the total will become 26, I can't
ping any more and I get the error:

:~$ ping test-size.masterpe.nl
ping: test-size.masterpe.nl: Temporary failure in name resolution

Is it possible that I hit a bug in systemd-resolved?



> I have no idea if this is relevant, I'm afraid, but just in case it is
> helpful, I had the problem described in this link and the steps given
> sorted it for me:
>
> https://askubuntu.com/questions/965527/dns-problems-after-upgrading-from-16-04-to-17-10-how-to-reset-the-dns-settings
>
>

I can resolve query's only when the answer gets to big I hit this issue.

Kind regards,

Michiel Piscaer

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: systemd-resolved

Tom H-4
In reply to this post by ubuntu-users mailing list
On Wed, Dec 13, 2017 at 8:00 AM, M. Piscaer via ubuntu-users
<[hidden email]> 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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: systemd-resolved

ubuntu-users mailing list


On 14-12-17 13:15, Tom H wrote:

> On Wed, Dec 13, 2017 at 8:00 AM, M. Piscaer via ubuntu-users
> <[hidden email]> 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

Kind regards,

Michiel Piscaer

--

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: systemd-resolved

Tom H-4
On Thu, Dec 14, 2017 at 7:27 AM, M. Piscaer via ubuntu-users
<[hidden email]> wrote:

> On 14-12-17 13:15, Tom H wrote:
>> On Wed, Dec 13, 2017 at 8:00 AM, M. Piscaer via ubuntu-users
>> <[hidden email]> 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.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: systemd-resolved

ubuntu-users mailing list


On 14-12-17 23:27, Tom H wrote:

> On Thu, Dec 14, 2017 at 7:27 AM, M. Piscaer via ubuntu-users
> <[hidden email]> wrote:
>> On 14-12-17 13:15, Tom H wrote:
>>> On Wed, Dec 13, 2017 at 8:00 AM, M. Piscaer via ubuntu-users
>>> <[hidden email]> 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
>>

<... SNIP ....>
>
> 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.
>

I have created an bug:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1738375

I hope that I have done it correctly.

Kind regards,

Michiel Piscaer


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: systemd-resolved

Tom H-4
On Tue, Dec 19, 2017 at 6:44 AM, M. Piscaer via ubuntu-users
<[hidden email]> wrote:
>
> I have created an bug:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1738375

Thanks for letting us know.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users