Hey Ori,
I believe the delivery service specific TTL setting issue you describe
is a bug. We haven't been on 1.7 for some time, but to the best of my
knowledge it's still an issue. TC-200 and TC-254 document the issue.
We're at the Traffic Control summit now, and will be doing a bug scrub
later
Hi,
I am using TC 1.7.
I have an HTTP delivery service and would like to change the TTL of the A
records traffic router is responding with,
When changing the parameters tld.ttls.A or tld.ttls. it has no effect
on the TTLs passed in the CRConfig.json. It always stays 3600, which is
different