dog icon indicating copy to clipboard operation
dog copied to clipboard

A command-line DNS client.

Results 76 dog issues
Sort by recently updated
recently updated
newest added

First of all, thanks a lot for this really nice DNS client! dog was recently packages in nixpkgs. I have opened a pull request to also add the shell completions...

packaging

hi, for testing purposes, it would be really useful if `dog` could allow self signed certs for `--tls`.

- The version of dog being used (`dog --version`): dog-v0.1.0-x86_64-pc-windows-msvc (the name of the release I use) - The command-line arguments you are using: .`\dog.exe -q . -t ANY -n...

One killer feature would be to have a hint on the resolution source. For example, if I do `dog example.com` and I have `example.com`remmaped in my `/etc/hosts` file, it should...

feature request

Commonly used in existing tools are flags -4 and -6. Constraining query to a specific protocol family is essential to validate if query/response behaviour may differ between IPv4 and via...

feature request

I certainly miss AXFR support to view all records in _zone_ and have to fall back to `dig`

feature request

Maybe something like: ./dog -H @https://doh:[email protected]/dns-query example.nl Albeit this method is deprecated as per RFC3986, par. 3.2.1, so perhaps "-u doh -p BeGentle" would be the better approach.

feature request

Hey there! I noticed that for DoT and DoH there is no way to pin the resolver's IP while still passing the hostname that should be used for TLS's SNI....

feature request

Is there any way to generate and include .debs in the release page? I've seen other projects have them, so I imagine there's a Cargo utility to generate them, and...

packaging

When trying to query against a specified nameserver, the command fails. Please see the output below. ``` $ ./dog --version dog ● command-line DNS client v0.1.0 https://dns.lookup.dog/ $ ping -6...

errors › invalid output