Dynamic IP & cache DNS

[Brad Knowles]

At 5:12 PM -0400 9/10/01, Kevin Darcy wrote:

>  I recently proposed a protocol extension that would implement a "callback" to
>  nameservers when a particular piece of data changes (using a generalized form
>  of NOTIFY). This would, I think, provide the best of both worlds -- being
>  able to set a reasonably-long TTL in the general case but at the same time
>  being able to make sudden changes visible rapidly. Unfortunately, the
>  proposal was shot down as requiring the maintenance of too much state
>  information in nameservers.

	As well as being simply unnecessary.  Domain managers can reduce 
their TTLs before making a change that they know needs to propagate 
quickly, and then re-instate more realistic TTLs once the change has 
been made.

	There's simply no need to have your "callback" mechanism, and it 
is way too much work to expect nameservers to be able to deal with. 
They're having a hard enough time just keeping up with the number of 
queries per second they can have aimed at them during times of 
stress, running out of memory, etc....

-- 
Brad Knowles, <brad.knowles at skynet.be>

H4sICIFgXzsCA2RtYS1zaWcAPVHLbsMwDDvXX0H0kkvbfxiwVw8FCmzAzqqj1F4dy7CdBfn7
Kc6wmyGRFEnvvxiWQoCvqI7RSWTcfGXQNqCUAnfIU+AT8OZ/GCNjRVlH0bKpguJkxiITZqes
MxwpSucyDJzXxQEUe/ihgXqJXUXwD9ajB6NHonLmNrUSK9nacHQnH097szO74xFXqtlbT3il
wMsBz5cnfCR5cEmci0Rj9u/jqBbPeES1I4PeFBXPUIT1XDSOuutFXylzrQvGyboWstCoQZyP
dxX4dLx0eauFe1x9puhoi0Ao1omEJo+BZ6XLVNaVpWiKekxN0VK2VMpmAy+Bk7ZV4SO+p1L/
uErNRS/qH2iFU+iNOtbcmVt9N16lfF7tLv9FXNj8AiyNcOi1AQAA