I had opened a case on this issue and in a few days was talking to the
nearly the right person. They acknowledged the issue, saying "We have seen
multiple users face this issue previously so I have opened a ticket with our
IT team to have this checked and rectified."
I followed up in mid-May and I heard back:
We have identified the issue but have still not got a resolution
for the fix. We have been interacting with several customers
and getting the input and have also put together a team to get
this fixed at the earliest. I got an update today that this will
be fixed in the coming 2 weeks but no commitments have been made.
I will keep you posted on the proceedings.
Once again, my apologies for the inconvenience caused due to the
delay in getting this fixed.
I asked that they remove the AAAA in the meantime and provide me a test URL,
but I never heard back.
I'm guessing that there's a load-balancer issue.
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
