search

AdguardTeam / AdGuardDNS

Public DNS resolver that protects you from ad trackers
https://adguard-dns.io/
GNU Affero General Public License v3.0
744 stars 61 forks source link

Unable to access Disney+ on Smart TV #674

Closed ghost closed 9 months ago

ghost commented 9 months ago

Platform

Other

Protocol

DNS-over-TLS

Do you use AdGuard app?

No I don't

Your configuration

DNS Server: AdGuard DNS private Protocol: DoT Filter: AdGuard DNS filter Userlist: None TV: Samsung Router: FRITZ!Box 7590 AX

Traceroute to AdGuard DNS

justin@Justins-MacBook-Pro ~ % traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 64 hops max, 52 byte packets
 1  192.168.178.1 (192.168.178.1)  10.690 ms  2.709 ms  1.760 ms
 2  100.103.128.1 (100.103.128.1)  7.020 ms  7.911 ms  6.681 ms
 3  10.241.1.54 (10.241.1.54)  8.262 ms  6.891 ms  7.129 ms
 4  gi0-0-0-1.bng1.vdc01.syd.aussiebb.net (202.142.143.119)  6.335 ms  8.057 ms  6.482 ms
 5  be50-3999.cfl3.20wha.qld.aussiebb.net (119.18.32.104)  7.093 ms  7.316 ms  6.682 ms
 6  10.241.13.167 (10.241.13.167)  16.928 ms  18.126 ms  17.343 ms
 7  as60068.syd.edgeix.net.au (202.77.88.64)  17.262 ms  18.242 ms  17.984 ms
 8  dns.adguard.com (94.140.14.14)  18.035 ms  18.813 ms  19.370 ms

Issue Details

  1. Set configuration as per above
  2. Turn on Samsung Smart TV
  3. Open Disney+

Expected Behavior

Disney+ loads.

Actual Behavior

Disney+ instantly shows a white page will show unable to connect to cd-dmgz-bamgrid.com, and Disney+ will not load. AdGuard DNS filtering log shows that it's not blocked.

Screenshot 2023-10-05 at 3 00 01 pm

When doing an dnslookup, it shows it is blocked though.

justin@Justins-MacBook-Pro ~ % dnslookup cd-dmgz-bamgrid.com 94.140.14.14
dnslookup 1.10.0
Server: 94.140.14.14

dnslookup result (elapsed 119.201031ms):
;; opcode: QUERY, status: NXDOMAIN, id: 47354
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;cd-dmgz-bamgrid.com.   IN   A

;; AUTHORITY SECTION:
com.    895 IN  SOA a.gtld-servers.net. nstld.verisign-grs.com. 1696481992 1800 900 604800 86400

Setting my router to Google DNS, or Cloudflare DNS allows Disney+ to work again.

Screenshots

Screenshot 1:

Additional Information

No response

hagezi commented 9 months ago

The domain cd-dmgz-bamgrid.com does not exist. You must mean cd-dmgz.bamgrid.com. This is resolved perfectly via AdGuardDNS.

dig cd-dmgz.bamgrid.com @94.140.14.14

; <<>> DiG 9.16.44-Debian <<>> cd-dmgz.bamgrid.com @94.140.14.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7722
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 0
;; QUESTION SECTION:
;cd-dmgz.bamgrid.com.           IN      A

;; ANSWER SECTION:
cd-dmgz.bamgrid.com.    300     IN      CNAME   dvf2rc3rx4ypk.cloudfront.net.
dvf2rc3rx4ypk.cloudfront.net. 60 IN     A       18.66.248.67
dvf2rc3rx4ypk.cloudfront.net. 60 IN     A       18.66.248.12
dvf2rc3rx4ypk.cloudfront.net. 60 IN     A       18.66.248.129
dvf2rc3rx4ypk.cloudfront.net. 60 IN     A       18.66.248.93

;; Query time: 15 msec
;; SERVER: 94.140.14.14#53(94.140.14.14)
;; WHEN: Thu Oct 05 08:10:11 CEST 2023
;; MSG SIZE  rcvd: 154
ghost commented 9 months ago

The domain cd-dmgz-bamgrid.com does not exist. You must mean cd-dmgz.bamgrid.com. This is resolved perfectly via AdGuardDNS.

dig cd-dmgz.bamgrid.com @94.140.14.14

; <<>> DiG 9.16.44-Debian <<>> cd-dmgz.bamgrid.com @94.140.14.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7722
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 0
;; QUESTION SECTION:
;cd-dmgz.bamgrid.com.           IN      A

;; ANSWER SECTION:
cd-dmgz.bamgrid.com.    300     IN      CNAME   dvf2rc3rx4ypk.cloudfront.net.
dvf2rc3rx4ypk.cloudfront.net. 60 IN     A       18.66.248.67
dvf2rc3rx4ypk.cloudfront.net. 60 IN     A       18.66.248.12
dvf2rc3rx4ypk.cloudfront.net. 60 IN     A       18.66.248.129
dvf2rc3rx4ypk.cloudfront.net. 60 IN     A       18.66.248.93

;; Query time: 15 msec
;; SERVER: 94.140.14.14#53(94.140.14.14)
;; WHEN: Thu Oct 05 08:10:11 CEST 2023
;; MSG SIZE  rcvd: 154

No, that was the error my TV gave, and it's also what is appearing in the filtering logs (see screenshot in first post, where the TV is accessing the domain via the Home Router).

ghost commented 9 months ago

I'm going to chalk this up to a once off occurrence. As @hagezi said, it doesn't exist. For whatever reason the Disney+ app has tried to connect to cd-dmgz-bamgrid.com twice, but every other time has used cd-dmgz.bamgrid.com

I've had the service for around a month now, and when setting the filtering log to 30 days, the domain in question hasn't appeared again. My guess is that someone from the Disney+ team has accidentally used the wrong domains somewhere in the app, and under certain circumstances the app calls that wrong domain.

As I can't reproduce this again, there's not much point this being open for now.