[GitHub] [trafficcontrol] jhg03a commented on issue #2388: Global DNS TTL adjustment

2022-10-14 Thread GitBox
jhg03a commented on issue #2388: URL: https://github.com/apache/trafficcontrol/issues/2388#issuecomment-1279211865 And this override shouldn't impact DS who's TTL is already below the override TTL. -- This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [trafficcontrol] jhg03a commented on issue #2388: Global DNS TTL adjustment

2022-10-14 Thread GitBox
jhg03a commented on issue #2388: URL: https://github.com/apache/trafficcontrol/issues/2388#issuecomment-1279209539 As a secondary thing, it would be really nice to know what the max TTL was prior to imposing the override somehow. This is because when you first start to use this feature,

[GitHub] [trafficcontrol] jhg03a commented on issue #2388: Global DNS TTL adjustment

2022-10-09 Thread GitBox
jhg03a commented on issue #2388: URL: https://github.com/apache/trafficcontrol/issues/2388#issuecomment-1272605234 It probably wouldn't need to touch the actual ds, but rather just interpose itself as a higher priority value. -- This is an automated message from the Apache Git Service.

[GitHub] [trafficcontrol] jhg03a commented on issue #2388: Global DNS TTL adjustment

2021-03-16 Thread GitBox
jhg03a commented on issue #2388: URL: https://github.com/apache/trafficcontrol/issues/2388#issuecomment-800389629 I stuck it as medium because directly touching TODB for mass editing is the current workaround and it's quite dangerous.