community.spiceworks.com
Open in
urlscan Pro
45.60.13.212
Public Scan
URL:
https://community.spiceworks.com/topic/404215-dns-records-for-this-domain-are-configured-in-a-loop
Submission: On August 18 via manual from US — Scanned from DE
Submission: On August 18 via manual from US — Scanned from DE
Form analysis 1 forms found in the DOM
<form>
<i class="1692368322052 mag-glass"></i>
<input class="1692368322052 search-input" autocomplete="off" placeholder="Search Spiceworks">
<i class="clean-icon"></i>
<div class="1692368322052 trending-topics"></div>
<div class="1692368322052 search-box-results"></div>
</form>Text Content
Home * News & Insights * News & Insights Home * Artificial Intelligence * Innovation * IT Careers & Skills * Cloud * Cyber Security * Future of Work * All Categories * Marketing * HR * Finance * Community * Ask question * Community Home * Spiceworks Originals * Cloud * Collaboration * Networking * Water Cooler * Windows * All forums * How-Tos * Scripts * Vendors * Meetups * Reviews * Online Events Login Join Login Join * Home * Collaboration * Microsoft Exchange DNS RECORDS FOR THIS DOMAIN ARE CONFIGURED IN A LOOP Posted by Chad.w on Nov 5th, 2013 at 9:27 PM Microsoft Exchange We are seeing the following error on our Exchange 2010 SP3 server. This server is the only server in the company. "5.4.4 SMTPSEND.DNS.MxLoopback; DNS records for this domain are configured in a loop" The domain in question is our internal authoritative mail domain not an external mail domain. We have split DNS and DO NOT have MX records for any of our domains internally. Our default send connector is set to use DNS, not external DNS lookup settings on the transport server. We only get these error messages when an automation account we created tries to send an e-mail from a web app to an internal recipient. We do not have any issues with incoming mail from the internet, outgoing mail to the internet, allowed to relay receive connector relaying or internal e-mail. Any ideas? Would adding internal MX records resolve this or make it worse? Spice (2) Reply (12) flagReport Chad.w This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. habanero POPULAR TOPICS IN MICROSOFT EXCHANGE M365 Quarantine Policies Outlook desktop app will not allow encryption Exchange on-prem and Global Catalog Server error Resource Mailbox Owners Can No Longer Edit Events Multiple exchange server coexistence View all topics 12 REPLIES * mmoore12 This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. tabasco Nov 5th, 2013 at 9:54 PM Is it an external web app? Do you have a different internal domain name or is it the same? If it's an internal web app does it use an internal SMTP server (on IIS for instance) or the Exchange server? flagReport Was this post helpful? thumb_up thumb_down * OP Chad.w This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. habanero Nov 5th, 2013 at 10:09 PM The web app is internal running on a server in the domain. From what I understand, and I am not a developer, the application is authenticating to the exchange server with an account and sending mail that way. So not using relay. flagReport Was this post helpful? thumb_up thumb_down * mmoore12 This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. tabasco Nov 5th, 2013 at 10:16 PM It makes you wonder how the recipient email address is formatted by your web app. Is it using an external address format or internal? Are they the same? (I might be grasping a bit). flagReport Was this post helpful? thumb_up thumb_down * OP Chad.w This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. habanero Nov 5th, 2013 at 11:11 PM Just spoke with my development team and I think we are starting to gravitate toward a place where we think the issue exists. We are starting to think that it is an issue with one or more of our receive connectors. We have two that deal with SMTP traffic, the default receive connector which is configured the way it was during installation and a custom "Allowed to relay" connector that I created which is externally secured by IP address per this article Opens a new window. Another thing that is interesting is that these apps can actually send e-mail via this method without error, the error seems to come up when an NDR condition is run into. I have my team looking at spelling and e-mail addresses. Also, this article Opens a new window, though describing a different problem, describes how the receive connectors can get into a loop. So we are looking at that too. It makes me think it is less related to DNS / MX records and more to do with something being non-deliverable and looping back and forth to the internet to resolve. flagReport Was this post helpful? thumb_up thumb_down * mmoore12 This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. tabasco Nov 5th, 2013 at 11:22 PM NDR makes sense. I have seen this before where the Primary address is set as the SMTP routing address but this was incorrect and causing NDRs. Once the Routing address issue was fixed the NDRs went away. flagReport Was this post helpful? thumb_up thumb_down * OP Chad.w This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. habanero Nov 5th, 2013 at 11:26 PM Michael, Can you elaborate a bit more on what you mean? Where would I look into this? flagReport Was this post helpful? thumb_up thumb_down * mmoore12 This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. tabasco Nov 6th, 2013 at 2:32 PM In the Exchange Management Console under Recipient configuration, go to Mail Contacts (not mailbox) and find the problem recipient. Open the recipient properties. Click the email addresses tab and look for the routing email address entry. Does it conform to your domain standards? We had a user that appeared to me to have the wrong routing email address so I deleted it and changed it to be the same as their primary email address. Immediately the NDRs starting showing up in relation to this email address. I went back to the routing email address entry and tried all the possible address combinations until I found one that made it work again. flagReport Was this post helpful? thumb_up thumb_down * OP Chad.w This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. habanero Nov 7th, 2013 at 5:07 PM Thanks for the reply Michael. Our recipient is not a mail contact so I don't think this is our issue. flagReport Was this post helpful? thumb_up thumb_down * mmoore12 This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. tabasco Nov 7th, 2013 at 5:12 PM In Exchange 2010 all mailboxes and contacts are listed under Mail Contacts even if they're also under Mailboxes. It seems the only way you can view the email routing address is by viewing email addresses under Mail Contacts. flagReport Was this post helpful? thumb_up thumb_down * OP Chad.w This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. habanero Nov 7th, 2013 at 5:21 PM Weird. I don't see regular mailboxes in mail contacts and even for the contacts we have, I do not see any routing address field. Just SMTP, External and X400. flagReport Was this post helpful? thumb_up thumb_down * * mmoore12 This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. tabasco Nov 7th, 2013 at 5:31 PM My bad. We have a hybrid environment. This attribute only appears on the remote mailboxes, not local ones. Should have looked further. But as I said earlier it did fix the problem I was having. Sorry for being unhelpful. I think generally it's the right idea to believe that there's a problem with the recipient address, but obviously this cause doesn't apply to your environment. You may want to pull up your problem recipients in ADSIEdit and look at your problem recipient's proxyaddresses value or use Attribute Editor in ADUC. flagReport Was this post helpful? thumb_up thumb_down * OP Chad.w This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. habanero Nov 7th, 2013 at 5:35 PM You are not unhelpful at all and I thank you for your efforts here. It may come down to something really silly like a mispelled recipient or something else. It may also be that they are trying to deliver to a recipient that we do not have "donotreply@ourdomain.com" comes to mind. Right now the developers are looking into it more on their end as this is only happening with workflow they created. flagReport Was this post helpful? thumb_up thumb_down lock This topic has been locked by an administrator and is no longer open for commenting. To continue this discussion, please ask a new question. READ THESE NEXT... * IT DOCUMENTATION Best Practices & General IT Hi i am looking for an it documentation tool (open source) , what is there out there what we can use? this should be used for all the it instructions inside our departments. * * CYBER SECURITY ON PREMISES VS CLOUD Security I understand that the top three attack vectors which account for 99% of breaches are the following: Stolen Passwords which is an issue as people tend to re-use same passwords on many sites Phishing Attacks especially email such as BEC Vulnerability Expl... * SPARK! PRO SERIES - AUGUST 18, 2023 Spiceworks Originals Today is a special day. It is a day to celebrate getting up when you fall, dusting yourself off and starting again. Officially known in the United States as "Never Give Up" day, it is a day to remind yourself and others that success comes when you fight f... * DESKTOP POWER-UP ISSUE DESPITE VERIFIED PSU FUNCTIONALITY Hardware Good evening members of the SpiceWorks community,I find myself in a situation where I am encountering a challenge with a customer's desktop computer. The system fails to power on when the power button is pressed. After conducting diagnostic tests, I hav... * OFFICE 365 NOW REQUIRING MULTI MULTI FACTOR AUTHENTICATION Cloud Computing & SaaS We have noticed admins in Office 365 are being required to setup MFA with text AND The MS authenticator app.We are also experiencing some end users getting prompted to setup the app after Authenticating with a text.Ive had a ticket in with MS for a few we... * About * Contact * Support * Press / Media * Careers * SpiceWorld * Blog * * * * * * Sitemap * Privacy Policy * Terms of Use * Guidelines * Accessibility Statement * Do Not Sell My Personal Information * © Copyright 2006 - 2023 Spiceworks Inc. WE CARE ABOUT YOUR PRIVACY If you consent, we and our partners can store and access personal information on your device to provide a more personalised browsing experience. This is accomplished through processing personal data collected from browsing data stored in cookies. You can provide/withdraw consent and object to processing based on a legitimate interest at any time by clicking on the ‘Manage Preferences’ button.Our Privacy Policy WE AND OUR PARTNERS PROCESS DATA TO: Store and/or access information on a device. Personalised ads and content, ad and content measurement, audience insights and product development. Our Partners Reject All I Accept More Options