As far as I remember, the client does no caching at all. So caching of DNS records should be the responsibility of the machine's DNS caching resolver. Those normally adhere to TTLs. This said, you have to plan for a soft migration when using DNS anyways, as DNS caches interpret TTLs from their last fetch. So, the first fetching cache determines the start of requests going to your new servers, the last determines the end of requests going to the old ones. Setting very short TTLs on the old records first (but no shorter than 5 Minutes, different story), helps keeping this window short. Of course, after shortening the TTLs, wait until the old TTLs have run out or not all caches might have seen.
Hope this helps. _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
