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

Support custom TTLs #117

Closed
MalteJ opened this issue Apr 2, 2017 · 3 comments
Closed

Support custom TTLs #117

MalteJ opened this issue Apr 2, 2017 · 3 comments
Milestone

Comments

@MalteJ
Copy link

MalteJ commented Apr 2, 2017

Especially for k8s services it would be good to be able to set a lower TTL than 300 seconds.
When one node goes down it could take up to five minutes to have an updated DNS.

EDIT
just realized that the load balancer's IP address is used so my argumentation is not valid. Nevertheless a custom TTL would still be a good idea ;)

@linki
Copy link
Member

linki commented Apr 2, 2017

@MalteJ Custom TTLs are on our list and your described use case makes perfect sense, e.g. when running nginx-ingress-controller without a fronting service: https://github.com/linki/external-dns/blob/4d66ac1069164eb952bf8daef13b10ad6f51fa0d/docs/tutorials/nginx-ingress.md#without-a-separate-tcp-load-balancer

@szuecs
Copy link
Contributor

szuecs commented Nov 14, 2017

@linki I think we can close this issue, AWS is done, google has an open PR which will be merged soon others can implement as needed

@hjacobs
Copy link
Contributor

hjacobs commented Nov 22, 2017

@szuecs closing this issue as AWS and Google support are now both in the latest release v0.4.8.

@hjacobs hjacobs closed this as completed Nov 22, 2017
@hjacobs hjacobs modified the milestones: post-v1.0, v0.5 Nov 22, 2017
lou-lan pushed a commit to lou-lan/external-dns that referenced this issue May 11, 2022
Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants