doggo
doggo is a modern DNS command-line client for routine lookups, selected resolvers, encrypted DNS, reverse queries and JSON output.
What doggo is for
doggo is a DNS command-line client with readable tables and response timing. It supports A, AAAA, MX and TXT records, reverse lookups, one or more selected resolvers and several transport modes including UDP, TCP, DoH, DoT, DoQ and DNSCrypt. JSON output makes it practical to connect a lookup to a script or monitoring check.
Why compare resolvers
A single lookup represents one moment, one resolver and one network path. Browsers, security software, VPNs and operating systems may use different DNS settings, while cache TTL can make answers temporarily diverge. Record the type, resolver, protocol, response status and timing, then compare the result with authoritative configuration and the expected service behavior.
Privacy and network boundaries
A public resolver receives the domain names being queried. DoH or DoT encrypts the transport path, but the resolver can still see the request. Encrypted DNS may also interact with organization policies and auditing, so use an approved service rather than treating a successful answer as the only goal.
Maintenance note
This page was reviewed on 2026-08-23 against doggo 1.2.0, its query types, transport modes, JSON output, reverse lookup and diagnostic behavior. The archived package is a Windows x64 ZIP.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave doggo to this cloud drive
Baidu Netdisk
Save doggo to this cloud drive
doggo Windows DNS troubleshooting guide
Compare the default resolver with a selected resolver and protocol. Record the baseline first, then change one variable at a time.
Before you start
- Use a publicly queryable test domain and do not send private internal names to an unapproved public resolver.
- Confirm that the Windows x64 executable matches the system and that the network can reach DNS or HTTPS services.
- Record the current network, VPN, proxy and system DNS settings so differences have a known context.
Installation steps
- 01
Extract and verify the program
Unzip the package into a stable directory and run a help or version command from PowerShell.
- 02
Decide whether to add it to PATH
Run from the current directory for a one-off check. Add the tools directory to the user PATH only for scripts or regular troubleshooting, and pin the version.
- 03
Query a known domain first
Run a default A-record lookup for a known reachable domain and confirm terminal output, response time and basic network access.
Quick start
- 01
Inspect the default answer
Run doggo with a domain and review status, answers, TTL, resolver and latency rather than looking only for an IP address.
- 02
Compare types and resolvers
Query MX, TXT or AAAA records and use the resolver option to compare another server, noting answer and TTL differences.
- 03
Test encrypted DNS or JSON
Use an approved DoH endpoint for an HTTPS lookup. Enable JSON for automation and handle empty answers, timeouts and error states separately.
Usage tips
- DNS propagation is governed by TTL and cache behavior; compare authoritative records and cache age before calling an answer wrong.
- Encrypted DNS protects the transport from casual interception but does not make the resolver blind or bypass organizational policy.
- Pin output fields and version in scripts; colored tables are for people, not stable text parsing.
Troubleshooting and uninstall
Why does UDP time out while DoH succeeds?
Check the local firewall, VPN, provider or organization network for restrictions on port 53. This shows a transport-path difference, not that the domain is configured correctly.
Why do resolvers return different IP addresses?
Check CDN, geographic routing and split-horizon DNS, then compare authoritative records and TTL. Confirm the intended policy instead of choosing the result that merely looks familiar.
- Remove the program and script referencesRemove PATH and automation references before deleting the extracted directory, keeping query records needed to reproduce an incident.
Frequently asked questions
Can doggo replace nslookup or dig directly?
It handles common lookups with readable output and encrypted transports, but scripts that depend on dig-compatible flags should be tested before switching.
Does choosing a public DNS resolver expose the query?
The selected resolver receives the domain name. Encryption protects transport, not the resolver's visibility, so choose a service that fits privacy and organization policy.
Why does the browser disagree with doggo?
The browser may use its own DoH, cache, proxy or search-domain settings. Compare resolver, record type, TTL, IPv4/IPv6 and browser secure-DNS configuration.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.