AN>> Same here. The IPv6 connection for my BBS also had problems on friday AN>> because Dynv6 'forgot' the AAAA record that I've configured - but it AN>> seems to be a known problem. Maybe I rewrite the update script (and AN>> recreate the AAAA record on every prefix change) or switch to my own AN>> dyndns solution...
MvdV> We patiently wait... ;-) MvdV> Please share your experience with us.
I just noticed that Dynv6 lost my AAAA record again, so I chose to update my update script. Dynv6 is offering the use of 'nsupdate', and as I'm already using nsupdate for my own DynDNS solution, I just added a nsupdate call for my Dynv6 zone to the script. It's basically working as noted in the API documentation: https://dynv6.com/docs/apis
I hope that this solves the Dynv6 AAAA problem now - I hope that my IPv6 prefix changes more often than Dynv6 forgets my AAAA record :)
Regards, Anna
--- OpenXP 5.0.51 * Origin: Imzadi Box Point (2:240/5824.1)
