DNS Query Timeout

I have an email stuck in our outbound box on our exchange server 2010 (server 2008). It says DNS Query Failed. The .com is pipelineresourcesinc.com, so I did a nslookup on it, and I get this.

Server:  ntdc.alanritchey.loc
Address:  192.168.0.xxx

DNS request timed out.
    timeout was 2 seconds.
Name:    pipelineresourcesinc.com
Address:  64.118.87.14

So it resolves correctly, but it is timing out. We only have the one dns server and all other addresses resolve w/o this timeout (ie. google.com, abc.com, msn.com...). What is odd is that from my client pc and another server, it resolves correctly no timeout or anything.

I've done a ipconfig /flushdns and ipconfig /registerdns with no luck. Also I have disabled ipv6 as we are not using it.

This server is also a DC but does not handle DNS. I am not seeing anything related in the event viewer on either box.
bhiebAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bobsolfCommented:
You could give this a try...
On your server, open the DNS manager  (Admin Tools, DNS).
In the left pane of the console, Right-click on the server name and select properties from the menu.

Click the tab for Forwarders.
Select (single-click) the first forwarder in the list, then click the "edit" button at the bottom of the dialog box.  
You can then edit the number of seconds before queries timeout.  

You could also add another forwarder to a public DNS server (for example, you could add 8.8.8.8 for Google's DNS server).

Not sure if this will resolve your problem (no pun intended!), but it's worth a shot!

-BOb
bhiebAuthor Commented:
It may, but I'm curious as to why it is just this domain. The server is not under any load with only 70 users, and the email has been retrying all day so even if there was a high load once, it should go through fine the next time. I would take your approach as kind of a last resort one, as I'd rather get to the rood cause of why this particular .com is behaving odd, and only for this one server.

Is there something specific to server 2008 that I need to do to flush the dns? It appeared to go through fine.
bobsolfCommented:
Perhaps the nameserver holding the master lookup zone for that domain is having some connectivity issues or a heavy load, not your server.  It's possible that it is timing out, and then giving you the IP address already in your server's cache.

I understand wanting to get to the root of the issue, I just figured I'd make a suggestion to see if it would work for you.  

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bhiebAuthor Commented:
Must have been an issue with the server as a reboot of the mail server fixed it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.