No connection to NAS due to old DNS cache?

[chrisb1]

Hi,
today I came across a strange problem: My WAN reconnected and that means for me: new IPv6 prefix. Therfore also my NAS got a new IPv6 address. From this point on proxmox wasn't able to connect to the NAS via NFS anymore (via hostname). In my firewall log (pfSense) I saw, that proxmox tries to connect to the NAS via the old address with the old prefix. That obviously won't work.
But when trying ping6 nas.domain or dig AAAA nas.domain it works as expected --> new/correct address is used.

Why is proxmox sticking to the old address? What can I do to prevent this in the future?
Restarting proxmox after every WAN reconnect would probably work, but obviously that is not the prefered solution Also disabling IPv6 completely wouldn't appear to be an appropriate solution.

Thanks

 

[chrisb1]

Something I just noticed that might be relevant: When navigating to /mnt/pve and trying to execute ls the command hangs and I have to cancel it via CTRL+C.

in the WebGUI proxmox tells me, that /mnt/pve/qnap_nas does not exist or is unreachable (500)

 

[chrisb1]

Feels like talking to myself, but just in case anyone comes across the same problem
I had to reboot the proxmox host. After that i was able to at least execute dir within /mnt/pve/. Turns out that there is not only qnap_nas present but three more folders from NAS-connections I used to have but that were delete in the WebGUI. After the reboot I was able to manually delete all the folders and the after reconfiguring the NAS connection it works again.

--> solved for the moment, but I still have no clue, why the proxmox host didn't use the right IPv6 in the first place...

 

[chrisb1]

Have to "open" this again . After an ISP reconnect I got a different IPv6 prefix and this again breaks the connection to the NAS.
nslookup and dig are returning the correct address but proxmox tries to contact the old IPv6
Do I really have to restart proxmox every time I get a new IPv6 prefix?