pingcap / pingcap/tiup

Topology to resolve host IP address from DNS

Open
#2,720 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

contribution first-time-contributor type/feature-request
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

Feature Request

Describe the feature you'd like:
If a user has something like MagicDNS/Tailscale setup, could we get the ability to put the domain name instead of the actual IP in the topology? i.e.

...
pd_servers:
  - host: hostIP
  - host: node1.domain.net
  - host: node2.domain.net

tikv_servers:
  - host: node1.domain.net
 ...

Why the featue is needed:
Simplify setup

Describe alternatives you've considered:
Writing the actual IP

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the topology configuration parser and the code that validates or uses server host values. Check how pd_servers and tikv_servers are handled, then verify that both IP addresses and DNS names work throughout deployment and topology operations.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.