ddrill tries to query the most direct
authoritative nameserver, by-passing any recursive caching resolvers that might
prevent you from seeing a recently update record.
From the README:
When querying a record like `foo.bar.example.com` `ddrill` will query the FQDN
`foo.bar.example.com` for `NS` records.
If it finds them it will query those nameservers for the record directly.
If it does not, it shortens the FQDN to `bar.example.com` and tries again,
working up the chain until it (hopefully) finds a nameserver to use.
I wrote this to scratch a particular sysadmin itch. Also, my first Codeberg repo.
last updated: