DigitalOcean home
  • Droplets
  • Spaces
  • Kubernetes
  • Tools & Integrations
  • One-click Apps
  • API Documentation
  • Community
  • Tutorials
  • Q&A
  • Projects
  • Meetups
  • Customers
  • Pricing
  • Docs
  • Support
  • DigitalOcean home
  • Products
    • Droplets

      Scalable compute services.

    • Spaces

      Simple object storage.

    • Kubernetes

      Run managed Kubernetes clusters.

    • Tools & Integrations

      Automate your infrastructure.

    • One-click Apps

      Deploy pre-built applications.

    • API Documentation
  • Customers
  • Community
    • Community Overview

      Connect, share and learn

    • Tutorials

      DevOps and development guides

    • Questions & Answers

      Development and systems Q&A

    • Projects

      Community-built integrations

    Get Involved
    Write for DOnations
    Join us at a Meetup
    Featured Post
    An Introduction to Kubernetes

    by Justin Ellingwood

  • Pricing
  • Docs
  • Support
    • Documentation

    • Contact Support

    • Network Status

  • Home /
  • DO-I-2280 /
  • New idea
103 Vote

Allow PTR records to be set separately from the hostname displayed in the control panel

  • Guest
  • Sep 11 2018
  • Future consideration
DNS
  • Comments (18)
  • Votes (103)
  • Attach files
  • Guest commented
    26 Mar, 2019 04:36am

    Upvoted. Even the crap shared hosting providers let you set a PTR record. This is ridiculous.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    it would be great to have more control over PTR records.

    IPv4 pointers are set automatically to the droplet's name, and it seems that any IPv6 interfaces you configure for a droplet are automatically set to the droplet name as well.

    currently, you can only have one IPv4 IP on a droplet (i think), but you can have multiple IPv6 IPs for a droplet, and so here is where the ability to have individual PTR control would be great.

    It would be great to be able to have different PTRs for different IPs on a single droplet, i.e.:

    IPv4 IP points to domain1
    IPv6 IP2 points to domain2
    IPv6 IP2 points to domain3
    etc

    please implement this somehow or give us the option to delegate authority for the droplet's assigned IPv6 subnet so that we can run BIND (DNS server) on the droplet and manage PTR records ourselves that way

    GIVE US THE POWER please

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    +1 to this. Being able to set the individual ipv6 pointers would be very nice.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    yes, i know that you guys will only give us one IPv4 address per droplet, but we can also have one or more IPv6 addresses per droplet. we might not want the same PTR record for each of these IPs though. give us more control please so that we can set individual PTR records for each IP on each droplet (e.g. if there is one IPv4 address and five IPv6 addresses on a droplet, please let us individually set all six PTR records to whatever we want instead of just automatically setting them all to the same thing).

    thanks

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    otherwise at the very least, make a feature to let us have the authority to run BIND or something on a droplet and set up our PTR records that way if it is easier for you to code

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    DO would be perfect for me if it had this feature.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    I'm having this issue with my droplet - I want to add PTR records to the other ipv6 addresses. Tunnel Broker won't work properly for me as well.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    Still wish this was possible... Setting multiple IPv6 PTR records is a feature on so many other providers, why not DigitalOcean? It is the one thing that keeps DO from being perfect for me.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    This is required in order to support smtpd restrictions based on AAAA <==> PTR mapping. Without being able to set up a reverse mapping, mail sent from an otherwise properly configured droplet will be rejected by MTAs that implement this restriction.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    still waiting on this... we need a mechanism to get control of PTRs / FDQNs **INDEPENDENTLY** for each host (ipv4, each ipv6)

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    Yes will be great, and make more atractive from concurrent virtual hosting company.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    I have a WHM/Cpanel server and need to set PTR as rDNS so hotmail.com and others won't bounce emails from the domain

    XXXX.ip6.arpa. 1h IN PTR mail.example.com.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    it would be great to have more control over PTR records.

    IPv4 pointers are set automatically to the droplet's name, and it seems that any IPv6 interfaces you configure for a droplet are automatically set to the droplet name as well.

    currently, you can only have one IPv4 IP on a droplet (i think), but you can have multiple IPv6 IPs for a droplet, and so here is where the ability to have individual PTR control would be great.

    It would be great to be able to have different PTRs for different IPs on a single droplet, i.e.:

    IPv4 IP points to domain1
    IPv6 IP2 points to domain2
    IPv6 IP2 points to domain3
    etc

    please implement this somehow or give us the option to delegate authority for the droplet's assigned IPv6 subnet so that we can run BIND (DNS server) on the droplet and manage PTR records ourselves that way

    GIVE US THE POWER please

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    WHY ARE WE STILL WAITING FOR THIS?

    Lol, this is fundamental, what is wrong with DO?

    If you assign someone 15 addresses you either set all 15 for them or allow them to configure them!

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    Would love to have this available.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    I can only change my PTR record from one FQDN to another, but I cannot delete it if I've set it once. That sucks. Please add that option?

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    please and yes

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 06:26pm

    Please add this option.

    ×

    Attachments Open full size

  • +3
Log in / Sign up

Identify yourself with your email address

Subscribe

You won't be notified about changes to this idea.

Related ideas

DigitalOcean home

© 2018 DigitalOcean, LLC. All rights reserved.
Proudly made in NY

  • Twitter
  • Facebook
  • Instagram
  • YouTube
  • LinkedIn
  • Glassdoor
Company
About
Leadership
Blog
Careers
Partner Network
Referral Program
Events
Press
Legal & Security
Products
Droplets
Spaces
Kubernetes
Tools & Integrations
One-click Apps
API
Pricing
Documentation
Release Notes
Community
Tutorials
Meetups
Q&A
Write for DOnations
Droplets for Demos
Hatch
Shop Swag
Research Program
Currents Research
Open Source
Support
Contact Support
FAQ
Network Status