all, we currently have exchange 2007 on our domain-name.com however we rebranded to domain.com but we have not renamed the domain as yet due to the amount of work required to do this. we do experience email being unable to deliver due to the revers lookup as it resolves the server as server.domain-name.com as this is the fqdn. all spf and mx records are set to domain.comother than having to rename the domain is there anyway of resolving this i have thought of changing the fqdn in exchange to server.domain.com and adding this internally to dns ?hope that made senseAmatsoukis

Just ensure that the PTR record matches the FQDN that Exchange responds with in a HELO/EHLO response.Also ensure your SPF record is set correctly.That should be all that is needed to remedy this.OliverOliver Moazzezi | Exchange MVP, MCSA:M, MCTS:Exchange 2010, BA (Hons) Anim | http://www.exchange2007.com | http://www.exchange2010.com | http://www.cobweb.com |

I see it as six of one and a half dozen of the other. Either return the DNS settings to their original values or finish the migration to the new branding. Adding the new FQDN value to your internal DNS will not help people outside of your organization. Oliver is correct that setting your SPF and PTR records to the proper values will help, but your MX records will also need to be updated. If you are going to do all that, you may as well complete the migration to the new branding. I hope this helps . . .