Repository navigation
Run DNS in the background and remove the default query cap - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Start eligible A/AAAA lookups as input domains are parsed and keep processing source files and exclusions while the lookups run. A rolling worker window continuously submits queries as results arrive. The terminal and plain logs show cumulative DNS completions and scheduled queries across expansion rounds.
Remove the default 100,000-query limit. Preserve an explicit
--max-dns-queriescap and its existing sorted query priority. Final bundle generation waits for DNS results.All 34 unit tests passed. A CLI run with 50,001 synthetic domains and a mocked resolver processed all 100,002 queries and displayed
DNS 100,002/100,002 completed.