FbIN/public-dns-resolvers
1
0
Fork 0
mirror of https://github.com/trickest/resolvers.git synced 2026-04-18 06:06:14 +05:30
Code Issues Projects Releases Packages Wiki Activity

Update README.md

Browse source
This commit is contained in:
Mohammed Diaa 2022-05-09 03:38:32 +02:00 • committed by GitHub
commit 2c79bafcf9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -3,26 +3,26 @@
There are three files here:
- `resolvers.txt`
A simple list of resolver IP addresse, which you can pass directly to you DNS enumeration tool.
A simple list of resolver IP addresses, which you can pass directly to your DNS enumeration tool.
- `resolvers-extended.txt`
All of the resolvers in `resolvers.txt` with additional information about each server, including the organization it belongs to, its country, and how many times it has been detected as valid.
All of the resolvers in `resolvers.txt` with additional information about each server, including the organization it belongs to, its country, and how many times it has been detected as valid. If a resolver is valid enough times, it may earn its place in the next file.
- `resolvers-trusted.txt`
A list of trusted resolvers from organizations like Cloudflare, Google, etc. We recommend you use this list to re-validate the results you get with the main resolvers.
## How it Works
A [Trickest](https://trickest.com) workflow creates an initial dataset of resolvers from various sources then uses multiple instances of [dnsvalidator](https://github.com/vortexau/dnsvalidator) to validate and re-validate this dataset and make it as reliable as possible.
A [Trickest](https://trickest.com) workflow creates an initial dataset of resolvers from various sources and then uses multiple instances of [dnsvalidator](https://github.com/vortexau/dnsvalidator) to validate and re-validate this dataset and make it as reliable as possible.
![Trickest Workflow](resolvers.png "Trickest Workflow - Resolvers")
### TB; DZ (Too big; didn't zoom)
- We collect the inital dataset from three sources:
- We collect the initial dataset from three sources:
- [The Public DNS Server List](https://public-dns.info/nameservers.txt)
- A list of provider DNS servers collected from [bass](https://github.com/Abss0x7tbh/bass/tree/master/resolvers) (Thanks, [Abss0x7tbh](https://github.com/Abss0x7tbh)).
- A community-maintained list of resolvers on [janmasarik/resolvers](https://github.com/janmasarik/resolvers) (Thanks, [janmasarik](https://github.com/janmasarik)).
- This mega list of resolvers is then `sort -u`'d and split up into smaller chunks.
- This mega list of resolvers is then `sort -u`d and split up into smaller chunks.
- Multiple instances of [dnsvalidator](https://github.com/vortexau/dnsvalidator) are created to validate the resolver lists in parallel (Huge thanks to [vortexau](https://github.com/vortexau) and [codingo](https://github.com/codingo)).
- Then we run another round of [dnsvalidator](https://github.com/vortexau/dnsvalidator) to weed out any false-positives that survived the previous step.
- Then we run another round of [dnsvalidator](https://github.com/vortexau/dnsvalidator) to weed out any false positives that survived the previous step.
- The final resolvers list is passed to a `whois` script (which uses [APNIC](https://www.apnic.net/)'s API) to find out the organization and country to which each resolver belong.
- In the end, the workflow counts the number of times it found each resolver to be valid throughout all the previous runs and writes the frequency data to `resolvers-extended.txt`.
- This workflow is scheduled to run constantly.