Anyone have expirence with this?
We just cut over a customer to a new internet connection. Their mail.domain.com entries now point to a IP and when their users send mail out, it comes from their new internet IP that has no dns associated with it so all the recieving email server sees is the IP address. Their website is remotely hosted.
Anyone know what entires need to be setup to associate this IP with their domain name so email is trusted?
reverse DNS…
Thats what I am thinking. If the recieving email server does a lookup on the source IP, there is no domain associated with it.
What entry needs to be on the domain’s DNS to allow it to resolve
So call up the ISP who gave you the IPs and tell them you want reverse DNS setup for the mail server or gateway(if the mail server is NATed) to be mail.company.com or whatever the MX record was.
Ok waiting for fibertech to call back. Figured that is all I needed to do but wanted to double check.
Thanks
Only other thing I am confused on.
The IPs are from Fibertech.
The domain for the company is through register.com where all the mx records are.
Is the reverse dns setup through the ISP on the IPs or do I need to associate the public IP with something in register.com through the domain?
on the ISPs end…though they could technically delegate the IP block to the host and they can do it.
AT&T tries to pull that shit with us all the time.
Ya I told fibertech the mail server i need associated with our public IP.
waiting for it to propagate to see if they did it right. i wanted to make sure its just on them to setup and there was no DNS stuff I needed to change in the main domain.
Yeah, I know when we do AT&Ts work for them, there always seems to be an issue that arises. I don’t think our name servers really like to do rDNS
:word: