Opened 13 years ago
Closed 11 years ago
#10 closed enhancement (fixed)
Support multiple DNS views
Reported by: | Kris Deugau | Owned by: | somebody |
---|---|---|---|
Priority: | minor | Milestone: | 1.2 |
Version: | Keywords: | ||
Cc: |
Description (last modified by )
Mainly targetted at tinydns's "%name:allowedip" scope restriction; should be supportable with BIND views and/or split-horizon config
Change History (23)
comment:1 by , 13 years ago
Milestone: | → 1.4 |
---|
comment:2 by , 12 years ago
Description: | modified (diff) |
---|---|
Milestone: | 1.4 → 1.2 |
comment:3 by , 12 years ago
Summary: | Support multiple DNS views/clusters → Support multiple DNS views |
---|
comment:4 by , 12 years ago
comment:5 by , 12 years ago
(In [372]) /trunk
Checkpoint adding location/view support. See #10.
- minor location list template tweak
- extend importer to deal with locations on records, and location definitions
- extend exporter to handle locations
Also:
- minor SQL error-log cleanup (boolean types use 'y'/'n' or 'true'/'false'). See #25, sort of
- Fix handling of CNAME exports for reverse zones; the records look ugly but there's no simple way to autoconvert them to the template types on import
- Fix lurking buglet in tabledef update; we're using a 4-char field for locations to allow for legacy uses.
comment:6 by , 12 years ago
comment:7 by , 12 years ago
(In [375]) /trunk
Checkpoint adding locations/views. See #10.
- Tweak new locations table again with an internal serial for sorting and finding the "highest" previous location
- Complete "Add location" stub
- Fill in initial display page for "Edit location"
- Tweak location add/edit/update template a little, add new comments field to match new field in table
- Tweak location import so we don't end up with great long space-free fields similar to what can't be avoided with TXT (usually SPF/DomainKeys) records
- Fill in addLoc() stub
- Add getLoc()
- Tweak location export to strip commas and whitespace properly
comment:8 by , 12 years ago
comment:9 by , 12 years ago
comment:10 by , 12 years ago
comment:11 by , 12 years ago
(In [383]) /trunk
Checkpoint adding location support to UI. See #10.
- Add location entries to new domain, record list, and record add/edit templates
- Add UI sub to fill location dropdown on new domain and record add/edit templates
- Fix thinko in initial setting of location_view permission
- Handle display properly if user does not have location_view permission
- Add DB-interfacing subs in DNSDB.pm to get the default location set on a zone, and to return a list of locations suitable for a UI dropdown
comment:12 by , 12 years ago
comment:13 by , 12 years ago
comment:14 by , 12 years ago
comment:15 by , 12 years ago
comment:16 by , 12 years ago
comment:17 by , 12 years ago
comment:18 by , 12 years ago
comment:19 by , 12 years ago
comment:20 by , 12 years ago
comment:21 by , 12 years ago
comment:22 by , 12 years ago
(In [516]) /trunk
Tune up location/view handling on zone add. See #10.
Domains and revzones added with a location specified will actually use
that location. Documentation note: Zones specifying a location on
creation will only be visible to that location, because the SOA record
will be created with that location. A zone should be created with no
location set if records must be visible across multiple locations, or
publicly.
comment:23 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Haven't triggered any new bugs with locations/views, resolving
(In [370]) /trunk