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 /
  • FLIP-I-1 /
  • New idea
5 Vote

PTR records

Kubernetes nodes get assigned public IP's, but with no PTR as you can't choose the name of the droplet. Please provide either PTR on the assigned IP or to floating IP. This way we could use nodes for public mail servers, etc. Thank you in advance.

  • Guest
  • Feb 20 2019
  • Needs review
Floating IPs
  • Comments (3)
  • Votes (5)
  • Attach files
  • Guest commented
    16 Dec, 2019 08:54am

    merge https://ideas.digitalocean.com/ideas/DO-I-1023 ?

    ×

    Attachments Open full size

  • Cliff Hayes commented
    7 Sep, 2019 03:23pm

    I cannot use this service for our legitimate email servers without floating IP + reverse DNS. From the response given here https://www.digitalocean.com/community/questions/how-do-i-set-the-ptr-for-a-floating-ip it seems that you are not allowing reverse DNS to block spammers, but in fact you are blocking legitimate businesses. The right thing to do would be to find another way to block spammers.

    I have been fighting spammers for 15 years. Cloud computing was a godsend for them. The latest tactic is to spin up a few servers, send out a bunch of spam on fresh IPs, then make them disappear. I’ve been fighting one spammer for 10 months who has used over 300 ranges of IPs and counting. This tactic you have of not allowing reverse DNS for floating IPs is not stopping a spammer that uses IPs for one day. It is stopping legitimate businesses that want to establish a long term reputation of credibility on a certain IP, something that spammers do not want to do. You are hurting and not helping.

    BTW ... AWS has had this feature since 2010.

    ×

    Attachments Open full size

  • Rens Rikkerink commented
    14 Jun, 2019 07:38am

    I recently reported this to support and asked for the same, I was told to post an idea here but you already did :D

    ×

    Attachments Open full size

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