Adam D
asked on
Old Exchange server - new ISP cannot provide rDNS
I have an older exchange server which is working without a problem on my current ISP. I had to switch ISP's recently and my old ISP will be disconnected shortly.
Unfortunately, even though I WAS told my new ISP can provide rDNS for my on-premises email server, I am now being told they cannot.
I have a "persistent-IP" which is ALMOST a static public IP, but it must be from a block of public IP's they have in which I am probably being natted.
So, is there a way to setup a third-party rDNS so my emails from my on-premises server do not end up in spam or bounce?
Thanks.
Unfortunately, even though I WAS told my new ISP can provide rDNS for my on-premises email server, I am now being told they cannot.
I have a "persistent-IP" which is ALMOST a static public IP, but it must be from a block of public IP's they have in which I am probably being natted.
So, is there a way to setup a third-party rDNS so my emails from my on-premises server do not end up in spam or bounce?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
M A
If your ISP is not ready to create PTR for you as commented above it is better to find another ISP who can create PTR (RDNS) for you.
ASKER
Thanks for getting back to me.
Apparently the ISP is "unable" (through incompetence or otherwise) to provide rDNS/PTR records and yes I can get out of the contract but I am very limited in my choices of ISP's in my location. Essentially, they are it; as my old provider is no longer a viable alternative for many reasons.
I sent a note to SMTP2Go and they say their service will work with my Exchange server (I am running 2010 as part of an old SBS 2011 server) which works fine and which I am not replacing at this time.
Any thoughts on using them (or others) with the server and any security risk to the email content in doing so?
Thanks.
Apparently the ISP is "unable" (through incompetence or otherwise) to provide rDNS/PTR records and yes I can get out of the contract but I am very limited in my choices of ISP's in my location. Essentially, they are it; as my old provider is no longer a viable alternative for many reasons.
I sent a note to SMTP2Go and they say their service will work with my Exchange server (I am running 2010 as part of an old SBS 2011 server) which works fine and which I am not replacing at this time.
Any thoughts on using them (or others) with the server and any security risk to the email content in doing so?
Thanks.
Outgoing email routed through SMTP2Go is encrypted using SSL/TLS, so it is as secure (as it leaves your premises) as it is possible for normal email to be. From that point forward it depends on whether the recipient's site and any intervening sites support SSL/TLS.
You will need to update your SPF and DKIM to reflect SMTP2Go as the new authorized outgoing source.
You will need to update your SPF and DKIM to reflect SMTP2Go as the new authorized outgoing source.
ASKER
Thanks Dr. Klahn. I think this will be the way to go due to my current situation. :) I appreciate the help and quick response.