1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Correct way to do reverse dns PTR records with multiple domains

Discussion in 'Plesk for Linux - 8.x and Older' started by amandler, Aug 14, 2006.

  1. amandler

    amandler Basic Pleskian

    23
    57%
    Joined:
    Jul 10, 2006
    Messages:
    42
    Likes Received:
    0
    Hi folks -- can someone illuminate me as to the "correct" way to setup reverse DNS records when one has multiple domains on a single IP, such as is (usually) the case with Plesk? The default in-addr.arpa file that Plesk creates contains a separate entry for each domain hosted, which in our case is several hundred, all in a single file. However, SOME mail servers end up rejecting messages from our customers because they fail a reverse DNS test. NuVox.com is an example. Their engineers say the long laundry list of multiple domains per single IP is causing the problem. Is there another, better way to set this up?

    Many thanks!
     
  2. jspilon

    jspilon Guest

    0
     
    you should not use multiple rDNS entries per IP.
     
  3. amandler

    amandler Basic Pleskian

    23
    57%
    Joined:
    Jul 10, 2006
    Messages:
    42
    Likes Received:
    0
    Thanks

    Thanks for that. I received the same information from someone else, and edited the in-addr.arpa file to include a single entry for the IP address that hosts many domains. This resolved all the rDNS problems we were having with other email servers.

    Of course, everytime a domain is edited in Plesk it rebuilds all the in-addr.arpa files, so I had to create a script to check periodically and copy the fix back.

    This information should be widely disseminated since the default Plesk behavior is simply wrong.
     
  4. Who-m3

    Who-m3 Guest

    0
     
    Another fix would be to remove the PTR record from each domains' DNS as well as from the template. This would allow you to have everything operating the way it should without having to do a "dirty" cheat to get it going again.
     
  5. amandler

    amandler Basic Pleskian

    23
    57%
    Joined:
    Jul 10, 2006
    Messages:
    42
    Likes Received:
    0
    PTR Records

    yes, you're right. I've begun that process, but there are lots of domains to edit.

    I could not see how to tell the template that it should not put in a ptr record. Help on that would be appreciated.
     
  6. geonas

    geonas Guest

    0
     
    Login into plesk
    click on server under system in the left hand colum then the DNS Icon
    You will get the DNS Zone Template
    Place a check mark next to the PTR record and remove it.
     
  7. DCNet_James

    DCNet_James Guest

    0
     
    I would think you would only want to do these from the top level, but as I see above, I believe a reverse entry is auto-created for each A recorded within a domain, kind of stupid that it doesn't do a check against the current reverse zone to see if there is already an entry for it. I personally handle reverse DNS on a seperate set of dns servers outside of Plesk. I do not want my customers to be able to screw with reverse DNS, for obvious reasons.

    Thx
    James
     
  8. unhingedmedia

    unhingedmedia Guest

    0
     
    newbie question

    where is the in-addr.arpa file so I can edit it?
     
  9. blank_page

    blank_page Regular Pleskian

    24
    53%
    Joined:
    Dec 17, 2006
    Messages:
    229
    Likes Received:
    0
    HEllo,

    Creating ptr records / domain basis is a usless procedure.
    You only need one ptr and that is for the sending ip of your mailserver.
     
Loading...