Domino server caching "last known address"

Domino 8.5.2FP2 on i5/os lpar running 7.1.

Changed IP address of a domino server (LDAP02) on another lpar on a
different i. Changed our dns entries for it.

Back on our '01' lpar I can ping it and it gets the new address fine.
nslookup also works fine. WRKDOMSVR shows 8 domino servers. 7 of 8 can
run TRACE LDAP02 and it finds the new address. On NOTES01 however, it
retains old address:
08/20/2011 08:11:03 Network: Determining path to server LDAP02
08/20/2011 08:11:03 Network: Available Ports: TCPIP
08/20/2011 08:11:03 Network: Checking normal priority connection
documents only...
08/20/2011 08:11:03 Network: Allowing wild card connection documents...

08/20/2011 08:11:03 Network: Checking for LDAP02/DEKKO at last known
address '10.10.1.138' on TCPIP...
08/20/2011 08:11:08 Network: Unable to connect to LDAP02/DEKKO on
TCPIP (The server is not responding. The server may be down or you may
be experiencing network problems. Contact your system administrator if
this problem persists.)
08/20/2011 08:11:08 Network: No answer at last known address
08/20/2011 08:11:08 Network: Server LDAP02 is not responding

It's using "last known address" instead of finding new address.

Bouncing of server NOTES01 had no effect. Trace still used "last known
address".

I also did CFGTCP 12 and changed search priority from *LOCAL to *REMOTE
and back. A change here is supposed to refresh the i's cache. But since
ping and nslookup were already working fine I didn't have any hope that it
would do any good.
ou
Successful workaround: Add Connection document from NOTES01 to LDAP02
using IP address. But, it didn't make the change until server was
bounced. IOW the trace still picked up "last known address" and after the
bounce it used new IP address. Took connection document out and bounced
server again. It's back to using "last known address" but at least it's
using the new IP address. Still caching but now cache has current IP
address.

How do you turn off the caching?

Rob Berendt