1.0.10 • Published 4 years ago
soans v1.0.10
soans (SOA-based NS Lookup)
Find NS records in the DNS Hierarchy by discovering and directly querying SOA records.
Note: This library uses direct UDP/TCP communications to the Authorities so DNS caching is avoided and results are provided nearly immediately after records are added.
This library will take a given domain and walk through each of the subdomains
finding SOA records ("authorities") then check each authority for the
existence of an NS record.
For example, a domain of foo.bar.baz.scaffold.ly will do the following:
- Find
SOA(if any) on:bar.baz.scaffold.lybaz.scaffold.lyscaffold.lyly(TLDs fetchNSrecords)
- Then for each valid
SOA, find the first withNSrecords.- In the event the
SOArecord reports NS records (e.g. records have been added but the zone doesn't exist yet) return those NS records
- In the event the
CLI
$ npx soans scaffold.ly
ns-1014.awsdns-62.net
ns-1219.awsdns-24.org
ns-1914.awsdns-47.co.uk
ns-234.awsdns-29.comInstallation
yarn:
yarn add soansnpm:
npm install --save soansUsage
import { NsLookup } from 'soans';
(await NsLookup('facebook.com')).addresses;
// ["a.ns.facebook.com","b.ns.facebook.com","d.ns.facebook.com","c.ns.facebook.com"]
(await NsLookup('asdf.facebook.com')).addresses;
// Throws NoNameserversError
(await NsLookup('doesnotexist.doesnotexist')).addresses;
// Throws NoAuthoritiesError
(await NsLookup('facebook.com', { proto: 'tcp', defaultDns: '8.8.8.8' })).addresses;
// ["a.ns.facebook.com","b.ns.facebook.com","d.ns.facebook.com","c.ns.facebook.com"]Options
proto:
Set the default protocol, either tcp or udp. If tcp fails, fall back to udp.
Default: udp
defaultDns:
Set the default DNS to use for authoratitive lookups.
Default: one.one.one.one
Issues
Create an issue in GitHub issues for this repostiory.
Authors
Sponsored By
License
MIT