Plusnet DNS Issues

[#1]

Has anyone else been having an issue with Plusnet DNS not resolving some sites? Specifically, the site in question that I've been having problems with is www.netflix.com.
When I do an nslookup using the Plusnet DNS servers that my router (Technicolor TG582n) is using:

$ nslookup www.netflix.com 212.159.6.9
Server:		212.159.6.9
Address:	212.159.6.9#53
** server can't find www.netflix.com: NXDOMAIN

$ nslookup www.netflix.com 212.159.6.10
Server:		212.159.6.10
Address:	212.159.6.10#53
** server can't find www.netflix.com: NXDOMAIN

Though if I use Google DNS:

$ nslookup www.netflix.com 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53
Non-authoritative answer:
www.netflix.com	canonical name = dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com.
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.186.229
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.102
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.188.229
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.184.243
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.50
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.187.142

I can access the site from outside my Plusnet broadband (3G, work, etc), and various tools online are reporting that www.netflix.com is resolving fine for them too, so I don't think it's an issue with Netflix. Oddly enough, it's only www.netflix.com that isn't resolving, the domain itself and various subdomains used by them are working fine (netflix.com, signup.netflix.com, movies.netflix.com, etc).
It's been like this for more than a few days now, although I haven't noticed it on any other sites (so far). Can anyone else confirm whether or not this is happening to them too? Is it just me?!

[#2]

Not good... though it's working alright from my home connection (PN fibre)?

orbrey@LoudmouthHarry:~$ nslookup www.netflix.com 212.159.6.9
Server:         212.159.6.9
Address:        212.159.6.9#53
Non-authoritative answer:
www.netflix.com canonical name = dualstack.wwwservice--frontend-373494752.eu-wes                                                                             t-1.elb.amazonaws.com.
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.102
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.187.142
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.50
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.184.243
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.186.229
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.188.229
orbrey@LoudmouthHarry:~$ nslookup www.netflix.com 212.159.6.10
Server:         212.159.6.10
Address:        212.159.6.10#53
Non-authoritative answer:
www.netflix.com canonical name = dualstack.wwwservice--frontend-373494752.eu-wes                                                                             t-1.elb.amazonaws.com.
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.184.243
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.186.229
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.50
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.187.142
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.188.229
Name:   dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.102

[#3]

Matt (as per his post) can get this to resolve fine, however I can't and neither can Bob.
Taking a look now to see what's going on.

[#4]

Although strangely netflix.com (without the www) is working fine for all of us.
Can you raise a ticket with the nslookups on it and we'll get it looked into from here.

[#5]

Quote from: Chris

Although strangely netflix.com (without the www) is working fine for all of us.

Indeed! As I mentioned in my original post, the domain itself and the various subdomains (signup.netflix.com, movies.netflix.com) are all working fine, it only seems to be affecting www.netflix.com (that I know of).

Quote from: Chris

Can you raise a ticket with the nslookups on it and we'll get it looked into from here.

Done, question #76246172.

[#6]

Great, passing that over to the networks team to take a look.

[#7]

I have this exact same issue, it works on my mobile over 3G but not when on WIFI with my laptop or my iPhone.
Interestingly I am able to stream through the PS3 or Xbox 360 just fine

[#8]

We've flagged this up internally, streaming should be fine.
It seems simply going to www.netflix.com instead of netflix.com is where the issue is.

[#9]

If you try to browse to http://netflix.com it just redirects you to www.netflix.com which fails to resolve.
As far as I can see, plusnet's DNS servers are returning SERVFAIL not the NXDOMAIN quoted in the first post.
Edit:
I have come to the barely believable conclusion that Plusnet's DNS servers cannot resolve any hostnames containing 37349
dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com - timeout
dualstack.wwwservice--frontend-373484752.eu-west-1.elb.amazonaws.com - returns NXDOMAIN
www.37349.plus.net - times out (should be NXDOMAIN, probably)
www.37349.example.com - times out
as37349.peeringdb.com - time out (should resolve to 205.166.250.194)
Perhaps the problem is due to some security measure badly implemented: http://dnsamplificationattacks.blogspot.co.uk/2013/10/domain-37349info.html
A bit like last time when some security change blocked lookups for isc.org and ripe.net (I haven't found the thread where Plusnet eventually admitted it was their fault).

[#10]

I've passed this info to our network guys who'll be taking a closer look at this today.

[#11]

It seems the firewall rules may have been too aggressive which caused this, they have now been tweaked and you should now be able to resolve to www.Netflix.com.

Quote from: ejs

If you try to browse to http://netflix.com it just redirects you to www.netflix.com which fails to resolve. As far as I can see, plusnet's DNS servers are returning SERVFAIL not the NXDOMAIN quoted in the first post. Edit: I have come to the barely believable conclusion that Plusnet's DNS servers cannot resolve any hostnames containing 37349 dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com - timeout dualstack.wwwservice--frontend-373484752.eu-west-1.elb.amazonaws.com - returns NXDOMAIN www.37349.plus.net - times out (should be NXDOMAIN, probably) www.37349.example.com - times out as37349.peeringdb.com - time out (should resolve to 205.166.250.194)

You should now be able to resolve to these too.

[#12]

Looks like it's all working again at my end:

$ nslookup www.netflix.com 212.159.6.9
Server:		212.159.6.9
Address:	212.159.6.9#53
Non-authoritative answer:
www.netflix.com	canonical name = dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com.
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.50
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.184.243
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.187.142
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.188.229
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.186.229
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.102

$ nslookup www.netflix.com 212.159.6.10
Server:		212.159.6.10
Address:	212.159.6.10#53
Non-authoritative answer:
www.netflix.com	canonical name = dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com.
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.184.243
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.102
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.185.50
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.188.229
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.187.142
Name:	dualstack.wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Address: 176.34.186.229

Cheers for the help.