Solutions
-
Pa7rickStar's post in [Best practices] Force Wireguard to re-resolve DNS after IP change using DynDNS? was marked as the answerThanks! So running an user scripts seems to be the way to go 👍
Your script looks very cool! I tried the wireguard-tools/reresolve-dns.sh first, though. I cloned it to /mnt/user/system/wireguard-tools/reresolve-dns.sh and added an user script with this content (the script is running every 5 minutes):
#!/bin/bash /mnt/user/system/wireguard-tools/reresolve-dns.sh /etc/wireguard/wg0.conf /mnt/user/system/wireguard-tools/reresolve-dns.sh /etc/wireguard/wg1.confWorks like a charm. Even when I restarted the router at location B the tunnel was reestablished and Krusader copy processes continue without user intervention.