test(dns): update input, requires, and enable recursion

[dwisiswant0]

Proposed changes

Fix #6012

Checklist

• Pull request is created against the dev branch
• All checks passed (lint, unit/integration/regression tests etc.) with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Summary by CodeRabbit

• Tests
  • Updated DNS request test to use Google DNS server
  • Modified test expectations to check for multiple DNS results
  • Enabled DNS recursion in test configuration
• Chores
  • Updated minimum required Go version from 1.21.0 to 1.22.0
  • Aligned toolchain version with the new Go version
  • Retraction of version v3.2.0 noted due to a broken JavaScript protocol issue

[coderabbitai]

Walkthrough

The pull request modifies the TestDNSExecuteWithResults test in the DNS request test file. The changes update the DNS query parameters, including enabling recursion, changing the target IP to Google's DNS server (8.8.8.8), and adjusting the test expectations to look for multiple DNS results. These modifications aim to improve the test's reliability and accuracy in verifying DNS request functionality.

Changes

File	Change Summary
pkg/protocols/dns/request_test.go	- Set recursion to true - Updated target IP to "8.8.8.8" - Changed domain from "example.com" to "dns.google" - Modified result assertions to expect at least 2 results - Added verification for multiple DNS server IPs
go.mod	- Updated Go version from 1.21.0 to 1.22.0 - Updated toolchain version from go1.22.5 to go1.22.0 - Added version retraction for v3.2.0

Assessment against linked issues

Objective	Addressed	Explanation
Fix failing TestDNSExecuteWithResults	✅
Ensure test reflects expected behavior	✅

Poem

🐰 A DNS test hopping along,
With Google's servers, nothing wrong!
Recursion enabled, results galore,
Two IPs dancing through the core,
A rabbit's test of network lore! 🌐

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 98671a6 and 00d30c3.

📒 Files selected for processing (1)

• go.mod (1 hunks)

🔇 Additional comments (2)

go.mod (2)

Line range hint 284-284: LGTM: Well-documented version retraction.

The version retraction for v3.2.0 is properly documented with a clear reason (broken JavaScript protocol issue).

---

3-3: Verify compatibility with Go 1.22.0.

The upgrade from Go 1.21.0 to 1.22.0 is a major version bump. Please ensure all dependencies are compatible with Go 1.22.0.

✅ Verification successful

Go 1.22.0 upgrade appears safe to proceed.

The codebase and its dependencies show no compatibility issues with Go 1.22.0. All direct dependencies are using recent versions and no explicit version constraints were found.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any compatibility issues with Go 1.22.0

# Check if any dependencies explicitly require an older Go version
rg "go [0-9]+\.[0-9]+(\.[0-9]+)?" -g "go.mod" --no-filename

# Look for any Go version constraints in dependency documentation
rg -i "requires go (?:1\.2[0-1]|1\.[0-9]|[0-9])\." -g "*.md" --no-filename

Length of output: 146

---

Script:

#!/bin/bash
# Get direct dependencies and their versions
echo "Direct dependencies from go.mod:"
cat go.mod | awk '/^require \(/{p=1;next} /\)/{p=0} p{print}' | grep -v '^$'

# Check for any go.mod files in vendor directory that might specify different Go versions
echo -e "\nChecking vendor directory for different Go versions:"
fd -g 'go.mod' -t f vendor/ -x cat {} \; 2>/dev/null | grep "^go "

# Look for build constraints or Go version checks in .go files
echo -e "\nChecking for Go version constraints in source code:"
rg "^//\s*\+build\s+.*go" -g "*.go"
rg "go[0-9]{1,2}\.[0-9]{1,2}" -g "*.go" -C 2

Length of output: 17961

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.