• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Double-check IPv6to4 settings, please?

Started by Keiro, September 28, 2010, 01:29:41 PM

Previous topic - Next topic


Added! :D

Should work now... I think. One more question:

Would this work so long as I assign other IPs, say: 2001:470:c:67f::3 for example, to other domains on the server?


Yes, but you'll never be able to set reverse DNS since you are using the link /64 and not the routed /64.


Ah! Okay, so to make sure I can set reverse DNS, how would I proceed in this manner?


Configure IPs out of your routed /64 instead, on your server. Then you can control rDNS after delegation to whatever server or service you will use to manage it. Broker accounts get access to dns.he.net automatically if you want to use that service.


Gotcha, that's what I was trying to learn how to do, to route IPs out of my assigned /64.

Thanks a whole bunch for the help so far!

I'll be dropping by that service in a bit to check it out.

Edit: So, I click on Routed /48 and I see a bunch of stuff, in my tunnel detail list.



It took several hours of banging my head against the wall this morning.

Turns out it's not CSF at fault.

It's the darned kernel. We're running pre-2.6.20. Which means CSF kills the connections unintentionally.

HOWEVER! I can at least say that IPv6in4 now works!

Try checking shatteredtears.com via IPv6.  ;D

So... the solution is to essentially disable CSF and/or upgrade to post-2.6.2x kernel and reenable CSF to make it work.

For now, I'm just going to wait for a kernel upgrade and leave CSF disabled. :/