Exchange 2010 works with IPv6??? Check below
Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP). IPv6 is intended to correct many of the shortcomings of IPv4, which was the previous version of the IP. In Microsoft Exchange Server 2010, IPv6 is supported only when IPv4 is also used; a pure IPv6 environment isn't supported. Using IPv6 addresses and IP address ranges is supported only when both IPv6 and IPv4 are enabled on the computer running Exchange 2010, and the network supports both IP address versions. If Exchange 2010 is deployed in this configuration, all server roles can send data to and receive data from devices, servers, and clients that use IPv6 addresses.
This topic discusses IPv6 addressing in Exchange 2010. For additional background information about IPv6, see IPv6 and IPv6 Support in Exchange 2007 SP1 and SP2.
Exchange 2010 components and IPv6
|Server role on the source computer||Feature||IPv6 supported||Comments|
|Transport||IP Allow list and IP Block list||Yes||For more information about the IP Allow list, see Enable or Disable Connection Filtering and Understanding Connection Filtering.|
|Transport||IP Allow List providers and IP Block List providers||No||Currently, there is no widely accepted industry standard protocol for looking up IPv6 addresses. Most IP Block List providers don't support IPv6 addresses. If you allow anonymous connections from unknown IPv6 addresses on a Receive connector, you increase the risk that spammers will bypass IP Block List providers and successfully deliver spam into your organization.|
For more information about IP Block list providers, see "IP Block List Providers" in Understanding Connection Filtering.
|Transport||Sender reputation||No||The Protocol Analysis agent doesn't compute the sender reputation level (SRL) for messages that originate from IPv6 senders. For more information about sender reputation, see Understanding Sender Reputation.|
|Transport||Sender ID||Yes||For more information, see Understanding Sender ID.|
|Transport||Receive connectors||Yes||IPv6 addresses are accepted for the following components:|
For more information, see Understanding Receive Connectors.
|Transport||Send connectors||Yes||IPv6 addresses are accepted for the following components:|
For more information, see Understanding Send Connectors.
If you want to specify an IPv6 address for the SourceIPAddress parameter, make sure that the appropriate DNS AAAA and mail exchange (MX) records are configured correctly. This helps ensure message delivery if a remote messaging server tries any kind of reverse lookup test on the specified IPv6 address.
|Transport||Incoming message rate limits||Partial||Incoming message rate limits that you can set on a Receive connector, such as the MaxInboundConnectionPercentagePerSource parameter, the MaxInboundConnectionPerSource parameter, and the TarpitInterval parameter, only apply to a global IPv6 address. Link local IPv6 addresses and site local IPv6 addresses aren't affected by any specified incoming message rate limits. For more information about incoming message rate limits, see Understanding Message Throttling.|
|Unified Messaging||All features||No||Unified Messaging doesn't support IPv6 in any version of Exchange 2010. For more information about Unified Messaging, see Unified Messaging.|
|Mailbox (Database availability group member)||IPv6 addresses||Yes||Static IPv6 addresses are supported by Windows Server 2008 and the Cluster service. However, using static IPv6 addresses goes against best practices. Exchange 2010 on Windows Server 2008 doesn't support the configuration of static IPv6 addresses during setup.|
Failover clusters support Intra-site Automatic Tunnel Addressing Protocol (ISATAP). They support only IPv6 addresses that allow for dynamic registration in DNS. Link local addresses can't be used in a cluster.
For more information, see New High Availability and Site Resilience Functionality.
Return to top
Depending on your specific deployment, you may want to disable IPv6 on your Exchange servers. For example, because the Unified Messaging server role doesn't support IPv6, you may choose to disable IPv6 on those servers. To help you do this, use the instructions in IPv6 for Microsoft Windows: Frequently Asked Questions. You can also use these instructions to enable IPv6 if needed.