Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why does the enode nodeId information not support the domain name? #18340

Closed
zjsunzone opened this issue Dec 20, 2018 · 4 comments · Fixed by #18524
Closed

Why does the enode nodeId information not support the domain name? #18340

zjsunzone opened this issue Dec 20, 2018 · 4 comments · Fixed by #18524
Assignees

Comments

@zjsunzone
Copy link

Hi there,

please note that this is an issue tracker reserved for bug reports and feature requests.

For general questions please use the gitter channel or the Ethereum stack exchange at https://ethereum.stackexchange.com.

System information

Geth version: geth version
OS & Version: Windows/Linux/OSX
Commit hash : (if develop)

Expected behaviour

Actual behaviour

Steps to reproduce the behaviour

Backtrace

[backtrace]
@FrankSzendzielarz
Copy link
Member

The main reason is privacy.
Other reasons might include DNS attack vectors.
https://ethereum.stackexchange.com/questions/37445/is-it-possible-to-use-domain-names-in-place-of-ip-addresses-for-peer-nodes-stat

@easeev
Copy link

easeev commented Aug 14, 2019

Guys @karalabe @FrankSzendzielarz @fjl,

  1. Could you please elaborate on how IP is more private than a domain name? Both are just plaintext identifiers.
  2. Is it really that hard to add hostname resolution to IP similar to what Parity does? Will be very helpful to operate Geth nodes in modern environments (e.g. cloud).

@karalabe
Copy link
Member

karalabe commented Aug 14, 2019 via email

@easeev
Copy link

easeev commented Aug 15, 2019

Thanks @karalabe!

Could you review and merge #18524 then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants