yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] Chesterton2:
DJames,

Thank you for taking time to respond. The Country Code is US and the firmware version is Build 17250.

Following your suggestion, I did the following tests, all on my PC:

Test 1:

1. I blocked 8.8.8.8 and 8.8.4.4 with these IPTable commands for the Firewall:

iptables -I FORWARD -d 8.8.8.8 -j DROP

iptables -I FORWARD -d 8.8.4.4 -j DROP​

2. I rebooted the router, and I tried pinging 8.8.8.8 and 8.8.4.4. They both returned "Request timed out."

3. I changed the DNS settings in the router to those specified by Overplay.

4. I again rebooted the router. I verified that ping on my PC still failed for 8.8.8.8 and 8.8.4.4.

5. I rebooted the Chromecast to clear the DNS, and I issued ipconfig /flushdns on my PC.

6. I went to pluzz.francetv.fr and found a show that I knew would be country blocked. I played it without issue in a Chrome Tab. I then clicked Google Cast and casted the entire tab. This worked, though the video quality wasn't too good.

7. I then clicked Google Cast and chose the default - to cast the actual site, pluzz.francetv.fr, rather than the entire tab. This still gave the "Oops, shouldn't be here" error.

8. I then tried casting a video on the pluzz.francetv.fr site that I know is not country locked (at least from the US). It behaved the same - it worked when I cast the entire tab, but it failed the same way when I cast the actual site.

9. I tried casting Pandora from by Galaxy S4, and it failed as well.

10. I tried casting Youtube from my PC, and it WORKED.

Test 2:

1. I kept the Google IPs blocked, but I changed my router's DNS to be my provider's default, by replacing the Overplay IP addresses with 0.0.0.0.

2. I rebooted the router.

3. I flushed the PC's DNS cache with ipconfig /flushdns as before.

4. I rebooted the Chromecast.

5. I then tried casting a video on the pluzz.francetv.fr site that I know is not country locked, as I'd tried in step 8 above. This worked on the Chromecast with good quality video.

6. I then tried casting Pandora to the Chromecast from my Samsung Galaxy S4 and it worked as well, where it had failed in previous tests when Google's DNS addresses were blocked.

I think we can conclude the following, but I'm certainly no expert:

1. When Chromecast can't find Google's DNS servers, it refuses to use some DNS servers, such as Overplay's, for some sites or applications. In my case, it casted Youtube and a Chrome Tab, using the Overplay DNS with Google's blocked, but it would not cast Pandora or pluzz.francetv.fr.

2. When Chromecast can't find Google's DNS servers, but finds some alternate DNS servers, such as my provider's default one, then it acts just as if it had found a Google's DNS server. In other words, it casts Pandora but blocks pluzz.francetv.fr if the video is country locked.

I guess I could try a different DNS provider and see if it works differently. Has anyone else had success casting French content with Overplay?
[Google Chromecast] Chesterton2:
SOLVED!

I tried a different DNS provider, unlocator's 7 day free trial, and, to my surprise, everything started working! I guess there's something about Overplay's DNS servers that Chrome Cast doesn't like.

DJames and bhiga,

Thanks so much for your help in diagnosing this problem. Your questions enabled me to think of new tests that led to the conclusion that it could be my DNS provider.

:victory: :good::good::good:
[Google Chromecast] DJames1:
It is true that DNS unblocking services are not guaranteed to work the same on every device. In some cases it may work on a PC and not on the Chromecast. A few DNS services publish tables of the devices they have tested, but most can't afford the resources to test every device.
[Google Chromecast] 14rt:
Hi,

Can any experts teach me how to allow chromecast to view apps from my iphone (eg. BBC iplayer / netflix)?

I'm currently using a vpn on my iphone thus the apps work on the iphone. But when I press the cast tab on bbc iplayer it opens the app on chromecast but doesn't load and says error 94 on my phone and for netflix it opens the netflix on the chromecast and just doesn't load.

I'm currently on this router 2Wire 5012nv. xxx.setuprouter.com/router/2wire/5012nv-002/screenshots.htm

A step by step would be much helpful. Thanks :)
[Google Chromecast] DJames1:
The Chromecast has to use the same VPN as your phone to access that blocked content, so you have to do one of two things:

Method 1: Use a router that supports a VPN on the router (for example, a router with DD-WRT firmware).

Method 2: Use a DNS unblocking service and follow the procedures given in this thread to block Google DNS and push the desired DNS addresses to the Chromecast via DHCP.
[Google Chromecast] 14rt:
Hi. thanks for replying.

Ive read through the thread but i've no idea how to enable those on my router.

My router is 2Wire 5012nv. It can be seen at this site-

xxx.setuprouter.com/router/2wire/5012nv-002/screenshots.htm (change the xxx infront to www cos the forum doesnt let me posts links)

If theres anyone that can help me with this it'd be great.

Thanks
[Google Chromecast] ykphuah:
Hopefully the new chromecast update they mentioned in Google IO is going to remove this requirement. :D

They showcased that you don't need to be on the same WIFI network for you to cast.
[Google Chromecast] DJames1:
That would be nice, but I don't think it would help when the VPN is needed to bypass geoblocking.
[Google Chromecast] 14rt:
anyone able to help me? pls?
[Google Chromecast] bhiga:
Looks like you want to look in Settings > Broadband > Routing

or possibly Settings > Broadband > DNS Resolution
[Google Chromecast] 14rt:
Hi, thanks for replying :)

Here's what I get at DNS Resolution xxx.postimg.org/image/4e5vkl619/

May I know what do i key in those fields?
[Google Chromecast] bhiga:
That's not going to work (it's essentially a router-based HOSTS file)

What does Settings > Broadband > Routing look like?
[Google Chromecast] 14rt:
looks like this xxx.postimg.org/image/3tarng0wl/
[Google Chromecast] bhiga:
There you go. Try adding static routes like shown earlier in this thread.

You should replace 192.168.1.69 with an unused local IP address from your subnet.
[Google Chromecast] 14rt:
NICE! THANKS MAN! HOPE IT WORKS!

btw, how do i know which / find an unused ip address from my subnet?

sorry for the 101questions. im a noob just trying to get my chromecast to work :(

and thanks for being so patient with me
[Google Chromecast] bhiga:
You want to select an IP that falls withing the DHCP scope in

Settings > LAN > DHCP

For example, if it's set to 192.168.1.0/255.255.255.0 (default) then you would choose a very high number like 192.168.1.127

If it has a set range, add one to the last digit of the Last DHCP address.
[Google Chromecast] 14rt:
ok this is what shows up

xxx.postimg.org/image/62pyxzm4p/

which is unused?

Thanks again for your time
[Google Chromecast] bhiga:
Hmm, looks like the first half of the range is for dynamic assignment (1-127), while the second half of the range (128-253) is for static assignment, and the router is at the top of the range (254).

Since I don't expect you to go poking around the settings any time soon, change what's currently set to 192.168.1.253 to 192.168.1.25

2

, then set the routes to point to 192.168.1.253. That should work.
[Google Chromecast] ccarothers:
Has anyone been able to find a solution to this? I am assuming that ESPN has their own DNS servers that are gumming up the works, but that is just a guess.
[Google Chromecast] bhiga:
If you are rooted with Eureka-ROM, have set up a static route for Google DNS, or have blocked/redirected Google DNS, Chromecast is still using Google DNS so the provides see it wherever your ISP is.

You need to block the Google DNS requests so Chromecast uses your router's DNS, or you need to make your router redirect its requests elsewhere.

It's described quite a bit earlier in the thread by DJames1
[Google Chromecast] Andree16:
I spent 5 hours last night trying to get this to work, with no success I tried every trick in this entire thread but I still can't Chromecast through my VPN. I would really appreciate if anyone of you could look at my setup below and maybe identify what I am doing wrong.

I live in Sweden and using a VPN from USA. My tools are a Netgear n150 router, an Android tablet and of course a Chromecast.

The router is configured with the DNS provided by my VPN, see attached picture. Through this I have no problem accessing the US Netflix and to my android tablet I can stream content not available in Sweden. With this setting I can cast for example Avenges which is available in both Sweden and USA to my chromecast without a problem, but if I try to cast for example The Fifth Element which isn't available in Sweden I get an error on my TV screen with "Right now we have a problem with playing this title...". I can of course play The Fifth Element on my Android pad, just not cast it.

The next step is to setup the static routes, see the two attached pictures. I've tried multiple combinations, both 8.8.8.8 / 255.255.255.255 and 8.8.8.0 / 255.255.255.0, same with the IP ending with 4.4. Metric needs to be a value between 2-15. I've attached pictures of the current setup and my LAN setup. With these static routes active I can't cast ANYTHING to my Chromecast, Swedish and US material stops loading at 25% and I get the same error message as above. When I try and ping 8.8.8.8 / 8.8.4.4 through CMD I get timed out requests. The static routes are aparently working but I can't get the Chromecast to switch over to my alternative DNS.

Anyone notice what I've missed? Thanks in advance
[Google Chromecast] DJames1:
To get the static route to work you may need to tick the "Private" box in your static route setup on the Netgear router. You'll notice on the static route setup screen shots for other routers that there's a setting usually called Interface that can be set to LAN or WAN. Your Netgear router doesn't have that, but if you read the help text on that page it says that the Private setting limits the static route to the LAN side, so it may be the equivalent. You want the router to intercept the specified address and redirect it on the LAN side, not on the WAN side.

But your description doesn't make sense in some ways. You say that you are using a VPN, presumably with a U.S. gateway to access U.S. Netflix. But if you are using a U.S. VPN, then you don't have to block Google DNS. That's only needed if you are using a DNS. Which is it? Did you mean that you are using a DNS-based unblocking service from a VPN company? I doubt your router model even supports a router-based VPN.

Also we've heard from other European Chromecast owners here that the firmware on the units officially sold in Europe recently does not use Google DNS, so blocking it is unnecessary. Where is your Chromecast from, and what firmware version does it have?
[Google Chromecast] pburgess:
The problem is that Chromecast is pointed at Google's own DNS servers at 8.8.8.8 and 8.8.4.4. You need to block these addresses on your router.
[Google Chromecast] DJames1:
The latest update of the Netflix app for Android released Aug. 31 breaks the current DNS geo-unblocking services. Revert to version 3.7.1 for the moment.

The Chromecast is not affected (at least for the moment) since it uses its own Netflix app, but of course you won't be able to select titles to cast from the Android app with this problem.
[Google Chromecast] irishpancake:
Hi, I have encountered this problem with the latest Netflix when using Smarty DNS to stream US Netflix in Ireland, and definitely no streaming to the device, or log-in allowed if logged out, because of this forced Google DNS in Netflx now, regardless of Static Routes by-passing 8.8.8.8 and 8.8.4.4.

I have Nexus 7 2013, not rooted, but my moto g is rooted, and I was wondering, as I don't currently have a DD-WRT router to set iptables, which apparently works to get round this latest problem.

Is it possible to solve the routing by use of AFWall+ on my rooted phone??

I am not very familiar, but apparently iptables can be set up on your device with this app??

Below are iptables commands for DD-wrt routers, which should work for any Smart DNS service:

iptables -I PREROUTING -t nat -p udp -d 8.8.4.4 --dport 53 -j DNAT --to-destination [ Smart DNS server ]
iptables -I PREROUTING -t nat -p udp -d 8.8.8.8 --dport 53 -j DNAT --to-destination [ Smart DNS server ]

UnoTelly tutorial here:

http://help.unotelly.com/support/solutions/articles/165577-

UnoTelly announcement regarding this:

http://help.unotelly.com/support/solutions/articles/199318-netflix-3-7-2-not-working-on
[Google Chromecast] Matthew Carson:
I just noticed that my Chromecast has updated to build 19048, and I am having issues with Netflix streaming using Unlocator to stream outside the US. I wish I had checked and known there was another root method for the Chromecast now! My Android app has updated to 3.7.2, but I am still able to select and start titles on the Chromecast. It's just slow. I am only able to get 160 kbps or so. It plays for a while and then starts buffering, and gets to 99% and stops and won't play anymore. I can set it through a VPN but I'd rather not since it hurts performance and quality significantly. Any way to go back on the Chromecast version now? (I am working on going back on the Android app)

EDIT:Seems I may have just gotten very slow internet bandwidth at an unfortunate time. I am only blocking the DNS request from my Chromecast, not my phone. Perhaps that is why it still will let me select videos to stream to the Chromecast, but it won't play them on the phone?
[Google Chromecast] DJames1:
It's working for me on build 19048.
[Google Chromecast] DonJuan89:
It's working for me via UnlocatorDNS on the latest Eureka build and latest Android app version. But it's very slow all of a sudden. I usually get to highest bit rate in under a minute and it stays but now I can't get over 1050kbps after 5 minutes of playing the example short test clip.
[Google Chromecast] Mrwazsx:
geoblocking on chromecast

I'm not sure if the chromecast is unaffected, i tried with 3.7.1 A version which does not have the new geoblocking on the android app; but still does use the new chromecast interface. Maybe this could show the new geoblocking checks are also taking place on the new chromecast app.
[Google Chromecast] irishpancake:
But there is no connection with the CC version and whatever Netflix version you are using.

There have been many reports regarding problems with the new CC firmware, not just with Netflix.

But, for me anyway, old Netflix (3.7.1) and all other CC-enabled apps stream perfectly, both on the local Android device and to CC, which has been updated to the latest f/w (19048), and work fine also with Smart DNS.
[Google Chromecast] Mrwazsx:
Wow, How are you set up though. Do you use routing tables or do you just block the Google DNS.
[Google Chromecast] PunchTheLion:
Well this is bad news. Is it the beggining of the end for watching Netflix outside of official countries? We can't stay on 3.7.1 forever.
[Google Chromecast] DJames1:
Why not? I have a 2011 Toshiba Blu-Ray player with an old Netflix client that works perfectly, and I am very careful to avoid updating the firmware. These days updates are 80% likely to be negative.
[Google Chromecast] DJames1:
Further details emerging: The Android Netflix app v.3.7.2 looks up one of the key Google domains using Google DNS only. If it can't contact Google DNS, then it fails. Apparently though it will still work with geo-blocking services when it does this lookup successfully via Google DNS, so this new behavior might just be a bug due to sloppy coding by Netflix. But unfortunately you need to have Google DNS blocked in your router for the Chromecast, so Catch-22. Might be ok with Google DNS redirected via iptables in the router, if someone wants to test that.
[Google Chromecast] irishpancake:
I re-direct the Google DNS requests in the Router, using Static Routes, which works quite well. for casting anything like US Netflix, [the old 3.7.1], Hulu, BBC iPlayer in Ireland.

This is a UnoTelly Smart DNS Tutorial on setting up Static Routes to re-direct Google DNS requests from CC.

Remember, you need a subscription with a Smart DNS provider, and you should change the values below to the appropriate provider.

http://help.unotelly.com/support/articles/171252-

You can also use iptables if you have a dd-wrt router. [Google is your friend.......sometimes!!!]
[Google Chromecast] DJames1:
The static route method redirects Google DNS lookups to a black hole, so that no response is returned. That's equivalent to blocking Google DNS. That won't work with the new Android Netflix app 3.7.2. The iptables method might work because the app will get a valid response to its domain lookup.
[Google Chromecast] Matthew Carson:
OK, this explains why my settings are working. I have a Watchguard router (a commercial router) with the DNS servers set to Unlocator. Then I have a firewall policy that blocks DNS requests to Google ONLY from the Chromecast's IP address. Requests from other clients are unaffected. I can watch Netflix with 3.7.2 fine on my Android clients, and it works on the Chromecast with 19048.

Performance is another issue though.... It still is taking 10 minutes to buffer 6 minutes worth of low-quality video now. According to the Watchguard it is only getting 140 kbps. I'm still trying to determine if it is a bandwidth issue or the new Chromecast version causing the problem, or perhaps a combination of the two. I'm leaning towards the latter - I get double the bandwidth (280 kbps) watching on Android. I also am only getting about 1 Mbps from my fiber provider. It almost seems like the CC app is limiting the bandwidth to a fraction of the available bandwidth or something.

-Matt
[Google Chromecast] irishpancake:
Yeah, I did say Netflix 3.7.1 ;)

I think iptables will work with the latest Netflix, CC and Smart DNS, but I have not tried, as I need to get a dd-wrt enabled router.

BTW, any thoughts on my query above regarding iptables on an Android device using AFWall+:
[Google Chromecast] scandalousk:
Agreed. I've got it setup this way and it doesn't work. Naturally the desktop works and using Netflix 3.7.1 on my tablet and phone works. But the cc won't play as long as I can't use ip tables. I found out the asus rt ac68u has a hidden command window in which I can enter the commands so I'll try that.

I'll report back later.
[Google Chromecast] merlin2380:
HI this solution with iptables -I PREROUTING commands worked great for me

I have one router from my ISP Network #1 I can not change the DNS or run this commands, since I also have a raspberry pi Network #2 with openelec.

I used to connect chromacast to Network #2 and it worked great, recently last week or so the cc will not work in this network anymore, no netflix 3.7.2 or zattoo 1.6.3 or wilma or youtube or google photos, but when I move the CC to network #1 all the regular youtube and photos work.

Any Ideas? Did the last CC update break something?
[Google Chromecast] cmstlist:
Just tested with NetProtect in Canada. My router at my parents' place does not support redirect but I have been using a static route to block Google DNS. Netflix app launches fine on my Nexus 5 and allows me to search for and open US content, but errors out if I play it to the phone. However if I use the cast icon first to point to the Chromecast, and then press play on the content, it does stream successfully to the TV. If I flip it back to "This Device" it errors out again.
[Google Chromecast] irishpancake:
You probably have the latest Android Netflix App, which has Google DNS hard coded in the App.

You should clear data and cache for that App, uninstall, download and install the 3.7.1 version, link available on the thread, ensure to check no automatic update.....

it should work then, both streaming on your device and to CC. Do ensure Netflix doesn't auto update, or you're back to square one.

Have you set up static routes for both Google public DNS, 8.8.8.8 and 8.8.4.4??

Hope this helps!!
[Google Chromecast] Mrwazsx:
Sorry just asking because i have the exact same static route setup and 3.7.1 doesn't work for me, thanks though!
[Google Chromecast] cmstlist:
At this stage I never stream directly onto an Android screen so the status quo is OK but I can certainly downgrade if/when needed. Yes I have used static routes to block both of Google's DNS services at the router level.

Also any recommendations for an affordable router that has all of the newer wi-fi revisions but still supports custom firmware?
[Google Chromecast] PunchTheLion:
3.7.1 worked to Chromecast a few days ago but now it doesn't. It immeadiatly fails connection, in the past it would fail Google DNS then use my unblock Us DNS. It was perfect...This is getting really annoying now.

I can play back on nexus 5 just fine though, it is not a change on my end.

.
[Google Chromecast] Srandista:
Do you have rooted Chromcast? It's just for my info, if this will affect me too, because I will rooting my Chromecast really soon.
[Google Chromecast] PunchTheLion:
No, I do not have a rooted Chromecast.

Before making your call though, hopefully other people might be able to confirm if this is the case. My Chromecast works perfectly and very fast with YouTube and every other source but the region restricted ones like Netflix.

My Chromecast firmware is: 19084
[Google Chromecast] irishpancake:
Hi, I'm on a train at the moment, but I'll check when I get home.

It, casting US Netflix to CC, worked for me, even with the latest Netflix.

Netflix latest Android version only fails to stream to an Android device, regardless of router settings, etc.

I'm in Ireland, and I use Smarty DNS, and static routes in my Router for Googles 8.8.8.8 and 8.8.4.4.... to by-pass the CC's hard-coded DNS settings.

Can you confirm you have that setup of course with your particular Smart DNS provider Unblock US.

I only ask because there seems to be growing confusion regarding CC, it's latest f/m, and the additional problem caused by the latest Netflix App. in the case of users of Smart DNS services.

I think we need to separate out just who is experiencing what problem.

I hope you agree.
[Google Chromecast] PunchTheLion:
No problem.

I use Unblock-US, accessing netflix on the pc is fine.

For Chromecast, I have a static routing table setup on my router.

8.8.0.0 (google)

255.255.0.0 (subnet)

192.168.178.254 (router)

This has been working since I set it up in January. So for about 9 months with that routing table setup and unblock us I could get netflix from Android to Chromecast. Never an issue.

It seems they are cracking down because the latest netflix update from September is broken, so I reverted to using Netflix Android 3.7.1.

3.7.1 used to work on chromecast as of last week....but now without changing settings I get an error message when casting "we're having trouble playing this title right now"....It is not an accurate message because ALL titles have been like this for the last 24 hours.

It seems to me with the latest chromecast, it fails - I tried powering on and off, rebooting etc but for the last 24 hours it seems to be blocked after working for so many months. :crying:

I hope I am the only one. But as I say, without changing any setting after 9 months when I set it up in Jan, it is now blocked.
[Google Chromecast] lswai:
You are not the only one. I am having exact same problem. Only recently failed to cast netflix to CC. CC is running on latest 19084 firmware. Playing on my phone is fine. No change of configuration from my end.
[Google Chromecast] DJames1:
I just tried it and things still seems to be working fine for me, but the Netflix app on the Chromecast does look different, so it probably is a new version of the app.

With my Android tablet and my Chromecast both set to use a U.S. DNS, I can select and play a U.S.-only title on the tablet using Netflix 3.7.1, and then cast it to the Chromecast. Repeated tests will be needed to determine what's new about the new Chromecast app, and whether our results in any one test are just a fluke one way or the other. If Netflix is deliberately rolling out new versions of their app hard-coded to use Google DNS, I guess we'll find out soon.