I do not like the advice that the README gives to disable dnsmasq's DNS resolver for a few reasons. The first is the dnsmasq is able to enforce dnsmasq and for those using that, disabling it would be a regression in security. The second is that it is unnecessary because dnsmasq is able to forward DNS queries to netflix-no-ipv6-dns-proxy based on domain name. If netflix-no-ipv6-dns-proxy is running on 10.1.1.100, then this would be all that is needed to achieve forwarding for the TLDs and their subdomains:
server=/netflix.com/10.1.1.100
server=/nflximg.net/10.1.1.100
server=/nflxext.com/10.1.1.100
server=/nflxvideo.net/10.1.1.100
The third reason is that people using dnsmasq and the HE tunnel broker do not need to use netflix-no-ipv6-dns-proxy to unblock netflix. It turns out that a single line in dnsmasq is sufficient to enable netflix to work on my Apple TV and iPhone:
host-record=ios.nccp.netflix.com,0100::0
I confirmed that not only did things work, but the video traffic was going over IPv4 by observing that the traffic on my HE tunnel was 0 while verifying that netflix would stream.
dnsmasq does not support wildcarding for host-record, so I suspect that other platforms will need additional entries. I assembled a list after reading this article:
http://blog.chrislahaye.com/smart-dns-proxy-to-unblock-netflix-content/
host-record=android.nccp.netflix.com,0100::0
host-record=cbp.nccp.netflix.com,0100::0
host-record=ios.nccp.netflix.com,0100::0
host-record=playstation.nccp.netflix.com,0100::0
host-record=nintendo.nccp.netflix.com,0100::0
host-record=nrdp.nccp.netflix.com,0100::0
host-record=xbox.nccp.netflix.com,0100::0
It should not be hard to find out what the correct subdomain is for a given device if you use dnsmasq's log-queries
option, force the device to use the dnsmasq server and grep the dnsmasq.log file for the nccp.netflix.com subdomain.
Anyway, I do not mean to dismiss the excellent work that @cdhowie has done here, but I think that advice for dnsmasq users should be different.