Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suggested configuration results in open DNS resolver #11

Open
soletan opened this issue Aug 28, 2024 · 1 comment
Open

suggested configuration results in open DNS resolver #11

soletan opened this issue Aug 28, 2024 · 1 comment

Comments

@soletan
Copy link

soletan commented Aug 28, 2024

The configuration suggested for this plugin is turning a CoreDNS sservice into an open DNS resolver when using CoreDNS as a regular DNS server (not hidden in a k8s cluster). Having a warning as a minimum precaution on using that configuration would be helpful. Having a more specific configuration example limiting use of forward plugin to a certain domain would be even better, though I'm not 100% sure how secure this would be eventually.

@endreszabo
Copy link

We need clarification on why an authoritative DNS server would need to look up external CNAME records. Using the plugin/lookup to run another round of internal DNS lookup is completely fine, but letting it query an external forwarder is suboptimal, at minimum.

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

No branches or pull requests

2 participants