https://github.com/innovate-invent/dns
Dependency free, browser compatible, NodeJS dns library replacement. Implements RFC8484 and RFC1035. Supports most DNS over HTTPS servers.
https://github.com/innovate-invent/dns
browser browserify compatibility dns javascript library nodejs typescript
Last synced: 5 months ago
JSON representation
Dependency free, browser compatible, NodeJS dns library replacement. Implements RFC8484 and RFC1035. Supports most DNS over HTTPS servers.
- Host: GitHub
- URL: https://github.com/innovate-invent/dns
- Owner: innovate-invent
- License: mit
- Created: 2021-01-28T05:05:48.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2025-06-19T10:50:29.000Z (about 1 year ago)
- Last Synced: 2025-11-23T07:28:04.832Z (7 months ago)
- Topics: browser, browserify, compatibility, dns, javascript, library, nodejs, typescript
- Language: TypeScript
- Homepage:
- Size: 1000 KB
- Stars: 5
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# @i2labs/dns
Dependency free, browser compatible, NodeJS dns library replacement. Implements RFC8484 and RFC1035.
Supports most DNS over HTTPS servers.
Why would you want to make DNS requests from a browser? DNS has numerous
functions other than mapping domain names to IP addresses. SRV and TXT records offer the ability to do service discovery
and distribute information such as public keys.
**This library uses AbortController, which is not compatible with Internet Explorer.** A polyfill may be available,
but is not included.
See the [NodeJS dns documentation](https://nodejs.org/api/dns.html) for information on how to use this library.
The [caveats](https://nodejs.org/api/dns.html#dns_implementation_considerations) mentioned in the documentation
regarding `lookup`, `lookupService` and `reverse` do not apply. These functions call system operations not available to
the browser. In this implementation `lookup` simply aliases `resolve`, `lookupService` and `reverse` will throw errors
when called. `hints` and `verbatim` arguments of `lookup` are ignored. The errors are thrown in a way that any proper
error handling that would normally be present while using the NodeJS dns library should also handle these errors.
`setLocalAddress` is a no-op function. `getServers` and `setServers` return/accept a list of strings containing the
hostnames of the 'DNS over HTTPS' providers that the resolver makes requests against.
`Resolver.resolve()` is extended to support most record types. If you want to bypass the modifications made to the response
values by the NodeJS dns specification, you can pass `{raw: true}` in the `options` object argument to get the full response object.
A best attempt to parse record data as much as possible was made. Due to an inconsistent mix of available documentation
for the record type data layouts, not all are complete. See [rfc_rdata.ts](src/rfc_rdata.ts) for the RDATA layout descriptions.
Any type that is marked as 'opaque' may change in the future with contributions to extend the parsing of that record type.
This library is able to function by using any 'DNS over HTTPS' services. The default resolver host is CloudFlare using
cloudflare-dns.com. Support for any of the providers listed under 'DNS over HTTPS' at https://en.wikipedia.org/wiki/Public_recursive_name_server
can be added. Currently, only providers (most of them) that implement [RFC8484](https://tools.ietf.org/html/rfc8484) are supported. Contributions are welcome.
`dns.Resolver` is implemented as a wrapper around the Promise based resolvers to support the callback interface. Pass an
instantiated Promise resolver to the constructor to wrap different provider resolvers:
```typescript
import dns from 'dns'
import RFCResolver from 'dns/rfc8484'
const resolver = new dns.Resolver(new RFCResolver({timeout: 30}));
```
All methods exported by the library use the RFC8484 resolver. Instantiate a resolver imported for the specific
provider submodule to use that provider. `class Resolver` implementations export `lookup` and `lookupService` in
addition to the methods defined in the [NodeJS dns documentation](https://nodejs.org/api/dns.html).
# Use
```js
import * as dns from 'dns'
dns.promises.resolve('example.i2labs.ca').then(result=>console.log(result))
```
### Webpack
```js
// webpack.config.js
module.exports = {
alias: {
'dns': '@i2labs/dns'
}
}
```
### Browserify
```shell script
browserify -r '@i2labs/dns:dns' ...
```
## Alternatives
| Alternative | DoH Servers | NodeJS dns | RFC1035 | Dependencies |
| ----------- | ----------- | ---------- | ------- | ------------ |
| [doh-js-client](https://www.npmjs.com/package/doh-js-client) | google cloudflare cleanbrowsing | ✗ | ✗ | ✓ |
| [http-dns](https://www.npmjs.com/package/http-dns) | google | dns.resolveSrv() only | ✗ | ✓ |
| [fetch-dns](https://www.npmjs.com/package/fetch-dns) | ? | ✓ | ✗ | ✓ |
| [dohc](https://www.npmjs.com/package/dohc) | ? | ✗ | ✗ | ✓ |
| [google-dns](https://www.npmjs.com/package/google-dns) | google | ✗ | ✗ | ✓ |
| [dns-over-https](https://www.npmjs.com/package/dns-over-https) / [alternate](https://www.npmjs.com/package/@leeroy/dns-over-https) | google | ✗ | ✗ | ✓ |
| [dns-over-http](https://www.npmjs.com/package/dns-over-http) | ? | ✗ | ✗ | ✓ |
| [chrome-dns](https://www.npmjs.com/package/chrome-dns) | google | Chrome plugin only | ✗ | ✓ |
| [jsdns](https://www.npmjs.com/package/jsdns) | ? | ✗ | ✗ | ✓ |
[dns-packet-typescript](https://www.npmjs.com/package/dns-packet-typescript) - Alternate RFC1035 deserializer