Question
rDNS
- Posted November 16, 2013
Hello! I have 1 droplet have 3 domain. I need that for each domain was registered your rDNS. So there must be three record rDNS for each domain: 51.172.185.146.in-addr.arpa name = site1.com 51.172.185.146.in-addr.arpa name = site2.com 51.172.185.146.in-addr.arpa name = site3.com
How do I add these rDNS for each domain?
Make 3 droplets too expensive. Support DO in fact refused to solve my problem.
In the result I am unable to use mail. I.e. it does not reach the addressee, and blocked because of the error: “host mx1.example.com[999.888.777.666] said: 550 X-Host Lookup Failed: Reverse DNS lookup failed for 146.185.172.51 (failed)”
I need your help.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Kamal, not correct for your last statement. you can have as many PTR records for an IP as your heart desires. It is functionally and technically correct.
<blockquote>3. AFAIK DO only allows 1 rDNS (PTR) record per droplet/IP. If you want 3 rDNS (PTR) records, as in your example, you have to create 3 droplets. </blockquote> <br>That how it is for every provider. A single IP address cannot have more than one PTR/reverse DNS record.
Thanks to everyone for participating. Worked a day after renaming in control panel DO droplet on FQDN
A couple of things; <br> <br>1. Make sure to change ‘control.yourdomain.com’ in the Postfix config file. You want to set the domain and hostname in the config file to match your mx records. <br> <br>2. The rDNS (PTR) records should match your mx records for the server your mail server is on. So if you have ‘site1.com’ and your mx record is ‘mail.site1.com’ then you’ll want to rename the hostname for your droplet ‘mail.site1.com’. If, however, you have 2 droplets and one of those droplets is a dedicated mail server then only that droplet needs to have a hostname of ‘mail.site1.com’ while the other can be whatever you need. <br> <br>3. AFAIK DO only allows 1 rDNS (PTR) record per droplet/IP. If you want 3 rDNS (PTR) records, as in your example, you have to create 3 droplets. <br> <br>I would love the ability on DO to have multiple PTR records for a single IP or multiple IPs per droplet. Here’s to looking towards the future.
Yes, I rebooted the droplet. <br>A record in the DigitalOcean DNS Manager has the following form: @ 146.185.172.51. <br>Even now, I tried to send an email, but the email does not reach the addressee. Instead, after 5-6 hours I get a letter from MAILER-DAEMON@control.yourdomain.com (Mail Delivery System) with the title: "Delayed Mail (still being retried) " <br>and the text: <br>"Your message could not be delivered for more than 4 hour(s). <br>It will be retried until it is 5 day(s) old. <br> <br>For further assistance, please send mail to the postmaster. <br> <br>If you do so, please include this problem report. You can <br>delete your own text from the attached returned message. <br> <br>The mail system <br> <br><admin@r******.ru>: host mx1.fullspace.ru[81.222.134.105] said: 550 <br>X-Host Lookup Failed: Reverse DNS lookup failed for 146.185.172.51 (failed) <br>(in reply to RCPT to command) <br> <br><inform@r******.ru>: host mx1.fullspace.ru[81.222.134.105] said: 550 <br>X-Host Lookup Failed: Reverse DNS lookup failed for 146.185.172.51 (failed) <br>(in reply to RCPT to command) <br> <br>Reporting-MTA: dns; control.yourdomain.com <br>X-Postfix-Queue-ID: 04F76120F00 <br>X-Postfix-Sender: rfc822; dir@yutrust.ru <br>Arrival-Date: Sat, 16 Nov 2013 17:33:07 +0000 (UTC) <br> <br>Final-Recipient: rfc822; admin@r*******.ru <br>Original-Recipient: rfc822;admin@r******.ru <br>Action: delayed <br>Status: 4.0.0 <br>Remote-MTA: dns; mx1.fullspace.ru <br>Diagnostic-Code: smtp; 550 X-Host Lookup Failed: Reverse DNS lookup failed for <br>146.185.172.51 (failed) <br>Will-Retry-Until: Thu, 21 Nov 2013 17:33:07 +0000 (UTC) " <br> <br>What should I do?
Have you rebooted your droplet? Also, make sure you have an <code>A record</code> in the DigitalOcean DNS Manager, pointing to your droplet.
Yes FQDN she FQDN… Only messages from mailboxes do not reach the required destination.
In your <a href=“https://cloud.digitalocean.com/droplets”>DigitalOcean Control Panel</a>, make sure that the hostname you’ve assigned to your droplet is a fully qualified domain name (FQDN).