Horizon does not display TTLs for NS and SOA records
Bug #1675244 reported by
Matthew Taylor
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Designate |
New
|
Undecided
|
Unassigned | ||
| Designate Dashboard |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Originally reported here: https:/
Horizon does not display TTLs for NS and SOA records once a domain has been created.
Creation of the domain + specifying the TTL, then dig @ns.blah.com <domain here> NS (or SOA) indicates that the correct TTL is being applied.
This can be replicated by Creating a domain via Horizon, specifying a TTL at the time of creation, then Managing Records of the domain created shortly after.
Revision history for this message
| Dr. Jens Harbott (j-harbott) wrote | #1 |
| Changed in designate-dashboard: | |
| status: | New → Invalid |
To post a comment you must log in.
This is not specific to the dashboard, one can see the TTL not being set for the NS+SOA recordsets via the CLI, too. I'm not sure though whether this is intended behaviour or a bug.