Possibly an IPv6 routing issue here too.
Both nameservers affected, and have common address prefix, so it is all or
nothing.
cloudflare.net. 86259 IN SOA fred.ns.cloudflare.com.
dns.cloudflare.com. (
2014904817 ;serial
10000 ;refresh
2400 ;retry
604800 ;expire
3600 ) ;minimum
www.ietf.org. 1658 IN RRSIG CNAME 5 3 1800 (
20150627140549 20140627130739 40452 ietf.org.
Oggxi8gGJxwg0n+ ...
www.ietf.org. 1658 IN CNAME www.ietf.org.cdn.cloudflare.net.
----
[1]* fred.ns.cloudflare.com [173.245.59.113]
zone serial 2014904817
[1]* fred.ns.cloudflare.com [2400:cb00:2049:1:0:0:adf5:3b71]
### no response
[2] jean.ns.cloudflare.com [173.245.58.121]
zone serial 2014904817
[2] jean.ns.cloudflare.com [2400:cb00:2049:1:0:0:adf5:3a79]
### no response
Unsatisfactory response from 2 nameservers
________________________
On 27 June 2014 17:22, Stephane Bortzmeyer <bortzmeyer(_at_)nic(_dot_)fr> wrote:
On Fri, Jun 27, 2014 at 10:51:20AM -0400,
Christopher Morrow <morrowc(_dot_)lists(_at_)gmail(_dot_)com> wrote
a message of 29 lines which said:
maybe fixed now?
Yes, back to the correct name servers. See what happened during the
problem:
http://dnsviz.net/d/ietf.org/U61S3A/dnssec/