4 ms·
Also unavailable from Android devices…
by wtbob 12y ago
Also unavailable from Android devices…
- danyork 12y agoWhich would make sense because they may be set to use Google's Public DNS Servers (8.8.8.8 and 8.8.4.4 and the IPv6 equivalents). Google Public DNS has been performing full DNSSEC validation since May 2013: http://www.internetsociety.org/deploy360/blog/2013/05/confirmed-googles-public-dns-now-performs-dnssec-validation-for-all-queries-by-default/ http://www.internetsociety.org/deploy360/blog/2013/05/confir...
- yuhong 12y agoYea, it is fortunate that people on Twitter quickly figured this out.
- rb12345 12y agoTo be fair though, it's not that hard to test for DNSSEC breakage if you have dig available. If "dig +cdflag example.com A IN" works and "dig +adflag example.com A IN" returns SERVFAIL, it's DNSSEC's fault. (If that latter command returns responses without the ad flag, the domain lacks DNSSEC signing.)
- danyork 12y agoIf it's currently unavailable on Android, you should be able to start seeing the site again whenever the TTL of the DNS records ages out... this just happened for me on my own home network where I have a DNSSEC-validating DNS resolver on the edge of my network. However, when I do "dig +dnssec @8.8.8.8 ds hbonow.com" I don't get any DS records back, indicating that the issue should be fixed on Google's PDNS. Can you tell what DNS servers you are using on your Android device? It may be that your ISP is doing DNSSEC validation and experiencing a similar TTL issue.
- wtbob 12y agoI was being snarky, since HBO Now reportedly supports only Apple clients.
- danyork 12y agoToo funny... completely missed the snark in the midst of all the discussion here. :-) And you're right - HBO Now is only on Apple devices right now... so getting to the website from Android wouldn't matter.