Bug 487252
| Summary: | Build with --enable-fixed-rrset | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bernie Innocenti <bernie+fedora> |
| Component: | bind | Assignee: | Adam Tkac <atkac> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | atkac, ovasik, pwouters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-03-09 10:58:40 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: | |||
It will significantly increase memory footprint. Could you please specify why do you need exact rrset order, please? (In reply to comment #1) > It will significantly increase memory footprint. Could you please specify why > do you need exact rrset order, please? It allows one to have several PTR records to match all the A records of a machine, while clients will generally pick only the first one. Having correct PTR records for ns1.example.com is a requirement for nameservers in some TLDs, but if the IP is associated with several services, you don't want "ns1.example.com" to show up randomly for your host. Anyway, if it considerably increses memory usage, we can probably live without. If you are able to setup your machines without rrset-order option it would be nice because additional memory consumtion with fixed rrsets is non-trivial. I'm closing this bug for now. If you _really_ need named build with --enable-fixed-rrset please reopen this bug. Thanks. |
This is required in order to make the following configuration work as expected: rrset-order { type PTR order fixed; order cyclic; }; I don't know what the impact is on performance and other features, but there might be a reason why this is not enabled by default.