On 23 Nov 2020, Michiel van der Vlist said the following...
 
 Mv> So... it is not your provider that changed the prefix. That would affect
 Mv> thefirst 64 bits. It is within your own local network that the host
 Mv> part, the last64 bits have changed. So the issue is a local issue and
 Mv> should be addressedlocally.

Thanks for pointing that out.  Somewhere along the line I must have forgotten to update /etc/dhcpcd.conf with:

slaac hwaddr

It was still set to the default of: slaac private

It looks like DNS is already updated with the new address & ipv6scanner.com is showing 24553 & 24554 as open with an address of:

2607:fea8:ab00:e4f:dea6:32ff:fe60:847b


Jay

... Corduroy pillows are making headlines

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)