A few minutes ago I received an email from the tech who was communicating my case with their network team that the solution was migrated from their staging environment to production. I just now confirmed that the issue is now resolved.
The actual fix was not communicated to me. I have asked why they just didn't remove the AAAA while troubleshooting. Frank -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bernhard Schmidt Sent: Tuesday, May 14, 2013 4:47 PM To: [email protected] Subject: Re: Looking for support.netapp.com contact Am 03.04.2013 20:03, schrieb Bernhard Schmidt: > today I had the first "we enabled IPv6 and $something is really broken" > incident for months, if not years. https://support.netapp.com connects, > sends a certificate and then just hangs. Of course this does not trigger > any failover, so the site was completely broken from the user > perspective. Not too happy to introduce them to > network.dns.ipv4OnlyDomains in Firefox :-( 6 weeks later it is still broken. If SOMEONE is considering buying from them I would appreciate some bashing of the sales clerk, maybe that would wake them up. Bernhard
