1.1.1.1 does not resolve spotify.com

Hi, I am having issues resolving spotify.com for some hours now. It seems also to include some or all of their subdomains. I am using DoT with “FRITZ!Box 7530”.

➜  ~ nslookup spotify.com 1.1.1.1
Server:         1.1.1.1
Address:        1.1.1.1#53

** server can't find spotify.com: REFUSED
  • https://cloudflare-dns.com/help/#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJZZXMiLCJpc0RvaCI6Ik5vIiwicmVzb2x2ZXJJcC0xLjEuMS4xIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjAuMC4xIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTExMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJZZXMiLCJkYXRhY2VudGVyTG9jYXRpb24iOiJGUkEiLCJpc1dhcnAiOiJObyIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==
  • https://dnsviz.net/d/spotify.com/dnssec/

Additional Information

➜  ~ dig spotify.com @1.1.1.1

; <<>> DiG 9.18.14 <<>> spotify.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 29635
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 26 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Sun Apr 23 22:27:25 CEST 2023
;; MSG SIZE  rcvd: 40

➜  ~ dig spotify.com @1.0.0.1

; <<>> DiG 9.18.14 <<>> spotify.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 41269
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 23 msec
;; SERVER: 1.0.0.1#53(1.0.0.1) (UDP)
;; WHEN: Sun Apr 23 22:27:37 CEST 2023
;; MSG SIZE  rcvd: 40

➜  ~ dig spotify.com @8.8.8.8

; <<>> DiG 9.18.14 <<>> spotify.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30639
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;spotify.com.                   IN      A

;; ANSWER SECTION:
spotify.com.            195     IN      A       35.186.224.25

;; Query time: 13 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Apr 23 22:27:46 CEST 2023
;; MSG SIZE  rcvd: 56

➜  ~ dig +short CHAOS TXT id.server @1.1.1.1
"FRA"
➜  ~ dig +short CHAOS TXT id.server @1.0.0.1
"FRA"
➜  ~ dig @ns3.Cloudflare.com whoami.Cloudflare.com txt +short
"2003:e5:f(redacted)"

Kind Regards
Marcel

4 Likes

I got the same issue with the DNSv6-Server.

Get an dns_probe_finished_nxdomain at all spotify domains/services with Cloudflare.
I already restart the dns client und used /flushdns.

Spotify just work when I use the provider or google dns actually :frowning:

Having the exact same issue. Spotify on my phone won’t work, nor on my PC nor in my browser. Only when I change to another DNS I can listen to music.

1 Like

I can resolve spotify.com through the 1.1.1.1 variants just fine, from various locations that are reaching multiple different Cloudflare locations.

Are you people still having issues?

If so, can you (@j1m, @NilZ) please also provide the output of:

dig +nsid CHAOS TXT id.server @1.1.1.1
dig +nsid CHAOS TXT id.server @1.0.0.1
dig +nsid CHAOS TXT id.server @2606:4700:4700::1111

dig +nsid spotify.com @1.1.1.1
dig +nsid spotify.com @1.0.0.1
dig +nsid spotify.com @2606:4700:4700::1111
nslookup -class=CHAOS -type=TXT id.server 1.1.1.1
nslookup -class=CHAOS -type=TXT id.server 1.0.0.1
nslookup -class=CHAOS -type=TXT id.server 2606:4700:4700::1111

nslookup spotify.com 1.1.1.1
nslookup spotify.com 1.0.0.1
nslookup spotify.com 2606:4700:4700::1111

If you have IPv6 connectivity, please also test the IPv6 variant and report back.

I am having the same issue since yesterday. I also use DOT and a Fritxbox 7590.

Yes through my wireguard tunnel on my phone I am still not able to open Spotify.com: DNS_PROBE_FINISHED_NXDOMAIN

Disabling wireguard, with just 5G(no Cloudflare set up) it works fine.

I’ll be home in ~40min to check directly.

Having the same issue, also using Fritzbox 7590. Needed to switch to a different dns server for now

Hi, thanks for informing us about the problem. It should now be resolved. If you’re still having issues please let us know.

4 Likes

Hi @sebastiaan,

fixed for me. Weird problem though?

Thank you :slight_smile:

Thanks for the fast fix, can you explain what the problem was?

3 Likes

Also working again for me! Thanks :slight_smile:

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.