Why isn't Netflix working after only playing one show?
February 6, 2020 6:14 PM Subscribe
Netflix is throwing a DNS error three days in a row but only AFTER it plays one show - any ideas how to fix this?
Three days in a row Netflix will pay one show, then have an error when doing something like looking for the next episode. Then when I try to load netflix I suddenly get a DNS error:
This site can’t be reachedwww.netflix.com’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
I am on a Mac and have tried two versions of Chrome, Safari and Firefox and it keep throwing the error. Have tried a reboot. Tried clearing cache. Nothing seems to work. Yet if I launch the app on my phone or AppleTV (on the same wifi network) that works fine.
I am pulling my hair out. Help!
Three days in a row Netflix will pay one show, then have an error when doing something like looking for the next episode. Then when I try to load netflix I suddenly get a DNS error:
This site can’t be reachedwww.netflix.com’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
I am on a Mac and have tried two versions of Chrome, Safari and Firefox and it keep throwing the error. Have tried a reboot. Tried clearing cache. Nothing seems to work. Yet if I launch the app on my phone or AppleTV (on the same wifi network) that works fine.
I am pulling my hair out. Help!
Response by poster: Update: if I use my phone as a hotspot it DOES work fine - the same browsers that throw a DNS error on my network work fine when using my phone as a hotspot. But my phone works fine on the wifi network when using the netflix app.
posted by UMDirector at 6:19 PM on February 6, 2020
posted by UMDirector at 6:19 PM on February 6, 2020
Best answer: Change your Mac's DNS settings for its main connection; you can use 8.8.8.8 and 8.8.4.4, two public servers provided by google. Another option is the classic 4.2.2.1, currently from Level 3 Communications.
posted by Sunburnt at 6:32 PM on February 6, 2020 [1 favorite]
posted by Sunburnt at 6:32 PM on February 6, 2020 [1 favorite]
Best answer: Also worth trying:
1.1.1.1
(I think 1.1.1.2 is their alternate....)
posted by pompomtom at 6:39 PM on February 6, 2020
1.1.1.1
(I think 1.1.1.2 is their alternate....)
posted by pompomtom at 6:39 PM on February 6, 2020
DNS is not a browser issue, it's something weird going on with your network. I agree, change to 8.8.8.8 or 1.1.1.1
posted by bradbane at 8:32 PM on February 6, 2020
posted by bradbane at 8:32 PM on February 6, 2020
+1 to the DNS changes listed above.
As to the why: Do you manage your own home network? Maybe a DNS blocking service was recently set up and Netflix's browser player uses some that are on a block list. It could also be your internet provider doing who-knows-what.
If you're interested in tracking down more detailed errors, you could start playing Netflix, then open up the browser's' dev tools (Firefox's Menu > Web Developer > Network viewer is my preferred one; Chrome has menu > more tools > developer tools > network). It's a lot of info, but it will have a thorough log of the domains being queried and the response, so timeouts/errors should show up.
posted by enigmango at 8:40 PM on February 6, 2020
As to the why: Do you manage your own home network? Maybe a DNS blocking service was recently set up and Netflix's browser player uses some that are on a block list. It could also be your internet provider doing who-knows-what.
If you're interested in tracking down more detailed errors, you could start playing Netflix, then open up the browser's' dev tools (Firefox's Menu > Web Developer > Network viewer is my preferred one; Chrome has menu > more tools > developer tools > network). It's a lot of info, but it will have a thorough log of the domains being queried and the response, so timeouts/errors should show up.
posted by enigmango at 8:40 PM on February 6, 2020
This thread is closed to new comments.
posted by UMDirector at 6:15 PM on February 6, 2020