Dev1 Galaxy Forum / New info about "Temporary failure resolving 'deb.devuan.org'"

Re: New info about "Temporary failure resolving 'deb.devuan.org'"

dummy@example.com (KnightTemplar) — Tue, 30 Sep 2025 18:14:14 +0000

These are my sources.list below if anyone interested in copying them and add to your sourceds.list:

##############################

## Devuan Default Repositories

#deb http://deb.devuan.org/merged daedalus main non-free-firmware non-free contrib
#deb-src http://deb.devuan.org/merged daedalus main non-free-firmware non-free contrib

#deb http://deb.devuan.org/merged daedalus-security main non-free-firmware non-free contrib
#deb-src http://deb.devuan.org/merged daedalus-security main non-free-firmware non-free contrib

#deb http://deb.devuan.org/merged daedalus-updates main non-free-firmware non-free contrib
#deb-src http://deb.devuan.org/merged daedalus-updates main non-free-firmware non-free contrib

## Devuan-Backports
#deb http://deb.devuan.org/merged daedalus-backports main non-free-firmware non-free contrib

################################################################

## Devuan Mirrors (Use in case Devuan Default Repos are failing)

## Devuan Mirrors Repositories-1

deb http://gnlug.org/pub/devuan/merged daedalus main non-free-firmware non-free contrib

deb http://gnlug.org/pub/devuan/merged daedalus-updates main non-free-firmware non-free contrib

deb http://gnlug.org/pub/devuan/merged daedalus-security main non-free-firmware non-free contrib

## Devuan-Backports
#deb http://gnlug.org/pub/devuan/merged daedalus-backports main non-free-firmware non-free contrib

## Devuan Mirrors Repositories-2
## Devuan-Backports

## Devuan Mirrors Repositories-3
## Devuan-Backports

################################

Re: New info about "Temporary failure resolving 'deb.devuan.org'"

dummy@example.com (KnightTemplar) — Tue, 30 Sep 2025 16:21:09 +0000

Hi all, like greenjeans said, gnlug works fine, that's the ones I'm using on my systems, good luck!

Re: New info about "Temporary failure resolving 'deb.devuan.org'"

dummy@example.com (pcalvert) — Sat, 20 Sep 2025 07:18:01 +0000

SHADUS_TAIN wrote:

This has never been an issue with any other distro I've worked with (Mint, Debian, Artix, AntiX, Fedora, etc.) The goal is for Devuan to properly update /etc/resolv.conf at boot like every other distro. I came to Devuan looking for stability and init freedom. Hopefully this sheds some light onto the actual cause of the issue people have been having. Let's work together to fix this issue... ideas?

I believe that this (potential) solution will probably fix the problem for you:

https://dev1galaxy.org/viewtopic.php?pid=48040#p48040

Re: New info about "Temporary failure resolving 'deb.devuan.org'"

dummy@example.com (Altoid) — Thu, 18 Sep 2025 18:38:26 +0000

Hello:

greenjeans wrote:

... as deb.devuan.org goes, I get no result from pinging ...

Just checking for you:

$ ping deb.devuan.org
PING deb.rr.devuan.org (131.188.12.211) 56(84) bytes of data.
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=1 ttl=49 time=231 ms
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=2 ttl=49 time=231 ms
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=3 ttl=49 time=231 ms
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=4 ttl=49 time=231 ms
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=5 ttl=49 time=231 ms
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=6 ttl=49 time=231 ms
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=7 ttl=49 time=231 ms
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=8 ttl=49 time=232 ms
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=9 ttl=49 time=231 ms
^C
--- deb.rr.devuan.org ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 14091ms
rtt min/avg/max/mdev = 231.240/231.392/231.600/0.101 ms
$

Using ifupdown after nuking network manager, no problems.
/etc/resolv.conf immutabled.

Best,

Re: New info about "Temporary failure resolving 'deb.devuan.org'"

dummy@example.com (greenjeans) — Thu, 18 Sep 2025 17:52:11 +0000

Not having any of the issues with /etc/resolve.conf that were mentioned, using sysvinit and Network Manager.

But as far as deb.devuan.org goes, I get no result from pinging it at all. I've been using a direct mirror for a long time. Gnlug works awesome here in the midwest US.

Re: New info about "Temporary failure resolving 'deb.devuan.org'"

dummy@example.com (stargate-sg1-cheyenne-mtn) — Thu, 18 Sep 2025 15:47:50 +0000

ai/llvm/bot traffic, ftw...

it is what it is...sigh...

Re: New info about "Temporary failure resolving 'deb.devuan.org'"

dummy@example.com (luvr) — Thu, 18 Sep 2025 15:31:49 +0000

I have been getting “Network is unreachable” errors for the past few days:

# apt update
Get:1 file:/opt/linuxluvr-daedalus/linuxluvr daedalus-luvr InRelease [4,608 B]
Get:1 file:/opt/linuxluvr-daedalus/linuxluvr daedalus-luvr InRelease [4,608 B]
Get:2 [url]https://dl.google.com/linux/chrome/deb[/url] stable InRelease [1,825 B]
Hit:3 [url]https://files.eid.belgium.be/debian[/url] bookworm InRelease
Get:4 [url]https://dl.google.com/linux/chrome/deb[/url] stable/main amd64 Packages [1,215 B]
Ign:5 [url]http://deb.devuan.org/merged[/url] daedalus InRelease
Ign:6 [url]http://deb.devuan.org/merged[/url] daedalus-security InRelease
Ign:7 [url]http://deb.devuan.org/merged[/url] daedalus-updates InRelease
Err:8 [url]http://deb.devuan.org/merged[/url] daedalus Release
  Cannot initiate the connection to deb.devuan.org:80 (2a0a:e5c0:10:3::6eeb). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:9e40::180). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2407:b6c0::12). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f9:2a:fa9::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2801:82:80ff:8000::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f8:140:1102:2b76:955d:b48f:bdf3). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:878:346::116). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:4ca0:4300::1:19). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2800:a8:c001::a). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:e42:102:1704:160:16:137:156). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a03:4000:28:24c::). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0d:eb00:8006::acab). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4ff:f0:dd3a::1). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2401:c080:2000:229e:4b70:fe82:36ed:f788). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2602:817:2000:401::138). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:67c:1220:8b0::93e5:b013). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2604:a880:5:1::154:0). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0a:4cc0:c0:4676:4242:4242:4242:4242). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:638:a000:1021:21::1). - connect (101: Network is unreachable)
Err:9 [url]http://deb.devuan.org/merged[/url] daedalus-security Release
  Cannot initiate the connection to deb.devuan.org:80 (2a0a:e5c0:10:3::6eeb). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:9e40::180). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2407:b6c0::12). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f9:2a:fa9::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2801:82:80ff:8000::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f8:140:1102:2b76:955d:b48f:bdf3). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:878:346::116). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:4ca0:4300::1:19). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2800:a8:c001::a). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:e42:102:1704:160:16:137:156). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a03:4000:28:24c::). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0d:eb00:8006::acab). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4ff:f0:dd3a::1). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2401:c080:2000:229e:4b70:fe82:36ed:f788). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2602:817:2000:401::138). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:67c:1220:8b0::93e5:b013). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2604:a880:5:1::154:0). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0a:4cc0:c0:4676:4242:4242:4242:4242). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:638:a000:1021:21::1). - connect (101: Network is unreachable)
Err:10 [url]http://deb.devuan.org/merged[/url] daedalus-updates Release
  Cannot initiate the connection to deb.devuan.org:80 (2a0a:e5c0:10:3::6eeb). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:9e40::180). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2407:b6c0::12). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f9:2a:fa9::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2801:82:80ff:8000::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f8:140:1102:2b76:955d:b48f:bdf3). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:878:346::116). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:4ca0:4300::1:19). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2800:a8:c001::a). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:e42:102:1704:160:16:137:156). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a03:4000:28:24c::). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0d:eb00:8006::acab). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4ff:f0:dd3a::1). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2401:c080:2000:229e:4b70:fe82:36ed:f788). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2602:817:2000:401::138). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:67c:1220:8b0::93e5:b013). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2604:a880:5:1::154:0). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0a:4cc0:c0:4676:4242:4242:4242:4242). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:638:a000:1021:21::1). - connect (101: Network is unreachable)
Reading package lists... Done
E: The repository 'http://deb.devuan.org/merged daedalus Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.devuan.org/merged daedalus-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.devuan.org/merged daedalus-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

If I subsequently retry the update a few minutes later, then everything returns to normal.

New info about "Temporary failure resolving 'deb.devuan.org'"

dummy@example.com (SHADUS_TAIN) — Wed, 17 Sep 2025 23:41:58 +0000

New info about "Temporary failure resolving 'deb.devuan.org'"

Greetings...

This is a fresh install on the following hardware:
Lenovo Thinkpad X1 Carbon 5th Gen
CPU: Intel Core i7-7600U Processor (2C/4T) @ 2.8 GHz 4 MB Cache
RAM: 16GB
Storage: 2TB NVMe
GFX: Intel HD Graphics 620

Using: devuan_daedalus_5.0.1_amd64_netinstall.iso
init: runit
DE: LXQt

I run the installer and the install concludes successfully. As others have reported, after the install I reboot, login, open a shell and...

$ sudo apt update
[sudo] password for USER: 
Ign:1 http://deb.devuan.org/merged daedalus InRelease
Ign:2 http://deb.devuan.org/merged daedalus-security InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:1 http://deb.devuan.org/merged daedalus InRelease
Ign:2 http://deb.devuan.org/merged daedalus-security InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:1 http://deb.devuan.org/merged daedalus InRelease
Ign:2 http://deb.devuan.org/merged daedalus-security InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Err:1 http://deb.devuan.org/merged daedalus InRelease
  Temporary failure resolving 'deb.devuan.org'
Err:2 http://deb.devuan.org/merged daedalus-security InRelease
  Temporary failure resolving 'deb.devuan.org'
Err:3 http://deb.devuan.org/merged daedalus-updates InRelease
  Temporary failure resolving 'deb.devuan.org'
Reading package lists... Done    
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.devuan.org/merged/dists/daedalus/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/daedalus-security/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/daedalus-updates/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

So let us get some information...

$ ping -c 3 google.com
PING google.com (142.250.191.110) 56(84) bytes of data.
64 bytes from ord38s28-in-f14.1e100.net (142.250.191.110): icmp_seq=1 ttl=118 time=81.4 ms
64 bytes from ord38s28-in-f14.1e100.net (142.250.191.110): icmp_seq=2 ttl=118 time=81.5 ms
64 bytes from ord38s28-in-f14.1e100.net (142.250.191.110): icmp_seq=3 ttl=118 time=134 ms

--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 81.396/98.831/133.589/24.577 ms

Okay, that works...

$ ping -c 3 deb.devuan.org
ping: deb.devuan.org: Temporary failure in name resolution

That's odd...

$ nslookup deb.devuan.org
Server:         192.168.254.254
Address:        192.168.254.254#53

Non-authoritative answer:
deb.devuan.org  canonical name = deb.rr.devuan.org.
Name:   deb.rr.devuan.org
Address: 152.53.121.155
Name:   deb.rr.devuan.org
Address: 131.188.12.211
Name:   deb.rr.devuan.org
Address: 147.78.194.22
Name:   deb.rr.devuan.org
Address: 195.85.215.180
Name:   deb.rr.devuan.org
Address: 103.146.168.12
Name:   deb.rr.devuan.org
Address: 95.216.15.86
Name:   deb.rr.devuan.org
Address: 200.236.31.1
Name:   deb.rr.devuan.org
Address: 46.4.50.2
Name:   deb.rr.devuan.org
Address: 130.225.254.116
Name:   deb.rr.devuan.org
Address: 141.84.43.19
Name:   deb.rr.devuan.org
Address: 190.64.49.124
Name:   deb.rr.devuan.org
Address: 160.16.137.156
Name:   deb.rr.devuan.org
Address: 65.108.230.29
Name:   deb.rr.devuan.org
Address: 185.178.192.43
Name:   deb.rr.devuan.org
Address: 114.34.81.84
Name:   deb.rr.devuan.org
Address: 94.16.114.15
Name:   deb.rr.devuan.org
Address: 185.236.240.103
Name:   deb.rr.devuan.org
Address: 5.161.180.234
Name:   deb.rr.devuan.org
Address: 67.219.104.166
Name:   deb.rr.devuan.org
Address: 23.169.200.138
Name:   deb.rr.devuan.org
Address: 147.229.176.19
Name:   deb.rr.devuan.org
Address: 54.246.199.172
Name:   deb.rr.devuan.org
Address: 148.72.159.76
Name:   deb.rr.devuan.org
Address: 134.199.205.102
Name:   deb.rr.devuan.org
Address: 185.32.21.88
;; Truncated, retrying in TCP mode.
Name:   deb.rr.devuan.org
Address: 2a0a:4cc0:c0:4676:4242:4242:4242:4242
Name:   deb.rr.devuan.org
Address: 2001:638:a000:1021:21::1
Name:   deb.rr.devuan.org
Address: 2a0a:e5c0:10:3::6eeb
Name:   deb.rr.devuan.org
Address: 2a01:9e40::180
Name:   deb.rr.devuan.org
Address: 2407:b6c0::12
Name:   deb.rr.devuan.org
Address: 2a01:4f9:2a:fa9::2
Name:   deb.rr.devuan.org
Address: 2801:82:80ff:8000::2
Name:   deb.rr.devuan.org
Address: 2a01:4f8:140:1102:2b76:955d:b48f:bdf3
Name:   deb.rr.devuan.org
Address: 2001:878:346::116
Name:   deb.rr.devuan.org
Address: 2001:4ca0:4300::1:19
Name:   deb.rr.devuan.org
Address: 2800:a8:c001::a
Name:   deb.rr.devuan.org
Address: 2001:e42:102:1704:160:16:137:156
Name:   deb.rr.devuan.org
Address: 2a01:4f9:1a:aa0c::29
Name:   deb.rr.devuan.org
Address: 2a03:4000:28:24c::
Name:   deb.rr.devuan.org
Address: 2a0d:eb00:8006::acab
Name:   deb.rr.devuan.org
Address: 2a01:4ff:f0:dd3a::1
Name:   deb.rr.devuan.org
Address: 2401:c080:2000:229e:4b70:fe82:36ed:f788
Name:   deb.rr.devuan.org
Address: 2602:817:2000:401::138
Name:   deb.rr.devuan.org
Address: 2001:67c:1220:8b0::93e5:b013
Name:   deb.rr.devuan.org
Address: 2604:a880:5:1::154:0

$ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1

I also run a Debian machine so I know this resolv.conf is not correct. Also begs a question (questions at end of post). After running Connman UI Setup...

$ cat /etc/resolv.conf
domain home
search home
nameserver 192.168.254.254

$ ping -c 3 deb.devuan.org
PING deb.rr.devuan.org (152.53.121.155) 56(84) bytes of data.
64 bytes from v2202501232017310025.powersrv.de (152.53.121.155): icmp_seq=1 ttl=55 time=133 ms
64 bytes from v2202501232017310025.powersrv.de (152.53.121.155): icmp_seq=2 ttl=55 time=132 ms
64 bytes from v2202501232017310025.powersrv.de (152.53.121.155): icmp_seq=3 ttl=55 time=132 ms

--- deb.rr.devuan.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 132.197/132.428/132.599/0.169 ms

$ sudo apt update
[sudo] password for USER: 
Get:1 http://deb.devuan.org/merged daedalus InRelease [43.0 kB]
Get:2 http://deb.devuan.org/merged daedalus-security InRelease [33.2 kB]
Get:3 http://deb.devuan.org/merged daedalus-updates InRelease [33.4 kB]
Fetched 110 kB in 6s (18.4 kB/s)    
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

Everything seems to work, right? After a reboot /etc/resolv.conf reverts back to...

# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1

What the?... Odd. So I start poking about, not running Connman UI Setup. After awhile /etc/resolv.conf gets properly updated...

domain home
search home
nameserver 192.168.254.254

So let's see if the system eventually updates resolv.conf on it's own, while limiting our interaction with it...
[clipping the redundant output to 'cut to the chase']

--
third boot...

$ uptime
 20:05:19 up  1:13,  1 user,  load average: 0.00, 0.00, 0.00

$ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1

$ uptime
 20:41:56 up  1:49,  1 user,  load average: 0.00, 0.00, 0.00

$ cat /etc/resolv.conf
domain home
search home
nameserver 192.168.254.254

--
fourth boot...

$ uptime
 15:52:57 up  1:51,  1 user,  load average: 0.01, 0.01, 0.00

$ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1

$ uptime
 16:05:46 up  2:04,  1 user,  load average: 0.00, 0.00, 0.00

$ cat /etc/resolv.conf
domain home
search home
nameserver 192.168.254.254

--
fifth boot...

$ uptime
 18:08:40 up  1:41,  2 users,  load average: 0.00, 0.00, 0.00

$ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1

$ uptime
 18:12:51 up  1:45,  2 users,  load average: 0.04, 0.03, 0.00

$ cat /etc/resolv.conf
domain home
search home
nameserver 192.168.254.254

--
sixth boot...

$ uptime
 14:44:37 up  1:23,  1 user,  load average: 0.00, 0.00, 0.00

$ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1

$ uptime
 14:57:17 up  1:35,  1 user,  load average: 0.00, 0.00, 0.00

$ cat /etc/resolv.conf
domain home
search home
nameserver 192.168.254.254

...and on and on...

So the result of this little experiment begs several questions...

Why is Devuan taking over an hour and thrity minutes to properly update /etc/resolv.conf instead of at boot time?
Is there some setting(s) that didn't get properly setup during the install?
Is this an issue with runit and/or Connection Manager?
Why does google.com resolve but not deb.devuan.org with a bad /etc/resolv.conf?
Why is there such a variance in the time needed to update /etc/resolv.conf?
Is there some setting(s) that can be changed so that /etc/resolv.conf gets properly updated at boot time?
How did this get past testing?

This has never been an issue with any other distro I've worked with (Mint, Debian, Artix, AntiX, Fedora, etc.) The goal is for Devuan to properly update /etc/resolv.conf at boot like every other distro. I came to Devuan looking for stability and init freedom. Hopefully this sheds some light onto the actual cause of the issue people have been having. Let's work together to fix this issue... ideas? Thanks.