Bug 788870
| Summary: | BIND logs errors about DNS environment too verbosely | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | PGE <pro_green_european> |
| Component: | bind | Assignee: | Adam Tkac <atkac> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | CC: | azelinka, ovasik |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 13:41:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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: