
July 8th, 2012, 11:01 AM
|
|
|
|
IPv4/IPv6 is just the transport method utilized, and is not necessarily directly related to the IP address reported. If the sending machine and the receiving machine both reside on an IPv6 network, IPv6 addresses will be utilized and reported. If the sending machine and the receiving machine both reside on an IPv4 network, IPv4 addresses will be utilized and reported. But if either machine is utilizing a Tunnel Broker to bridge from one network to the other, things get a little confusing as a Tunnel Broker resides on both networks. It is the responsibility of the receiving server to add the originating sender's IP address to the email header. IPv6 is not universally implemented yet, so it is somewhat of a toss up as to what gets reported when it comes from a Tunnel Broker?
J.A. Coutts
Addendum: For example, Google (who is a strong supporter of IPv6) reports MX records for google.com as:
aspmx.l.google.com [173.194.79.27]
alt1.aspmx.l.google.com [209.85.225.26]
alt2.aspmx.l.google.com [74.125.45.26]
alt3.aspmx.l.google.com [173.194.76.26]
alt4.aspmx.l.google.com [173.194.73.27]
but no AAAA records for any of them
To find the IPv6 server, you have to use ipv6.google.com, which reports an MX of:
ipv6.l.google.com with no A record
and a AAAA record of [2001:4860:8005:000:000:000:000:067]
Last edited by couttsj : July 8th, 2012 at 12:08 PM.
|