On 14/08/14 09:44, Chris Barnes wrote:
Hi Christopher,
So that works perfectly for Netflix because any part of that service that
cares about Geolocation is in the Netflix domain.
Hulu on the other hand, has services that are outside of the Hulu domain
that take issue with my location -
Awesome thanks for the tip with dnsmasq.
--
Kind Regards,
Christopher Barnes
e. chris.p.bar...@gmail.com
On 14/08/2014 6:51 PM, Michael Chesterton che...@chesterton.id.au wrote:
On 14/08/14 09:44, Chris Barnes wrote:
Hi Christopher,
So that works perfectly for Netflix because any part
For a individual target hosts, i.e. not a whole domain, if you're the one
doing the lookup, you could also use /etc/hosts.
On Thu, Aug 14, 2014 at 9:03 PM, Chris Barnes chris.p.bar...@gmail.com
wrote:
Awesome thanks for the tip with dnsmasq.
--
Kind Regards,
Christopher Barnes
e.
Yep, except Apple TV, Roku, and other Netflix Hulu enabled devices don't
usually have a Hosts file you can change. So DNS or Dnsmasq is really the
only option for this scenario.
--
Kind Regards,
Christopher Barnes
e. chris.p.bar...@gmail.com
On 14/08/2014 10:34 PM, Christopher Vance
Hey people,
Got a bit of a tricky question, well it seems tricky to me.
I want to use bind to resolve a single host address for a very large zone I
don't own.
The background is that I'm trying to circumvent georestrictions on TV
streaming site.
I've determined that the host on the internet
From what you've written, it sounds to me as if the issue is where the
Akamai host thinks you are. If so, then DNS and bind are totally uninvolved.
Geo-location is normally done using IP addresses. You can change your IP
address by using a proxy, in which case Akamai will understand you to be
Hi Christopher,
You're right that this Akamai hostdoesnt like my location, and you're right
that Bind and DNS *alone* arent going to resolve that.
But the bigger part of my fix that I havent revealed is that I change the
ip address of hosts to point to loop-back addresses on a server in the US,
So you have your own server in the US. I would suggest Netflix is seeing
that server's public IP address in the US as the origin of requests, which
means you get Netflix's approval to download. I don't think the proxy vs
port forwarding thing makes a difference.
The apparent difference between
Correct, The Netflix servers are seeing my requests come from my server in
the US. Thats the whole point of having the server in the U.S. And it works
very well for getting access to Netflix.
Netflix and Hulu both use Akamai, although Netflix appears to use other
CDNs as well. The difference is
Ok turns out the problem was just a typo I had overlooked NUMEROUS times. I
had been watching /var/log/bind.log which hadnt reported any problems. It
wasnt until I took at look at /var/log/syslog that I saw the problem.
localhost named[19832]: zone a248.e.akamai.net/IN: loading from master
file
10 matches
Mail list logo
