29 Jan
2012
29 Jan
'12
5:41 p.m.
Hi Keith,
On Sun, Jan 29, 2012 at 05:14:12PM +0000, Keith Williams wrote:
There are, of course, times when you need a very short
rfresh etc - when
testing or changing records. And I suppose it is possible, for any number
of reasons, to forget to change back.
Setting a low refresh will not help you with testing as it's the TTL
on individual records that matters there. Also regardless of your
refresh, modern nameservers send out a NOTIFY when they change their
zone content, and this triggers an immediate refresh.
So I struggle to see the point of a low refresh time, but I actually
don't care if people want a low refresh; the problem comes when the
expire is close to or the same as the refresh.
I have no idea why someone would want their domain to break after 5
minutes (or a day) of no contact between secondary and primary but
am of course happy to let people do it if it's intentional.
I think your suggestion is a good one but would it be
possible to write the
code so that if refresh or expire time is below a certain amount, or the
difference between them is less than a certain figure/proportion then the
alerts are switched off for that domain and a warning given on the panel
page. It's then up to the customer to keep an eye on it.
Even though alerts can still be disabled right now without asking
support, you would still recommend that no alerts are sent in this
case?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting