-
|
I'm using dnsX to check sources from old lists, and have results as follows: Input: https://github.com/HexxiumCreations/threat-list/blob/gh-pages/domainsonly I'd expect the resulting list to have 2,978 entries with dead sources giving a "NXDOMAIN" status code. Are hosts returning "NXDOMAIN" still alive? Are all the completely dead hosts filtered out automatically? From "Running dnsX" I'm guessing dead hosts are filtered, but just want to double-check. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
@T145 Yes, not sure what cmd you used to run dnsx, but on default run it filters dead record, but optionally you can include other type of response as well if using Here is the output for the same input https://temp.sh/EUjhf/filtered.json that only contains valid DNS entries only. |
Beta Was this translation helpful? Give feedback.
-
|
My command is similar to this: cat domainsonly | dnsx -r ./configs/resolvers.txt -json -silent -rcode $(seq -s, 0 23) -retry 2Does this not print only valid DNS entries? |
Beta Was this translation helpful? Give feedback.
-
|
update the cmd to include only |
Beta Was this translation helpful? Give feedback.
-
|
I think my confusion was between switching the context in either "active" and "valid." Only active hosts are printed, and host DNS validity is filtered by the response code. Thanks for the help! |
Beta Was this translation helpful? Give feedback.
@T145 Yes, not sure what cmd you used to run dnsx, but on default run it filters dead record, but optionally you can include other type of response as well if using
rcodeflag.Here is the output for the same input https://temp.sh/EUjhf/filtered.json that only contains valid DNS entries only.