yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] gonzule:
Custom DNS server and HOLA!

Would it be possible to run my own DNS server, and use that server with HOLA! ?

I can run netflix on android and on my pc with HOLA! without any problems, so i was thinking maybe it could be possible to run a DNS server on an old android phone i have laying around, and then installing HOLA! on the same phone and linking both apps together. Would that work or not?

I have it configured with servers ultimate, but my router is really crappy and I cant configure routing tables properly.
[Google Chromecast] DJames1:
Use Hola? That doesn't seem like a good idea for a couple of reasons:

1. It would be complicated. Hola keeps their gateway addresses secret. You'd probably have to log Hola's internet activity and pick out the gateway addresses, then do some custom coding to use them in your own DNS server. They change frequently, so you'd have to do a lot of ongoing work. It might not work at all if Hola uses other security measures to verify that the access is only from the legit Hola app.

2. Hola logs your internet history for commercial purposes. They aren't a charity, they're selling your information.

There are free DNS services that work just fine and don't have those problems, so it seems like a lot of work for no good reason.
[Google Chromecast] nicolaspy:
SOLUTION: I emailed Unlocator and they got back to me the next day (Nov. 5) and just said to try it again, which did work for me. They must have changed something

on their end to fix it. I'm going to try and fish out of them what they did, but I was super impressed that they responded so quickly with a solution.

Thanks zoot1 for replying. I am going to add this forwarding rule in the firewall setup in addition as a preventative measure. I don't see how it could hurt things. That sound pretty awesomely sneaky, for those who want to delve in further, there is a post here: http://xdaforums.com/showthread.php?p=49365627#post49365627

Hey DJames1,

Android - BBC iPlayer 4.3.1.2

I know there is a version number on the Chromecast when it says "Ready to Cast" but I am not at home to check it. It's been a couple weeks since the fix so it may have updated since I encountered the issue.

Thank you to both of you for your contributions to this thread and the general workaround
[Google Chromecast] DJames1:
Another workaround is to use the Plex BBC channel and cast it to the Chromecast. That's currently working.
[Google Chromecast] nicolaspy:
Thanks! I'll have to keep that one in mind as backup.
[Google Chromecast] smartpr1v4t3:
Hey Guys,

i found another solution for my netflix apps.

I havent a chromecast but all my other devices works with this method.

The benefit of this is that only the specified IPs using the alternative DNS Server.

I am still searching for a solution that i can foward only the DNS requests to 8.8.8.8 and 8.8.4.4 but i cant find a solution for DD WRT

Commands Firewall:

iptables -t nat -A PREROUTING -i br0 -s SOURCE(CHROMECAST)/32 -p udp --dport 53 -j DNAT --to (DESTINATION-DNS)

iptables -t nat -A PREROUTING -i br0 -s SOURCE(CHROMECAST)/32 -p tcp --dport 53 -j DNAT --to (DESTINATION-DNS)

example SmartDNSProxy

iptables -t nat -A PREROUTING -i br0 -s 192.168.1.55/32 -p tcp --dport 53 -j DNAT --to 23.21.43.50

iptables -t nat -A PREROUTING -i br0 -s 192.168.1.55/32 -p udp --dport 53 -j DNAT --to 23.21.43.50
[Google Chromecast] snapilica2003:
Hello,

I've been trying to setup iptables to use the netflix app on my tablet. For chromecasting it's pretty straight forward, my issue is that i can no longer play videos on the tablet. Here is my current setup:

iptables -t nat -A PREROUTING --destination 8.8.8.8 -j DNAT --to 149.154.157.61
iptables -t nat -A PREROUTING --destination 8.8.4.4 -j DNAT --to 149.154.157.61
iptables -t nat -A POSTROUTING -j MASQUERADE

I've been trying to find out exactly what the masquerade line does, and how it affects other packets sent through the network. With the current setup I can barely open a movie on the tablet (i get error 12001) but if i keep trying it eventually works.
[Google Chromecast] zoot1:
Try the method posted above your post where you only forward the traffic from the chromecast:

iptables -t nat -A PREROUTING -i br0 -s SOURCE(CHROMECAST)/32 -p udp --dport 53 -j DNAT --to (DESTINATION-DNS)
iptables -t nat -A PREROUTING -i br0 -s SOURCE(CHROMECAST)/32 -p tcp --dport 53 -j DNAT --to (DESTINATION-DNS)
[Google Chromecast] snapilica2003:
There's no need as watching netflix on chromecast works perfectly with any method. My only issue is with watching netflix with the latest app right on the tablet, without chromecasting.
[Google Chromecast] mondohow:
Unotelly? If it's an Android tablet then check out their support database for a work-around. I can't post outside links yet sorry.

Basically, the updated version of Netflix (=> 3.7.2) seems to be forcing the use of Google DNS.
[Google Chromecast] snapilica2003:
Exactly and the workaround posted on their site and also here is to use the redirects posted many times around here. Problem is, it doesn't seem to be working perfectly. For whatever reason, when I hit play i get a loading sign and more often the 12001 error... but if i keep pushing and hit play many times it will eventually load the content.

This makes me believe that the DNS redirect doesn't work properly... and there are some timeouts somewhere that allows content to be played once in a while. I think we're missing something in those iptables and thus my initial post in asking further details on the MASQUERADE line.
[Google Chromecast] DJames1:
Use version 3.7.1 of the Netflix app. It works fine.

Some of the DNS providers have researched the latest problem with the erratic behavior of Netflix, and they say that it is because Netflix is rotating between different servers that appear to react differently. That's why it fails a few times in a row and then suddenly succeeds. So probably not due to the iptables at our end, or a random timing glitch.
[Google Chromecast] snapilica2003:
Version 3.7.1 works fine-ish. It has a bug displaying subtitles correctly. If the subtitle has 2 lines it shrinks the first line and cuts it off. It's not game breaking, yet it does get annoying.

Plus what can stop Netflix to decide to kill access of versions lower than 3.7.2
[Google Chromecast] mondohow:
How can I tell if this needs to be added or if my router automatically ads it?

iptables -t nat -A POSTROUTING -j MASQUERADE

I'm using an RT-AC66 running Tomato Shibby latest.

Thanks...
[Google Chromecast] zoot1:
My router is working without this line .

I am using dd-wrt
[Google Chromecast] Rylo:
Any idea on how to get this working on a fritzbox 7360 ? Or could you tell me what 'option' your router needs to have. Thanks!
[Google Chromecast] fishyrelic:
I haven't used the fritzbox 7360 but it appears to be a generic consumer grade router and will most likely not have any traffic redirecting/manipulating capabilities. You would either need an advanced router like a cisco or a firewall such as a dell sonicwall.
[Google Chromecast] Rylo:
It seems your correct. Thanks for your quick reply.

Or i need to build my own firmware and add one of these packages >> http://freetz.org/wiki/packages
[Google Chromecast] DJames1:
Looks like Netflix has broken geo-unblocking in the latest version of the Android and iOS apps (Android app now at version 3.8.3). And the casting Chromecast won't work any more with older versions of the apps, so using an older version to get around the problem won't work. Thanks a lot Netflix!

Not sure yet if this affects only the static-route-Google-DNS-to-nowhere method, or it also affects the Google-DNS-rediction-using-iptables method. Maybe someone can report about the latter? It may be a while before I get time to check.
[Google Chromecast] gpkgpk:
Thought it was just me, grr.

With the static-route-Google-DNS-to-nowhere method , Netflix+Chromecast is giving me the error "Sorry that title is not available to watch instantly. Please try another title" error message.

Anyone have any ideas? Tried the iptables tricks too, no luck.

gpk
[Google Chromecast] DJames1:
Strangely you can still browse and cast out-of-region Netflix content from the latest version of the Netflix Android app (3.8.3) - you just can't play it on the Android device itself. Set it to play on the Chromecast before you attempt to play anything. Also note that after updating the Netflix Android app, you must log in for the first time in your home region.

You can still play out-of-region content using the Netflix Android app version 3.7.1, but now the Netflix Chromecast app refuses to play content cast from that version and insists that you update it.

So you can't have both local and Chromecast capability at the same time.
[Google Chromecast] ykphuah:
Need to wait for the unlocator guys to outsmart the netflix guys!

I have given up on using android to cast to chromecast. Tried netflix from laptop chrome casting to chromecast, worked perfectly fine. Does the netflix webapp works on the chrome on android?
[Google Chromecast] skivnit:
all i'm getting is the "oops i shouldn't be here error" its playing fine on my Android phone and ipad, i guess all i can do now is use chrome to cast my screen from the laptop :(
[Google Chromecast] DJames1:
As far as I know, the current situation is:

- Netflix Android app up to version 3.7.1 works with DNS redirection and can play all content on the Android device. But as of a month or so ago, the Chromecast Netflix app will no longer accept casting from version 3.7.1 - it displays a message saying that you must update your Android app.

- The current version of the Netflix Android app (up to version 3.8.3 at least) only works partly with DNS redirection. It will allow you to browse all content, and it will cast it successfully to the Chromecast, but it will not play that content locally on the Android device itself.

This applies if you are blocking Google DNS. I don't know what happens if you are redirecting Google DNS with iptables commands - I have heard that it works erratically.

The situation is the same with all the DNS redirection services I have tested, and as far as I have read it is the same with all of them. Apparently the Netflix app is now doing something new with Google DNS, and for the Android app nobody has quite solved it. Netflix is continuing to update their app, so the situation might change at any time, for better or worse.

(Note that after updating the Netflix Android app, you must initially start it and log in from your home region.)
[Google Chromecast] skivnit:
Brain freeze when redirecting Google to another dns
[Google Chromecast] DJames1:
I just tested the Android Netflix app version 3.8.3 using my DD-WRT router with Google DNS redirected via iptables commands instead of using my regular router with Google blocked. It successfully plays out-of-region content locally on the Android device.

The format I am using is:

iptables -t nat -A PREROUTING -i br0 -p tcp --dport 53 -j DNAT --to <redirected dns ip address>

iptables -t nat -A PREROUTING -i br0 -p udp --dport 53 -j DNAT --to <redirected dns ip address>

I can't say whether it works reliably from this quick test, but it worked first time for me.
[Google Chromecast] ykphuah:
I too am using the forward everything to port 53 to unlocator, and netflix is playing fine on android, and mac. Chromecast won't even show the netflix app now. Tried with both old and new netflix app on android.

zzz, chromecast have just gotten less useful.
[Google Chromecast] ykphuah:
Realize one thing, the way to cast from android, is to let the show play on android first, and then only cast.

If I choose the cast first, then only play, it will never play.

I think someone mentioned this in previous posts but I didn't paid much attention to it previously.
[Google Chromecast] DJames1:
I found the opposite when using the Netflix app version 3.8.3 with Google DNS blocked by a static route in the router. It wouldn't work if I tried to play on Android first, but if I set it to cast to Chromecast first and then played the selection, it would cast successfully.
[Google Chromecast] ykphuah:
I am on the latest Netflix, its 3.9.1 according to Apps Info, if I just use the Blocked by Static Route method, netflix won't play at all on the android.
[Google Chromecast] DJames1:
I can't get Netflix to cast to the Chromecast at all any more when using an alternate DNS, whether blocking Google DNS or redirecting it.

Netflix appears to be making rapid changes with the specific intent of more effectively blocking access to out-of-region content. The Netflix Roku app has been affected too. It's always disappointing to see a company putting their development efforts into screwing with their customers on behalf of third parties rather than enhancing their product. Beginning of the end for Netflix I think, as it has beem for other companies when they lose sight of who the customer is.

What continues to work just fine are the old Netflix apps on my Blu-Ray players, so I guess I'll go back to using them.
[Google Chromecast] DJames1:
Surprisingly I was able to get both Android playback and Chromecast casting to work again using iptables commands after updating the Netflix Android app to version 3.9.1.

I'm suspicious that it wasn't the app version update that made the difference though. Too many variables to test here, especially since I'm not sure if trying to access Netflix from different regions on the same device in rapid succession would introduce another variable.

What I'm thinking might have happened is that I checked that Netflix region switching via iptables commands still worked with the Netflix Roku app, and then I paused it on the Roku and tested Android and Chromecast casting with the same media selection. Maybe it worked because Netflix was already streaming that selection to me on the Roku, and I just paused it on one device and then started streaming it again on another device on the same account. If that was the case, it occurs to me that one could possibly start a title streaming in PC web browser, pause it, then switch to Android and cast it. Maybe someone else having problems with the Android app currently could test that?
[Google Chromecast] ykphuah:
Yeah, the night after I posted the above, my playing on android stopped working again. :(:(:(

The most consistent way is to play it on my mac and cast it from there.
[Google Chromecast] Nexus_2761:
dumb question as I am new to dd-wrt, I have logged in via telnet and added my rules (getflix IP's)

iptables -t nat -A PREROUTING -i br0 -p tcp --dport 53 -j DNAT --to 54.252.183.4

iptables -t nat -A PREROUTING -i br0 -p udp --dport 53 -j DNAT --to 54.252.183.5

How do I get dd-wrt to save these now? :)
[Google Chromecast] ykphuah:
Surprise, youtube stopped casting for me, so I went back to try back all the different options.

Now I just need the static route trick on 8.8.8.8 (as per unlocator's instructions), and everything worked fine.

Youtube, Netflix on Android, Netflix on Android cast to Chromecast....
[Google Chromecast] DJames1:
Some interesting comments by Netflix chief product officer Neil Hunt at CES this week, in response to stories that Netflix is cracking down on the use of VPNs and DNS services to get around regional content restrictions.

"The claims that we have changed our policy on VPN are false"

"Speaking at this year's Consumer Electronics Show (CES) in Las Vegas, he said: "People who are using a VPN to access our service from outside of the area will find that it still works exactly as it has always done." He was speaking in response to widespread claims that the popular media streaming firm had begun a crackdown on customers who used VPNs at the behest of studios unhappy at their licensing arrangements being ignored. They followed complaints by Netflix users on Reddit that their normal VPN setups were no longer working."

"Mr Hunt said that the company had added a "failsafe" on its Android app to help users whose DNS provider was unreliable. "It's intended to make the application more robust when your own DNS provider is failing" "

""Netflix does block some VPN providers who are named in contracts it signs with movie and television studios""

Netflix officially verified Mr. Hunt's comments.

http://www.bbc.com/news/technology-30726631

http://www.cnet.com/news/netflix-calls-vpn-lock-out-claims-false-teases-possible-new-look-interface/
[Google Chromecast] phaserk1:
I have a Asus RT-N56U router (so no ip tables support) and with the static routes method it worked on my Chromecast, but not on the Android app.

But I found a working solution for this situation:

1. Find the Chromecast MAC and assign an IP in "LAN - DHCP Server"

2. Go to "Firewall - Network Services Filter" and block Google DNS requests from Chromecast IP

3. Don't forget to disable static routes if you used it before

Now it works fine on both Crhomecast and my tablets...
[Google Chromecast] DJames1:
So that amounts to saying that the Android Netflix app works if Google DNS is

not

blocked for the Android device?

Nope, I just tested that and it doesn't work that way for me. Looks like another one of those unknown variables giving inconsistent results.
[Google Chromecast] phaserk1:
Like I said, if Google DNS is blocked, the Android app takes very long time to load and eventually gives an error.

Reboot the device and make sure your DNS unblocking service is working (has the updated IP) and try again. Also try to ping 8.8.8.8 from the device too make sure it's not still blocked.
[Google Chromecast] skivnit:
Iptables stopped working but your method fixed it. Thanks

Sent from my SM-G900F
[Google Chromecast] DJames1:
Did all that, plus rebooted the router, killed the Netflix app, cleared app cache and restarted it. No good, doesn't work for me. My app version is 3.9.1. (To be clear, I don't have an Asus router, I'm testing the idea that the Android Netflix app will use the DNS unblocking service successfully if Google DNS is not blocked).

I tried again with a couple of different DNS services, and found that it works for some of them and not for others. For example USaccess.ca doesn't work, Unlocator does.
[Google Chromecast] farooknaji:
Static Route did work, now doesn't

I had a static route set to unblock-us which was working perfectly casting from my Android phone or in Chrome on my Windows PC. But today this stopped working. I am still able to play the video on my Android phone (or on the PC) but I get the usual 'We're having trouble...' message when I try to cast it to the Chromecast.

I can't figure out why this would have suddenly stopped working. Below is a picture of my router settings. Any hints or help would be great! No IPTABLE options on this router.
[Google Chromecast] Pietplezier:
I don't have any experience with chromecast + Iptables. Rooted chromecast here, no need to struggle with Iptables.

But this is the way i change the DNS server on my phone.

Nexus 5 with Android 5.0 Lollipop.

Netflix app version: 3.9.1. Current version from Playstore.

Override DNS to quick change to another DNS Address. (ROOTed phone required!)

Dnsflix.com as US dns server

This setup will play 100% Netflix on my phone, and successfully cast's to my Chromecast.
[Google Chromecast] DJames1:
Like maybe this thread, many previous posts? :)
[Google Chromecast] pustefix:
My setup (static route) used to work until recently I upgraded the Netflix version on my tablet. After that it will only work for Chromecast but not my Android tablet. Your method of using network services filter work for both my Chromecast and tablet (using AC68W). Thanks.
[Google Chromecast] andypen:
So happy to have found this post. After my Chromecast received the new 22062 firmware update I also lost all ability to cast Netflix to it. I'm running DDWRT on my router so had to add the following firewall commands under the admin tab:

iptables -I FORWARD -s 192.168.11.21 -d 8.8.8.8 -j DROP
iptables -I FORWARD -s 192.168.11.21 -d 8.8.4.4 -j DROP
iptables -I FORWARD -s 192.168.11.21 -d 209.244.0.3 -j DROP
iptables -I FORWARD -s 192.168.11.21 -d 209.244.0.4 -j DROP
iptables -I FORWARD -s 192.168.11.21 -d 208.67.222.222 -j DROP
iptables -I FORWARD -s 192.168.11.21 -d 208.67.220.220 -j DROP
[Google Chromecast] coloxim:
But if I'm not rooted, can I use IP table+ usaDNS server, without use a pay service like unlocator?

Thanks..
[Google Chromecast] Pietplezier:
No root (smartphone!) needed for My DNS changer.

Tested and it's working okey.

Don't have experience with iptables coz i have a rooted chromecast.
[Google Chromecast] coloxim:
Sorry... I was talking about chromecast... There are free dns and use iptables?or i have to pay the dns Service?

Thanks guys...
[Google Chromecast] clmbtti:
Cannot really tell about the iptables, but I am afraid you won’t find any reliable smart DNS service out there for free.
[Google Chromecast] DJames1:
https://tvunblock.com
[Google Chromecast] clmbtti:
Many cheers for the tip! Definitely worth checking out.
[Google Chromecast] Limeybastard:
Not sure if it helps but I got my Cisco Linksys EA4500 working to mirror BBC iPlayer on my chromecast. If anyone needs to know ask me.
[Google Chromecast] leocratus:
Well I didn't go through the whole thread, but I want to add this post for any openwrt users out there.

If you are using free service such dnsflix, there is a chance that you will have to change your US dns ip address. In that situation you will need to prepare configuration as simple as possible to change only dns server for specific host (netflix in this case). Please add lines in files listed below.

/etc/firewall.user

iptables -t nat -A PREROUTING -d 8.8.8.8 -j DNAT --to-destination x.x.x.x
iptables -t nat -A PREROUTING -d 8.8.4.4 -j DNAT --to-destination x.x.x.x

/etc/config/dhcp

config dnsmasq
list server '/netflix.com/y.y.y.y'

x.x.x.x - enter your gateway (not US dns ip!). That redirects you on your ISP dns servers and you don't have to change it every time dns service will change.

y.y.y.y - enter your US dns ip. This is the only place to change US dns in your configuration.

Above Configuration works perfectly for all devices in your LAN.
[Google Chromecast] mltan_bdo:
Anybody help how to root chromecast?
[Google Chromecast] bhiga:
Please check the Index thread. If you already have one, it is probably not rootable anymore unless you haven't set it up yet.
[Google Chromecast] :
Can anyone help me???!! Totally lost!! I just want to use my chromecast but it doesn't work. Did some research turns out that it doesn't work in my region because google blocked our IPs so I'll have to use a VPN. But my modem doesn't support vpns. Till about a week ago I shared my computer's VPN connection and it worked! But now that vpns are blocked it doesn't. So right now VPN doesn't work in my country on PC but on android, it does surprisingly. Anyways, I was wondering if Chromecast update could be done in another way... I mean I enabled the colored search results of google which is available only in the U.S. via Market Unlocker, VPN and gps location faker but this, is a pickle...

Any Suggestions?
[Google Chromecast] DJames1:
You'll have to be much clearer if you want meaningful help.

What exactly isn't working? What are you attempting to cast to the Chromecast and from what device?

You say Google blocked your IPs? That doesn't seem likely. Do you mean that you are encountering geo-blocking of all IPs from your country with certain apps? Which apps in particular?

You say that you were sharing your computer's VPN connection? How? By bridging a secondary wireless network on one computer? But now it stopped working because "vpns are blocked"? What makes you think that your VPN is being blocked? Did you try a different VPN gateway, or a different VPN? Have you tried using a DNS unblocking service instead?

What is your problem with Chromecast updates? Do you mean that Google is not providing Chromecast updates for your country? They didn't block any countries in the past, but it's always possible they might have started now that the Chromecast is available with different firmware versions in different countries. Did you try with a VPN?
[Google Chromecast] YOU THINK KNOW ME:
I can't believe it works in my home country Oman. Lolll

Thanks bro.