Announcements

Help Wizard

Step 1

NEXT STEP

repository.spotify.com inaccessible via current Internet Protocol

repository.spotify.com inaccessible via current Internet Protocol

Device

Computer

Operating System

Ubuntu MATE 22.04 - Linux


My Question or Issue

The repository.spotify.com server is inaccessible via current Internet Protocol a.k.a. IPv6. Debian/Ubuntu Linux client can't be installed and/or updated because its respository can't be reached in an IPv6-only environemnt. The client, once installed, works perfectly fine in the same IPv6-only environment.


Terminal output:

~$ sudo aptitude update
[...]
Ign http://repository.spotify.com stable InRelease
[...]
Err http://repository.spotify.com stable InRelease
Could not resolve 'repository.spotify.com'
[...]
W: Failed to fetch http://repository.spotify.com/dists/stable/InRelease: Could not resolve 'repository.spotify.com'
[...]
W: Some index files failed to download. They have been ignored, or old ones used instead.


~$ dig AAAA repository.spotify.com

; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> AAAA repository.spotify.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49727
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;repository.spotify.com. IN AAAA

;; ANSWER SECTION:
repository.spotify.com. 12 IN CNAME d2czmavkeme1ql.cloudfront.net.

;; AUTHORITY SECTION:
d2czmavkeme1ql.cloudfront.net. 612 IN SOA ns-227.awsdns-28.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 14 msec
;; SERVER: 2606:4700:4700::1111#53(2606:4700:4700::1111) (UDP)
;; WHEN: Wed Aug 23 21:45:58 -03 2023
;; MSG SIZE rcvd: 172

 

~$ ping6 repository.spotify.com
ping6: repository.spotify.com: Address family for hostname not supported

Reply
1 Reply

Looks like it's now fixed and accessible!

 


$ dig repository.spotify.com

; <<>> DiG 9.18.30-0ubuntu0.24.04.2-Ubuntu <<>> AAAA repository.spotify.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36042
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;repository.spotify.com. IN AAAA

;; ANSWER SECTION:
repository.spotify.com. 292 IN CNAME tls13.spotifycdn.map.fastly.net.
tls13.spotifycdn.map.fastly.net. 52 IN AAAA 2a04:4e42:4e::762
tls13.spotifycdn.map.fastly.net. 52 IN AAAA 2a04:4e42:4f::762

;; Query time: 2 msec
;; SERVER: ::1#53(::1) (UDP)
;; WHEN: Mon Apr 07 13:10:46 -03 2025
;; MSG SIZE rcvd: 152


$ ping -c1 repository.spotify.com
PING repository.spotify.com (2a04:4e42:4f::762) 56 data bytes
64 bytes from 2a04:4e42:4f::762: icmp_seq=1 ttl=55 time=9.12 ms

--- repository.spotify.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 9.117/9.117/9.117/0.000 ms


 Thanks to everyone involved! 🙂

Suggested posts

Let's introduce ourselves!

Hey there you,   Yeah, you! 😁   Welcome - we're glad you joined the Spotify Community!   While you here, let's have a fun game and get…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random