You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0507cbe
Browse filesBrowse the repository at this point in the historyBrowse files
Flag and retry lookups with one failed record type (#357)
Resolve returned a plain Found as soon as any requested type answered,
dropping the error of a type that timed out, was refused or failed. The
failure was neither retried nor counted, so -diff-records could report a
name as changed while the run's verdict stayed complete.
Lookup.ResolvePartial now retries a partial answer like a failed one, up
to Attempts, and returns the records flagged partial when the failed
type never answers. The scan marks such results (Result.Partial, a
"partial" JSON field, PARTIAL in text with records), counts them in
Stats.Partial, lowers the verdict as failed lookups do, and -diff-records
no longer reports a partial name as changed.
Fixes#357
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
68
68
- Less memory on large wordlists and busy scans: `-sources`, `-ct`, `-axfr` and `-permute` check their names against the wordlist without building a set as large as it (about 200 MB per feature and target on a 5M-line list), a `-simulate-zone` lab scan no longer keeps a count per queried name (about 170 MB on a 1M-line list), and a `CNAME` lookup reads a UDP answer into a buffer sized for the 1232-byte EDNS payload it advertises instead of 64 KB. Results are unchanged (#321).
69
69
70
70
### Fixed
71
+
- A name whose lookup of one requested type timed out, was refused or failed while another type answered is no longer a plain found result with the records that came back. The whole lookup is tried again up to `-attempts`, and when the failed type never answers the result is marked partial: a `partial` field in JSON and JSONL, `PARTIAL` in text with `-show-records`, a `partial answers` line in the breakdown, and `Stats.Partial` in the library. Partial answers lower the run's verdict as failed lookups do (degraded at 1%), and `-diff-records` does not report a partial name as changed, since its missing records may only be a lookup that failed (#357).
71
72
- Resuming a scan stopped in its `-permute` pass (Ctrl+C or `-max-duration`) no longer scans the finished main pass again. Under `-recursive` that repeated every lookup below the saved names, and a name the repeat found anew changed the permutation candidate list, so the resumed pass started at the wrong place in a different list, skipping some candidates and testing others twice. The resume state now records that the main pass finished, and the resumed run goes straight to the permutation pass with the saved names as its seeds (#358).
72
73
- When `-max-queries` or `-max-duration` stops a scan whose wordlist holds multi-label entries (such as `dev.api`), the untested names are counted as they would have been: ones `-exclude` would remove count as excluded rather than skipped, so a run whose only untested names were out of scope stays complete, and under `-recursive` a name the rest of the scan would have reached through two parents is counted as skipped once, so tested, skipped and excluded add up to the candidate total (#361).
73
74
- A CNAME target or name server that exists but has no A or AAAA record (NODATA, such as a name with only MX or TXT records) is no longer marked `dangling` or `dangling-ns`: Go reports it as not-found like a name that does not exist, so a target whose address lookup comes back empty now gets one more A query, and only an NXDOMAIN answer marks it. A probe that times out or fails marks nothing (#362).
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -634,6 +634,8 @@ A public name that answers with an internal address leaks how the network behind
634
634
635
635
The scope is an `internal_address` field in JSON and JSONL, `INTERNAL=<scope>` in text with `-show-records`, and a count in the breakdown and the run-quality report (`internal_addresses`). CSV is unchanged: each row already holds one address in its `value` column. Simulated results are never marked, since their addresses are invented.
636
636
637
+
A name that answered for one `-type` while another type's lookup still timed out, was refused or failed after `-attempts` is reported with the records that came back and marked partial: a `"partial": true` field in JSON and JSONL, `PARTIAL` in text with `-show-records`, and a `partial answers` count in the breakdown. Partial answers lower the run's verdict as failed lookups do, and `-diff-records` never reports a partial name as changed.
638
+
637
639
### Monitoring for new subdomains
638
640
639
641
`-diff previous.jsonl` reports only what changed since an earlier run: `+ name` for new subdomains and `- name` for ones that disappeared (only when the run's verdict is `complete`, and only after a fresh lookup of the name returns NXDOMAIN, so names this run did not test and failed lookups are never mistaken for removals). The `-o` file keeps the full current results for the next comparison, and the exit code is `4` when anything changed. The repository is also a GitHub Action (`uses: TMHSDigital/subenum@<release>`) that installs a verified release, keeps the baseline as an artifact, writes a job summary and fails on a bad verdict; [docs/monitoring.md](docs/monitoring.md) documents it and a hand-written scheduled workflow that opens an issue when new names appear.
0 commit comments