Not able send email to any of AOL users

[crazyaboutlinux]

yes, it is showing the same please check below details


[root@saturn ~]# dig aol.com mx @resolver.qwest.net

; <<>> DiG 9.2.4 <<>> aol.com mx @resolver.qwest.net
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9031
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 17

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

;; ANSWER SECTION:
aol.com. 1334 IN MX 15 mailin-03.mx.aol.com.
aol.com. 1334 IN MX 15 mailin-04.mx.aol.com.
aol.com. 1334 IN MX 15 mailin-01.mx.aol.com.
aol.com. 1334 IN MX 15 mailin-02.mx.aol.com.

;; AUTHORITY SECTION:
aol.com. 1334 IN NS dns-02.ns.aol.com.
aol.com. 1334 IN NS dns-07.ns.aol.com.
aol.com. 1334 IN NS dns-01.ns.aol.com.
aol.com. 1334 IN NS dns-06.ns.aol.com.

;; ADDITIONAL SECTION:
mailin-02.mx.aol.com. 2733 IN A 205.188.155.72
mailin-02.mx.aol.com. 2733 IN A 205.188.249.91
mailin-02.mx.aol.com. 2733 IN A 64.12.137.89
mailin-02.mx.aol.com. 2733 IN A 64.12.138.120
mailin-03.mx.aol.com. 183 IN A 205.188.109.56
mailin-03.mx.aol.com. 183 IN A 205.188.252.17
mailin-03.mx.aol.com. 183 IN A 64.12.138.153
mailin-04.mx.aol.com. 185 IN A 64.12.138.57
mailin-04.mx.aol.com. 185 IN A 64.12.138.88
mailin-04.mx.aol.com. 185 IN A 205.188.159.216
mailin-01.mx.aol.com. 34 IN A 64.12.139.249
mailin-01.mx.aol.com. 34 IN A 205.188.156.248
mailin-01.mx.aol.com. 34 IN A 205.188.159.57
dns-07.ns.aol.com. 297 IN A 64.236.1.107
dns-06.ns.aol.com. 3269 IN A 149.174.54.153
dns-02.ns.aol.com. 3360 IN A 205.188.157.232
dns-01.ns.aol.com. 41680 IN A 64.12.51.132

;; Query time: 9 msec
;; SERVER: 205.171.3.65#53(205.171.3.65)
;; WHEN: Mon Mar 9 20:01:29 2009
;; MSG SIZE rcvd: 491

[sparek-3]

What is the contents of the /etc/resolv.conf file?

You really need to check with your datacenter and see what DNS resolvers you are suppose to be using. If you are using the correct ones that your datacenter says that you should be using, then you should point out that they are not resolving AOL's MX records properly.

Alternatively, you can use OpenDNS's DNS servers, although if your datacenter has an in house DNS server, then it is probably best to use it.

[mtindor]

yes, it is showing the same please check below details


[root@saturn ~]# dig aol.com mx @resolver.qwest.net

<SNIP>

Ok, you did that - now do dig aol.com mx (all by itself) - Then compare it with dig aol.com mx @resolver.qwest.net. You'll see the difference. As they keep mentioning to you, you have a problem with your resolvers.

Sparek-3 asked what you have in /etc/resolv.conf. One or both of the nameservers listed in your /etc/resolv.conf are either not resolving properly or are set up to not answer your queries. You must speak to your provider about that.

When your machine attempts to look up the MX records for AOL.com, it contacts [or attempts to contact] the servers listed in your /etc/resolv.conf. If those resolvers don't have valid information [or won't return it because of the way they are configured], then you won't get any useful results when you do a dig either.

Mike

[crazyaboutlinux]

What is the contents of the /etc/resolv.conf file?

You really need to check with your datacenter and see what DNS resolvers you are suppose to be using. If you are using the correct ones that your datacenter says that you should be using, then you should point out that they are not resolving AOL's MX records properly.

Alternatively, you can use OpenDNS's DNS servers, although if your datacenter has an in house DNS server, then it is probably best to use it.

Below are conents of the /etc/resolv.conf

[root@saturn ~]# vi /etc/resolv.conf
nameserver 69.72.212.42
nameserver 69.72.212.43
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
"/etc/resolv.conf" 2L, 48C

[Pixelpirat]

Both nameserver doesn't resolve any domain out of there authoritative domainzones.
Use two other nameservers and ask your datacenter which a request forwarden to resolve the request.

HTH
Pixelpirat

[mtindor]

It looks like those nameservers listed in your /etc/resolv.conf are bound to your own server. That means that your machine uses its own nameservers for DNS resolution.

i'm thinking that you might have a situation where you are running CentOS 5.x and that "named" is probably running with some funky views . You might have to do some work on your bind (named) to get it to work properly resolving domains internally and externally.

Mike

[crazyaboutlinux]

now finally let me know what to do in order to resolve this issue permanently

& do i need to inform our DC

Nilesh

[mtindor]

Finally let you know? I don't think so man. We've been more than generous attempting to help you with your problem. But you're the one who is a server admin. You have got to figure these things out.

We've pointed you in the right direction but can't just solve every problem, especially with no access and for no money. That's not the way the world works I think we've attempted to help you as best we can.

Your /etc/named.conf likely needs modified so that named is configured to allow your machine to do recursive lookups via its own nameservers. Need to make sure your named.conf is configured properly and that you aren't blocking any DNS query ports.

Mike

[crazyaboutlinux]

oh i c

Thanks MiKe & thanks a lot to all generous

I'll do that & let you know once i get it done

Thanks again

byee