[OpenAFS-devel] caching of AFSDB records.

[Måns Nilsson]

--==========1664BD0AC05E4764A43C==========
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,=20

I just had an issue where an old AFSDB record showed up, pointing to an
obsolete server. The client (Solaris, stable 1.2.late) learned this through
its resolver, and kept it, regardless of what I tried in the DNS end (that
is my normal realm of work, so AFS problems look like DNS issues, much like
the hammer-and-nail proverb;-) the client would not relearn. I had to
manually tell it about the real server.=20

>From this I assume that the client caches the result of "dig $REALM AFSDB
+short" somewhere internally. Is this the case, where (if anywhere) is the
knob, and what are the defaults? It might be noted that I did not wait
untill the TTL of the DNS record had expired, so if there is an internal
TTL that is decreased in concert with the DNS TTL that is fine -- that
gives me a knob in DNS..=20

--=20
M=C3=A5ns Nilsson                    Systems Specialist
+46 70 681 7204   cell                      KTHNOC
+46 8 790 6518  office                 MN1334-RIPE

Hello.  I know the divorce rate among unmarried Catholic Alaskan
females!!

--==========1664BD0AC05E4764A43C==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFDdF9y02/pMZDM1cURAroqAJ9eAHbsYZqTP5OIQFwA3o2ZoOWkegCfUfnS
BGzcXDpYoelnB/72FLGbxr0=
=pGLL
-----END PGP SIGNATURE-----

--==========1664BD0AC05E4764A43C==========--