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

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

dummy@example.com (stargate-sg1-cheyenne-mtn) — Mon, 18 Nov 2024 13:59:10 +0000

this forum thread has references to DNS:

https://dev1galaxy.org/viewtopic.php?id=6925

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

dummy@example.com (bai4Iej2need) — Mon, 18 Nov 2024 08:47:30 +0000

2 years eight days later !
Threads which sleep that long should really be buried automatically after a grace period. 90/180/365 Days ?

maybe sth for the admins

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

dummy@example.com (vrgovinda) — Sun, 17 Nov 2024 14:50:33 +0000

@Grumpy

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

How to do this?

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

dummy@example.com (aluma) — Wed, 09 Nov 2022 13:56:36 +0000

If you go from http://deb.rr.devuan.org/ to mirror_status.html and then from this page, you can see the apt-panopticon results page report.
There's a lot about the state of the mirror network.

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

dummy@example.com (ralph.ronnquist) — Wed, 09 Nov 2022 12:06:38 +0000

One option is that you identify which mirror is good or the best for you, and then add that resolution into your /etc/hosts.

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

dummy@example.com (Digit) — Wed, 09 Nov 2022 10:59:41 +0000

I'm still afflicted with this. (and plusnet user)

What solutions/workarounds are there?

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

dummy@example.com (chris2be8) — Wed, 20 Jul 2022 16:11:32 +0000

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.

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

dummy@example.com (Marjorie) — Wed, 20 Jul 2022 14:09:40 +0000

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.

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

dummy@example.com (ralph.ronnquist) — Wed, 20 Jul 2022 00:44:53 +0000

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.

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

dummy@example.com (Grumpy) — Tue, 19 Jul 2022 22:06:28 +0000

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?

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

dummy@example.com (Head_on_a_Stick) — Tue, 19 Jul 2022 15:14:38 +0000

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:~$

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

dummy@example.com (caner) — Tue, 19 Jul 2022 14:39:01 +0000

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??

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

dummy@example.com (Marjorie) — Tue, 19 Jul 2022 13:17:57 +0000

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

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

dummy@example.com (gg) — Tue, 19 Jul 2022 10:22:31 +0000

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

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

dummy@example.com (Grumpy) — Tue, 19 Jul 2022 10:21:16 +0000

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