Alias doesn't work with Remote HSD Node

Nathanwoodburn commented 2 years ago

Expected Behavior

Bob should allow using a specified port to do DNS requests for alias

Current Behavior

Bob doesn't have any alias with Remote HSD Node. The DNS resolving is working.

Images

Context (Environment)

This means I can't use a remote node to send people HNS ;(

Logs

No Logs taken. If it would help, I can recreate the problem and record the logs

rithvikvibhu commented 2 years ago

That looks like different ports in the images. Try setting 53501 in settings?

Nathanwoodburn commented 2 years ago

Opps, the first image was from a previous attempt as getting it to work. The ports were correct. The send to doesn't even show the alias option. Is it set to not work at all on remote HSD?

rithvikvibhu commented 2 years ago

Oh just thinking about it now, it wouldn't work. Because when in RPC, there is no local DNS server running.

Now we could add a field to set a custom IP address for the dns resolver (not just port), but that brings in other problems:

Bob itself won't do dnssec/dane verify, it just trusts the resolver to do it
If the resolver isn't local, its responses may be intercepted (same reason non-localhost RPC requires https)
Since we depend on this DNS for DANE, it's too risky to just hope users understand this and secure their resolver-Bob connection.

Thinking of what can be done,

Resolve DNS over rpc (add feature to hsd first)
DNS resolver over socket, not port (then we can keep it enabled, no need of the toggle, and no port conflicts)
Hide an option to set the resolver address - bury it deep in settings with lots of warnings
anything else?

kyokan / bob-wallet