[
https://issues.apache.org/jira/browse/TC-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Durfey updated TC-289:
---------------------------
Labels: crconfig soa ttl (was: )
> Delivery service TTLs/SOA data are hard coded in CRConfig generation code
> -------------------------------------------------------------------------
>
> Key: TC-289
> URL: https://issues.apache.org/jira/browse/TC-289
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Router
> Reporter: Eric Friedrich
> Priority: Minor
> Labels: crconfig, soa, ttl
>
> The TTLs and SOA timing data (retry, etc) that appear in the delivery service
> object in the CRConfig are currently hardcoded. This means, for example, that
> there is no way to adjust the TTL or timing values in the SOA, or TTLs of
> things like NS records. These should be configurable on a
> per-delivery-service basis, and if the values don't exist, the defaults from
> the Traffic Router's profile parameters should be used. Only if the profile
> parameters are missing should we fall back to hardcoded values.
> https://github.com/Comcast/traffic_control/issues/178
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
