gpicart
asked on
What fqdn to provide to isp to setup reverse dns
I have been asked by our ISP to send in the IP and fqdn for the server I want the reverse dns set up for. Now, our email domain is domainname.com but when I go through the owa I use the mail.domainname.com that I created during the a record creation. So my question is do I give them the fqdn domainname.com or the A record name mail.domainname.com?
Hypercat (Deb)
It depends on the purpose of the PTR record. If you are doing it to comply with anti-spam requirements, as I suspect you are, you want the PTR to resolve to your mail server's FQDN. That would be mail.domainname.com.
ASKER
Im doin it because messages sent out from out mail server get tagged as spam when going to certain domains, such as gmail
ASKER
So I understand that for the reason I discribed above "Im doin it because messages sent out from out mail server get tagged as spam when going to certain domains, such as gmail" I should use the mail.domainname.com not the domainname.com. Is this correct?
Yes, that's it exactly. I guess I should add a caveat: I'm also assuming that this is what your Exchange server uses in its email header. That would be important, because if your Exchange server isn't using your correct (public) FQDN in the header, then the PTR record won't solve your problem. If you're not sure about this, to check it open the ESM, expand the levels under your server name until you see your SMTP virtual server object; right-click, go to Properties, then go to the Delivery tab. On that tab, click the Advanced button and make sure that what shows there in the FQDN box is the actual public FQDN of your server (not the internal server name).
ASKER
in there I had domainname.com not the email.domainname.com. i changed it to email.domainname.com but I want to make myself clear. The domain name that was purchased was domainname.com. When creating the mx record i created the email.domainname.com. This being the case, you still say to use the email.domainname.com? And if so do you think that may hav been causing the issue that certain domains would mark our email as spam?
ASKER
Any answers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great answer and it really helps me to understand this all better.
Thankyou! I am a company tech, the above poster "gpicart" explained my situation exacly 2 months earlier. I just feel lucky that I got to have someone clearly articulate my question and someone else give a clearly defined solution all within three minutes. GO Experts Exchange !!!!!