Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global DNS TTL adjustment #2388

Closed
jhg03a opened this issue Jun 11, 2018 · 7 comments · Fixed by #7143
Closed

Global DNS TTL adjustment #2388

jhg03a opened this issue Jun 11, 2018 · 7 comments · Fixed by #7143
Labels
medium impact impacts a significant portion of a CDN, or has the potential to do so new feature A new feature, capability or behavior Traffic Ops related to Traffic Ops

Comments

@jhg03a
Copy link
Contributor

jhg03a commented Jun 11, 2018

As a SRE, I would like the ability to adjust all delivery service DNS TTLs to a lower temporary value. This would allow for quicker turnaround time when performing Traffic Router maintenance that involves restarts. This can be performed today with a direct SQL query, but that's a non-advised solution.

@jhg03a jhg03a added new feature A new feature, capability or behavior Traffic Ops related to Traffic Ops usability labels Jun 13, 2019
@mitchell852
Copy link
Member

@jhg03a - severity level? minor, medium, major?

@jhg03a jhg03a added the medium impact impacts a significant portion of a CDN, or has the potential to do so label Mar 16, 2021
@jhg03a
Copy link
Contributor Author

jhg03a commented Mar 16, 2021

I stuck it as medium because directly touching TODB for mass editing is the current workaround and it's quite dangerous.

@mitchell852
Copy link
Member

@jhg03a - what exactly does this sql query look like? update the ttl on all delivery services to X? if that was performed how would you revert that?

@jhg03a
Copy link
Contributor Author

jhg03a commented Oct 9, 2022

It probably wouldn't need to touch the actual ds, but rather just interpose itself as a higher priority value.

@jhg03a
Copy link
Contributor Author

jhg03a commented Oct 14, 2022

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, you still have to wait for existing TTL to expire regardless.

@jhg03a
Copy link
Contributor Author

jhg03a commented Oct 14, 2022

And this override shouldn't impact DS who's TTL is already below the override TTL.

@awilson75
Copy link

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, you still have to wait for existing TTL to expire regardless.

And this override shouldn't impact DS who's TTL is already below the override TTL.

This needs to be created as a separate issue and shouldn't block the work we have ready to release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium impact impacts a significant portion of a CDN, or has the potential to do so new feature A new feature, capability or behavior Traffic Ops related to Traffic Ops
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants