[89428] in North American Network Operators' Group
Re: DNS TTL adherence
daemon@ATHENA.MIT.EDU (Simon Waters)
Wed Mar 15 10:26:10 2006
From: Simon Waters <simonw@zynet.net>
To: Rodney Joffe <rjoffe@centergate.com>
Date: Wed, 15 Mar 2006 15:25:38 +0000
In-Reply-To: <D2478EF1-5A42-4FEA-859A-16BE1271BA34@centergate.com>
Cc: nanog@merit.edu
Errors-To: owner-nanog@merit.edu
On Wednesday 15 Mar 2006 14:16, you wrote:
>
> Let me help you become aware, then...
:)
> Some people don't believe it is a bug, and therefor don't see that
> anything needs "fixing".
Oh the one shown is a bug, and needs fixing.
> Feel free to, for example, send 2 consecutive queries for a record
> that has a short (<10,000 second TTL) to 212.23.11.206.
Safecom http response, busybox on telnet, some sort of embedded Linux device.
Safecom sell routers...
Of course can't tell if the broken DNS behaviour is the device, or possibly it
is proxying upstream DNS servers.
> This behavior is unfortunately not unique.
Alas what others peoples servers do, shouldn't be an issue for you. Your
problem is they can be coerced into a DoS attack, not that the data is stale.