David C. Rankin wrote:
The updated host and server were both happy with what the new IP was for the updated hosts (simple nslookup confirmed that), but my Leap 15.0 laptop still had the old IP cached somewhere (nscd?) and was unable to reconnect to the remote updated hosts after they were rebooted (I could connect with ssh -Y NEWIP just fine)
So the problem was my laptop still holding the old IPs in cache somewhere.
That would be nscd.
What do I restart or how can I flush the cache so my laptop has the new IP for the client so name resolution works from my laptop?
nscd -i hosts
or just restart nscd.
Thank you Per, that is what looked logical -- though having never played with nscd I glad I checked.
The underlying issue is what changed in the 5.6.5 kernel that causes hosts to recalculate their TXT record has so that the next dhcpd update to DNS issues an address but complains the address TXT records are "not mine." -- oh well, I'll stumble through that one tomorrow.