Should the user be allowed to specify FQDNs for HS TARGETs?
Spinoff of #18029 (moved).
The current behavior is to accept any of a raw port, IP address + port, or FQDN + port. We also will accept oddball (historic) inet_aton() style IP addresses (raw hex) depending on if the system implements getaddrinfo() correctly or not.
I'm inclined to leave this as is, and if users care that the HS will hit up the system resolver at initialization time, it should be obvious that they need to specify the target by IP. That said, documentation clarification that an FQDN is acceptable would be ideal.
Since both torrc and ADD_ONION style HSes call into common code, changing the behavior to never hit up the resolver is trivial as well.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information