Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Set PTR for Linode nodes IPs

Open
  • Is something wrong?
#127 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, kubernetes
Domain
cloud, infrastructure, networking

Research direction

Start by reviewing how LKE cluster nodes are created and recycled, focusing on where Linode node IPs become available for configuration. Define how a cluster-level PTR or RDNS setting would be declared and verify that the setting is reapplied after node recycle actions, so newly created nodes retain the desired reverse-DNS behavior.

Written by the indexing model from the issue text.

Description

Standalone Linodes have the option to set Reverse DNS (RDNS / PTR record on the IP address).

For LKE: While the underlying Linodes in a LKE cluster is still accessible (and we can set PTR record on the Linodes there), this won't survive a node recycle action.

Would it be possible to declare the desired PTR setting for all nodes in a LKE cluster? This would allow any node to send emails with the correct PTR setting, even if the nodes are recycled.

Dominant language
Go
Stars
94
Forks
75
Avg merge
1d 20h
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linode/linode-cloud-controller-manager

All issues in linode/linode-cloud-controller-manager

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.