[SOLVED] gpg: WARNING: DNS is not properly configured

Chuck9365 · 2024-08-27 14:44:43

After I do

 yay -Syu

this is the message I get:

 :: PGP keys need importing:
 -> ABAF11C65A2970B130ABE3C479BE3E4300411886, required by: linux-mainline
:: Import? [Y/n] y
:: Importing keys with gpg...
gpg: WARNING: DNS is not properly configured
gpg: keyserver receive failed: No such file or directory
 -> problem importing keys

Last edited by Chuck9365 (2024-08-30 09:41:01)

seth · 2024-08-27 19:37:17

grep keyserver /etc/pacman.d/gnupg/gpg.conf
ping keyserver.ubuntu.com # speculating on the keyserver
getent ahostsv4 keyserver.ubuntu.com
getent ahostsv4 keyserver.ubuntu.com
drill keyserver.ubuntu.com # or alternatively:
dig keyserver.ubuntu.com
resolvectl status

Chuck9365 · 2024-08-28 07:46:34

This is what i got

 keyserver-options timeout=10
keyserver-options import-clean
keyserver-options no-self-sigs-only
PING keyserver.ubuntu.com (185.125.188.26) 56(84) bytes of data.
^C
--- keyserver.ubuntu.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1014ms

185.125.188.26  STREAM keyserver.ubuntu.com
185.125.188.26  DGRAM  
185.125.188.26  RAW    
185.125.188.27  STREAM 
185.125.188.27  DGRAM  
185.125.188.27  RAW    
185.125.188.26  STREAM keyserver.ubuntu.com
185.125.188.26  DGRAM  
185.125.188.26  RAW    
185.125.188.27  STREAM 
185.125.188.27  DGRAM  
185.125.188.27  RAW    
Warning: Could not create a resolver structure: Could not open the files ((null))
Try drill @localhost if you have a resolver running on your machine.
;; communications error to ::1#53: connection refused
;; communications error to ::1#53: connection refused
;; communications error to ::1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused

; <<>> DiG 9.20.1 <<>> keyserver.ubuntu.com
;; global options: +cmd
;; no servers could be reached
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-d
ns.com
                      2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google

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

Link 3 (enp42s0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported

Last edited by Chuck9365 (2024-08-28 07:48:43)

seth · 2024-08-28 11:56:35

So ping can resolve but not reach keyserver.ubuntu.com

;; communications error to ::1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; no servers could be reached

is a problem and the mostr likely explanation is

resolv.conf mode: missing

/etc/resolv.conf isn't a symlink to /run/systemd/resolve/stub-resolv.conf and apparently also nothing lis listening on 127.0.0.0:53 so it seems resolved also isn't providing local DNS.

Sanity check, how do you intend to configure the network?

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Chuck9365 · 2024-08-28 15:34:26

bluetooth.service                        | bluetooth.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
ipp-usb.service                          | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
paccache.timer                           | timers.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
seatd.service                            | multi-user.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

seth · 2024-08-28 15:45:25

So NM, see https://wiki.archlinux.org/title/Networ … d-resolved create the symlink and either restart NM and resolved or reboot.

Sidebar: Why is seatd running?

Chuck9365 · 2024-08-28 16:04:21

I cannot create a symlink

ln -s /etc/resolv.conf /run/systemd/resolve/stub-resolv.conf  
ln: failed to create symbolic link '/run/systemd/resolve/stub-resolv.conf': File exists

I also edited /etc/NetworkManager/conf.d/dns.conf and nothing has changed. I don't know if that matters, but my /etc/resolv.conf was empty before I tried to make a symlink.

seth · 2024-08-28 16:30:59

"man ln"
It's "ln -s TARGET LINK"

my /etc/resolv.conf was empty before I tried to make a symlink

The previous outputs made it look like it didn't exist at all?
If the file actually exists NM should enter the resolver entries (192.168.1.1) and configure resolved, but that doesn't seem to have happened?

If the symlink doesn't fix this, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

so we know what's actually going on there.

Chuck9365 · 2024-08-28 17:10:37

Yeah, it still doesn't work

ln -s run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
ln: failed to create symbolic link '/etc/resolv.conf': File exists

here's the output
http://0x0.st/XviA.txt

Last edited by Chuck9365 (2024-08-29 10:17:17)

seth · 2024-08-28 19:17:32

Of course it doesn't work - remove the target or use "-f" - unless /etc/resolv.conf is now actually properly written (after a reboot)
The file has previously not existed:

Aug 28 18:24:09 archlinux avahi-daemon[638]: Failed to open /etc/resolv.conf: Invalid argument
Aug 28 18:25:42 archlinux dirmngr[28585]: stat'ing '/etc/resolv.conf' failed: No such file or directory
Aug 28 18:25:42 archlinux dirmngr[28585]: stat'ing '/etc/resolv.conf' failed: No such file or directory
Aug 28 18:25:42 archlinux dirmngr[28585]: failed to load '/etc/resolv.conf': No such file or directory

Then edit your post and use code tags or, better, restore the 0x0.st link, There's no point in copying around the internet.

Chuck9365 · 2024-08-29 10:57:20

sorry man but i still cannot create a symlink. I removed

etc/resolv.conf  
/run/systemd/resolve/stub-resolv.conf 
/run/systemd/resolve/resolv.conf 
/usr/lib/systemd/resolv.conf

and restarted systemd as well as NM and now /etc/resolf.conf is actually written, meaning it has something in it.
After yay -Syu i only get this error message

:: Importing keys with gpg...
gpg: keyserver receive failed: No data
 -> problem importing keys

after trying to make a symlinks i get following errors

ln -f /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
ln: failed to create hard link '/etc/resolv.conf' => '/run/systemd/resolve/stub-resolv.conf': Invalid cross-device link

ln -s /run/systemd/resolve/stub-resolv.conf
ln: failed to create symbolic link './stub-resolv.conf': File exists

ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf 
ln: failed to create symbolic link '/etc/resolv.conf': File exists

Last edited by Chuck9365 (2024-08-29 11:02:56)

seth · 2024-08-29 12:53:04

You should at some point read the ln manapge

I removed

Why?
Re-install systemd, /usr/lib/systemd/resolv.conf isn't some runtime created file.

now /etc/resolf.conf is actually written, meaning it has something in it

"resolv.conf" - and *what* does it have written in it?

After yay -Syu

Leaving aside the yay part, forget about updating the system - we need to fix your network config first.

=> re-run https://bbs.archlinux.org/viewtopic.php … 0#p2192420

Chuck9365 · 2024-08-29 14:36:19

Re-install systemd, /usr/lib/systemd/resolv.conf isn't some runtime created file.

done

# Generated by NetworkManager
nameserver 127.0.0.53
options edns0 trust-ad

=> re-run https://bbs.archlinux.org/viewtopic.php … 0#p2192420

keyserver-options timeout=10
keyserver-options import-clean
keyserver-options no-self-sigs-only
PING keyserver.ubuntu.com (185.125.188.26) 56(84) bytes of data.
^C
--- keyserver.ubuntu.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1022ms

185.125.188.26  STREAM keyserver.ubuntu.com
185.125.188.26  DGRAM  
185.125.188.26  RAW    
185.125.188.27  STREAM 
185.125.188.27  DGRAM  
185.125.188.27  RAW    
185.125.188.27  STREAM keyserver.ubuntu.com
185.125.188.27  DGRAM  
185.125.188.27  RAW    
185.125.188.26  STREAM 
185.125.188.26  DGRAM  
185.125.188.26  RAW    
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 62163
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; keyserver.ubuntu.com.	IN	A

;; ANSWER SECTION:
keyserver.ubuntu.com.	597	IN	A	185.125.188.27
keyserver.ubuntu.com.	597	IN	A	185.125.188.26

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; SERVER: 127.0.0.53
;; WHEN: Thu Aug 29 16:34:23 2024
;; MSG SIZE  rcvd: 70

; <<>> DiG 9.20.1 <<>> keyserver.ubuntu.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45866
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;keyserver.ubuntu.com.		IN	A

;; ANSWER SECTION:
keyserver.ubuntu.com.	597	IN	A	185.125.188.26
keyserver.ubuntu.com.	597	IN	A	185.125.188.27

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Aug 29 16:34:23 CEST 2024
;; MSG SIZE  rcvd: 81

Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: foreign
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 (enp42s0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported

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

seth · 2024-08-29 15:18:34

DNS resolution works (now), it's normal that keyserver.ubuntu.com doesn't respond to ICMP requests (but the resolution there works as well)
But there's apparently no keyserver configured
Try adding "keyserver hkps://keyserver.ubuntu.com" to /etc/pacman.d/gnupg/gpg.conf

https://wiki.archlinux.org/title/Pacman … loper_keys
https://wiki.archlinux.org/title/Pacman … _keyserver

Chuck9365 · 2024-08-29 16:55:36

I managed to make a symlink

sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

but still no luck in solving the initial problem, I already added the keyserver to gpg.conf

seth · 2024-08-29 17:02:40

STOP FLAILING AROUND.

You broke the dns resolution with that, at least until a restart of resolved and Networkmanager.
Read the wiki, decide how you want to handle dns, configure that, reboot, leave that alone, ensure that DNS Resolution still works, try again.

Stop using yay, run pacman -v --debug -Syu and Post the Output

Chuck9365 · 2024-08-29 17:44:04

Sorry. Here's the output

Root      : /
Conf File : /etc/pacman.conf
DB Path   : /var/lib/pacman/
Cache Dirs: /var/cache/pacman/pkg/  
Hook Dirs : /usr/share/libalpm/hooks/  /etc/pacman.d/hooks/  
Lock File : /var/lib/pacman/db.lck
Log File  : /var/log/pacman.log
GPG Dir   : /etc/pacman.d/gnupg/
Targets   : None
:: Synchronizing package databases...
 core downloading...
 extra downloading...
 multilib downloading...
:: Starting full system upgrade...
 there is nothing to do

seth · 2024-08-29 20:17:09

So it's some yay thing?
…

ABAF11C65A2970B130ABE3C479BE3E4300411886, required by: linux-mainline

Yeah, it's for an AUR package
https://aur.archlinux.org/packages/linu … ent-980382

It should™ however no longer result in DNS complaints?

Chuck9365 · 2024-08-30 09:38:49

Alright. Everything is fine now. That's for your help, man.

Arch Linux

#1 2024-08-27 14:44:43

[SOLVED] gpg: WARNING: DNS is not properly configured

#2 2024-08-27 19:37:17

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#3 2024-08-28 07:46:34

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#4 2024-08-28 11:56:35

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#5 2024-08-28 15:34:26

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#6 2024-08-28 15:45:25

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#7 2024-08-28 16:04:21

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#8 2024-08-28 16:30:59

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#9 2024-08-28 17:10:37

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#10 2024-08-28 19:17:32

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#11 2024-08-29 10:57:20

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#12 2024-08-29 12:53:04

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#13 2024-08-29 14:36:19

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#14 2024-08-29 15:18:34

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#15 2024-08-29 16:55:36

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#16 2024-08-29 17:02:40

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#17 2024-08-29 17:44:04

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#18 2024-08-29 20:17:09

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

#19 2024-08-30 09:38:49

Re: [SOLVED] gpg: WARNING: DNS is not properly configured

Board footer