로그인
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > 포럼 홈 > Transport > 451 4.4.0 DNS query failed to some domains from Hub transport
질문하기질문하기
포럼 검색:
 

답변됨451 4.4.0 DNS query failed to some domains from Hub transport

  • 2009년 3월 24일 화요일 오후 7:50regriffith1 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표
    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.


     

답변

모든 응답

  • 2009년 3월 24일 화요일 오후 8:24Johan VeldhuisMVP사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표
    Hi,

    Please disable IPv6 by following the steps below:

    To disable IPv6 (source http://technet.microsoft.com/en-us/library/bb629624.aspx )

    1. In Control Panel, open Network and Sharing Center.

    2. In the Tasks list, click Manage network connections.

    3. Right-click the connection from which you want to remove IPv6, and then click Properties.

    4. Click to clear the Internet Protocol Version 6 (TCP/IPv6) check box, and then click OK.

    5. Close Network Connections, and then close Network and Sharing Center.

    6. In Windows Explorer, locate the hosts file in the following location:

      %windir%\System32\drivers\etc

    7. In Notepad, open the hosts file.

    8. In the hosts file, remove the following entry:

      ::1 localhost

    9. Save and then close the hosts file.

    10. Start Registry Editor.

    11. Expand the following subkey:

      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip6\Parameters

    12. Right-click Parameters, point to New, and then click DWORD (32-bit) Value.

    13. Type DisabledComponents, and then press ENTER to name the new value.

    14. Right-click DisabledComponents, and then click Modify.

    15. In the Value data box, type FFFFFFFF, and then click OK.

    16. Exit Registry Editor, and then restart the computer.

    Regards,

    Johan

    blog: www.johanveldhuis.nl
     
  • 2009년 3월 25일 수요일 오후 8:01regriffith1 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표
    Thanks for the suggestion.  I have already set all this (I was thinking the link I listed had that information as well).  I have also tried both FFFFFFFF and 000000FF. 
     
  • 2009년 3월 26일 목요일 오전 8:21Allen SongMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨
    로그인하여 투표
    0
    로그인하여 투표
    Hi,

    Please run nslookup -q=mx domain.com (the problematic domain) command in CMD, then post the information on the forum.

    Thanks

    Allen
     
  • 2009년 4월 8일 수요일 오전 6:59Allen SongMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨
    로그인하여 투표
    0
    로그인하여 투표
    Hi,

    Until now, that is the product issue in Exchange 2007 which running on Windows Server 2008. If any update, I will inform you.

    Thanks

    Allen
     
  • 2009년 9월 11일 금요일 오후 5:30MarcoBr 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표

    Hi,

    Have microsoft released any update on this?
    I have a similar promblem with some domains.


    Complements,

    Marco

     
  • 2009년 11월 4일 수요일 오전 9:34Edwin Bak 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표
    Still no patch or update from microsoft? I've inserted the 2 domains in the hosts file now and it's working but it's not the must beautiful solution i've seen... :(
    a search on google will bring several users with the exact same problems but nobody seems to have has a real solution for this problem.
    If somebody has a solution please share it with us..

    Thanks..
     
  • 2009년 11월 5일 목요일 오후 2:49erikfr 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표
    Hi Edwin,
    Could you tell me how you added the domain in the hosts file?
    Ive added the domains dns and mailservers ip in the hosts file without any luck.
    Thanks
    Erik
     
  • 2009년 11월 6일 금요일 오전 2:14Allen SongMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    로그인하여 투표
    0
    로그인하여 투표
    Hi Guys,

    For this issue, please try to refer to the the below thread to workaround this issue:
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/a9b1a718-7b22-4678-aa91-c8ecebb4c6fa

    Thanks

    Allen