Exim or Networking issue

[t9clkclnr]

I have a problem with one of my servers (trtinfo.com) that can't seem to send email to dataproductsplus.com (external domain)

I have another server in the same data center that does not have this problem (ourdedicatedserver.info).
I've disabled APF, (which is installed on both servers) and still no luck.

I've restarted the antirelayd, I've verified the DNS on dnsreport.com for trtinfo.com.
I've added an SPF record to my zone, I've had my upstream provider setup reverse dns & PTR records on both servers.

I've run trace route via mail trouble shoot in WHM, and it can't find host. Timeout's each time.

problematic server:
WHM 10.8.0 cPanel 10.8.1-S114
CentOS 4.2 i686 - WHM X v3.1.0
Intel(R) Pentium(R) 4 CPU 2.66GHz (gig ram)
Exim: exim-4.52-7

server with no issues:
WHM 10.8.0 cPanel 10.8.1-R113
RedHat 9 i686 - WHM X v3.1.0
Dual Intel(R) Pentium(R) 4 CPU 2.80GHz
Exim: exim-4.52-7

Anyone know what i can do fix this?
Mail queue reports this error:
***@dataproductsplus.com R=lookuphost defer (-1): host lookup did not complete
dataproductsplus.com is hosted at rackspace.com

 

[xerophyte]

looks like your server has problem resolving that domain mx record, try to dig inside the server see if you are able to get all the dns info for that domain.

you can grep the whole error message using exigrep dataproductsplus.com /var/log/exim_main

whole error should have much info

 

[t9clkclnr]

Thanks Xero. I wrote the output to a text file.

I looked at the error logs and it doesn't tell me anything i wasn't already privy to.

it only reports the error of host name not found, or cant look up and then it timesout.

Any other ideas?

 

[chirpy]

On the server that doesn't work, does:

dig mx dataproductsplus.com

...give you the same results as when run on the server tat does work?

 

[t9clkclnr]

hey Chirpy..this is what i'm getting

here is the bad server:
; <<>> DiG 9.2.4 <<>> mx dataproductsplus.com
;; global options: printcmd
;; connection timed out; no servers could be reached

here is the good server:

; <<>> DiG 9.2.1 <<>> mx dataproductsplus.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38192
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;dataproductsplus.com. IN MX

;; ANSWER SECTION:
dataproductsplus.com. 86400 IN MX 10 dataproductsplus.com.

;; AUTHORITY SECTION:
dataproductsplus.com. 86400 IN NS ns.rackspace.com.
dataproductsplus.com. 86400 IN NS ns2.rackspace.com.

;; ADDITIONAL SECTION:
dataproductsplus.com. 86400 IN A 64.39.9.39

;; Query time: 134 msec
;; SERVER: 205.234.219.222#53(205.234.219.222)
;; WHEN: Sun Apr 23 13:17:01 2006
;; MSG SIZE rcvd: 115

 

[Lyttek]

have you run (can you?) a shell traceroute on both the DNS and IP address? This would tell you whether it's a DNS issue, a network issue, etc.

 

[t9clkclnr]

Lyttek, here is the dump of the traceroute

doing a traceroute on the domain returns
"unknown host"

running traceroute on the IP returns:
1 vrid.gw.chg.servercentral.net (64.202.115.253) 0.380 ms 0.257 ms 0.225 ms
2 tagged.j1.ord.scnet.net (64.202.111.113) 0.522 ms 0.501 ms *
3 109.so-2-0-0.cr1.ord1.us.nlayer.net (69.31.111.49) 0.559 ms 1.013 ms 0.433 ms
4 eqix.chcg.twtelecom.net (206.223.119.36) 0.987 ms 0.971 ms *
5 core-01-so-0-1-0-0.chcg.twtelecom.net (66.192.244.21) 2.690 ms 1.017 ms 1.270 ms
6 dist-01-so-1-0-0-0.snan.twtelecom.net (66.192.246.22) 30.333 ms 31.067 ms 31.819 ms
7 hagg-01-ge-0-3-0-510.snan.twtelecom.net (66.192.246.137) 32.222 ms 29.150 ms 29.099 ms
8 * * *
9 64.39.2.33 (64.39.2.33) 33.382 ms 33.820 ms 32.405 ms
10 64.39.2.82 (64.39.2.82) 33.903 ms 33.115 ms 33.975 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

is there anything i can do internally to get my server to be able to send emails to this domain?

 

[Lyttek]

If traceroute can't complete the IP route between your computer and the recipient, (which is what I'm reading from all the**** lines) then it's not a problem with your computer; it's a routing issue somewhere on the network.

Do the same traceroutes from a known working location, and see what the results are. It may shed some light on what the breakdown may actually be.

 

[t9clkclnr]

Thanks for your Help Lyttek

I am going to contact RackSpace.com today to see if they can look a little deeper as to what is happening.

I will post my findings for anyone in need.