ipns:// should respect DNS resolver settings
See original GitHub issueProblem
If Brave user decides to use custom DNS over HTTPS resolver via UI below, go-ipfs does not respect that choice, and uses cleartext resolver provided by the OS.
Proposed change
Every time custom DNS over HTTPS resolver is set via the UI in “Privacy and security” settings, Brave should add/update .
(top-level resolver) in DNS.Resolvers
map in the $IPFS_PATH/config
file.
Making changes to this map requires node reboot for changes to be applied
Issue Analytics
- State:
- Created a year ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
What is InterPlanetary Naming System(IPNS)? | by ... - Medium
In this part, we will dive into the Naming System of IPFS, InterPlanetary Naming System(IPNS). We will explore: What is the need for...
Read more >Understanding IPFS in Depth(3/6) - HackerNoon
In this part, we will dive into the Naming System of IPFS, InterPlanetary Naming System(IPNS). We will explore: What is the need for...
Read more >DNS Security: Threat Modeling DNSSEC, DoT, and DoH
Anyway, so looking at how to secure the DNS, we need to consider the ... they may not know how to change e.g.,...
Read more >K12140128: Overview of the DNS resolver - AskF5
The validity of the cached DNS responses is determined by their respective Time-To-Live (TTL) and the oldest entries are removed by the cache...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
cc @spylogsster thoughts on wiring this up?
Should this be reopened?