If you are moving your domain name registrar for reverse lookup support, then you are wasting your money. The reverse lookup is set by the owner of the IP address. It is basically a lookup on the IP to see if it matches what your server is announcing itself as. Many of the first line support people at ISPs here the words "DNS" and tell you to go to your domain name registrar, because they don't understand the difference between conventional (forward) DNS which matches name to an IP address, and reverse DNS, which matches IP address to the name. Simon. -- Simon Butler MCP, MCSA, MVP:Exchange Amset IT Solutions Ltd. e: simon@xxxxxxxxxxxx w: www.amset-it.com w: www.amset.info ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew English Sent: 15 May 2006 20:47 To: exchangelist@xxxxxxxxxxxxx Subject: RE: [ExchangeList] Re: Exchange Que Ah okay.. That explains it. I am in the process of moving our domain from Network Solutions to Register.com because NS refuses to support reverse MX lookup (PTR). Sigh. Regards, Andrew ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx on behalf of Ollo Lloyd Sent: Mon 15/05/2006 3:27 PM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: Exchange Que I recently had the same problem and was able to fix it by having my ISP create a PTR for my mail server. You may contact your ISP and make sure that the reverse lookup record exists and is correct. Ollo ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew English Sent: Monday, May 15, 2006 12:27 PM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: Exchange Que A couple of issues: Some emails are not going out because "The remote server did not respond to a connection attempt", and "Unable to bind the destination server in DNS". How do I fix this problem? Thanks Regards, Andrew