jlu5 / ansible-dn42 Goto Github PK

Sometimes wg tunnels fail to start up, e.g. if the remote endpoint's DNS fails to resolve or points to a stale IP. In the first case especially the tunnel can get stuck in an invalid state that doesn't accept remote connections - it may be better to automatically detect these dead tunnels and reset them periodically.

These should be pointing to the nameservers listed in the registry (xxxx.registry-sync.dn42) and not the dn42 delegation servers.

As PowerDNS only accepts IPs (not domains) in forward-zones, I think some level of manual translation is needed from the registry-sync.dn42 hostnames to actual IP addresses.