Opened 12 years ago
Last modified 9 years ago
#41 new enhancement
Add flag table for deciding which blocks have rDNS RPC actions done
Reported by: | Kris Deugau | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 3.0 |
Version: | Keywords: | ||
Cc: |
Description
Rather than hope and pray that all netblocks can and will have rDNS trackable and manageable in the IPDB, add a table recording which ranges/blocks should show the rDNS field and make the necessary RPC calls. This allows a more gradual transition from other management of rDNS to IPDB-propagated changes.
Change History (6)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
(In [754]) /trunk
Wrap almost all existing RPC calls in suitable barriers so we don't try
to make changes for IP blocks not in dnsadmin:
- Add new allocation (any type - note, may not handle edge case of a multizone block well or at all)
- Allocation update
- Split block
- Shrink block
- Delete allocation (arguably this could be done unconditionally)
Note an exception to skipping rDNS changes when deleting a master block.
Fix a minor logic bug in getBlockRDNS; return the cached value and leave
the cached flag set if nothing was retrieved. This seems marginally less
wrong than retrieving nothing and unsetting the flag.
(In [753]) /trunk