Insync not able to resolve apt.insync.io Debian Bullseye [FIXED]

I tried to install insync on opensuse-tumbleweed and then on Linux Mint Debian (LMDE5). Both times the client was not able to contact or resolve apt.insync.io or yum.insync.io (I think).

This is a copy of what I see when I try to update:
“sam@sam-nuc10i7fnh:~$ sudo apt update
Err:1 http://apt.insync.io/debian bullseye InRelease
Could not resolve ‘apt.insync.io
Hit:2 http://mirrors.accretive-networks.net/debian bullseye InRelease
Hit:3 http://mirrors.accretive-networks.net/debian bullseye-updates InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Hit:5 http://mirrors.accretive-networks.net/debian bullseye-backports InRelease
Hit:6 https://packages.microsoft.com/repos/edge stable InRelease
Ign:7 http://packages.linuxmint.com elsie InRelease
Hit:8 http://packages.linuxmint.com elsie Release
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
All packages are up to date.
W: Failed to fetch http://apt.insync.io/debian/dists/bullseye/InRelease Could not resolve ‘apt.insync.io
W: Some index files failed to download. They have been ignored, or old ones used instead.
sam@sam-nuc10i7fnh:~$”

Any ideas?

Exactly the same for Ubuntu 20.04, neither insync.io, nor apt.insync.io can’t be resolved (no A records whatsoever).

Thank you for reporting the issue. I’ve alerted our Linux team regarding this and will be updating you!

Hello! This has been fixed. Please try again!

Thanks Mia,

It seems to be working again. Did a server get unplugged? Lol.

1 Like

No, it expired but seems like we didn’t get alerted prior😅 We’ll be more proactive with this to prevent any trouble on your end!

I’m still seeing this but for Ubuntu:

➜ sudo apt update; apt list --upgradable
...
Err:10 http://apt.insync.io/ubuntu jammy Release
404  Not Found [IP: 0.0.0.0 80]
Reading package lists... Done
E: The repository 'http://apt.insync.io/ubuntu jammy Release' no longer has a Release file.
➜ dig apt.insync.io

; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> apt.insync.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36248
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;apt.insync.io.			IN	A

;; ANSWER SECTION:
apt.insync.io.		2593	IN	CNAME	insync-apt.b-cdn.net.
insync-apt.b-cdn.net.	2	IN	A	0.0.0.0

;; Query time: 7 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Fri Aug 12 18:55:00 PDT 2022
;; MSG SIZE  rcvd: 92

Notice the 0.0.0.0. I’ve never blocked that host, but when I explicitly added insync-apt.b-cdn.net to my allow list in Pi-hole:

➜ dig apt.insync.io

; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> apt.insync.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1562
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;apt.insync.io.			IN	A

;; ANSWER SECTION:
apt.insync.io.		2525	IN	CNAME	insync-apt.b-cdn.net.
insync-apt.b-cdn.net.	35	IN	A	185.180.13.248

;; Query time: 19 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Fri Aug 12 18:56:08 PDT 2022
;; MSG SIZE  rcvd: 92

Did insync-apt.b-cdn.net get added to a deny list?

Hmm, OK, so at some point, not sure when, I must have blocked b-cdn.net because I see it in my block list. I’m not sure when that happened because I’ve been out of town for the last few days, so… :confused:

False alarm!

@jc00ke Thanks for updating us that it’s been sorted out. I appreciate it!