-
Notifications
You must be signed in to change notification settings - Fork 790
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
Feature: Unbound: AAAA-only mode #5944
Comments
@maurice-w can you check 4bc0871 for me on top? too many variables in the config and if/else bootstrap for my taste |
@fichtner Thanks for the clean-up, works fine! We don't strictly need the core/src/etc/inc/plugins.inc.d/unbound.inc Line 128 in 4bc0871
Same here for .= :core/src/etc/inc/plugins.inc.d/unbound.inc Line 131 in 4bc0871
|
for consistency and later additions all the conditionals should only append (and clear lines if they add full configuration lines). |
Makes sense, I'll keep that in mind. Thanks! |
sorry my dumb question but I'm new to OPNsense and Unbound |
@KDGundermann There is no A-only mode. What problem would that solve? |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
Some poorly implemented devices (IoT) do have IPv6 support, but prefer IPv4 whenever possible. These devices do perform DNS queries for A + AAAA records. If both exist, they should use IPv6, but actually use IPv4. Some devices don't even "fall back" to IPv6 in case IPv4 connections fail. The solution to this is only sending AAAA records in DNS responses, which successfully forces these devices to use IPv6.
Describe the solution you like
I would like an option in the Unbound settings which removes all A records from responses. Since this only makes sense if all host names have AAAA records, this option should only apply if DNS64 is enabled.
Additional context
This is also useful for testing which devices / applications brake if there are no A records in DNS at all.
The text was updated successfully, but these errors were encountered: