Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
Please allow us to have more than one PTR record for revDNS for those of us that have multiple virtual domains and would like to set up fully resolving forward and reverse DNS
Simple use case:
Serve email for two domains from a single droplet, e.g. mail.domain1.com, mail.domain2.com
Need reverse domain support for both email domains that are being used. Using separate droplets would be a solution, but why incur more cost and complexity for something so simple.
Why would you want this? It is technically possible - but for what purpose? General rule of thumb is 'One IP - One PTR'; most software that checks the reverse DNS for IPs are build around that same assumption.
Can you clarify why you really want several PTR's?
'One IP - One PTR' is not a general rule of thumb - many servers do mail, dns, http, etc, using the same IP address, so it is normal to have multiple PTR records for each A record with the same IP address
resolvers are required to search through all the PTR records returned in order to find a match ... " "it's the law" :)
also see the suggestion "allow droplet vps in-addr.arpa records to be CNAME as well as PTR"
I have multiple domains on my droplet but I currently can only have one PTR record.
This is a serious problem as some mail spam filters won't allow an e-mail through if it does not have an associated reverse DNS (PTR) record.
Currently, the only way around this problem is to place each domain on a separate Droplet if you wish to use e-mail without danger of it getting stopped by some spam filters.
Please give us functionality to have multiple PTR records on one droplet.
You won't be notified about changes to this idea.