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

dnsdist cache can send out ttl=0 answers, confusing some clients #7534

Closed
ahupowerdns opened this issue Mar 1, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@ahupowerdns
Copy link
Member

commented Mar 1, 2019

The dnsdist cache will decrement the TTL of records for you (unless configured not to). This will currently occasionally lead to TTL=0 answers going out on the wire.

It turns out there are clients that check a certain IP address continuously and will recheck in 'TTL seconds'. Perhaps this is not exactly their behaviour, but on receiving a TTL=0 answer, these devices enter into a tight loop where they keep re-retrieving the IP address until they see a non-zero TTL.

It may be wise for dnsdist to not ever return TTL=0 answers, just to prevent this problem.

Something like this was discussed in this thread on dns-operations: https://lists.dns-oarc.net/pipermail/dns-operations/2019-January/018308.html

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.