BIND 10 #2755: the use of "list" structures for configuration considered harmful
BIND 10 Development
do-not-reply at isc.org
Sun Mar 3 10:51:23 UTC 2013
#2755: the use of "list" structures for configuration considered harmful
-------------------------------------+-------------------------------------
Reporter: cas | Owner:
Type: defect | Status: new
Priority: medium | Milestone: New
Component: Unclassified | Tasks
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: Core | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by cas):
Replying to [comment:1 vorner]:
>There's a need for list in data_sources (the ordering does matter, for
performance and for preference if the zone is provided from more places).
while a "list" structure does matter for performance, it should only
exist in memory in the processes, but not in the configuration files
(neither on the server, nor in the API or in the user interfaces).
where ordering does matter, the configuration objects should have a
property of "priority/preference" or "weight". DNS, DHCP and Network
admins are familiar with that concepts (MX-, SRV-records, DHCP server
priority, router priority in OSPF). The order is generated when the
configuration is applied based on the relative values.
Using "priority/preference/weight" values, the values can be set without
knowing the list index and without overwriting other existing
configuration items.
--
Ticket URL: <http://bind10.isc.org/ticket/2755#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list