Ryan Emerle
Ryan Emerle
We should apply unique constraints where the domain demands/assumes it. We cannot have the same zone twice in the `zone` table, and we can't have the same record twice in...
Going to leave this open, seems like something we need to address.
This can help us now as we need to work around this limitation by assigning ourselves to the owner group temporarily, then making the mod. Marking as `ready`
There has been some discussion on this, specifically around whitelisting certain `dotted labels` via configuration. Given that there are specific patterns for various verifications, I think it's a safe approach...
This issue will also occur in the following scenario 1. In an otherwise empty zone `example.com` you create a RRSet with label `foo.bar` 1. Once the authoritative name server (ANS)...
We can enhance the zone view as part of Portal 2.0. We have a global record search that provides read-only access to existing zones
Seems related to #641. If we already have read-only support, then we're just making all users "support users"? May be interesting to see how much effort this really is.
This issue just looks to solve the opaqueness problem, so let's be sure to keep blobs where necessary for zone sync and queueing. However, let's consider a hash-based approach to...
Seems easy to verify and fix if producible.
Seems like low-hanging fruit that can improve site reliability in case of an outage. Moving to ready.