I set up my network so far that I can recieve emails via IPv6.
Server IPv6 Address: 2001:470:abc2:666::1/64
Client IPv6 Address: 2001:470:abc2:666::2/64
Routed /64: 2001:470:abc3:666::/64
For the rDNS I'm using he.net.
There I set up the DNS for 2001:470:abc3:666::/64. But my server runs with the IP 2001:470:abc2:666::2 not with abc3! How can I setup a PTR entry for 2001:470:abc2:666::2 and not 2001:470:abc3:666::2?
I almost think that I made an error but I don't know what went wrong.
The ranges are modified but you should get the point.
Please unblock your ip ranges, I have no idea what i'm reading
I updated my question. Now the IPs are valid even if I have other ranges. (I don't like to post public my ip address)
Edit:
Ah I got it. Like you told in "Professional LEVEL" problem: Your MX does not appear to have working RDNS (http://www.tunnelbroker.net/forums/index.php?topic=2085.0) I have to setup an IP from the second range in my case 2001:470:abc3:666::1
Since you didn't provide real IPs, I made certain rDNS was pushed out on both your tunnels.
Quote from: rekire on November 28, 2011, 02:43:50 PM
I updated my question. Now the IPs are valid even if I have other ranges. (I don't like to post public my ip address)
You could always use the 2001:db8::/32 documentation prefix too
Quote from: cholzhauer on November 28, 2011, 04:59:38 PMYou could always use the 2001:db8::/32 documentation prefix too
That wouldn't help in this case since the problem was too little information in the post.
Quote from: kasperd on November 29, 2011, 05:13:40 AM
Quote from: cholzhauer on November 28, 2011, 04:59:38 PMYou could always use the 2001:db8::/32 documentation prefix too
That wouldn't help in this case since the problem was too little information in the post.
Good point
I simply missed that the lower ip range is for routing only and not for client IPs and rDNS. Since I'm using the higher ip range everything works fine.