The officially official Devuan Forum!

You are not logged in.

#1 2022-07-17 13:07:37

gipi
Member
Registered: 2020-06-03
Posts: 14  

"Temporary failure resolving 'deb.devuan.org' "

For the last three days (at least), apt update does not function. I cannot resolve the URL, even though I am connected to the internet and connection works. Worked perfectly fine few days ago, and i did not remove any relevant package in the meantime. Does anyone know what is happening?

Offline

#2 2022-07-17 15:50:57

chris2be8
Member
Registered: 2018-08-11
Posts: 155  

Re: "Temporary failure resolving 'deb.devuan.org' "

First try pinging the address in the URL and see if you get a response.

Then put the URL into a browser and see what it shows.

If still stuck post the contents of /etc/apt/sources.list here. And full output from apt update.

Offline

#3 2022-07-18 21:19:27

Grumpy
Member
Registered: 2022-07-18
Posts: 6  

Re: "Temporary failure resolving 'deb.devuan.org' "

Hi, first post here.
I think I'm having the same problem as the OP

Update fails as

$ sudo apt update
Err:1 http://deb.devuan.org/merged chimaera InRelease
  Temporary failure resolving 'deb.devuan.org'
Err:2 http://deb.devuan.org/merged chimaera-updates InRelease
  Temporary failure resolving 'deb.devuan.org'
Hit:3 http://pkgmaster.devuan.org/merged chimaera-security InRelease
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/chimaera/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/chimaera-updates/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

Ping gives

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

/etc/apt/sources.list contains

# deb cdrom:[Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012]/ chimaera contrib main non-free 

# deb cdrom:[Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012]/ chimaera non-free main contrib 

deb http://deb.devuan.org/merged/ chimaera main non-free contrib 
deb-src http://deb.devuan.org/merged/ chimaera main non-free contrib 

deb http://pkgmaster.devuan.org/merged/ chimaera-security main contrib non-free 
deb-src http://pkgmaster.devuan.org/merged/ chimaera-security main contrib non-free 

# chimaera-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.devuan.org/merged/ chimaera-updates main contrib non-free 
deb-src http://deb.devuan.org/merged/ chimaera-updates main contrib non-free 

Martin

Online

#4 2022-07-18 23:16:22

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 731  

Re: "Temporary failure resolving 'deb.devuan.org' "

@Grumpy, with all respect, it's kind of like contacting your bike manufacturer when you, on your way to the shop, find that there is a temporary road closure.

More precisely, the Temporary failure in resolving 'deb.devuan.org' notice is from the initial phase in the networking when the apt software (on your computer) attempts to find an IP address for that service. The service itself is not involved in that phase.

Offline

#5 2022-07-19 06:52:35

gg
Member
Registered: 2022-07-19
Posts: 2  

Re: "Temporary failure resolving 'deb.devuan.org' "

I'm having the same issue described by gipi and Grumpy: Temporary failure in resolving 'deb.devuan.org'. I'm on a Devuan Ceres.
Should this be important, I'm using connman to manage my net connection.
I was able to update my system by adding a couple of mirror addresses in the sources.list

However, what is very strange to me is that I have another ceres installation on a virtual machine (qemu + net in user mode) on the same hardware and it works perfectly.
Furthermore I tried also with another VM (unfortunately not Devuan) running system wide (qemu + virtual net) and also with this one I can ping and browse deb.devuan.org.

The only differences that I can see is that the main installation uses a wifi connection while VMs are fooled to think they are on cable.

Any hint?

Ciao
gg

Offline

#6 2022-07-19 08:06:26

Grumpy
Member
Registered: 2022-07-18
Posts: 6  

Re: "Temporary failure resolving 'deb.devuan.org' "

Thank for the tip Ralph

it's kind of like contacting your bike manufacturer when you, on your way to the shop, find that there is a temporary road closure.

is close but

it's kind of like contacting your bike manufacturer when you, try to find the address of the shop only to find it has been removed from the local business directory.

would be closer.

I did a few pings
google.com worked
devuan.org worked
deb.devuan.org FAILED

I searched and found that I should cat /etc/resolv.conf

# Generated by NetworkManager
search lan
nameserver 192.168.1.254

The only DNS was my ISP (PlusNet in the UK). PlusNet must have removed the entry for deb.devuan.org in the last couple of weeks.

I added an entry in networkmanager for OpenDNS and everything works now.

Online

#7 2022-07-19 10:06:05

caner
Member
Registered: 2022-07-19
Posts: 2  

Re: "Temporary failure resolving 'deb.devuan.org' "

I'm with BT (British Telecom) ISP and recently having the same problem. I wonder why UK ISPs are blocking deb.devuan.org? It is not a controversial URL  -  or is it? Lets try openDNS.

Offline

#8 2022-07-19 10:21:16

Grumpy
Member
Registered: 2022-07-18
Posts: 6  

Re: "Temporary failure resolving 'deb.devuan.org' "

BT is, I think, the parent company of PlusNet so it could just be a BT problem

Online

#9 2022-07-19 10:22:31

gg
Member
Registered: 2022-07-19
Posts: 2  

Re: "Temporary failure resolving 'deb.devuan.org' "

Restarted connman and the problem seems fixed.
Maybe some DNS cache not properly cleaned?

Offline

#10 2022-07-19 13:17:57

Marjorie
Member
From: Teignmouth, UK
Registered: 2019-06-09
Posts: 153  

Re: "Temporary failure resolving 'deb.devuan.org' "

Seems to be working fine, using dnscrypt-proxy (hence local DNS server IP: 127.0.0.1#53 ) and Zen as my ISP in the UK.

marjorie@grendel:~$ dig deb.devuan.org

; <<>> DiG 9.16.27-Debian <<>> deb.devuan.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29801
;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;deb.devuan.org.			IN	A

;; ANSWER SECTION:
deb.devuan.org.		2399	IN	CNAME	deb.rr.devuan.org.
deb.rr.devuan.org.	2399	IN	A	130.225.254.116
deb.rr.devuan.org.	2399	IN	A	185.203.114.135
deb.rr.devuan.org.	2399	IN	A	185.178.192.43
deb.rr.devuan.org.	2399	IN	A	95.216.15.86
deb.rr.devuan.org.	2399	IN	A	125.228.189.120
deb.rr.devuan.org.	2399	IN	A	5.9.122.185
deb.rr.devuan.org.	2399	IN	A	185.183.113.131
deb.rr.devuan.org.	2399	IN	A	200.236.31.1
deb.rr.devuan.org.	2399	IN	A	46.4.50.2
deb.rr.devuan.org.	2399	IN	A	160.16.137.156
deb.rr.devuan.org.	2399	IN	A	195.85.215.180
deb.rr.devuan.org.	2399	IN	A	185.38.15.81
deb.rr.devuan.org.	2399	IN	A	89.174.102.150
deb.rr.devuan.org.	2399	IN	A	158.69.153.121
deb.rr.devuan.org.	2399	IN	A	141.84.43.19
deb.rr.devuan.org.	2399	IN	A	131.188.12.211

;; Query time: 43 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jul 19 14:10:01 BST 2022
;; MSG SIZE  rcvd: 320

I assume the list of IP are those of the component mirrors in the round-robin, so for the first 130.225.254.116 the corresponding DNS is mirrors.dotsrc.org.

marjorie@grendel:~$ dig -x 130.225.254.116

; <<>> DiG 9.16.27-Debian <<>> -x 130.225.254.116
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20569
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
;; QUESTION SECTION:
;116.254.225.130.in-addr.arpa.	IN	PTR

;; ANSWER SECTION:
116.254.225.130.in-addr.arpa. 3594 IN	CNAME	116.96-27.254.225.130.in-addr.arpa.
116.96-27.254.225.130.in-addr.arpa. 3594 IN PTR	mirrors.dotsrc.org.

;; Query time: 23 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jul 19 14:13:31 BST 2022
;; MSG SIZE  rcvd: 113

Last edited by Marjorie (2022-07-19 13:19:55)

Offline

#11 2022-07-19 14:39:01

caner
Member
Registered: 2022-07-19
Posts: 2  

Re: "Temporary failure resolving 'deb.devuan.org' "

Now using Cloudflare DNS system and all is working well. Thank to @Grumpy for pointing in the right direction. Are you all served by UK ISPs that are having problems? Pure speculation but is using a distro without systemd being targeted by GCHQ??

Last edited by caner (2022-07-19 14:39:35)

Offline

#12 2022-07-19 15:14:38

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 2,532  

Re: "Temporary failure resolving 'deb.devuan.org' "

Grumpy wrote:

PlusNet must have removed the entry for deb.devuan.org in the last couple of weeks.

I'm with PlusNet:

alpine:~$ dig +short @192.168.0.1 deb.devuan.org 
deb.rr.devuan.org.
5.9.122.185
125.228.189.120
185.183.113.131
185.178.192.43
46.4.50.2
160.16.137.156
195.85.215.180
185.38.15.81
158.69.153.121
89.174.102.150
141.84.43.19
131.188.12.211
130.225.254.116
185.203.114.135
95.216.15.86
200.236.31.1
alpine:~$
caner wrote:

is using a distro without systemd being targeted by GCHQ?

No.

alpine:~$ ls -l /sbin/init
lrwxrwxrwx 1 root root 12 Feb 13 10:10 /sbin/init -> /bin/busybox
alpine:~$

Offline

#13 2022-07-19 22:06:28

Grumpy
Member
Registered: 2022-07-18
Posts: 6  

Re: "Temporary failure resolving 'deb.devuan.org' "

HoaS, I have two laptops, one my daily driver had been updating properly until about 10 days ago, the other had not been turned on for two months, neither would resolve deb.devuan.org until I added OpenDNS. The router was supplied by PlusNet, my ISP.
Both laptops also have a flavour of Ubuntu installed with DNS being looped in some way by systemd (127.0.0.63)  I think. I have no idea about systemd, Both Ubuntu installs resolved deb.devuan.org.
Any ideas?

Online

#14 2022-07-20 00:44:53

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 731  

Re: "Temporary failure resolving 'deb.devuan.org' "

Possibly this all has been an effect of an apparent misconfiguration of Devuan's authoritative name servers such that some of them only served the ipv6 addresses for deb.devuan.org.

This has been corrected, so things might improve.

Offline

#15 2022-07-20 14:09:40

Marjorie
Member
From: Teignmouth, UK
Registered: 2019-06-09
Posts: 153  

Re: "Temporary failure resolving 'deb.devuan.org' "

Grumpy wrote:

Both laptops also have a flavour of Ubuntu installed with DNS being looped in some way by systemd (127.0.0.63)  I think. I have no idea about systemd, Both Ubuntu installs resolved deb.devuan.org.
Any ideas?

Indeed, systemd in it's usual feature creep tries to provide DNS resolution (and just about anything else) as well as init functions in this case with systemd-resolved.
Of course you don't find it on Devuan.
I use dsncrypt-proxy which uses a similar redirection to 127.0.0.1#53 to provide a local first-point-of-call for DNS (Port 53 is the default port for DNS queries). Along with local caching the proxy then looks up DNS on DNS servers out there on the internet. In the case of dnscrypt-proxy these are dns-over-https or dnscrypt servers and mine polls for ones that are DNSSEC and local.
In dnscrypt-proxy I can block evil DNS and IP. I don't know whether systemd-resolved has this capability, however clearly a systemd OS would be rather foolish to use deb.devuan.org as its repositories are systemd-free.

Offline

#16 2022-07-20 16:11:32

chris2be8
Member
Registered: 2018-08-11
Posts: 155  

Re: "Temporary failure resolving 'deb.devuan.org' "

Checking a bit more:

chris@rigel:~/bin$ host deb.devuan.org
deb.devuan.org is an alias for deb.rr.devuan.org.
deb.rr.devuan.org has address 200.236.31.1
deb.rr.devuan.org has address 125.228.189.120
deb.rr.devuan.org has address 185.178.192.43
deb.rr.devuan.org has address 160.16.137.156
deb.rr.devuan.org has address 195.85.215.180
deb.rr.devuan.org has address 89.174.102.150
deb.rr.devuan.org has address 131.188.12.211
deb.rr.devuan.org has address 185.203.114.135
deb.rr.devuan.org has address 158.69.153.121
deb.rr.devuan.org has address 185.38.15.81
deb.rr.devuan.org has address 95.216.15.86
deb.rr.devuan.org has address 46.4.50.2
deb.rr.devuan.org has address 130.225.254.116
deb.rr.devuan.org has address 141.84.43.19
deb.rr.devuan.org has address 185.183.113.131
deb.rr.devuan.org has address 5.9.122.185
deb.rr.devuan.org has IPv6 address 2a0a:e5c0:2:2:400:c8ff:fe68:bef3
deb.rr.devuan.org has IPv6 address 2001:638:a000:1021:21::1
deb.rr.devuan.org has IPv6 address 2001:4190:801c:1::150
deb.rr.devuan.org has IPv6 address 2001:878:346::116
deb.rr.devuan.org has IPv6 address 2a01:4f9:2a:fa9::2
deb.rr.devuan.org has IPv6 address 2a01:4f8:162:7293::14
deb.rr.devuan.org has IPv6 address 2001:4ca0:4300::1:19
deb.rr.devuan.org has IPv6 address 2001:e42:102:1704:160:16:137:156
deb.rr.devuan.org has IPv6 address 2a01:4f8:140:1102:2b76:955d:b48f:bdf3
deb.rr.devuan.org has IPv6 address 2607:5300:61:95f:7283:11d9:f86:e691
deb.rr.devuan.org has IPv6 address 2801:82:80ff:8000::2
deb.rr.devuan.org has IPv6 address 2a01:9e40::180
deb.rr.devuan.org has IPv6 address 2a02:2a38:1:400:422a:422a:422a:422a

The first line of output is noteworthy.

So if you still have problems try ping deb.rr.devuan.org and see if that works. It's *possible* that just the alias deb.devuan.org was missing from the DNS server you were using.

If that also fails try host deb.devuan.org to see if the alias is there but not deb.rr.devuan.org.

The other thing that could happen is that one or more of the servers the load is shared over was down/inaccessible. This could cause intermittent failures which would be a pain to sort out. Especially if they are only blocked from some IP addresses.

Offline

Board footer