TomK via FreeIPA-users wrote:
Getting a scenario where the hostname doesn't resolve to the new IP if
the VM is recreated multiple times against an IPA server.
I've tried clearing the caches on the clients but no luck. I have to
allow a specific amount of time to pass before I can use the DNS name
that now points to a different (new) IP that was assigned via DHCP.
This apparently also impacts the automounter and it won't work until
much later either. I won't be able to use the NFS mount configured
until then. On initial login users need to wait about 5 minutes before
they can login with home folder set to / instead as a result:
Using username "abc.123\sam".
Using keyboard-interactive authentication.
Creating home directory for abc.123\sam.
Last login: Wed Feb 20 02:39:18 2019 from 192.168.0.76
Could not chdir to home directory /n/abc.123/sam: No such file or directory
Has anyone seen this scenario before and have a general high level idea
where I could start to poke? Seems to me like a DNS Cache Refresh or
Timeout but not sure about the specifics.
/n/abc.123/sam exists and mount works off of other hosts that have been
around for a while.
I'd guess it is the DNS TTL. You'd need to lower that in the DNS server.
I assume this is some sort of dev or qe box that is re-provisioned