Is the DNS domain sufficiently generic to become js-dns and become useful for more generic DNS operations? #16
Description
What is your research hypothesis/question?
I know you were using dns-packet before, and we changed to building our own DNS parser and generator.
I had a look at the code, it looks pretty extensive. I'm wondering how much work would need to be done on it to make it generic enough for generic DNS operations.
PKE will have some dns resolution related bootstrapping logic... and things like DNSSEC and other operations may be relevant.
Also I was wondering how come you have some functions that look like existing JS code can do:
function encodeUInt16BE(value: number): Uint8Array {
const buffer = new Uint8Array(2);
new DataView(buffer.buffer).setUint16(0, value, false);
return buffer;
}
function encodeUInt32BE(value: number): Uint8Array {
const buffer = new Uint8Array(4);
new DataView(buffer.buffer).setUint32(0, value, false);
return buffer;
}
Review existing ideas, literature and prior work
- 1. I wonder how much cross-over can there be with ENS https://github.com/ensdomains/ensjs-v3/blob/main/packages/ensjs/package.json
Research conclusion
Look at PKE's private network bootstrapping issue and figure out if we need a js-dns package.
Sub-Issues & Sub-PRs created
- ...
- ...
- ...