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

k8s-dns ttl never expire #77860

thepiger opened this issue May 14, 2019 · 2 comments


None yet
4 participants
Copy link

commented May 14, 2019

I have a problem with the resolution of name outside kubernetes (like google or api of service use) wouldn't update because the TTL of the records is setted to a value like 4292482298.
When kubedns' pod start the ttl is correctly setted to 300 and it is refreshed every 5 minutes.
With dig i'm monitoring the ttl count down and i'm seeing that it restart from 300 but after some days of working it change to 4292482298 that is more than 130 years.


  • Kubernetes version v1.11.3
  • hardware configuration: vSphere
  • OS :CoreOS1855
  • Kernel 4.14.67-coreos
  • Install tools: kubespray
  • k8s-dns-kube-dns-amd64:1.14.13

This comment has been minimized.

Copy link

commented May 14, 2019

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network and removed needs-sig labels May 14, 2019


This comment has been minimized.

Copy link

commented May 14, 2019

/triage unresolved

Comment /remove-triage unresolved when the issue is assessed and confirmed.

🤖 I am a bot run by vllry. 👩‍🔬

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.