DNS problem?

By lrobinson ·
We have 1 exchange 2003 server. Out of nowhere one day we stopped receiving emails from some, but not all, domains (internal emails worked fine). Also, outgoing emails seemed to get stuck in queues for longer than normal.

I checked message tracking for expected incoming emails but found nothing. My first guess was that there was a DNS problem. Our domain hosting company assured me that all DNS settings were correct, but our ISP said we were missing a reverse DNS record. They added the record at that time. According to the ISP there was no maintenance or configuration changes of any kind recently and more than likely the reverse dns was just never there. We have been using this ISP for months, and never had any problems previously--could that be true?

Atleast a week later most email communication is working fine, but still some domains cannot reach us or we recieve emails up to a day and a half late. I am certain this must be DNS related as I had someone send a bounceback message to my personal account which stated: "Failed to connect to the recipients mail server. No DNS information was found for the '' domain."

Can anyone offer an explanation of what might have caused this problem out of nowhere? What about a solution for the domains that still can't reach us or outgoing emails that are stuck in the queues longer than they should be? Also, the outgoing emails that are in the queue longer than normal are going to the domains we have trouble receiving from.

Thanks in advance!

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Fix your DNS problems..

Fix your DNS problems.

If you're having problems Web surfing, you may have a DNS problem. Here are quick ways to fix it.
DNS, though, can be your foe as well as your friend. DNS problems may stop you from being able to visit Web sites. If you're having problems connecting, it doesn't take much work to see if DNS is the cause, and if it is, to try to fix it.
To find out whether DNS is a potential culprit when you're having trouble connecting to a site, first ping the site to which you can't connect by issuing the ping command at the command prompt, like this:
If the site is live, you'll get an answer like this
[ with 32 bytes of data:

Reply from bytes=32
time=22ms TTL=235
Reply from bytes=32
time=23ms TTL=235
Reply from bytes=32
time=23ms TTL=235
Reply from bytes=32
time=24ms TTL=235

Ping statistics for
Packets: Sent = 4, Received = 4,
Lost = 0 (0% loss),
Approximate round trip times in
Minimum = 22ms, Maximum = 24ms,
Average = 23ms
If it's not, you'll get a response like this:
Ping request could not find host.
Please check the name and try again.
If you ping a site and it's live but you can't connect to it with your browser, a DNS problem might be the reason. If you suspect you're having a DNS problem, take the following actions:
Check your HOSTS file
If your HOSTS file contains an incorrect or outdated listing, you won't be able to connect. Even if you don't recall adding listings to a HOSTS file, it still might contain listings, because some Internet accelerator utilities edit them without telling you. Open your HOSTS file with Notepad and see if the site you can't connect to is listed there. If it is, delete the entry, and you should be able to connect.
For details about editing a HOSTS file, see "Hack DNS for lightning-fast Web browsing."
Check your DNS settings
Make sure your DNS settings are correct for your ISP or network. If you've changed your DNS settings to use a service such as OpenDNS, for example, you might have entered them incorrectly.
Find out from your ISP or network administrator what your DNS settings are supposed to be, or check the OpenDNS site (or another DNS service) for their server settings. Once you've done that, you'll need to make sure that you've entered the DNS settings properly.
Check the article "Hack DNS for lightning-fast Web browsing" for details about how to change your DNS settings. Then change the DNS servers to the proper ones, or choose "Obtain DNS server address automatically" if your ISP or network administrator tells you to use that setting.
Flush your DNS cache
The problem might be related to your DNS cache, so flush it out. To flush the cache, type ipconfig /flushdns at a command prompt.
Find out if your ISP is having DNS problems
Your ISP could be the source of the problem. One possibility is that one of its DNS servers is down and you're trying to access the downed server. If you know the addresses of the DNS servers, ping each of your ISP's DNS servers, and if any of them don't respond, remove them from your DNS list.
If you don't know the address of the DNS servers and you're supposed to use the choose "Obtain DNS server address automatically" setting, you'll have to call your ISP to see whether its DNS servers are having problems. Alternately, you can use the OpenDNS servers instead of your ISP's DNS servers. For details, see "Hack DNS for lightning-fast Web browsing."

Please post back if you have any more problems or questions.

Collapse -

Are there any specific bounce messages?

by Selltekk In reply to DNS problem?

We had a similar issue. Upon further investigation we found that the sender (outside our domain) was getting error 550 bounce messages.

If this is the case, you may find some useful information here:

Hope this helps.

Related Discussions

Related Forums