castroe5
asked on
When I type my mail ip on MXtoolbox.com, I get timeout errors from three diffrent blacklists. how can I clear out these errors.
Everytime I send to an email account such as comcast, sbcglobal, and cox, I get delivery failures from my exchange server.
ASKER
On my DNS server, how do I check the forwarders?
ASKER
I was able to check the forwarders and my DNS servers were not listed. I added my DNS servers to the list. I hope that fixes the problem. What else can I check that could be causing this?
ASKER
thank you for your advise TEKserver
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
From my exchange box, I was unable to ping those comcast and cox mail servers such as mx1.comcast.net, mx2.comcast.net. I tried the corresponding ip address and it also failed. Therefore I have a dns and routing issue. how can I fix the routing and dns problem? What is a good start?
ASKER
The response gave me insight but was not an accurate solution.
Well, had you not impatiently closed the question with a "B" grade, I probably would have tried to continue helping you troubleshoot the problem. It would most likely have looked something like this:
*********
Did you try the telnet tests? As I hinted at before, your router/firewall may be blocking outgoing pings. It's also possible that the mail servers you're pinging are configured not to respond to pings themselves (not an uncommon way to protect against Ping Flood type attacks).
If you still can't reach the mail servers by IP address using telnet on port 25, then you have a routing or port blocking problem - NOT a DNS problem. Don't waste your time trying to chase DNS settings and resolutions; you're better off troubleshooting the routing. Check your router for any settings that might be blocking or misdirecting traffic. Also, a program such as PingPlotter can help run traceroutes on non-standard ports (like port 25, for instance) to see where the route is failing. You can also try the telnet test on port 110 (POP), to see if port 25 is being blocked. And it's probably a good idea to contact your ISP and get them to help troubleshoot; ISP's will usually only block port 25 inbound on residential connections (to prevent users from running mail servers at cheaper residential rates rather than commercial rates), but they may know something or be able to find something that will help.
*********
But, since the question is already closed, I guess I won't post that ...
;)
(Seriously, though, thanks for the Accept, even if it was only grade "B", and good luck!)
*********
Did you try the telnet tests? As I hinted at before, your router/firewall may be blocking outgoing pings. It's also possible that the mail servers you're pinging are configured not to respond to pings themselves (not an uncommon way to protect against Ping Flood type attacks).
If you still can't reach the mail servers by IP address using telnet on port 25, then you have a routing or port blocking problem - NOT a DNS problem. Don't waste your time trying to chase DNS settings and resolutions; you're better off troubleshooting the routing. Check your router for any settings that might be blocking or misdirecting traffic. Also, a program such as PingPlotter can help run traceroutes on non-standard ports (like port 25, for instance) to see where the route is failing. You can also try the telnet test on port 110 (POP), to see if port 25 is being blocked. And it's probably a good idea to contact your ISP and get them to help troubleshoot; ISP's will usually only block port 25 inbound on residential connections (to prevent users from running mail servers at cheaper residential rates rather than commercial rates), but they may know something or be able to find something that will help.
*********
But, since the question is already closed, I guess I won't post that ...
;)
(Seriously, though, thanks for the Accept, even if it was only grade "B", and good luck!)
So if those are the only errors you see in the MXToolBox report, then you don't have a blacklist problem. Check your DNS server that serves your Exchange box, and make sure its forwarders are configured correctly so that the Exchange box can resolve external domains correctly.
:)