Hide Forgot
Description of problem: Newer versions of BIND (>= 9.7.1) have the option to filter AAAA (ipv6) records for ipv4-only clients. Version-Release number of selected component (if applicable): 9.8.2-0.17.rc1 Steps to Reproduce: 1. Add `filter-aaaa-on-v4` to named options. 2. Run `service named reload` 3. Watch for error in messages log. Actual results: Error from messages log: option 'filter-aaaa-on-v4' is not configured Expected results: If bind-9.8 is compiled with configure option `--enable-ipv6`, then `--enable-filter-aaaa` should also be a configure option. This should help in dual-stack environments where some clients are ipv4-only, and both A and AAAA records exist for a given hostname. Additional info: Suggested fix: Add `--enable-filter-aaaa` to configure options in bind.spec
Created attachment 817562 [details] bind.spec.patch proposed configure option attached in patch
(In reply to Eric Wolfe from comment #0) > If bind-9.8 is compiled with configure option `--enable-ipv6`, then > `--enable-filter-aaaa` should also be a configure option. Not necessarily. filter-aaaa-on-v4 should be used only when really necessary, since it can cause some problems. But I agree that we should enable the choice to users.
Tomas, yes, I understand it may not be appropriate in all cases. I really just want the ability to test this in our environment, using the package as shipped with RHEL.
*** Bug 1036563 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1373.html