Usage Examples

These examples showcase how to combine different features for powerful DNS querying.

Basic Queries

Simple A record lookup:
Terminal window
```
doggo example.com
```
Query for a specific record type:
Terminal window
```
doggo AAAA example.com
```
Query multiple record types simultaneously:
Terminal window
```
doggo A AAAA MX example.com
```

Query using a specific DNS resolver:
Terminal window
```
doggo example.com @1.1.1.1
```

Use DNS-over-HTTPS (DoH):

doggo example.com @https://cloudflare-dns.com/dns-query

Use DNS-over-TLS (DoT):
Terminal window
```
doggo example.com @tls://1.1.1.1
```
Query multiple resolvers and compare results:
Terminal window
```
doggo example.com @1.1.1.1 @8.8.8.8 @9.9.9.9
```

Perform a reverse DNS lookup:
Terminal window
```
doggo --reverse 8.8.8.8
```
Set query flags for DNSSEC validation:
Terminal window
```
doggo example.com --do --cd
```
Use the short output format for concise results:
Terminal window
```
doggo example.com --short
```
Show query timing information:
Terminal window
```
doggo example.com --time
```

Perform a reverse lookup with short output and custom resolver:
Terminal window
```
doggo --reverse 8.8.8.8 --short @1.1.1.1
```
Query for MX records using DoH with JSON output:
Terminal window
```
doggo MX example.com @https://dns.google/dns-query --json
```
Use IPv6 only with a specific timeout and DNSSEC checking:
Terminal window
```
doggo AAAA example.com -6 --timeout 3s --do
```

Use JSON output for easy parsing in scripts:

doggo example.com --json | jq '.responses[0].answers[].address'

Batch query multiple domains from a file:
Terminal window
```
cat domains.txt | xargs -I {} doggo {} --short
```
Find all nameservers for a domain and its parent domains:
Terminal window
```
doggo NS example.com example.com. com. . --short
```

Extract all MX records and their priorities:

doggo MX gmail.com --json | jq -r '.responses[0].answers[] | "\(.address) \(.preference)"'

Count the number of IPv6 addresses for a domain:

doggo AAAA example.com --json | jq '.responses[0].answers | length'

Enable debug logging for verbose output:
Terminal window
```
doggo example.com --debug
```
Compare responses with and without EDNS Client Subnet:
Terminal window
```
doggo example.com @8.8.8.8
doggo example.com @8.8.8.8 --z
```
Test DNSSEC validation:
Terminal window
```
doggo rsasecured.net --do @8.8.8.8
```
This example uses a domain known to be DNSSEC-signed. The --do flag sets the DNSSEC OK bit.

Note: DNSSEC validation can be complex and depends on various factors:
- The domain must be properly DNSSEC-signed
- The resolver must support DNSSEC
- The resolver must be configured to perform DNSSEC validation
If you don’t see DNSSEC-related information in the output, try using a resolver known to support DNSSEC, like 8.8.8.8 (Google) or 9.9.9.9 (Quad9).
Compare responses with and without EDNS Client Subnet:
Terminal window
```
doggo example.com @8.8.8.8
doggo example.com @8.8.8.8 --z
```

Check for DNSSEC records (DNSKEY, DS, RRSIG):

doggo DNSKEY example.com @8.8.8.8
doggo DS example.com @8.8.8.8
doggo RRSIG example.com @8.8.8.8

Verify DNSSEC chain of trust:

doggo example.com --type=A --do --cd=false @8.8.8.8