Skip to content

Conversation

@ibigbug
Copy link
Member

@ibigbug ibigbug commented Oct 25, 2025

🤔 This is a ...

  • New feature
  • Bug fix
  • Performance optimization
  • Enhancement feature
  • Refactoring
  • Code style optimization
  • Test Case
  • Branch merge
  • Workflow
  • Other (about what?)

🔗 Related issue link

close #938

💡 Background and solution

Implements EDNS Client Subnet support for DNS queries to provide geolocation hints to upstream DNS servers.

Problem: DNS queries don't include client subnet information, which can result in suboptimal CDN routing and slower response times.

Solution:

  • Added edns-client-subnet configuration option in DNS settings
  • Supports both IPv4 and IPv6 subnet configuration
  • Automatically applies appropriate subnet based on query type (prefers IPv6 for AAAA queries)
  • Respects existing EDNS Client Subnet options in queries

Configuration example:

dns:
  edns-client-subnet:
    ipv4: 1.2.3.0/24
    ipv6: 2001:db8::/56

📝 Changelog

  • New feature: Added EDNS Client Subnet support for DNS queries
  • Configuration: New edns-client-subnet option with ipv4 and ipv6 fields
  • Behavior: Automatically includes client subnet information in upstream DNS queries when configured

☑️ Self-Check before Merge

  • Doc is updated/provided or not needed
  • Changelog is provided or not needed

🤖 Generated with Claude Code

@ibigbug ibigbug changed the title add edns subnet config feat(dns): add edns subnet config Oct 25, 2025
@ibigbug ibigbug merged commit fc9ebc5 into master Oct 25, 2025
29 of 31 checks passed
@ibigbug ibigbug deleted the issue-938 branch October 25, 2025 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] add ECS support for DNS

2 participants