Replies: 3 comments 2 replies
-
I bet DNS and other parts of the network stack provide a large surface area for attackers. Much like implementing your own crypto library, probably not something to be done without a good reason. So perhaps good to start out with a convenience wrapper around the system DNS resolution that doesn't get too clever. |
Beta Was this translation helpful? Give feedback.
1 reply
-
This project looks pretty impressive: https://github.com/hickory-dns/hickory-dns |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We must be able to resolve dns queries to responses. There are a few things to consider:
If we use the default resolver, a hostname will consist of 0 or more ip addresses (ipv4 and/or ipv6). They all have a ttl from the browser perspective.
We should be able to force flush this dns cache easily
We should be able to simply add our own custom entries:
For instance. Foo.test.com resolves to 127.0.0.1
This could be ipv4, ipv6 and even round robin with multiple ips
Wildcard should be supported: *.localdev resolves to 127.0.0.1
We should be able to use DoH and dns sec
We should allow in-memory storage only when configured. No ip/host caching is flushed to disk and thus must be retrieved on the next startup of the browser
Beta Was this translation helpful? Give feedback.
All reactions