Netflix not working in Buster

[sirfer]

Here's a tricky one.
I went to watch netflix and I get this message in Chromium and Firefox.

This site can’t be reached
http://www.netflix.com’s server IP address could not be found.
Try:
Checking the connection
Checking the proxy, firewall, and DNS configuration
ERR_NAME_NOT_RESOLVED

The thing is, Netflix works on a Pepperment 10 install, on my phone and on a live CD (via USB drive) on another computer in the house.
So of course changing DNS addresses and gateway and other network settings hasn't helped.

Any ideas? I have done my due diligence with googling etc but haven't come up with much as it seems to be a local issue.

PS. Edit to add that if I start Netflix by tethering to mobile internet via my phone and then switch to the home wired connection using dhclient, Netflix continues to work fine.

Many thanks in advance.

[sickpig]

his site can’t be reached
http://www.netflix.com’s server IP address could not be found.

netflix is https not http.
Are you using proxy or vpn?

[sirfer]

Sorry, my bad, yes I have tried http vs https and the result is the same.
No proxies or VPNs are involved. Just a regular copper line ADSL connection with pretty much default settings.

Just to emphasise my last edit:
I start Netflix by tethering to mobile internet via my phone and then switch to the home wired connection using dhclient, Netflix continues to work fine.

[sickpig]

The loadbalancer for netflix is

Code: Select all

dualstack.wwwservice--frontend-san-vpc0-1072607415.us-west-2.elb.amazonaws.com

The alternate dns names are -


see which ones are accessible from your location

[sirfer]

None of the above

I swear I tried them all by typing them in manually

Also used the trick of starting Netflix using mobile data then switching to the copper line and still can't ping netflix.com even when it is working :/

[sickpig]

Also used the trick of starting Netflix using mobile data then switching to the copper line and still can't ping netflix.com even when it is working :/

That's expected, they block icmp traffic.

I suspect issues with your dns.
check -

Code: Select all

dig www.netflix.com

See if you can get a response.

[sirfer]

This is what I get using dig...

steve@ssda3:~$ dig www.netflix.com

; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> www.netflix.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45701
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.netflix.com. IN A

;; ANSWER SECTION:
www.netflix.com. 16 IN CNAME www.dradis.netflix.com.
www.dradis.netflix.com. 16 IN CNAME www.us-west-2.internal.dradis.netflix.com.
www.us-west-2.internal.dradis.netflix.com. 16 IN CNAME dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com.
dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 34.216.122.36
dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 35.165.194.49
dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 34.213.113.6
dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 52.24.4.22
dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 52.33.157.25
dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 52.34.38.200
dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 52.34.158.161
dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 54.187.176.196

;; AUTHORITY SECTION:
us-west-2.elb.amazonaws.com. 1003 IN NS ns-1475.awsdns-56.org.
us-west-2.elb.amazonaws.com. 1003 IN NS ns-1769.awsdns-29.co.uk.
us-west-2.elb.amazonaws.com. 1003 IN NS ns-332.awsdns-41.com.
us-west-2.elb.amazonaws.com. 1003 IN NS ns-560.awsdns-06.net.

;; Query time: 23 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Oct 02 01:18:09 NZDT 2020
;; MSG SIZE rcvd: 460

Not sure if this points to any errors :/

[sickpig]

Not sure if this points to any errors :/

No it doesn't except for some reason your dns cache is ridiculously low.

check -

Code: Select all

curl -v https://www.netflix.com

[sirfer]

Code: Select all

steve@ssda3:/~$ curl -v https://www.netflix.com
* Expire in 0 ms for 6 (transfer 0x55724d72fdc0)
....etc
* Expire in 8 ms for 1 (transfer 0x55724d72fdc0)
* Could not resolve host: www.netflix.com
* Expire in 10 ms for 1 (transfer 0x55724d72fdc0)
* Closing connection 0
curl: (6) Could not resolve host: www.netflix.com

BTW this is a vanilla Buster install with just openbox, tint2, web browsers, thunar and a few other basic apps, so FWIW I haven't been monkeying about with it at all really

No it doesn't except for some reason your dns cache is ridiculously low.

How can you tell? And what does that mean? Sorry for being such a newb :/
Thanks for the help so far btw.

[sickpig]

Code: Select all

dualstack.wwwservice2--frontend-san-vpc0-571120560.us-west-2.elb.amazonaws.com. 25 IN A 34.216.122.36

The number 25 is the number of seconds the A record gets cached in your ns.

You need to disable ipv6 to fix the resolution error. Google is your friend. Also try with 1.1.1.1 as the ns instead of your isp's ns.

[sirfer]

Brilliant! Disabling ipV6 worked a treat!

Thanks so much