pancho15
asked on
Email could not be delivered because the domain name was unresolvable:
Hi,
We have an exhcnage 2007 server with Mailmarshal (for mail scanning) running on the DMZ, we use Active Directory DNS for internal
A number of users have been receiving the following message randomaly (sometimes mail will go and then it will fail again.
Could not be delivered because the domain name was unresolvable:
Unable to resolve route compayxxx.com.au (MX) - *
Our Internal DNs is pointing to our ISP DNS and also using root hints. Not sure what is going on as, I tried running a NSLOOKUP command from both DMZ and Exchange and DNS server and it resolves.... although I noticed the first time I tried it came back with nothing, tried a second time and it resolved.
We only started noticing the problem in the last 2 days (no changes that I'm aware of)
Any ideas?
We have an exhcnage 2007 server with Mailmarshal (for mail scanning) running on the DMZ, we use Active Directory DNS for internal
A number of users have been receiving the following message randomaly (sometimes mail will go and then it will fail again.
Could not be delivered because the domain name was unresolvable:
Unable to resolve route compayxxx.com.au (MX) - *
Our Internal DNs is pointing to our ISP DNS and also using root hints. Not sure what is going on as, I tried running a NSLOOKUP command from both DMZ and Exchange and DNS server and it resolves.... although I noticed the first time I tried it came back with nothing, tried a second time and it resolved.
We only started noticing the problem in the last 2 days (no changes that I'm aware of)
Any ideas?
ASKER
We are using Optus (Uecomm DNS settings)
ASKER
So I should use 8.8.8.8 in the forwarders tab of our DNS server?
Any other settigns I should check?
Any other settigns I should check?
You have to use your ISP DNS, it is the nearest to you. Have you check your firewall? You must resolve the address at the first attempt.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can use your ISP DNS in the forwarder TAB , if you do not have the ISP DNS then you can use above google Public DNS IP address in the DNS forwarded Tab
1) I would first suggest you to check "Use the External DNS Lookup settings on the Transport Server" option under Network tab in Send Connector to check this issue. If the issue persists,
2) Make sure you are running latest Exchnage 2007 2/3 is running on the server
Update Rollup 3 for Exchange Server 2007 SP2 fixes the issues that are described in the following Microsoft Knowledge Base articles:
976108 (http://support.microsoft.com/kb/976108/ ) "451 4.4.0 DNS Query Failed" status message in an Exchange Server 2007 Edge Transport server
Letus know the results.
1) I would first suggest you to check "Use the External DNS Lookup settings on the Transport Server" option under Network tab in Send Connector to check this issue. If the issue persists,
2) Make sure you are running latest Exchnage 2007 2/3 is running on the server
Update Rollup 3 for Exchange Server 2007 SP2 fixes the issues that are described in the following Microsoft Knowledge Base articles:
976108 (http://support.microsoft.com/kb/976108/ ) "451 4.4.0 DNS Query Failed" status message in an Exchange Server 2007 Edge Transport server
Letus know the results.
ASKER
Thanks guys
Will try these and get back
Will try these and get back
ASKER
Thanks, it worked fine with google DNS settings . I assume our Provider was having DNS issues.
If this improves the flow, then it would indicate the issue is with your ISP dns servers.
Are you using Telstra Clear by chance?