update caching nameserver immediately

[Simon Waters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Will Yardley wrote:
>
> and without setting ridiculously low TTLs?

I think a TTL that matches the length of time a record is going to be
valid for isn't ridiculously low, but then I pondered doing the Cisco
NAT fudge which updates TTL (in the packet as it passes the firewall)
based on the expected life of a NAT mapping in the firewall, which means
that the TTL is so low the DNS lookups are discardable, and caching
doesn't help.

Remember individual client operating systems probably have some DNS
caching ability these days, that will respect TTL.

Come on what are you moving around behind the scenes? I assume it is
only one or two records?

If it isn't a routine thing, then caches can just be restarted, if it is
routine a low TTL for those records seems sensible, rather than hacking
some out off band fudge.
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/gr48GFXfHI9FVgYRAmpiAJoC2e8xEUw0kMtjqlGOWUq+/vVYjwCgwcIo
C7Iq5tnEwpCcPup/NuxroWo=
=BME9
-----END PGP SIGNATURE-----