feat(cli): add custom dns resolver option

[khanhnt2]

What's changed:

1. trust-dns-resolver is rebranded to hickory-resolver so I updated the dns resolver library to hickory-resolver, https://github.com/hickory-dns/hickory-dns/releases/tag/v0.24.0

2. Add --resolver option to CLI to use custom dns resolver, you can pass the file path or string comma-delimited list. For example:

# Download resolvers list to a file
$ curl 'https://raw.githubusercontent.com/trickest/resolvers/main/resolvers-trusted.txt' -o 'resolvers-trusted.txt'
$ rustscan -a hackerone.com --resolver resolvers-trusted.txt

Or

$ rustscan -a hackerone.com --resolver 1.1.1.1,8.8.8.8

[bee-san]

Hi! Mind pushing an empty commit? CI has failed to pick this up and I think it'll only pick it up on a new commit? 🤔

[khanhnt2]

Hi @bee-san , I just pushed an empty commit, can you check again?

[bee-san]

Thank you @khanhnt2 !

Just some points :)

• The linting is failing :(

I think this logic might work better:

1. Read from default resolver file. In Linux this is this file. Maybe HickoryDNS has this built in already somewhere or an arg we can use?
   ^^ This should happen without an argument I think
2. We have a Rustscan config file , I think you can use that here to define resolvers too as it'll be useful to not have to redefine them all the time, and you can have system-wide resolvers vs just Rustscan ones

If user enters the resolver argument:
3. Read from file
if fail to read file then:
4. Split string and use those as resolvers
5. If resolvers fail to... resolve, I think RustScan's error handling will take care of this already 🤔

What do you think? Let me know. Thank you for your contribution! <3 :) And maybe some tests would be nice too <3

[bee-san]

Maybe a bit much for 1 PR.

What about:

1. Add some tests
2. Check if Hickory uses the DNS default file?

And I'll make a ticket to address the others :)