Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multi domain wildcard filtering #159

Closed
marcelo321 opened this issue Nov 3, 2022 · 1 comment · Fixed by #313
Closed

multi domain wildcard filtering #159

marcelo321 opened this issue Nov 3, 2022 · 1 comment · Fixed by #313
Assignees
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@marcelo321
Copy link

Please describe your feature request:

I want to start using shuffledns and I think a core element it is lacking is multi domain wildcard filtering. Let's say you have a list of 10k subdomains from different root domains, it would be ideal to run:

cat subs | shuffledns -r resolvers

and that shufflendns resolves all subdomains, and then does wildcard filtering subdomain by domain.

Describe the use case of this feature:

Similar to what 'puredns' does, it resolves any list given, and then checks for all wildcards. As it is right now, you would have to loop over every single different root domain, which makes it a bit useless as it wastes so much time like that.

@marcelo321 marcelo321 added the Type: Enhancement Most issues will probably ask for additions or changes. label Nov 3, 2022
@Mzack9999 Mzack9999 self-assigned this Apr 29, 2024
@Mzack9999
Copy link
Member

Mzack9999 commented Apr 29, 2024

Tasks:

  • Improve wildcard filtering performance
  • Implement any missing functionality available in other similar engines such as puredns

@ehsandeep ehsandeep linked a pull request Apr 30, 2024 that will close this issue
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants