Closed mr-karan closed 2 months ago
Need to prioritize concurrent resolver lookup support though to improve performance.
Just pushed a concurrent version of lookups. Speed up is around 80% :rocket:
time doggo example.com A AAAA CNAME MX NS PTR SOA SRV TXT CAA @1.1.1.1
0.01s user 0.01s system 1% cpu 1.356 total
time ./bin/doggo.bin example.com A AAAA CNAME MX NS PTR SOA SRV TXT CAA @1.1.1.1
0.00s user 0.01s system 4% cpu 0.297 total
related, but different: there's an ANY (meta?) query type, which depends on server-side support and seems to be deprecated, but still widely deployed. for reference, see dig any x.com
That's still possible with doggo ANY x.com @8.8.8.8
. However, most large scale DNS servers are moving away from ANY
so it's not a good idea to depend on this.
Using
--any
it will query multiple common record types.