Name resolution not working

Watson · 2023-02-11 11:01:13

During the construction of a Minecraft server, I attempted to fix the IP address by adjusting the network settings, and since then, name resolution is not working.

$ ping google.com

name or service not known

$ ping 1.1.1.1

This works.

The result of the command:

journalctl -u systemd-resolved -b -0

was flooded with the following message:

Using degraded feature set TCP instead of UDP for DNS server ::1.

At this point, I believe that the routing table is not broken.
I suspect that the problem lies with systemd-resolve.

I do not have dig in my environment.
networkmanager is available

Please let me know if there is any additional information needed.

Head_on_a_Stick · 2023-02-11 11:18:11

Are you using a VPN or proxy?

Watson wrote:

I attempted to fix the IP address by adjusting the network settings

You should post exactly what you did. A vague description isn't much help: https://bbs.archlinux.org/viewtopic.php?id=57855

Please also post the output of

resolvectl --no-p
stat /etc/resolv.conf
grep -v '^$\|^#' /etc/systemd/resolved.conf
ls -lR /etc/systemd/system

Does restarting systemd-resolved get things working again?

How about

resolvectl flush-caches

Presuming /etc/resolv.conf is a symlink, does replacing that with a static file with this content fix things:

nameserver 1.1.1.1

Relevant: https://github.com/systemd/systemd/issues/13432 & https://bbs.archlinux.org/viewtopic.php?id=237993

Watson · 2023-02-11 11:54:15

Thank you for your response.

The command you entered contains some Japanese, but please bear with me.

Sure, I was indeed using ProtonVPN. I don't remember the exact details of what I changed in the IP settings, I'm sorry. I left this issue unattended for a month, so it's been a while.

The /etc/resolve.conf file contains only the following entry:

nameserver 1.1.1.1

┌──(XXXX⟑Arch)-[~/Documents]
└─$ resolvectl --no-p
Global
          Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
   resolv.conf mode: missing
Fallback DNS Servers 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

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

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

Link 4 (ipv6leakintrf0)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: ::1
       DNS Servers: ::1
        DNS Domain: ~.

Link 5 (enp2s0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.3.1
       DNS Servers: 192.168.3.1

Link 6 (wlan0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.3.1
       DNS Servers: 192.168.3.1

                                                                                                           
┌──(XXXX⟑Arch)-[~/Documents]
└─$ stat /etc/resolve.conf                                                                             1 ⨯
  File: /etc/resolve.conf
  Size: 19        	Blocks: 8          IO Block: 4096   通常ファイル
Device: 8,50	Inode: 1049695     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-02-11 19:40:28.833347539 +0900
Modify: 2023-02-11 19:40:18.000014086 +0900
Change: 2023-02-11 19:40:18.000014086 +0900
 Birth: 2023-02-11 19:40:18.000014086 +0900
                                                                                                           
┌──(XXXX⟑Arch)-[~/Documents]
└─$ grep -v '^$\^#' /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. 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=
#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
                                                                                                           
┌──(XXXX⟑Arch)-[~/Documents]
└─$ ls -lR /etc/systemd/system
/etc/systemd/system:
合計 28
drwxr-xr-x 2 root root 4096 Dec 10 12:29 bluetooth.target.wants
lrwxrwxrwx 1 root root   41 Dec 10 12:29 dbus-org.bluez.service -> /usr/lib/systemd/system/bluetooth.service
lrwxrwxrwx 1 root root   41 Dec 23 01:05 dbus-org.fedoraproject.FirewallD1.service -> /usr/lib/systemd/system/firewalld.service
lrwxrwxrwx 1 root root   48 Dec  7 13:53 dbus-org.freedesktop.network1.service -> /usr/lib/systemd/system/systemd-networkd.service
lrwxrwxrwx 1 root root   57 Jan  2 17:02 dbus-org.freedesktop.nm-dispatcher.service -> /usr/lib/systemd/system/NetworkManager-dispatcher.service
lrwxrwxrwx 1 root root   48 Dec  7 13:53 dbus-org.freedesktop.resolve1.service -> /usr/lib/systemd/system/systemd-resolved.service
lrwxrwxrwx 1 root root   49 Dec  7 13:58 dbus-org.freedesktop.timesync1.service -> /usr/lib/systemd/system/systemd-timesyncd.service
lrwxrwxrwx 1 root root   35 Dec  7 13:58 display-manager.service -> /usr/lib/systemd/system/gdm.service
drwxr-xr-x 2 root root 4096 Dec  7 13:51 getty.target.wants
drwxr-xr-x 2 root root 4096 Jan  2 17:02 multi-user.target.wants
drwxr-xr-x 2 root root 4096 Jan  2 17:02 network-online.target.wants
drwxr-xr-x 2 root root 4096 Dec  7 13:53 sockets.target.wants
drwxr-xr-x 2 root root 4096 Dec  7 13:58 sysinit.target.wants
drwxr-xr-x 2 root root 4096 Dec  7 13:52 timers.target.wants

/etc/systemd/system/bluetooth.target.wants:
合計 0
lrwxrwxrwx 1 root root 41 Dec 10 12:29 bluetooth.service -> /usr/lib/systemd/system/bluetooth.service

/etc/systemd/system/getty.target.wants:
合計 0
lrwxrwxrwx 1 root root 38 Dec  7 13:51 getty@tty1.service -> /usr/lib/systemd/system/getty@.service

/etc/systemd/system/multi-user.target.wants:
合計 0
lrwxrwxrwx 1 root root 46 Jan  2 17:02 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 41 Dec 23 01:05 firewalld.service -> /usr/lib/systemd/system/firewalld.service
lrwxrwxrwx 1 root root 40 Dec 22 20:38 nftables.service -> /usr/lib/systemd/system/nftables.service
lrwxrwxrwx 1 root root 40 Dec  7 13:51 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 42 Dec 26 14:18 syncthing@XXXX.service -> /usr/lib/systemd/system/syncthing@.service
lrwxrwxrwx 1 root root 48 Dec  7 13:53 systemd-networkd.service -> /usr/lib/systemd/system/systemd-networkd.service
lrwxrwxrwx 1 root root 35 Dec 23 01:22 ufw.service -> /usr/lib/systemd/system/ufw.service
lrwxrwxrwx 1 root root 47 Dec 31 21:48 vmware-networks.service -> /usr/lib/systemd/system/vmware-networks.service

/etc/systemd/system/network-online.target.wants:
合計 4
lrwxrwxrwx 1 root root 58 Jan  2 17:02 NetworkManager-wait-online.service -> /usr/lib/systemd/system/NetworkManager-wait-online.service
lrwxrwxrwx 1 root root 60 Dec  7 13:53 systemd-networkd-wait-online.service -> /usr/lib/systemd/system/systemd-networkd-wait-online.service

/etc/systemd/system/sockets.target.wants:
合計 0
lrwxrwxrwx 1 root root 47 Dec  7 13:53 systemd-networkd.socket -> /usr/lib/systemd/system/systemd-networkd.socket

/etc/systemd/system/sysinit.target.wants:
合計 0
lrwxrwxrwx 1 root root 57 Dec  7 13:53 systemd-network-generator.service -> /usr/lib/systemd/system/systemd-network-generator.service
lrwxrwxrwx 1 root root 48 Dec  7 13:53 systemd-resolved.service -> /usr/lib/systemd/system/systemd-resolved.service
lrwxrwxrwx 1 root root 49 Dec  7 13:58 systemd-timesyncd.service -> /usr/lib/systemd/system/systemd-timesyncd.service

/etc/systemd/system/timers.target.wants:
合計 0
lrwxrwxrwx 1 root root 36 Dec  7 13:52 fstrim.timer -> /usr/lib/systemd/system/fstrim.timer

Head_on_a_Stick · 2023-02-11 12:11:44

Watson wrote:

The /etc/resolve.conf file contains only the following entry:
nameserver 1.1.1.1

That's not the file I asked about. We need to know about /etc/resolv.conf (no second "e"). The stat output is also misdirected.The grep command is missing the "|" character but that doesn't matter. Copy&paste might work better for you than transcription.

The resolvectl output seems to show 192.168.3.1 as the nameserver with systemd-resolved acting as a consumer rather than a provider. Read the systemd-resolved man page to find out how to use it as a provider.

Is 192.168.3.1 the address for your router? What do you see if you enter that address in your browser?

I think the VPN might be the problem here but I've never used a VPN so you'll have to wait for somebody who has. Post all the relevant configuration files please. Does disabling the VPN get things working? You should probably also provide more details in respect of this Minecradt server.

And finally note that NetworkManager and systemd-networkd are both enabled, which can cause conflicts and network problems. Pick one and disable the other.

Watson · 2023-02-11 17:33:23

I'm sorry. I'm posting the question from another terminal, and I find it inconvenient to copy and paste, so I've been writing it down.

┌──(XXXX⟑Arch)-[/etc]
└─$ stat /etc/resolv.conf
File: /etc/resolv.conf
Size: 19 Blocks: 8 IO Block: 4096 通常ファイル
Device: 8,50 Inode: 1049695 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2023-02-12 01:40:58.280259794 +0900
Modify: 2023-02-11 19:40:18.000014086 +0900
Change: 2023-02-12 01:40:34.566926190 +0900
Birth: 2023-02-11 19:40:18.000014086 +0900

┌──(XXXX⟑Arch)-[/etc]
└─$ grep -v '^$\|^#' /etc/systemd/resolved.conf
[Resolve]
DNSSEC=no

┌──(XXXX⟑Arch)-[/etc]
└─$

The resolvectl output seems to show 192.168.3.1 as the nameserver with systemd-resolved acting as a consumer rather than a provider. Read the systemd-resolved man page to find out how to use it as a provider.

>>> I was also wondering why 192.168.3.1 is the nameserver. Do your outputs show something like 1.1.1.1 or 8.8.8.8 here? Also, is it possible for the router to handle the name resolution process? It takes time to read man pages, but I will give it a try.

Is 192.168.3.1 the address for your router? What do you see if you enter that address in your browser?

>>> Yes, that's correct. You can communicate with 192.168.3.1 to configure the router.

I think the VPN might be the problem here but I've never used a VPN so you'll have to wait for somebody who has. Post all the relevant configuration files please. Does disabling the VPN get things working? You should probably also provide more details in respect of this Minecradt server.

>>> When I checked protonvpn-cli, it appears to not be working. Additionally, I have accidentally deleted all the directories related to the Minecraft server setup.

And finally note that NetworkManager and systemd-networkd are both enabled, which can cause conflicts and network problems. Pick one and disable the other.

>>> I installed NetworkManager to configure GUI network settings using Gnome. There were no issues after installation, but is it necessary to disable one of them?

Head_on_a_Stick · 2023-02-11 18:07:22

Watson wrote:

I was also wondering why 192.168.3.1 is the nameserver.

Probably assigned by NetworkManager. The content of /etc/resolv.conf will confirm this because NM adds a commented header to the file.

Watson wrote:

is it possible for the router to handle the name resolution process?

Yes. Your ISP can handle that via the router. Such a situation is very common and is the default behaviour for NM.

Watson wrote:

When I checked protonvpn-cli, it appears to not be working.

I wrote:

You should post exactly what you did. A vague description isn't much help: https://bbs.archlinux.org/viewtopic.php?id=57855

Watson wrote:

is it necessary to disable one of them?

Yes. Disable systemd-networkd if you're using NM.

seth · 2023-02-11 20:15:02

In case that doesn't fix it, post the output of

ip a
ip r
dig google.com
nmap -p 53 192.168.3.1

'm posting the question from another terminal, and I find it inconvenient to copy and paste, so I've been writing it down.

It's your time, but usb keys exist and they can carry information from one terminal to another

Watson · 2023-02-12 03:59:53

┌──(XXXX⟑Arch)-[~/Documents]
└─$ protonvpn-cli status  

No active Proton VPN connection.

┌──(XXXX⟑Arch)-[~/Documents]
└─$ systemctl disable systemd-networkd.service
Removed "/etc/systemd/system/dbus-org.freedesktop.network1.service".
Removed "/etc/systemd/system/sockets.target.wants/systemd-networkd.socket".
Removed "/etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service".
Removed "/etc/systemd/system/multi-user.target.wants/systemd-networkd.service".
Removed "/etc/systemd/system/sysinit.target.wants/systemd-network-generator.service".

┌──(XXXX⟑Arch)-[~/Documents]
└─$ systemctl disable systemd-network-generator.service

┌──(XXXX⟑Arch)-[~/Documents]
└─$ systemctl disable systemd-networkd.service

┌──(XXXX⟑Arch)-[~/Documents]
└─$ systemctl stop systemd-network-generator.service

┌──(XXXX⟑Arch)-[~/Documents]
└─$ systemctl stop systemd-networkd.service

┌──(XXXX⟑Arch)-[~/Documents]
└─$ reboot

┌──(XXXX⟑Arch)-[~]
└─$ systemctl --type=service
  UNIT                                                                                      LOAD   A>
  ---------------------------------------------------------------------------------------------------
  accounts-daemon.service                                                                   loaded a>
  bluetooth.service                                                                         loaded a>
  colord.service                                                                            loaded a>
  dbus.service                                                                              loaded a>
  gdm.service                                                                               loaded a>
  kmod-static-nodes.service                                                                 loaded a>
  lvm2-monitor.service                                                                      loaded a>
  NetworkManager.service                                                                    loaded a>
  polkit.service                                                                            loaded a>
  rtkit-daemon.service                                                                      loaded a>
  syncthing@XXXX.service                                                                    loaded a>
  systemd-binfmt.service                                                                    loaded a>
  systemd-fsck@dev-disk-by\x2duuid-a80d7f58\x2dc9db\x2d4c47\x2d920e\x2d2fef7509ed5e.service loaded a>
  systemd-fsck@dev-disk-by\x2duuid-FC73\x2d26B8.service                                     loaded a>
  systemd-journal-flush.service                                                             loaded a>
  systemd-journald.service                                                                  loaded a>
  systemd-logind.service                                                                    loaded a>
  systemd-modules-load.service                                                              loaded a>
  systemd-random-seed.service                                                               loaded a>
  systemd-remount-fs.service                                                                loaded a>
  systemd-resolved.service                                                                  loaded a>
  systemd-sysctl.service                                                                    loaded a>
  systemd-timesyncd.service                                                                 loaded a>
  systemd-tmpfiles-setup-dev.service                                                        loaded a>
  systemd-tmpfiles-setup.service                                                            loaded a>
  systemd-udev-trigger.service                                                              loaded a>
  systemd-udevd.service                                                                     loaded a>
  systemd-update-utmp.service                                                               loaded a>
  systemd-user-sessions.service                                                             loaded a>
  systemd-zram-setup@zram0.service                                                          loaded a>
  udisks2.service                                                                           loaded a>
  ufw.service                                                                               loaded a>
  upower.service                                                                            loaded a>
  user-runtime-dir@1000.service                                                             loaded a>
  user@1000.service                                                                         loaded a>
  vmware-networks.service                                                                   loaded a>
  wpa_supplicant.service                                                                    loaded a>

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
37 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

┌──(XXXX⟑Arch)-[~]
└─$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
25581                      DENY        Anywhere                  
25580                      DENY        Anywhere                  

┌──(XXXX⟑Arch)-[~]
└─$ cat /etc/resolv.conf 
nameserver	1.1.1.1

┌──(XXXX⟑Arch)-[/etc/NetworkManager]
└─$ cat NetworkManager.conf 
# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.

[Resolve]
DNSOverTLS=yes

┌──(XXXX⟑Arch)-[/etc/NetworkManager]
└─$ nmcli            
enp2s0: connected から 有線接続 1
        "Realtek RTL8125 2.5GbE"
        ethernet (r8169), D8:BB:C1:CF:F0:66, hw, mtu 1500
        ip4 defolte
        inet4 192.168.3.17/24
        route4 192.168.3.0/24 metric 100
        route4 default via 192.168.3.1 metric 100
        inet6 fe80::15df:156c:ca13:1e78/64
        route6 fe80::/64 metric 1024

ipv6leakintrf0: connected から pvpn-ipv6leak-protection
        "ipv6leakintrf0"
        dummy, 2A:91:54:97:24:CC, sw, mtu 1500
        ip6 defolte
        inet6 fe80::e56d:8bb5:a8de:8198/64
        inet6 fdeb:446c:912d:8da::/64
        route6 fdeb:446c:912d:8da::/64 metric 95
        route6 default via fdeb:446c:912d:8da::1 metric 95
        route6 fe80::/64 metric 1024

wlan0: connected から (My home WIFI SSID)
        "Intel Alder Lake-S PCH CNVi"
        wifi (iwlwifi), F0:57:A6:0B:65:80, hw, mtu 1500
        inet4 192.168.3.16/24
        route4 192.168.3.0/24 metric 600
        route4 default via 192.168.3.1 metric 600
        inet6 fe80::9086:e577:ecc2:7663/64
        route6 fe80::/64 metric 1024

DNS configuration:
        servers: ::1
        interface: ipv6leakintrf0

        servers: 192.168.3.1
        interface: wlan0

        servers: 192.168.3.1
        interface: enp2s0

Also, the interface called "ipv6leakintrf0" appears to belong to ProtonVPN....
The message "Using degraded feature set TCP instead of UDP for DNS server ::1." in journalctl may be due to not having Protonvpn running.

Last edited by Watson (2023-02-12 06:27:16)

Watson · 2023-02-12 06:29:21

sorry. I do not have the dig command.

┌──(XXXX⟑Arch)-[~]
└─$ nmap -p 53 192.168.3.1
Starting Nmap 7.93 ( https://nmap.org ) at 2023-02-12 15:14 JST
Nmap scan report for 192.168.3.1
Host is up (0.0014s latency).

PORT   STATE SERVICE
XX/tcp open  domain

Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
                                                                                      
┌──(XXXX⟑Arch)-[~]
└─$ ip a
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: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
    inet 192.168.110.1/24 brd 192.168.110.255 scope global vmnet1
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fec0:1/64 scope link 
       valid_lft forever preferred_lft forever
3: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
    inet 192.168.167.1/24 brd 192.168.167.255 scope global vmnet8
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fec0:8/64 scope link 
       valid_lft forever preferred_lft forever
4: ipv6leakintrf0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 2a:91:54:97:24:cc brd ff:ff:ff:ff:ff:ff
    inet6 fdeb:446c:912d:8da::/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::e56d:8bb5:a8de:8198/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
5: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d8:bb:c1:cf:f0:66 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.17/24 brd 192.168.3.255 scope global dynamic noprefixroute enp2s0
       valid_lft 73614sec preferred_lft 73614sec
    inet6 fe80::15df:156c:ca13:1e78/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
6: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f0:57:a6:0b:65:80 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.16/24 brd 192.168.3.255 scope global dynamic noprefixroute wlan0
       valid_lft 73613sec preferred_lft 73613sec
    inet6 fe80::9086:e577:ecc2:7663/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
                                                                                      
┌──(XXXX⟑Arch)-[~]
└─$ ip r
default via 192.168.3.1 dev enp2s0 proto dhcp src 192.168.3.17 metric 100 
default via 192.168.3.1 dev wlan0 proto dhcp src 192.168.3.16 metric 600 
192.168.3.0/24 dev enp2s0 proto kernel scope link src 192.168.3.17 metric 100 
192.168.3.0/24 dev wlan0 proto kernel scope link src 192.168.3.16 metric 600 
192.168.110.0/24 dev vmnet1 proto kernel scope link src 192.168.110.1 
192.168.167.0/24 dev vmnet8 proto kernel scope link src 192.168.167.1

seth · 2023-02-12 07:22:37

Try "drill", dig is in https://archlinux.org/packages/extra/x86_64/bind/

UNIT                                                                                      LOAD   A>

Don't copy and paste out of the pager, redirect the output into a file.

[Resolve]
DNSOverTLS=yes

nmap -p 853 192.168.3.1

I'll bet your right arm that your gateways DNS server doesn't support DoT and your nmcli config says

        servers: 192.168.3.1
        interface: wlan0

        servers: 192.168.3.1
        interface: enp2s0

=> configure those nics to use 1.1.1.1 or disable DoT

Watson · 2023-02-13 06:49:54

Seth and Head_on_a_Stick,

After stopping and disabling systemd-network related services, I changed /etc/resolv.conf to au (japan provider) once from arch-chroot, and after rebooting, name resolution became possible. The nameserver in resolv.conf after the reboot was rewritten by the network manager to the address of the router, and it seems that name resolution is being performed on the router side. Thank you for your cooperation.

seth · 2023-02-13 08:47:35

You'll have to change the DNS configuration in NM by either defining the DNS server or telling it to stay away from resolv.conf
https://wiki.archlinux.org/title/Networ … management

Thank you for your cooperation.

"support" - cooperation is slightly different.

Arch Linux

#1 2023-02-11 11:01:13

Name resolution not working

#2 2023-02-11 11:18:11

Re: Name resolution not working

#3 2023-02-11 11:54:15

Re: Name resolution not working

#4 2023-02-11 12:11:44

Re: Name resolution not working

#5 2023-02-11 17:33:23

Re: Name resolution not working

#6 2023-02-11 18:07:22

Re: Name resolution not working

#7 2023-02-11 20:15:02

Re: Name resolution not working

#8 2023-02-12 03:59:53

Re: Name resolution not working

#9 2023-02-12 06:29:21

Re: Name resolution not working

#10 2023-02-12 07:22:37

Re: Name resolution not working

#11 2023-02-13 06:49:54

Re: Name resolution not working

#12 2023-02-13 08:47:35

Re: Name resolution not working

Board footer