Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Trying to filter AAAA records like this:
options {
filter-aaaa-on-v4 yes;
filter-aaaa { 192.168.0.1; };
};
Version-Release number of selected component (if applicable):
bind-9.7.3-8.P3.el6_2.2.x86_64
How reproducible:
All the time
Steps to Reproduce:
1. Install bind.
2. Try to enable filter-aaaa & filter-aaaa-on-v4.
Actual results:
/etc/named.conf:64: option 'filter-aaaa-on-v4' is not configured
/etc/named.conf:64: parsing failed
Expected results:
No error messages like this in logfile:
named[1269]: DNS format error from DNSSERVER#53 resolving www.dom.tld/AAAA for client IPADDRESS#54915: invalid response
Additional info:
The filter-aaaa* options don't help you with the "invalid response" errors. Those errors indicate that other servers respond with invalid answers.
The filter-aaaa* options aren't currently compiled in bind and their primary use is not to return AAAA records to clients. They don't control if named asks for AAAA records and caches them (named always asks for AAAA records).
More proper solution for this issue is to backport patch for bug #645544 to RHEL-6. With that fix those error messages will only appear when you start named with "-d1" parameter.
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-2012-0830.html
Description of problem: Trying to filter AAAA records like this: options { filter-aaaa-on-v4 yes; filter-aaaa { 192.168.0.1; }; }; Version-Release number of selected component (if applicable): bind-9.7.3-8.P3.el6_2.2.x86_64 How reproducible: All the time Steps to Reproduce: 1. Install bind. 2. Try to enable filter-aaaa & filter-aaaa-on-v4. Actual results: /etc/named.conf:64: option 'filter-aaaa-on-v4' is not configured /etc/named.conf:64: parsing failed Expected results: No error messages like this in logfile: named[1269]: DNS format error from DNSSERVER#53 resolving www.dom.tld/AAAA for client IPADDRESS#54915: invalid response Additional info: