Hello!
I have Pihole set up on my network and I have been constantly noticing that my pc running Arch makes a lot of queries to 133.195.216.95.in-addr.arpa, which after searching online is an reverse dns lookup for redirect.archlinux.org. It is currently the most looked up domain on my network and I'd like to at least know what it does and if I can tone it down a little since the number of times it is looked up seems excessive.
Thanks!

Last edited by Andreiva (2022-08-22 14:58:07)

https://wiki.archlinux.org/title/Networ … nnectivity ?
Otherwise you could wireshark your system to identify the offending process.

Are you using NM?
The existing file is /usr/lib/NetworkManager/conf.d/20-connectivity.conf - /etc/NetworkManager/conf.d/20-connectivity.conf is where you're supposed to alter that to not touch the pacman controlled file.

Read the actual paragraph, not just the fancy boxes.

Yeah, sorry about that.
/usr/lib/NetworkManager/conf.d/20-connectivity.conf has the uri set as "http://ping.archlinux.org/nm-check.txt" so it's not that

Is illogical - it is "most likely" that…

Let's see whether whatever installed archlinux for you activated NM

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

avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
ckb-next-daemon.service                  | multi-user.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.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
deluged.service                          | multi-user.target.wants
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
fstrim.timer                             | timers.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
kill_kwin.service                        | multi-user.target.wants
libvirtd-ro.socket                       | sockets.target.wants
libvirtd.service                         | multi-user.target.wants
libvirtd.socket                          | sockets.target.wants
lm_sensors.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
sshd.service                             | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
tlp.service                              | multi-user.target.wants
ufw.service                              | multi-user.target.wants
virtlockd.socket                         | sockets.target.wants
virtlogd.socket                          | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

Based on how it's configured shouldn't it try to access http://ping.archlinux.org instead of redirect.archlinux.org?

0 ✓ neumann@ThinkCentre ~ $ nslookup ping.archlinux.org
Server:		::1
Address:	::1#53

Non-authoritative answer:
ping.archlinux.org	canonical name = redirect.archlinux.org.
Name:	redirect.archlinux.org
Address: 95.216.195.133
Name:	redirect.archlinux.org
Address: 2a01:4f9:c010:2636::1

0 ✓ neumann@ThinkCentre ~ $ host 95.216.195.133
133.195.216.95.in-addr.arpa domain name pointer redirect.archlinux.org.
0 ✓ neumann@ThinkCentre ~ $ 

Inofficial first vice president of the Rust Evangelism Strike Force