Protocol Tweaks

Doggo provides several options to tweak the DNS protocol parameters, allowing for fine-grained control over your queries.

Query Flags

Doggo supports setting various DNS query flags:

--aa    Set Authoritative Answer flag
--ad    Set Authenticated Data flag
--cd    Set Checking Disabled flag
--rd    Set Recursion Desired flag (default: true)
--z     Set Z flag (reserved for future use)
--do    Set DNSSEC OK flag

Examples

Request an authoritative answer:
Terminal window
```
doggo example.com --aa
```
Request DNSSEC data:
Terminal window
```
doggo example.com --do
```
Disable recursive querying:
Terminal window
```
doggo example.com --rd=false
```

EDNS Options

EDNS (Extension Mechanisms for DNS) provides additional capabilities beyond basic DNS queries. Doggo supports several EDNS0 options:

--nsid      Request Name Server Identifier
--cookie    Request DNS Cookie for enhanced security
--padding   Request EDNS padding for privacy
--ede       Request Extended DNS Errors
--ecs       EDNS Client Subnet (e.g., '192.0.2.0/24')

EDNS Examples

Name Server Identifier (NSID) - Identify which server responded:
Terminal window
```
doggo google.com --nsid @8.8.8.8
```
Output includes:
```
EDNS Information:
  NSID: gpdns-maa
```
EDNS Client Subnet (ECS) - Get geo-aware responses:
Terminal window
```
# Query as if from USA
doggo netflix.com --ecs 8.8.8.0/24 @8.8.8.8

# Query as if from India
doggo netflix.com --ecs 49.207.0.0/24 @8.8.8.8
```
This reveals how CDNs route traffic based on client location. Netflix will return different IP addresses for different regions!
DNS Cookie - Enhanced security against spoofing:
Terminal window
```
doggo example.com --cookie @1.1.1.1
```
EDNS Padding - Privacy protection against traffic analysis:
Terminal window
```
doggo example.com --padding @1.1.1.1
```
Extended DNS Errors (EDE) - Detailed error information:
Terminal window
```
doggo nonexistent.example --ede @1.1.1.1
```

Combine multiple EDNS options:

doggo example.com --nsid --cookie --padding --do @8.8.8.8

Understanding ECS (EDNS Client Subnet)

ECS allows DNS resolvers to include client subnet information in queries, enabling authoritative servers to provide location-aware responses. This is commonly used by:

CDNs (Content Delivery Networks) to direct users to nearby servers
Streaming services like Netflix to serve region-specific content
Cloud providers to optimize latency

How it works:

You specify a subnet (e.g., --ecs 8.8.8.0/24)
DNS resolver includes this in the query to the authoritative server
Server responds with IPs optimized for that geographic region
Response includes the actual scope used (e.g., Scope: 24)

Real-world example:

# From USA - returns AWS US-East servers
doggo netflix.com --ecs 8.8.8.0/24 @8.8.8.8

# From India - returns AWS EU-Ireland servers
doggo netflix.com --ecs 49.207.0.0/24 @8.8.8.8

# Different IPs returned based on location!

This lets you test geo-routing without traveling to different countries!