IPv6 with Local Exchange sending Bounce Backs

OAC Technology
OAC Technology used Ask the Experts™
on
We have a client who is on Comcast with a static IPv4 address and local Exchange.  Comcast has started rolling out IPv6 on everything and they are now receiving bounce backs when sending out (message below).  I've contacted Comcast and they say that they cannot assign a static IPv6 address, therefore we cannot set reverse DNS for IPv6.  I have added their IPv6 address to their SPF record which solved the issue temporarily, but since the IPv6 is dynamic it has changed, then they get bounce backs again.

We have a number of clients behind a hardware firewall, which we disable IPv6 on, and they are not having any problems as they are only communicating with the world on IPv4.

Any idea on a permanent fix to resolve this IPv6 dynamic address issue that inevitably causes bounce backs?

Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
The following organization rejected your message: mx.google.com.
________________________________________
Sent by Microsoft Exchange Server 2007

Diagnostic information for administrators:
Generating server: SERVER.[xxxx].local
[xxxx]@gmail.com
mx.google.com #550-5.7.1 [2601:[xxxx]:c05c] Our system has detected that 550-5.7.1 this message does not meet IPv6 sending guidelines regarding PTR 550-5.7.1 records and authentication. Please review 550-5.7.1 https://support.google.com/mail/?p=ipv6_authentication_error for more 550 5.7.1 information. x75si3472751ioi.11 - gsmtp ##
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2015
Commented:
Exchange 2007 and Exchange 2010 does not support IPv6 yet.

Newer version like Exchange 2013 and 2016 are supporting IPv6.
OAC TechnologyProfessional Nerds

Author

Commented:
We're not having an issue with Exchange itself, the problem is the bounce back we receive when sending.  I don't see how the version of Exchange would be causing this type of bounce back, but again, I don't know which is why I'm here.  If this is the case, is there any more information you could provide?
Top Expert 2015
Commented:
Please check this article
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

OAC TechnologyProfessional Nerds

Author

Commented:
Thank you, good article.  One client we're having the issue with is on Exchange 2010, the other is on Exchange 2013.

In both cases, everything seems to be working as far as IPv6 is concerned, the issue is with external spam filters, namely Google in this case, bouncing back messages with the message in my original post.

We are not able to get reverse DNS setup on the IPv6 address because it is not static, and since it's not static and keeps changing, SPF records need to be updated frequently.

So, in either case of whether or not the version of Exchange supports IPv6, the issue is not appear to be with Exchange itself.  (Exchange was the best tag I could use on this post)
Top Expert 2015
Commented:
Why IPv6 is not static in your case? If you are using Public IPs then they will be static else your natting will not work.
OAC TechnologyProfessional Nerds

Author

Commented:
Comcast does not offer static IPv6.  The client does have static IPv4, but Comcast says they cannot assign static IPv6.
Top Expert 2015
Commented:
I think dynamic IPs are unsupported for public networks when we publish DNS and SPFs

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial