I hit the systemd wall (probably)

Questions about cabled networking
Forum rules
Before you post please read how to get help
User avatar
yossarian_yon
Level 1
Level 1
Posts: 23
Joined: Sun Jun 03, 2018 3:21 am

Re: I hit the systemd wall (probably)

Post by yossarian_yon » Thu Dec 20, 2018 1:10 pm

Back on "M19C", manualy changed resolv.conf in /ETC. There is clash between two DNS and 55 is not working
here is output

Code: Select all

yoss@gray:~$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor
   Active: active (running) since Thu 2018-12-20 17:55:57 CET; 53s ago
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
 Main PID: 595 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-resolved.service
           └─595 /lib/systemd/systemd-resolved

Dec 20 17:55:57 gray systemd[1]: Starting Network Name Resolution...
Dec 20 17:55:57 gray systemd-resolved[595]: Positive Trust Anchors:
Dec 20 17:55:57 gray systemd-resolved[595]: . IN DS 19036 8 2 49aac11d7b6f644670
Dec 20 17:55:57 gray systemd-resolved[595]: . IN DS 20326 8 2 e06d44b80b8f1d39a9
Dec 20 17:55:57 gray systemd-resolved[595]: Negative trust anchors: 10.in-addr.a
Dec 20 17:55:57 gray systemd-resolved[595]: Using system hostname 'gray'.
Dec 20 17:55:57 gray systemd[1]: Started Network Name Resolution.


yoss@gray:~$ systemd-resolve --status
Global
         DNS Servers: 192.168.5.55
          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 (enp2s0)
      Current Scopes: DNS
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
         DNS Servers: 1.1.1.1

yoss@gray:~$ systemd-resolve --flush-caches
yoss@gray:~$ systemd-resolve google.com
google.com: 172.217.23.206

-- Information acquired via protocol DNS in 17.2ms.
-- Data is authenticated: no
67 but still kicking

gm10
Level 19
Level 19
Posts: 9153
Joined: Thu Jun 21, 2018 5:11 pm

Re: I hit the systemd wall (probably)

Post by gm10 » Thu Dec 20, 2018 1:42 pm

yossarian_yon wrote:
Thu Dec 20, 2018 1:10 pm
manualy changed resolv.conf in /ETC. There is clash between two DNS and 55 is not working
That's an automatically generated file, it will be overwritten next boot at the latest. What did you change?

Also all your output looks just fine, I don't see any issues at all. Your DNS is working correctly using the .55 server, so what's the issue with that one?

User avatar
yossarian_yon
Level 1
Level 1
Posts: 23
Joined: Sun Jun 03, 2018 3:21 am

Re: I hit the systemd wall (probably)

Post by yossarian_yon » Thu Dec 20, 2018 2:04 pm

gm10 wrote:
Thu Dec 20, 2018 1:42 pm
yossarian_yon wrote:
Thu Dec 20, 2018 1:10 pm
manualy changed resolv.conf in /ETC. There is clash between two DNS and 55 is not working
That's an automatically generated file, it will be overwritten next boot at the latest. What did you change?

Also all your output looks just fine, I don't see any issues at all. Your DNS is working correctly using the .55 server, so what's the issue with that one?
I know it will be overwritten but before that doesn't connect. And .55 is down and i can't connect over ssh to that server
so I put in Net. manager 1.1.1.1 but it doesn't connect without manual change of resolv.conf. Complete mess.
It's enough for today, my brain is spinning. Have good day and thanks for everything
67 but still kicking

gm10
Level 19
Level 19
Posts: 9153
Joined: Thu Jun 21, 2018 5:11 pm

Re: I hit the systemd wall (probably)

Post by gm10 » Thu Dec 20, 2018 2:20 pm

Oh, my bad, that connection is on 1.1.1.1, I got confused by the global DNS server definition which shouldn't even be there - resolv.conf should just point to 127.0.0.53 and the rest is handled by systemd internally. Your DNS servers should only be configured in the Network Manager connection settings, i.e. that's where the 1.1.1.1 should be.

User avatar
yossarian_yon
Level 1
Level 1
Posts: 23
Joined: Sun Jun 03, 2018 3:21 am

Re: I hit the systemd wall (probably)

Post by yossarian_yon » Thu Dec 20, 2018 2:30 pm

gm10 wrote:
Thu Dec 20, 2018 2:20 pm
Oh, my bad, that connection is on 1.1.1.1, I got confused by the global DNS server definition which shouldn't even be there - resolv.conf should just point to 127.0.0.53 and the rest is handled by systemd internally. Your DNS servers should only be configured in the Network Manager connection settings, i.e. that's where the 1.1.1.1 should be.
That's exactly what I done, and tomorrow will be smarter. Thank you I learned a lot.
67 but still kicking

Post Reply

Return to “Ethernet”