watsonash: my suspicion is that Netflix will simply move to verify the location by forcing lookups to Google DNS and possibly OpenDNS servers.
Historically this was the case with the chromecast and the solution on this was previously to block the DNS to both google DNS and OpenDNS servers, the applicaiton would then fallback to whatever the DNS was set to on the device itself.
I have a public DNS group defined as this;
group {
address-group PublicDNS {
address 8.8.8.8
address 8.8.4.4
address 209.244.0.3
address 209.244.0.4
address 208.67.222.222
address 208.67.222.220
}
<snip>
Just for your reference I have published a few shell scripts and an unblocking tutorial for the Ubiquiti Edgerouter Lite (as well as a few other routers) here: http://www.geekzone.co.nz/forums.asp?forumid=151&topicid=171173
I am using host file redirection + DNS redirection (to my ER's dnsmasq server) and have a few dirty shell scripts to do the dirty with grabbing the latest dnsmasq file from dns4me. It also wouldn't surprise me if Netflix sign up accounts with these unblocking providers, does some research on where the traffic comes from and outright block them or block the IP ranges they use on a regular basis.
I've got many private servers in the US so could always do a L7 filter myself to pass Netflix through one of my VPS boxen. Like you say, we're smart and will get around it regardless. I always see people having problems when blocking Google DNS (instead of doing a redirect) so this to a degree is already happening. The correct and only solution to get around this is to use + do a DNS redirection to make whatever app, computer, web browser etc you use think it is in-fact using the right IP to contact the service via means of DNS redirection.
For example doing "dig @8.8.8.8 a netflix.com" generates the same IP as a dig on my ISP's DNS or routers DNS server or even a site that doesn't have a public DNS resolver, my devices know no better and have no way of verification either.



