hashicorp / hashicorp/memberlist
Using DNS names in Config.AdvertiseAddr
- Dominant language
- Go
- Stars
- 4.1k
- Forks
- 478
- Avg merge
- 15h 58m
- Merged PRs (30d)
- 3
Description
I am wondering why you cannot use a DNS name for the `AdvertiseAddr` in the config. Is there a reason for this? Would that mean have to do the name resolution myself before giving it to the memberlist config?
Here it expects that the `AdvertiseAddr` is an actual IP address:
https://github.com/hashicorp/memberlist/blob/b195c8e4fcc6284fff1583fd6ab09e68ca207551/memberlist.go#L369-L373
Contributor guide
Research direction
Start by reading memberlist.go around lines 369-373, where AdvertiseAddr is expected to be an IP address, and trace how that value is validated and consumed. Determine the intended behavior for DNS names, including when resolution should occur; done requires an agreed behavior with corresponding tests or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100