agentkolb
asked on
Delivery Delayed e-mails/DNS issues?
Just replaced my Exchange 2003 box with Server 2008 and Exchange 2010. Ever since doing that A few emails sent out of my domain to others seem to come back Delivery Delayed. They do eventually go through and never come back failed but they do tend to stick in the queue for almost a day sometimes.
The biggest culprits are yahoo.com and aol.com emails. In my queue they show up as 451 4.4.0 DNS query failed. When I attempt an nslookup -q=mx yahoo.com (or aol.com) both come back as timing out.
Thoughts?
The biggest culprits are yahoo.com and aol.com emails. In my queue they show up as 451 4.4.0 DNS query failed. When I attempt an nslookup -q=mx yahoo.com (or aol.com) both come back as timing out.
Thoughts?
ASKER
I get the nslookup from anywhere in my organization, however when i run it - it looks like it goes back to the exchange server to run it because it references that IP address... but that could be because my DNS is also on that server...
You are running DNS on your Exchange server? Is it also your AD controller?
ASKER
Unfortunately. Down the road we will be changing that - but for now it is all on that one server.
Is your DNS integrated into AD? Your AD controller needs to be pointing to itself for AD to work. You need to be forwarding all non-internal lookups externally, normally through your ISP. Is that how your server is configured?
Justin
Justin
ASKER
It is pointed to itself, where do i need to check to verify external requests are going elsewhere?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Now, that said, you should be able to get resolution to the external domains through NSLOOKUP. Do you get that failure from everywhere in your organization, or just from your Exchange server?
Justin