MSGID: 2:240/5824.1@fidonet fa18a3e1   
   REPLY: 2:280/5555 61dc2898   
   PID: OpenXP/5.0.51 (Linux) (x86_64)   
   CHRS: ASCII 1   
   TZUTC: 0100   
   Am 10.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:   
      
   Hallo Michiel,   
      
   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)   
   SEEN-BY: 1/123 15/0 80/1 90/1 92/1 105/81 106/201 120/340 123/131   
   SEEN-BY: 124/5016 129/331 153/757 7715 154/10 203/0 218/700 221/0   
   SEEN-BY: 221/1 6 226/30 229/110 206 317 400 424 426 428 550 664 700   
   SEEN-BY: 240/1120 5138 5411 5824 5832 5853 266/512 280/464 5003 5006   
   SEEN-BY: 280/5555 282/1038 292/854 8125 301/1 113 812 310/31 317/3   
   SEEN-BY: 320/219 322/757 341/234 342/200 396/45 423/120 460/58 633/280   
   SEEN-BY: 712/848 770/1 2452/250 2454/119 5020/545 1042 5058/104   
   PATH: 240/5824 5832 280/464 301/1 229/426