NetApp Support-Site not reachable over IPv6

[#1]

Hi,

the support-site is not reachable over an ipv6-connection:

user@computer:~# wget -6 support.netapp.com

--2013-04-03 10:18:10--  http://support.netapp.com/

Resolving support.netapp.com (support.netapp.com)... 2620:10a:4001:4000::a16

Connecting to support.netapp.com (support.netapp.com)|2620:10a:4001:4000::a16|:80... connected.

HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.

Retrying.

IPv4 is working fine:

user@computer:~# wget -4 support.netapp.com

--2013-04-03 10:24:57--  http://support.netapp.com/

Resolving support.netapp.com (support.netapp.com)... 216.240.18.16

Connecting to support.netapp.com (support.netapp.com)|216.240.18.16|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/html]

Saving to: `index.html'

2013-04-03 10:24:59 (34.6 KB/s) - `index.html' saved [27318]

Is the IPv6 dns-record intended or by mistake?

Best regards,

Bernd

[#2]

Confirming the exact same problems that Bernd stated.

Cheers,

Felix

[#3]

I too have the exact same problem.

[#4]

I'm also experiencing this.

[#5]

Thank you for the feedback.

We have opened a case against this.

Please stay tuned for a solution.

Thank you

[#6]

same problem, more info.

#dig support.netapp.com

; <<>> DiG 9.8.1-P1 <<>> support.netapp.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16142

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:

;support.netapp.com.            IN      A

;; ANSWER SECTION:

support.netapp.com.     30      IN      A       216.240.18.16

;; AUTHORITY SECTION:

support.netapp.com.     554     IN      NS      dc1-gl01.netapp.com.

support.netapp.com.     554     IN      NS      dc2-gl01.netapp.com.

support.netapp.com.     554     IN      NS      dc2-gl02.netapp.com.

support.netapp.com.     554     IN      NS      dc1-gl02.netapp.com.

;; ADDITIONAL SECTION:

dc1-gl01.netapp.com.    10      IN      A       202.3.113.55

dc1-gl02.netapp.com.    10      IN      A       202.3.113.56

dc2-gl01.netapp.com.    10      IN      A       216.240.31.245

dc2-gl02.netapp.com.    10      IN      A       216.240.31.246

;; Query time: 42 msec

;; WHEN: Mon Apr 22 13:33:08 2013

;; MSG SIZE  rcvd: 208

a subsequent dig on any of the dc*.netapp.com returns entries AAAA records:

#dig dc1-gl01.netapp.com | grep AAAA

ns021.netapp.com.       3184    IN      AAAA    2620:10a:4001:4000::a28

ns060.netapp.com.       3184    IN      AAAA    2620:10a:4003:4000::a221

#dig dc1-gl02.netapp.com | grep AAAA

ns021.netapp.com.       3177    IN      AAAA    2620:10a:4001:4000::a28

ns060.netapp.com.       3177    IN      AAAA    2620:10a:4003:4000::a221

#dig dc2-gl01.netapp.com | grep AAAA

ns021.netapp.com.       3169    IN      AAAA    2620:10a:4001:4000::a28

ns060.netapp.com.       3169    IN      AAAA    2620:10a:4003:4000::a221

#dig dc2-gl02.netapp.com | grep AAAA

ns021.netapp.com.       3166    IN      AAAA    2620:10a:4001:4000::a28

ns060.netapp.com.       3166    IN      AAAA    2620:10a:4003:4000::a221

#

always ns021 and ns060.   My guess is that Netapp does not really have an ipv6 web presence as of yet, and those are two machines that were provisioned with v6 by mistake..  but that's just a guess. 

[#7]

Just to give you an update.

We have been working this issue and it is still under investigation.  We have no definite area at this where the issue is originating. At this time we have had a route added back to a firewall in the stage environment and will be taking an action to restart the weblogic server/s once we get access to the Stage environment. Our goal is still to have this completed by the end of the week.  Once we have that up and running we will schedule some time with one of the customers to test through the stage environment and take logs again as we did earlier this month.

Thank you

[#8]

Hello there

This issue has now been fixed. Please do let us know if you run into issues going forward.

Thank you.

[#9]

It could have started earlier, but I noticed that starting around noon eastern on September 09, 2013 I've started having the same problem.  IPv6 does not work, whereas IPv4 does.

$ wget -6 support.netapp.com

--2013-09-10 07:33:08--  http://support.netapp.com/

Resolving support.netapp.com (support.netapp.com)... 2620:10a:4005:4000::a18

Connecting to support.netapp.com (support.netapp.com)|2620:10a:4005:4000::a18|:80... connected.

HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.

$ wget -4 support.netapp.com

--2013-09-10 07:34:05--  http://support.netapp.com/

Resolving support.netapp.com (support.netapp.com)... 216.240.21.18

Connecting to support.netapp.com (support.netapp.com)|216.240.21.18|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/html]

Saving to: `index.html'

2013-09-10 07:34:06 (83.5 KB/s) - `index.html' saved [27238]