MX Record

I would like to forward email coming into the domain ycbc.org to a mail server on a fixed IP address. Below is a copy of the MX record. We are attempting to get mail addressed to anyone@ycbcorg to go to the 209.222.26.117 it keeps resolving to 64.177.197.111 whenever I ping mail.ycbc.org. I am not more than a beginner when it comes to server admin (probably a good example of who not to give su access to)so any basic instructions on what I could be doing wrong would be appreciated. By the way I also did a name server reload.

ycbc   IN   SOA  ns.gghosting.com. hostmaster.gghosting.com. (
                200209117 86000 7200 3600000 600 )
                IN      NS      ns.gghosting.com.
                IN      NS      ns2.gghosting.com.

                IN      A       64.177.197.111
                IN      MX      10 mail.ycbc.org.
$ORIGIN ycbc.org.
mail            IN      A       209.222.26.117
ftp             IN      A       64.177.197.111
www             IN      A       64.176.204.105
gilman01Asked:
Who is Participating?
 
jlevieConnect With a Mentor Commented:
I don't see a problem from here. Consider the following:

chaos> host -t ns ycbc.org
ycbc.org. name server NS2.GGHOSTING.COM.
ycbc.org. name server NS.GGHOSTING.COM.

So you are the authoritative DNS for the domain...

chaos> host -t mx ycbc.org
ycbc.org. mail is handled by 10 mail.ycbc.org.

The MX record looks correct...

chaos> host mail.ycbc.org
mail.ycbc.org. has address 209.222.26.117

and the address is correct. There could be a problem with some Internet mail servers because:

chaos> host 209.222.26.117
Host 117.26.222.209.in-addr.arpa. not found: 3(NXDOMAIN)

obviously doesn't return mail.ycbc.org. Paranoid mail servers may reject email sent out from your mail server because of the lack of a reverse lookup that point back to your server. Another possible problem is that the actual mail server's hostname is ycbc_nt01.ycbc.org, which isn't what the MX record points to. Some anti-spam configurations are going to refuse mail from a server that isn't listed as being an MX host for the domain.

So it looks like DNS is working as it should. Perhaps you are looking at cached data? Or perhaps a local hosts file record that points to the wrong IP?
0
 
gilman01Author Commented:
Thanks - I appreciate knowing I did it correctly. The clients are reporting they are getting email this morning. Now I still try to ping mail.ycbc.org and get the 64.... address and not the 209.... adddress - go figure. Anyway I subscribe to the old school "if it aint broke don't fix it" and just happy they are getting their email.

0
 
jlevieCommented:
Have you checked to see if the system you are trying to ping from has local hosts records that point to the old address?

If it's a windows box have you rebooted since the change in the nameserver data?
0
 
gilman01Author Commented:
We are hosting the domain name on our server and just trying to point the MX record to their mail server which is in the buidling. Haven't a clue what they have running just got the IP address from the tech.

We started out with the understanding we were just parking it under another domain they have hosted on our server and suddenly found out they wanted email from this domain forwarded to their mail server - surprise - you know how that goes.

I did reload my nameserver. It could be it just took that long to propogate - and I am not sure how my server handles all this so I'm going on faith that it works. I guess the real test will be when I have to do it again.

Thanks again for your response.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.