Routing problem to OpenDNS IPV6 DNS

[lordvader]

Hi,

I discovered that by 2 days ago, my IPV6 route became very laggy. But it's ok since yesterday.

However, today I tried to test IPV6 DNS query on OpenDNS IPv6 DNS (2620:0:ccc::2 / 2620:0:ccd::2),

only got timeout respond.

So I tried to trace them, only reached 4 hops (stop on 10ge8-2.core1.pao1.he.net [2001:470:0:30::2]),

rest replied timeout too.

But I tested them with Online TraceRoute IPv6 later,

I got all respond from each hop on route.

I am wondering that have you made any adjustment on tunnelbroker service within these days?

Or is it just my problem? Thanks for help!

[prutsdink]

I'm having similar issues. It seems that traffic is going trough but not all.
When performing a traffic capture I see data, however not all packets that should be there are there.

Started today and found out that facebook isn't working anymore over the HE tunnel.  ;) >:(

Can somebody advice on this.

ping and traceroute work fine. HTTP is not working. Wireshark is complaining that it is missing a previous segment...

[lordvader]

Here are my test results. I ever considered sending them to OpenDNS,

but it supposes the problem of the he.net hops.

So if anyone can help me figure out the problem and solve it, I will be very appreciated.

Local Dig, no answer from OpenDNS IPV6 server


subnetonline.com Dig, correctly reply form OpenDNS IPV6 server


Local Traceroute to OpenDNS IPV6 server, stop at 4th hops


subnetonline.com Traceroute to OpenDNS IPV6 server, completed perfectly.

[lordvader]

Problem has been solved.

  1    <1 ms    <1 ms    <1 ms  2001:470:1f05:296::1
  2   176 ms   158 ms   163 ms  2001:470:1f04:296::1
  3   174 ms   170 ms   175 ms  2001:470:0:45::1
  4   161 ms   166 ms   155 ms  2001:470:0:30::2
  5   163 ms   169 ms   173 ms  2001:470:0:34::2
  6   201 ms   176 ms   172 ms  2001:504:0:3:0:3:6692:1
  7   181 ms   172 ms   171 ms  2620:0:ccc::2


> google.com
伺服器:  [2620:0:ccc::2]
Address:  2620:0:ccc::2

未經授權的回答:
名稱:    google.com
Addresses:  2607:f8b0:4007:804::1009
          74.125.224.142
          74.125.224.136
          74.125.224.130
          74.125.224.133
          74.125.224.137
          74.125.224.135
          74.125.224.134
          74.125.224.132
          74.125.224.129
          74.125.224.128
          74.125.224.131

Thank you very much admin!

[kcochran]

This is actually an OpenDNS issue.  Their Palo Alto router would seem to be a bit uncertain as to what to do with the inbound traffic, and they're investigating further.  In the meantime, Bay Area traffic will tend to go to one of their other sites instead.

Testing from various locations around the world will give you different results, as was noted earlier in the thread, as they anycast their DNS services, much as we do.  If you're in Amsterdam, you'll tend to get the Amsterdam instance.  In the Bay Area, you'll get a Bay Area one.  Etc.

And as always, if you're seeing a network issue, these forums are not the best place for reporting that to us.  Email ipv6@he.net for tunnelbroker.net issues.

[PatrickDickey]

Is there an update to this issue? I noticed in my TunnelInfo that my rdns addresses are set to OpenDNS. Should I change them to another provider (such as Google's IPv6 DNS), or do I have a choice?

Have a great day.:)
Patrick.

[ICURPNT2]

Is there an update to this issue? I noticed in my TunnelInfo that my rdns addresses are set to OpenDNS. Should I change them to another provider (such as Google's IPv6 DNS), or do I have a choice?

Have a great day.:)
Patrick.

Common Installation Problems w/Umbrella OpenDNS
Since obtaining Umbrella OpenDNS, my 2 PCs Windows Vista -32bit SP2 and Windows 7 -64bit SP1, have been manic, slow, and uncooperative. Java updates, Windows updates and others are returning countless errors. Windows Installer does not work, along with a corrupted Registry.

Setting for IPV6 thru my Comcast ISP are erratic, not to mention Google Chrome. The OpenDNS is working when I switch back, but Umbrella Prouser is maddening. I can't ping their site to gather information to troubleshoot, and trouble tickets returned for answers are extremely slow. I was hoping for some insight to what the problem could be.

Thank you in advance.

Nicholas (ICURPNT2)