• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

SPF record/reverse DNS problem on second IP

ScottGoddard

Basic Pleskian
Hi

I have a server with2 IP's. My main domain resolves to the first IP and I also have another domain which is set up on the second IP i.e:

Code:
maindomain.co.uk - 201.201.201.201
seconddomain.co.uk - 201.201.201.202
Sending main from maindomain works fine but when I send from seconddomain the Mail Server is listed as maindomain but the IP is listed as that of seconddomain so I get issues with being classified as Spam.

Header info:
Code:
Received: from maindomain.co.uk (maindomain.co.uk [201.201.201.202] (may be forged))
	by recipient.co.uk (8.14.2/8.14.1) with ESMTP id rA1GI6Jd057256
	for <[email protected]>; Fri, 1 Nov 2013 16:18:07 GMT
X-No-Auth: unauthenticated sender
Everything was set up in Plesk 11.5.30 using the standard settings, so I cannot see why this should be wrong? How do I correct this?

OS is CentOS 6.4 (Final)

Edit: The reverse DNS for both IPs resolves to maindomain.co.uk
 
Last edited:
second IP rDNS problems

I have exactly the same issue - I already added a second hostname to my etc/hosts for the second IP address, which works nice if I nslookup on my own servers, however it does not resolve for a normal nslookup. Probably I have to wait another 6 days until the TTL expires, but it would be good to know if I am on the right track... ?

127.0.0.1 localhost

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
85.214.143.xx hxxxxxxx.stratoserver.net hxxxxxxx.stratoserver.net
127.0.0.2 hxxxxxxx.stratoserver.net hxxxxxxx
81.169.138.xx mail.kitexxxxx.com mail.kitexxxxx.com
 
Scott: You said the reverse DNS for both IPs resolves to maindomain.co.uk -- well, that's your problem. You need to get whoever provides your IPs to change the second IP to resolve to seconddomain

mschwendtner: You cannot control rDNS from Plesk. rDNS is typically configured by whoever provides your IP addresses (strato). Maybe there's an option in your strato control panel for doing this yourself, or maybe you have to contact support.

Note that PTR records in Plesk's DNS records will only have an effect on local lookups (by your server). You cannot change rDNS results made by external DNS servers by changing PTRs in Plesk. You should still only have ONE domain with a PTR record per IP though. e.g. if domain.tld is the "main" domain for your shared IPs, it should have a PTR (pointing to the shared IP). No other domain using the shared IP should have a PTR (not that it matters hugely but it can mess up logs and mail headers).
 
Hi Faris,

thanks for the reply. I noticed that plesk cant control the rDNS, therefore I tried to change it through the root settings myself. I have a root server at strato so no problem with that.

I am running my own DNS through plesk for the domains on the second IP address (and that works fine for e.g. SPF records etc). However the server "above me" only has rDNS records for the main.tld (with the first shared IP) but not for second.tld (with the second shared IP on which I have the problems)

Therefore all the domains which are sitting on the main.tld IP address (the first address) resolve fine to rDNS, but not the domains sitting on second.tld (the second IP address).

You reckon this is something rather for strato support to get it up to their servers ? I guess every IP address they give me should resolve to an individual hostname, not two addresses resolve to the same hostname ?

thanks,
Markus
 
Correct. Basically rDNS is controlled by strato, in their DNS records, so they will need to implement the changes in one way or another.

Some co-lo/server rental companies allow the rDNS to be adjusted directly by the customer through a control panel of some sort. This is the case with us, for example. But others require that a ticket be opened in order for the provider to make the required changes manually. Either way, you should not have any difficulty in getting it done -- I'm sure strato will sort it out very quickly for you.
 
Back
Top