• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Making reverse lookups work

michaellunsford

michaellunsford

Regular Pleskian
well, this might not be plesk related -- but I don't know where else to post it.

I used to get the "possible break-in attempt" error when logging into SSH. Apparently the ISP has fixed this (for the moment) -- but it'll probably be back tomorrow.

One thing that's still "broke" is email. Any external email addresses receiving mail from my server will show my IP address "may be forged" in their headers.

Received: from server.example.com
(ds209-253.ipowerweb.com [xxx.xxx.xxx.xxx] (may be forged))
by ...com (Xserve/smtpin20/MantshX 4.0) with ESMTP id ...
Click to expand...

how do I make the "may be forged" go away?

Are there any other areas I should be looking to fix regarding this reverse lookup thing?
 
You must log in or register to reply here.

Similar threads

S
tcp-env Still Doing Reverse DNS Lookups with -Rt0
Replies
4
Views
8K
Gustave Stresen-Reuter
G
S
Email Stopped Working after Failed upgrade to 8.1
Replies
1
Views
3K
SpidermonBob
S
Back
Top