Remove From My Forums

Remote Server returned '554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -> DnsDomainIsInvalid: InfoMxLoopback'

Question
0

Sign in to vote
Hey can anyone help me overcome this issue??

i have set up my organisation as follows:

i have hyper-v machine hosting:

1 AD+DNS machine (Windows 2016) , (1 NIC configured with LAN settings 10.10.10.1) -- no internet connection

1 Exchange server 2016 , 2 NICs (one having the real IP , the other has LAN address 10.10.10.2)

the configuration is supposed to work on split-domain basis, meaning that i have domain names that are identical internally and externally,

i have an ISP hosted external domain, on which i configure my external DNS records, i configured records as follows:

on external domain: mail.xx.xxx.xx --> (my mail server real IP address)

autodiscover.xx.xxx.xx --> (my mail server real IP address)

owa.xx.xxx.xx --> (CNAME my mail server )

MX record pointing to my mail server real IP address

as for my internal DNS:

i have configured the forward zone (which is the parent domain name for mail.xx.xxx.xx [xx.xxx.xx])

the records: MX record (pointing to the internal ip address of my mail server = 10.10.10.2)

A record for mail --> pointing to the internal ip address of my mail server = 10.10.10.2

alias (CNAME) owa pointing to mail.xx.xxx.xx

of course i have configured the send connectors (not using the external DNS option)

and the receive connector

------------------------------------------------------end of configuration information-----------------------------

I have no problems receiving any mail from anywhere, my problem is with sending mail, for instance when i try to send to a gmail,outlook or any other domain it sometimes works and other times (maybe directly after few seconds) it may fail with the error:

Remote Server returned '554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -> DnsDomainIsInvalid: InfoMxLoopback'

original message headers:

Received: from mail.xx.xx.xx (10.10.10.2) by mail.xx.xxx.xx (10.10.10.2) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1415.2; Sun, 17 Feb 2019 00:52:43 -0800 Received: from mail.xx.xxx.xx([::1]) by mail.xx.xxx.xx([::1]) with mapi id 15.01.1415.002; Sun, 17 Feb 2019 00:52:43 -0800
look at the bold underlined LAN address in the error message,(10.10.10.2) this address sometimes changes
in the error message and can be the real IP address i use for mail server.
Sunday, February 17, 2019 9:13 AM

All replies

1

Sign in to vote
Hi,

Delete all the internal DNS settings you made for Mail, MX, CNAME etc. Restart exchange services and try again
Regards From: Exchange Online | World of Cloud Computing
- Marked as answer by Hussein Badran Monday, February 18, 2019 8:04 AM
- Unmarked as answer by Hussein Badran Monday, February 18, 2019 8:11 AM
Sunday, February 17, 2019 4:57 PM
0

Sign in to vote
i did as you told me, it worked immediately, then i tested once more and the error surfaced again ! :(

In the first test i tried to send to multiple recipients (outlook,gmail ,..etc) and it worked fine, then in the second test round the outlook recipient couldn't get the message for the same reason

--------------------error message --------------------------------------------------------------

hussein.badran@outlook.com (hussein.badran@outlook.com)
A problem occurred during the delivery of your message likely due to invalid DNS record configuration. This could be a temporary situation. Please try to resend the message later. If the problem continues, contact your email admin.

Diagnostic information for administrators:

Generating server: mail.t3.com.eg

hussein.badran@outlook.com
Remote Server returned '554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -> DnsDomainIsInvalid: InfoMxLoopback'

Original message headers:

Received: from mail.t3.com.eg (197.161.144.73) by mail.t3.com.eg (197.161.144.73) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1415.2; Mon, 18 Feb 2019 00:06:33 -0800 Received: from mail.t3.com.eg ([::1]) by mail.t3.com.eg ([::1]) with mapi id 15.01.1415.002; Mon, 18 Feb 2019 00:06:33 -0800 From: Hussein Badran <hussein.badran@t3.com.eg> To: Hussien Badran <husseinbadran@gmail.com>, "hussein.badran@outlook.com" <hussein.badran@outlook.com>, "Hb@et3.co" <Hb@et3.co>, "hbadran@tra.gov.eg" <hbadran@tra.gov.eg>, exchange admin <exchadmin@t3.com.eg> Subject: Howdy Thread-Topic: Howdy Thread-Index: AQHUx2DSgGQ2RkJ55UK00MehHWyUlw== Date: Mon, 18 Feb 2019 08:06:33 +0000 Message-ID: <2f7f5aa6b8024cc39e2ef11eb6caf1c5@t3.com.eg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [81.21.106.117] Content-Type: multipart/alternative; boundary="_000_2f7f5aa6b8024cc39e2ef11eb6caf1c5t3comeg_" MIME-Version: 1.0

---------------------------------------------------------------------------------------------

when trying to send again to the failing recipient the address in the error message changes
- Edited by Hussein Badran Monday, February 18, 2019 8:14 AM
Monday, February 18, 2019 8:04 AM

Delivery has failed to these recipients or groups:

hussein.badran@outlook.com (hussein.badran@outlook.com)
A problem occurred during the delivery of your message likely due to invalid DNS record configuration. This could be a temporary situation. Please try to resend the message later. If the problem continues, contact your email admin.

Diagnostic information for administrators:

Generating server: mail.t3.com.eg

hussein.badran@outlook.com
Remote Server returned '554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -> DnsDomainIsInvalid: InfoMxLoopback'

Original message headers:

Received: from mail.t3.com.eg (10.10.10.2) by mail.t3.com.eg (10.10.10.2) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1415.2; Mon, 18 Feb
 2019 00:12:45 -0800
Received: from mail.t3.com.eg ([::1]) by mail.t3.com.eg ([::1]) with mapi id
 15.01.1415.002; Mon, 18 Feb 2019 00:12:45 -0800
From: Hussein Badran <hussein.badran@t3.com.eg>
To: Hussien Badran <husseinbadran@gmail.com>, "hussein.badran@outlook.com"
      <hussein.badran@outlook.com>, "Hb@et3.co" <Hb@et3.co>, "hbadran@tra.gov.eg"
  <hbadran@tra.gov.eg>, exchange admin <exchadmin@t3.com.eg>
Subject: Howdy
Thread-Topic: Howdy
Thread-Index: AQHUx2DSgGQ2RkJ55UK00MehHWyUlw==
Date: Mon, 18 Feb 2019 08:12:45 +0000
Message-ID: <3f427c4a4be643dab8d3b2ddf9f9b3ac2f7f5aa6b8024cc39e2ef11eb6caf1c5@t3.com.eg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [81.21.106.117]
Content-Type: multipart/alternative;
        boundary="_000_3f427c4a4be643dab8d3b2ddf9f9b3ac2f7f5aa6b8024cc39e2ef11_"
MIME-Version: 1.0

Monday, February 18, 2019 8:14 AM

0

Sign in to vote
Hi,

It seems like sort of DNS issue. You can use Nslookup tool to verify MX records are configured properly.

Additionally, please check if the send connector is configured correctly. You can run the following command and post the result here with sensitive information hidden.

Get-SendConnector <connector name> |fl

Regards,

Dawn Zhou

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.
Thursday, February 21, 2019 2:26 AM
0

Sign in to vote

Hi,

How is everything going? If there is any update or anything unclear, please feel free to post it here. I'm glad to provide further help.

Regards,

Dawn Zhou

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.

Monday, February 25, 2019 9:56 AM
0

Sign in to vote
Dears

i have the same issue please advise

[PS] C:\Windows\system32>Get-SendConnector internet |fl

AddressSpaces : {SMTP:*;1}
AuthenticationCredential :
CloudServicesMailEnabled : False
Comment :
ConnectedDomains : {}
ConnectionInactivityTimeOut : 00:10:00
ConnectorType : Default
DNSRoutingEnabled : True
DomainSecureEnabled : False
Enabled : True
ErrorPolicies : Default
ForceHELO : False
Fqdn :
FrontendProxyEnabled : False
HomeMTA : Microsoft MTA
HomeMtaServerId : WIN-3E88J3BTPJO
Identity : internet
IgnoreSTARTTLS : False
IsScopedConnector : False
IsSmtpConnector : True
MaxMessageSize : 35 MB (36,700,160 bytes)
Name : internet
Port : 25
ProtocolLoggingLevel : None
Region : NotSpecified
RequireOorg : False
RequireTLS : False
SmartHostAuthMechanism : None
SmartHosts : {}
SmartHostsString :
SmtpMaxMessagesPerConnection : 20
SourceIPAddress : 0.0.0.0
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {WIN-3E88J3BTPJO}
TlsAuthLevel :
TlsCertificateName :
TlsDomain :
UseExternalDNSServersEnabled : False

[PS] C:\Windows\system32>
- Edited by malak.esa Sunday, August 9, 2020 8:09 AM
Sunday, August 9, 2020 7:57 AM

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?

Asked by:

Remote Server returned '554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -> DnsDomainIsInvalid: InfoMxLoopback'

Question

All replies

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?

Asked by:

Remote Server returned &#39;554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -&gt; DnsDomainIsInvalid: InfoMxLoopback&#39;

Question

All replies

Remote Server returned '554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -> DnsDomainIsInvalid: InfoMxLoopback'