Exchange 2007 hub running on Windows Server 2008. IPv6 has been disabled per http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx . Looking at a packet capture, I see the following:
DNS Standard query AAAA webmail.xxxxxxxxx.com
DNS Standard query response, Server failure
Both servers are in the same AD domain/site and running Windows Server standard 2008 SP1.
Email will sit in the queue until it expires.
Nslookup (from Windows XP or hub server) against the same DNS server will resolve the xxxxxxxxx.com to webmail.xxxxxxxxx.com with a valid IP address. I can telnet using port 25 to that IP address from the Hub server without any problems.
Once the hub server receives the DNS error, it will retry again at the set time interval using IPv6 DNS query. Of course it fails again and the pattern continues until the email expires.
If I put the mx record in the hosts file, email is delivered immediately.
I have seen http://technet.microsoft.com/en-us/library/bb878121.aspx where it mentions having the DNS server respond to a second query, but the trace doesn't even show a second attempt.
No smarthost involved in outgoing email.
The destinations worked in Exchange 2003 on Windows Server 2003. If we redirect the email from Exchange 2007 to Exchange 2003, it will be delivered. Not a good solution since we are removing 2003.
I would expect when the IPv6 query fails it would try IPv4. This does not seem to be the case with Server 2008.
DNS Standard query AAAA webmail.xxxxxxxxx.com
DNS Standard query response, Server failure
Both servers are in the same AD domain/site and running Windows Server standard 2008 SP1.
Email will sit in the queue until it expires.
Nslookup (from Windows XP or hub server) against the same DNS server will resolve the xxxxxxxxx.com to webmail.xxxxxxxxx.com with a valid IP address. I can telnet using port 25 to that IP address from the Hub server without any problems.
Once the hub server receives the DNS error, it will retry again at the set time interval using IPv6 DNS query. Of course it fails again and the pattern continues until the email expires.
If I put the mx record in the hosts file, email is delivered immediately.
I have seen http://technet.microsoft.c
No smarthost involved in outgoing email.
The destinations worked in Exchange 2003 on Windows Server 2003. If we redirect the email from Exchange 2007 to Exchange 2003, it will be delivered. Not a good solution since we are removing 2003.
I would expect when the IPv6 query fails it would try IPv4. This does not seem to be the case with Server 2008.