You are not logged in.

Pages: 1

#1 2018-09-28 08:39:23

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,163
Website

[solved] systemd-resolved not resolving DNS queries

On our digital signage systems, we use systemd-networkd in combination with systemd-resolved to provide network connection and DNS resolution.
The systemd-networkd configuration is as follows:

$ cat /etc/systemd/network/50-wired.network 
[Match]
Name=en*

[Network]
DHCP=yes

The systemd-resolved configuraion is the default:

$ cat /etc/systemd/resolved.conf 
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
#FallbackDNS=1.1.1.1 9.9.9.10 8.8.8.8 2606:4700:4700::1111 2620:fe::10 2001:4860:4860::8888
#Domains=
#LLMNR=yes
#MulticastDNS=yes
#DNSSEC=allow-downgrade
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=udp

Since some recent update the DNS resolving does not work any longer within the network of our manufacturer.
It worked, however with an image of an Arch Linux snapshot from a couple of months ago.
Since then, I did not change any systemd-networkd or systemd-resolved related configuration.
The current setup also works in my company's office and on our digital signage systems in the wild.
However our manufacturer claims that they did not change their network setup and that the respective hardware would get DNS resolution with windows.
So I have to consider, that some systemd-resolved related changes resulted in our systemd not getting DNS resolution at our manufacturer's office.
Also, a migration from systemd-networkd and systemd-resolved to dhcpcd fixes the issue. I.e. the failing DNS resolution does not occur with dhcpcd.
However migrating (back) to dhcpcd is not a good option, since we migrated from it to systemd-* because of other issues we had with dhcpcd on our productive systems in the wild.

As for further information on the setup, the resolv.conf is linked as suggested in the wiki and systemd manual:

$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 39 28. Sep 10:08 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

The log of systemd-resolved on the problematic system in out manufacturer's network is as follows:

$ journalctl -u systemd-resolved -b --no-pager
-- Logs begin at Tue 2018-06-26 12:44:11 CEST, end at Fri 2018-09-28 11:11:17 CEST. --
Sep 28 10:08:46 1.6041001 systemd[1]: Starting Network Name Resolution...
Sep 28 10:08:46 1.6041001 systemd-resolved[284]: Positive Trust Anchors:
Sep 28 10:08:46 1.6041001 systemd-resolved[284]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Sep 28 10:08:46 1.6041001 systemd-resolved[284]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Sep 28 10:08:46 1.6041001 systemd-resolved[284]: Negative trust anchors: 10.in-addr.arpa 16.172.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 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Sep 28 10:08:46 1.6041001 systemd-resolved[284]: Using system hostname '1.6041001'.
Sep 28 10:08:47 1.6041001 systemd[1]: Started Network Name Resolution.
Sep 28 10:08:47 1.6041001 systemd-resolved[284]: request_name_destroy_callback n_ref=1
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question arch.pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question arch.pool.ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 1.arch.pool.ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 1.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 2.arch.pool.ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 2.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 3.arch.pool.ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 3.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 1.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 1.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 2.arch.pool.NTP.oRg IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 2.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 2.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 3.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 3.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question arch.pool.NTP.oRg IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.NTP.oRg IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.ntp.org IN A: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question arch.pool.NTP.oRg IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 1.arch.pool.NTP.oRg IN DS: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 1.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:08:50 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 1.arch.pool.ntp.org IN A: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 2.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 2.arch.pool.ntp.org IN A: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 3.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 3.arch.pool.ntp.org IN A: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN SOA: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.NTP.oRg IN DS: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.NTP.oRg IN SOA: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question 0.arch.pool.ntp.org IN A: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question ntp.org IN DS: no-signature
Sep 28 10:09:02 1.6041001 systemd-resolved[284]: DNSSEC validation failed for question pool.ntp.org IN DS: no-signature
[snip]

I am confused about all the DNSSEC validation errors but am not sure whether they are related to the problem.
For comparison, here's an excerpt of the log from one of our productive systems out there:

$ journalctl -au systemd-resolved --since=10:30
-- Logs begin at Mon 2018-02-19 08:56:05 CET, end at Fri 2018-09-28 10:31:29 CEST. --
Sep 28 10:31:25 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 217.172.in-addr.arpa IN SOA: no-signature
Sep 28 10:31:25 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 19.217.172.in-addr.arpa IN DS: no-signature
Sep 28 10:31:25 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 19.217.172.in-addr.arpa IN SOA: no-signature
Sep 28 10:31:25 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN DS: no-signature
Sep 28 10:31:25 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN SOA: no-signature
Sep 28 10:31:25 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN PTR: no-signature
Sep 28 10:31:27 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 217.172.in-addr.arpa IN SOA: no-signature
Sep 28 10:31:27 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 19.217.172.in-addr.arpa IN DS: no-signature
Sep 28 10:31:27 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN DS: no-signature
Sep 28 10:31:27 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN SOA: no-signature
Sep 28 10:31:27 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN PTR: no-signature
Sep 28 10:31:29 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 217.172.in-addr.arpa IN SOA: no-signature
Sep 28 10:31:29 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 19.217.172.in-addr.arpa IN DS: no-signature
Sep 28 10:31:29 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 19.217.172.in-addr.arpa IN SOA: no-signature
Sep 28 10:31:29 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN DS: no-signature
Sep 28 10:31:29 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN SOA: no-signature
Sep 28 10:31:29 300.1030020 systemd-resolved[304]: DNSSEC validation failed for question 67.19.217.172.in-addr.arpa IN PTR: no-signature

Both systems are identical in configuration and hardware.
The only difference is the network, they run on.
Pinging on the system is the wild works:

$ ping google.de
PING google.de (172.217.19.67) 56(84) bytes of data.
64 bytes from 172.217.19.67: icmp_seq=1 ttl=55 time=23.8 ms
64 bytes from 172.217.19.67: icmp_seq=2 ttl=55 time=22.6 ms
^C
--- google.de ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 33ms
rtt min/avg/max/mdev = 22.579/23.204/23.829/0.625 ms

However, interestingly, the first ping response took about 10 seconds to appear.
On the problematic system in our manufacturer's office it does not:

$ LANG=C ping google.de
ping: google.de: Name or service not known

Finally, here are the excerpts of resolvectl.
Working system in the wild:

$ resolvectl --no-pager
Global
       LLMNR setting: yes
MulticastDNS setting: yes
  DNSOverTLS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes
Fallback DNS Servers: 1.1.1.1
                      9.9.9.10
                      8.8.8.8
                      2606:4700:4700::1111
                      2620:fe::10
                      2001:4860:4860::8888
          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 4 (tun0)
      Current Scopes: LLMNR/IPv4 LLMNR/IPv6
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes

Link 3 (enp4s0)
      Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes
  Current DNS Server: 81.209.202.46
         DNS Servers: 217.71.105.254
                      81.209.202.46
                      8.8.8.8

Link 2 (enp3s0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes

Problematic system at our manufacturer's:

$ resolvectl --no-pager
Global
       LLMNR setting: yes
MulticastDNS setting: yes
  DNSOverTLS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes
Fallback DNS Servers: 1.1.1.1
                      9.9.9.10
                      8.8.8.8
                      2606:4700:4700::1111
                      2620:fe::10
                      2001:4860:4860::8888
          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 4 (tun0)
      Current Scopes: LLMNR/IPv4 LLMNR/IPv6
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes

Link 3 (enp4s0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes

Link 2 (enp3s0)
      Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes
  Current DNS Server: 10.4.0.254
         DNS Servers: 10.4.0.254

I noticed, that on the latter system, the ISP's and fallback Google servers are missing from the list of DNS servers.
Why is that?
Any help is welcome.

Update:
/run/systemd/resolve/stub-resolv.conf of both systems:

$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53

/run/systemd/resolve/resolv.conf on the problematic system:

$ sudo cat /run/systemd/resolve/resolv.conf 
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 10.4.0.254

/run/systemd/resolve/resolv.conf on a working system:

$ cat /run/systemd/resolve/resolv.conf 
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 217.71.105.254
nameserver 81.209.202.46
nameserver 8.8.8.8

PPS:
I just read and tried this.
However setting DNSSEC=no does not solve solves the problem.

Sorry for the noise. I wish the search function would yield better results.
You may want to merge this or close for deletion.

Last edited by schard (2018-09-28 10:25:27)

Inofficial first vice president of the Rust Evangelism Strike Force

Offline

Pages: 1

Board footer

Powered by FluxBB