You are not logged in.

#1 2023-02-16 16:21:26

BrainyXS
Member
Registered: 2023-02-16
Posts: 9

DNS Resolution stopped working

After a system upgrade (pacman -Syu) today, no domain names can be looked up. Networking is working fine, I can "ping 8.8.8.8" and ping "1.1.1.1" which are my DNS servers. However, "ping google.com" or any other domains do not work.
Any help is appreciated.

My /etc/resolv.conf:

# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# 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 should typically 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 1.1.1.1
nameserver 1.1.1.1
nameserver 8.8.8.8
# Too many DNS servers configured, the following entries may be ignored.
nameserver 9.9.9.9
search .

All the IP-Adresses CAN be pinged

dig google.com:
;; communications error to 1.1.1.1#53: timed out
;; communications error to 1.1.1.1#53: timed out
;; communications error to 1.1.1.1#53: timed out
;; communications error to 1.1.1.1#53: timed out
;; communications error to 8.8.8.8#53: timed out

; <<>> DiG 9.18.11 <<>> google.com
;; global options: +cmd
;; no servers could be reached

systemctl status systemd-resolved.service$

 Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Thu 2023-02-16 17:10:03 CET; 10min ago
Feb 16 17:19:28 brainysrv systemd[1]: systemd-resolved.service: Got notification message from PID 459 (WATCHDOG=1)
Feb 16 17:19:45 brainysrv systemd-resolved[459]: Using degraded feature set TCP instead of UDP for DNS server 9.9.9.9.
Feb 16 17:19:59 brainysrv systemd-resolved[459]: Using degraded feature set UDP instead of TCP for DNS server 1.1.1.1.
Feb 16 17:20:05 brainysrv systemd-resolved[459]: Using degraded feature set UDP instead of TCP for DNS server 8.8.8.8.
Feb 16 17:20:09 brainysrv systemd-resolved[459]: Using degraded feature set TCP instead of UDP for DNS server 1.1.1.1.
Feb 16 17:20:17 brainysrv systemd[1]: systemd-resolved.service: Got notification message from PID 459 (WATCHDOG=1)
Feb 16 17:20:20 brainysrv systemd-resolved[459]: Using degraded feature set UDP instead of TCP for DNS server 1.1.1.1.
Feb 16 17:20:30 brainysrv systemd-resolved[459]: Using degraded feature set UDP instead of TCP for DNS server 1.1.1.1.
Feb 16 17:20:40 brainysrv systemd-resolved[459]: Using degraded feature set TCP instead of UDP for DNS server 1.1.1.1.
Feb 16 17:20:52 brainysrv systemd-resolved[459]: Using degraded feature set UDP instead of TCP for DNS server 9.9.9.9.

Last edited by BrainyXS (2023-02-16 16:55:31)

Offline

#2 2023-02-16 16:41:23

seth
Member
Registered: 2012-09-03
Posts: 38,739

Re: DNS Resolution stopped working

Please use "code" tags, https://bbs.archlinux.org/help.php#bbcode
Edit your post in this regard.

ip a; ip r
resovlectl status
nmap 1.1.1.1

Te doubled "nameserver 1.1.1.1" entry is weird
Try to

systemctl restart systemd-resolved

and post your resolved configuration.
Edit: /etc/systemd/resolved.conf

Last edited by seth (2023-02-16 16:42:01)

Online

#3 2023-02-16 17:00:27

BrainyXS
Member
Registered: 2023-02-16
Posts: 9

Re: DNS Resolution stopped working

my resolved configuration is

#  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. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the resolved.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
#
# See resolved.conf(5) for details.

[Resolve]
# Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
# Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
# Google:     8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
# Quad9:      9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
DNS=1.1.1.1
FallbackDNS=1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google
#Domains=
#DNSSEC=no
#DNSOverTLS=no
#MulticastDNS=yes
#LLMNR=yes
#Cache=yes
#CacheFromLocalhost=no
#DNSStubListener=yes
#DNSStubListenerExtra=
#ReadEtcHosts=yes
#ResolveUnicastSingleLabel=no

I see 1.1.1.1 is set as DNS and as FallbackDNS.
I will remove it from Fallback DNS and restart the system.
My new edited configuration file looks like this:

#  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. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the resolved.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
#
# See resolved.conf(5) for details.

[Resolve]
# Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
# Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
# Google:     8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
# Quad9:      9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
DNS=1.1.1.1
FallbackDNS=9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google
#Domains=
#DNSSEC=no
#DNSOverTLS=no
#MulticastDNS=yes
#LLMNR=yes
#Cache=yes
#CacheFromLocalhost=no
#DNSStubListener=yes
#DNSStubListenerExtra=
#ReadEtcHosts=yes
#ResolveUnicastSingleLabel=no

After a system-reboot. the /etc/resolv.conf still lokes same as before, 1.1.1.1 as double entry.
Is this a problem?

Offline

#4 2023-02-16 17:11:09

seth
Member
Registered: 2012-09-03
Posts: 38,739

Re: DNS Resolution stopped working

Not necessarily. Can you now resolve domains?
What about the ouput of the other commands?

On a wild guess, uncomment

DNSSEC=no
DNSOverTLS=no

Online

#5 2023-02-16 17:18:49

BrainyXS
Member
Registered: 2023-02-16
Posts: 9

Re: DNS Resolution stopped working

No, still not able to resolve domains

ip a; ip r
resovlectl status
nmap 1.1.1.1

results in

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 78:24:af:9c:52:74 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 10.50.1.188/24 brd 10.50.1.255 scope global dynamic noprefixroute eno1
       valid_lft 85399sec preferred_lft 85399sec
    inet6 fe80::6db7:de4b:6291:ad5f/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: br-37e57991796a: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:68:0b:c3:e2 brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-37e57991796a
       valid_lft forever preferred_lft forever
4: br-6fce635245ba: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:f6:14:30:cf brd ff:ff:ff:ff:ff:ff
    inet 172.20.0.1/16 brd 172.20.255.255 scope global br-6fce635245ba
       valid_lft forever preferred_lft forever
5: br-7a45619d5282: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:0e:90:ef:9b brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-7a45619d5282
       valid_lft forever preferred_lft forever
6: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:df:de:ec:85 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:dfff:fede:ec85/64 scope link
       valid_lft forever preferred_lft forever
7: br-dcf19a869662: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:7a:1d:0e:78 brd ff:ff:ff:ff:ff:ff
    inet 172.24.0.1/16 brd 172.24.255.255 scope global br-dcf19a869662
       valid_lft forever preferred_lft forever
    inet6 fe80::42:7aff:fe1d:e78/64 scope link
       valid_lft forever preferred_lft forever
8: br-0ca7fe89168f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:25:de:dc:55 brd ff:ff:ff:ff:ff:ff
    inet 172.23.0.1/16 brd 172.23.255.255 scope global br-0ca7fe89168f
       valid_lft forever preferred_lft forever
    inet6 fe80::42:25ff:fede:dc55/64 scope link
       valid_lft forever preferred_lft forever
10: veth8134f30@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether 52:cb:25:00:f7:d4 brd ff:ff:ff:ff:ff:ff link-netnsid 6
    inet6 fe80::50cb:25ff:fe00:f7d4/64 scope link
       valid_lft forever preferred_lft forever
12: veth95347f7@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dcf19a869662 state UP group default
    link/ether 6e:fa:91:aa:3c:f8 brd ff:ff:ff:ff:ff:ff link-netnsid 8
    inet6 fe80::6cfa:91ff:feaa:3cf8/64 scope link
       valid_lft forever preferred_lft forever
14: vethc002dd4@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether 7a:c7:fb:03:bf:e5 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::78c7:fbff:fe03:bfe5/64 scope link
       valid_lft forever preferred_lft forever
16: veth10ad49f@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether 9a:a7:ac:d3:fd:83 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::98a7:acff:fed3:fd83/64 scope link
       valid_lft forever preferred_lft forever
18: vethb14d161@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether be:53:9c:d3:9d:ff brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::bc53:9cff:fed3:9dff/64 scope link
       valid_lft forever preferred_lft forever
20: veth8b8f0ef@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether 7e:61:65:18:fd:05 brd ff:ff:ff:ff:ff:ff link-netnsid 7
    inet6 fe80::7c61:65ff:fe18:fd05/64 scope link
       valid_lft forever preferred_lft forever
22: vethbd3e0df@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dcf19a869662 state UP group default
    link/ether 82:78:f3:83:6b:00 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::8078:f3ff:fe83:6b00/64 scope link
       valid_lft forever preferred_lft forever
24: vethafab1ee@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether a2:11:a9:2e:f3:40 brd ff:ff:ff:ff:ff:ff link-netnsid 4
    inet6 fe80::a011:a9ff:fe2e:f340/64 scope link
       valid_lft forever preferred_lft forever
26: vethb30d162@if25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dcf19a869662 state UP group default
    link/ether 4a:0b:33:b9:7b:c2 brd ff:ff:ff:ff:ff:ff link-netnsid 7
    inet6 fe80::480b:33ff:feb9:7bc2/64 scope link
       valid_lft forever preferred_lft forever
28: veth32f834d@if27: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether 52:a8:bd:51:94:64 brd ff:ff:ff:ff:ff:ff link-netnsid 5
    inet6 fe80::50a8:bdff:fe51:9464/64 scope link
       valid_lft forever preferred_lft forever
30: veth710673f@if29: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dcf19a869662 state UP group default
    link/ether 96:cf:34:34:3f:11 brd ff:ff:ff:ff:ff:ff link-netnsid 4
    inet6 fe80::94cf:34ff:fe34:3f11/64 scope link
       valid_lft forever preferred_lft forever
32: veth6b28e73@if31: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether ea:23:68:be:54:89 brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet6 fe80::e823:68ff:febe:5489/64 scope link
       valid_lft forever preferred_lft forever
34: veth5b08988@if33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dcf19a869662 state UP group default
    link/ether 26:eb:6f:23:52:a6 brd ff:ff:ff:ff:ff:ff link-netnsid 5
    inet6 fe80::24eb:6fff:fe23:52a6/64 scope link
       valid_lft forever preferred_lft forever
36: vethd118523@if35: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether 4e:8a:96:aa:2f:07 brd ff:ff:ff:ff:ff:ff link-netnsid 9
    inet6 fe80::4c8a:96ff:feaa:2f07/64 scope link
       valid_lft forever preferred_lft forever
38: veth4e8dbee@if37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether 96:dc:17:b4:56:d1 brd ff:ff:ff:ff:ff:ff link-netnsid 11
    inet6 fe80::94dc:17ff:feb4:56d1/64 scope link
       valid_lft forever preferred_lft forever
40: veth0310c2b@if39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether be:e6:30:50:e0:b4 brd ff:ff:ff:ff:ff:ff link-netnsid 10
    inet6 fe80::bce6:30ff:fe50:e0b4/64 scope link
       valid_lft forever preferred_lft forever
42: vethfd06d3a@if41: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dcf19a869662 state UP group default
    link/ether c6:f0:4d:f1:03:24 brd ff:ff:ff:ff:ff:ff link-netnsid 9
    inet6 fe80::c4f0:4dff:fef1:324/64 scope link
       valid_lft forever preferred_lft forever
44: vethe39c708@if43: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ca7fe89168f state UP group default
    link/ether ea:a6:34:a8:a5:3e brd ff:ff:ff:ff:ff:ff link-netnsid 8
    inet6 fe80::e8a6:34ff:fea8:a53e/64 scope link
       valid_lft forever preferred_lft forever
46: vetha35c46e@if45: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dcf19a869662 state UP group default
    link/ether e2:45:ad:4d:41:96 brd ff:ff:ff:ff:ff:ff link-netnsid 11
    inet6 fe80::e045:adff:fe4d:4196/64 scope link
       valid_lft forever preferred_lft forever
48: veth8e56cc4@if47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dcf19a869662 state UP group default
    link/ether 76:2f:1c:84:d5:57 brd ff:ff:ff:ff:ff:ff link-netnsid 10
    inet6 fe80::742f:1cff:fe84:d557/64 scope link
       valid_lft forever preferred_lft forever
default via 10.50.1.1 dev eno1 proto dhcp src 10.50.1.188 metric 1024
default via 10.50.1.1 dev eno1 proto dhcp src 10.50.1.188 metric 20100
1.1.1.1 via 10.50.1.1 dev eno1 proto dhcp src 10.50.1.188 metric 1024
8.8.8.8 via 10.50.1.1 dev eno1 proto dhcp src 10.50.1.188 metric 1024
9.9.9.9 via 10.50.1.1 dev eno1 proto dhcp src 10.50.1.188 metric 1024
10.50.1.0/24 dev eno1 proto kernel scope link src 10.50.1.188 metric 100
10.50.1.1 dev eno1 proto dhcp scope link src 10.50.1.188 metric 1024
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
172.18.0.0/16 dev br-7a45619d5282 proto kernel scope link src 172.18.0.1 linkdown
172.19.0.0/16 dev br-37e57991796a proto kernel scope link src 172.19.0.1 linkdown
172.20.0.0/16 dev br-6fce635245ba proto kernel scope link src 172.20.0.1 linkdown
172.23.0.0/16 dev br-0ca7fe89168f proto kernel scope link src 172.23.0.1
172.24.0.0/16 dev br-dcf19a869662 proto kernel scope link src 172.24.0.1
zsh: command not found: resovlectl
Starting Nmap 7.93 ( https://nmap.org ) at 2023-02-16 18:15 CET
Nmap scan report for 1.1.1.1
Host is up (0.017s latency).
Not shown: 996 filtered tcp ports (no-response)
PORT     STATE SERVICE
80/tcp   open  http
443/tcp  open  https
8080/tcp open  http-proxy
8443/tcp open  https-alt

Nmap done: 1 IP address (1 host up) scanned in 20.94 seconds

Still not able to resolve domains.

Offline

#6 2023-02-16 17:38:42

seth
Member
Registered: 2012-09-03
Posts: 38,739

Re: DNS Resolution stopped working

What's up w/ docker and all the bridges and virtual ethernet devices?
Do we maybe also have an ip filter along that?

zsh: command not found: resovlectl

Oh c'mon.

resolvectl status

Online

#7 2023-02-16 17:51:49

BrainyXS
Member
Registered: 2023-02-16
Posts: 9

Re: DNS Resolution stopped working

resolvectl status:

Global
          Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
   resolv.conf mode: uplink
 Current DNS Server: 1.1.1.1
         DNS Servers 1.1.1.1
Fallback DNS Servers 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google

Link 2 (eno1)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 1.1.1.1
       DNS Servers: 1.1.1.1 8.8.8.8 9.9.9.9

Link 3 (br-dcf19a869662)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 4 (docker0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 5 (br-0ca7fe89168f)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 6 (br-37e57991796a)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 7 (br-6fce635245ba)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 8 (br-7a45619d5282)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 10 (veth78182da)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 12 (vethb2d10fb)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 14 (veth77d4688)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 16 (veth608c4eb)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 18 (veth92096c7)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 20 (veth6207495)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 22 (veth1f0be44)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 24 (veth9c1038a)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 26 (vethda19330)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 28 (vetha09b0cd)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 30 (veth271a8c5)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 32 (vethffaa46b)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 34 (vetha199d0a)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 36 (veth5478d83)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 38 (vetha75a582)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 40 (vethd3e4b18)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 42 (veth7caeff0)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 44 (veth9b711c1)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 46 (veth42f1c94)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 48 (veth96b468f)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

I have several docker container installed and running. Currently, a bitwarden instance is running, as well as bettercrewlink. I also tend to start more container when needed.
docker ps:

CONTAINER ID   IMAGE                                   COMMAND                  CREATED        STATUS                    PORTS
 NAMES
1fe8159bc992   bitwarden/nginx:2022.12.0               "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)   80/tcp, 0.0.0.0:80->8080/tcp, :::80->8080/tcp, 0.0.0.0:443->8443/tcp, :::443->8443/tcp   bitwarden-nginx
aaf15273471e   bitwarden/admin:2022.12.0               "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)   5000/tcp
 bitwarden-admin
43b0143fa2ef   bitwarden/identity:2022.12.0            "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)   5000/tcp
 bitwarden-identity
88719d6721c4   bitwarden/events:2022.12.0              "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)   5000/tcp
 bitwarden-events
fb76f662c84e   bitwarden/web:2022.12.0                 "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)
 bitwarden-web
afda651c6c07   bitwarden/sso:2022.12.0                 "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)   5000/tcp
 bitwarden-sso
f993911d2b06   bitwarden/mssql:2022.12.0               "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)
 bitwarden-mssql
d50d0a8b4bc3   bitwarden/attachments:2022.12.0         "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)
 bitwarden-attachments
1b7ce8fde473   bitwarden/api:2022.12.0                 "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)   5000/tcp
 bitwarden-api
086ea2893ee0   bitwarden/notifications:2022.12.0       "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)   5000/tcp
 bitwarden-notifications
21bb6aa74e95   bitwarden/icons:2022.12.0               "/entrypoint.sh"         7 weeks ago    Up 25 minutes (healthy)   5000/tcp
 bitwarden-icons
95bec9be8bce   ohmyguus/bettercrewlink-server:latest   "docker-entrypoint.s…"   3 months ago   Up 25 minutes             0.0.0.0:11000->9736/tcp, :::11000->9736/tcp
 betterCrewlink

Offline

#8 2023-02-16 18:01:27

seth
Member
Registered: 2012-09-03
Posts: 38,739

Re: DNS Resolution stopped working

Can you temporarily cut those out?
I also just noticed that 1.1.1.1 doesn't have port 53 open - there's the reason of the failure, but cause unknown.

Online

#9 2023-02-16 19:03:59

BrainyXS
Member
Registered: 2023-02-16
Posts: 9

Re: DNS Resolution stopped working

I got it working by grabbing a arch installer usb stick, arch-chroot into the system and run pacman -Syu again. Now everything is working again

Offline

#10 2023-02-16 20:49:11

seth
Member
Registered: 2012-09-03
Posts: 38,739

Re: DNS Resolution stopped working

What was updated?
Are you sure it's not because of the reboot?
Are the docker/bridges/veth's/bitwarden still in place?
Is 1.1.1.1:53 no open?

Online

Board footer

Powered by FluxBB