Approved: Fortect
You may find an error indicating that it is displaying the dnsconnectordelivery 2007 error exchange. There are a number of steps you can take to resolve this issue, so let’s talk about that now.
- 2 minutes to read.
-
- Applies to:
- Exchange Server 2013 Enterprise, Exchange Server 2013 Standard Edition, Exchange Server 2010 Enterprise, Exchange Server Next Year Standard, Exchange Server 2016 Enterprise Edition, Exchange Server Standard 2016 Edition
Error Sending Emailonline Mail For Some Remote Domains
This issue can occur if the remote DNS servers ignore the AAAA request or return an unexpected response.
To work around this issue, create assigned remote domains for the ribbon. (Create a connector redirector for each domain). Then, no doubt, configure Send connectors to use the remote domain’s email web host as an efficient host. To do this, follow these steps:
- Check the IP address of the MX movie (mail server) for the affected remote zone. Use or nslookup Look up MX records .
- Create a new connector for this domain. Make sure to configure the settings:
- In the Address Store section, add the affected remote domain, such as contoso.com.
2. In the network settings, select the smart mail routing option using the following types. Usually add the IP address of the MX record that you verified in your personal step.
You can use the default for other settings. AdditionalFor details, see Configuring a Dedicated Send Connector for a Specific Domain .
As you can see, when Exchange Server sends email to this type of remote domain, it bypasses the request DN and directly connects to the remote domain’s web email server using the IP address.
When You Email Me On All Remote Problem Domains, An Error Occurs
This can happen because the DNS server used by Microsoft Exchange Server is down. By default, Exchange uses the DNS settings on the server’s network adapter to route outgoing remote e-mail.
To resolve this issue, troubleshoot a new local DNS server or configure an external DNS server to route mail remotely. Follow these steps to configure an external DNS server to remotely manage mail routing:
-
Open the Properties page of the Exchange server that owns the Send connector, then add most of the DNS IP address for public. servers < / a> addparameter for external DNS lookup.
-
Select the option “Use exact lookups for external DNS settings on servers, and the option for transport role in the connector that is responsible for the most important remote routing.”
-
Question
-
I have a problem sending emails to a specific trusted domain.
Let’s call it the problem domain for discussion.
I can only give and receive names from others.
I am using SBS 2008 with Exchange 2007
I am using DNS to getAnd I also checked the box on the Network tab of the Send Detector Network tab to use the external transport DNS lookup settings for the DNS server that is on the DNS server of my ISP board.
When I open nslookup from this command line, I get
C: Windows system32> nslookup
standard server: unknown address
: fe80 :: 1d11: 6c69: c59: 9c72so I say use it for IP
> Server 10.202.2.220
Standard Server: [10.202.2.220]
Address: 10.202.2.220> eauctions.ie
Server: [ 10.202 2.220]
Address: 10.202.2.220Answer:
unauthorized name: problem domain.ie
Address: XX.XXX.XXX.XX <- the correct It-IPand dissolves well.
When I check the connection log, I see the following image
CC9CC817F1FDB6, SMTP, problemdomain.ie, +, 97d0d5db-0bc1-426d-b9e4-347c59db8bbe
2010-03-29T12: 00: 35.914Z, 08CC9CC817F1FDB6, SMTP, euctions, euctions, t,> .e. 85.91.1.129 process
2010-03-29T12: 00: 35.914Z, 08CC9CC817F1FDB6, SMTP, problemdomain.ie, -, DNS query for ‘DnsConnectorDelivery’: ‘problemdomain.ie’: ’97d0d5db-0bc1 – 426d-b9e4 – 347c59db8bbe ‘failed with error: ErrorRetryThen I see that his Sen SMTP connector is using the external server’s DNS, no cannot connect to the server.
If I then put this particular server in nslookup to manage the insert, I get the following
C: Windows system32> nslookup
Standard Server: Unknown
Address: fe80 :: 1d11: 6c69: c59: 9c72> Server 85.91.1.129
Default server: [85.91.1.129]
address: 85.91.1.129> collection q = mx
> problemdomain.ie
server: [85.91.1.129]
Address: 85.91.1.129Unauthorized response:
problemdomain.ie MX preference is 10, mail = Exchanger smtpxx.cp.irishdomains.co
mApproved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
- 1. Download Fortect and install it on your computer
- 2. Launch the program and click "Scan"
- 3. Click "Repair" to fix any issues that are found
problemdomain.ie nameserver = ns1.irishdomains.com
problemdomain.ie nameserver means ns2.irishdomains.com and smtpxx.cp.irishdomains.com Internet Address = XX. XXX.XXX. XX
ns1.irishdomains.com Internet Address = XX.XXX.XXX.XX
ns2.irishdomains.com Internet Address = XX.XXX.XXX.XX
>So I seem to agree with the non-NS lookup command line version, but not the one specifically used by Exchange
Anyone have any ideas?
Regards,
Albert
The Answers
-
FIXED!
I don’t knowwhich was fixed, but I think it was a DNS dilemma
I found that the mail server IP solution stored in my DNS cache is not correct.
Although I assumed I had external DNS lookup enabled, it was disabled when it was disabled again.
I found this post asking me to clear the cache on your current DNS server
http://blog.brainlitter.com/archive/2009/06/19/exchange-2007-difficulty-delivering-email-to-some-domains-%E2%80%93-error-451-4- 4-0-dns-query-failed.aspx
Then I checked the SMTP Send Connector setup and found the Secondary DNS was not checked, as soon as I checked the product again the message was delivered
>
2010-03-29T14: 13: 16.269Z, 08CC9D5838032365, SMTP