locked
Unable to recive email 554 5.4.4 SMTPSEND.DNS.NonExistentDomain RRS feed

  • Question

  • Hey

    I am (trying) setting up a new Exchange Server 2016 and this is the first time that i have tried to setup a Exchange Server.

    When i try to send a email to the server from testconnectivity.microsoft.com i get a " 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX2 " error from but in the server logs it looks like this

    2019-04-04T13:33:30.189Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,1,10.1.1.10:25,40.69.150.142:7362,>,"220 server.domain Microsoft ESMTP MAIL Service ready at Thu, 4 Apr 2019 15:33:29 +0200",
    2019-04-04T13:33:30.331Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,2,10.1.1.10:25,40.69.150.142:7362,<,EHLO www.testexchangeconnectivity.com,
    2019-04-04T13:33:30.331Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,3,10.1.1.10:25,40.69.150.142:7362,>,250  server.domain Hello [40.69.150.142] SIZE 37748736 PIPELINING DSN ENHANCEDSTATUSCODES STARTTLS AUTH LOGIN 8BITMIME BINARYMIME CHUNKING,
    2019-04-04T13:33:30.474Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,4,10.1.1.10:25,40.69.150.142:7362,<,MAIL FROM:<DoNotReply@TestExchangeConnectivity.com>,
    2019-04-04T13:33:30.474Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,5,10.1.1.10:25,40.69.150.142:7362,*,08D6B8F82B4CF16F;2019-04-04T13:33:30.188Z;1,receiving message
    2019-04-04T13:33:30.474Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,6,10.1.1.10:25,40.69.150.142:7362,>,250 2.1.0 Sender OK,
    2019-04-04T13:33:30.616Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,7,10.1.1.10:25,40.69.150.142:7362,<,RCPT TO:<test@maildomain.com>,
    2019-04-04T13:33:30.616Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,8,10.1.1.10:25,40.69.150.142:7362,>,250 2.1.5 Recipient OK,
    2019-04-04T13:33:30.759Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,9,10.1.1.10:25,40.69.150.142:7362,<,DATA,
    2019-04-04T13:33:30.759Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,10,10.1.1.10:25,40.69.150.142:7362,>,354 Start mail input; end with <CRLF>.<CRLF>,
    2019-04-04T13:33:30.906Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,11,10.1.1.10:25,40.69.150.142:7362,*,,Proxy destination(s) obtained from OnProxyInboundMessage event. Correlation Id:9fd4dbb0-6cb1-4759-900b-e2eed91ac291
    2019-04-04T13:33:30.907Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,12,10.1.1.10:25,40.69.150.142:7362,*,,Message or connection acked with status Fail and response 554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain internalproxy -> DnsDomainDoesNotExist: InfoDomainNonexistent
    2019-04-04T13:33:30.907Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,13,10.1.1.10:25,40.69.150.142:7362,>,451 4.7.0 Temporary server error. Please try again later. PRX2 ,
    2019-04-04T13:33:31.049Z,DHS\DHS Internet recive Connector,08D6B8F82B4CF16F,14,10.1.1.10:25,40.69.150.142:7362,-,,Remote(SocketError)

    I get a "554 5.4.4 SMTPSEND.DNS.NonExistentDomain" error that i cant figure out how to fix or whats causing it.

    I am guessing that i has somthing to do with the DNS so for info, I am using a DNS server hosted on the same machine as the exchange server and the entire thing is behind a NAT.

    Any hint or idea of what might be causing the error would  be much appreciated! 

    Thanks in advance,

    Oscar

    Thursday, April 4, 2019 2:34 PM

All replies

  • Hi Oscar,

    Yes, this is a DNS issue. My guess is your connector is probably using an incorrect DNS entry to send/receive email. Is Exchange 2016 on a Virtual environment? if yes, please go to the Exchange Admin center - servers - select the server - edit and make sure you choose the correct network adapter which is configured to use the Internal DNS.


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Niko.Cheng Wednesday, April 10, 2019 9:20 AM
    Friday, April 5, 2019 7:07 AM
  • Hi

    I have checked the DNS settings in the Exchange Admin center and the DNS is pointed to my internal DNS server but i still have the same error.

    I am not running Exchange on a VM rather i am running it directly on a Windows Server 2016 box.

    Any other ideas on a solution?

    Best Regards

    Oscar Eriksson

    Thursday, April 11, 2019 2:04 PM
  • Hi Oscar,

    Please refer to the following similar case and check if get any hints:

    https://social.technet.microsoft.com/Forums/exchange/en-US/be568eab-45c1-4648-88df-99f4939dd845/mailflow-broken-error-451-470?forum=exchangesvrsecuremessaging

    Quote:

    turns out that ex2013 has huge problems when you leave the DNS lookups setting in the server properties to "All network adapters", instead you should select a specific NIC or enter the IPs of your DNS servers manually. well, this is mentioned in numerous threads all over the forums and obviously for many people, that was the solution.
    BUT...i still had no mail flow after setting the DNS servers manually and my logs still filled up with DNS errors. in the end it turned out that the setting in the ECP only configures the transport service, but NOT the the frontend transport service. you can easily check this with get-transportservice and get-frontendtransportservice and looking at the ExternalDNS and InternalDNS settings...sure enough, for me only the Transport Service had the configuration applied that i set in the ECP.
    so, i configured set-frontendtransportservice with the same DNS settings as the transport service, and finally my mailflow is working...i can hardly believe it, and i can't believe that i found literally nothing about this behavior/bug of the ECP on the net. so, this is my solution - maybe it helps someone else :)


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Niko.Cheng Tuesday, April 16, 2019 9:24 AM
    Monday, April 15, 2019 8:27 AM