Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sending delayed - DNS query failed

Status
Not open for further replies.

biglebowski

Technical User
Jan 29, 2004
3,117
GB
I have just migrated from SBS 2003 to SBS 2008 and now intermittently we are getting delayed delivery messages. They seem to be for the same destination domains but do not happen all the time. If left the messages will eventually be received at the destination but can take up to 24 hrs. It is only affecting outgoing messages. I've had a look at the MS technote for the error but this didn't help.

451 4.4.0 DNS Query Failed

weight.png
 
I've just done dns lookups for some of the domains and can't ping the domains or telnet on port 25 to any of the destinations. Do i need to add our ISPs DNS servers to Microsoft Exchange > Server Configuration > Hub transport for the external lookup? It's a single NIC server.

weight.png
 
well added them anyway and it's made no difference. Just about had enough of sbs 2008 now, it's been nothing but a pain in the arse since it went in.

weight.png
 
Can you lookup the MX records using external DNS sources? If so, can you telnet to them and get a reply? If either is no, it's not a server problem.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
I used to lookup the mx records for the domains and tried to ping/telnet the various names listed. This was never an issue with sbs 2003 and has only started occurring since migrating to 2008.

ps If I test this from home it works ok (ping & telnet)

weight.png
 
Using network-tools.com doesn't do anything for you. You need to do the lookups from the server. Then try telnetting. Ping means nothing. NOTHING.

You must be able to telnet and successfully send a test message completely before we can look at the server as a cause.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Well all the queues have cleared and emails have been sent. I've done nothing to fix this and DNS is still screwed:

C:\Users\administrator.OFFICE>nslookup
Default Server: UnKnown
Address: fe80::fb0b:xxx:xxxx:xxxx

C:\Users\administrator.OFFICE>nslookup xxxxx.co.uk
Server: UnKnown
Address: fe80::fb0b:xxx:xxxx:xxxx
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: xxxxx.co.uk
Address: 213.121.xxx.xxx


C:\Users\administrator.OFFICE>nslookup xxxxx.com
Server: UnKnown
Address: fe80::fb0b:xxx:xxxx:xxxx

Name: xxxxx.com




weight.png
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top