Wireguard - ReResolve DNS Endpoint

[foschi]

Hello everyone.

The endpoint field in the peer of the WireGuard connection allows the insertion of a domain name, however this is resolved in the IP address only to the activation of the connection.
The following code by Jason A. Donenfeld (Creator of WireGuard) was created to allow you to avoid doing off+on in the event that peer has changed IP address.

https://github.com/WireGuard/wireguard-tools/blob/master/contrib/reresolve-dns/reresolve-dns.sh

Is it expected to be implemented in the future? Please do it otherwise I have to try to do it custom to make my Speedster capable of detecting the change of IP address and trying to restore the connection with peer, in this way it is useful to use the domain name and make sense.

Thank you!

Edited August 4 by foschi

[Le ecureuil]

В 27.07.2024 в 21:15, foschi сказал:

Hello everyone.

The endpoint field in the peer of the WireGuard connection allows the insertion of a domain name, however this is resolved in the IP address only to the activation of the connection.
The following code by Jason A. Donenfeld (Creator of Wiregarded) was created to allow you to avoid doing off+on in the event that peer has changed IP address.

https://github.com/WireGuard/wireguard-tools/blob/master/contrib/reresolve-dns/reresolve-dns.sh

Is it expected to be implemented in the future? Please do it otherwise I have to try to do it custom to make my Speedster capable of detecting the change of IP address and trying to restore the connection with peer, in this way it is useful to use the domain name and make sense.

Thank you!

Hello.

Our userspace code has nothing in common with the original Donenfeld's code. We implemented it by scratch, and of course we support reresolving in case of connection termination (or restart by the command of a user).

For better experience feel free to try version 4.2.

[foschi]

On 7/30/2024 at 2:27 PM, Le ecureuil said:

Hello.

Our userspace code has nothing in common with the original Donenfeld's code. We implemented it by scratch, and of course we support reresolving in case of connection termination (or restart by the command of a user).

For better experience feel free to try version 4.2.

Thanks for the reply.

How long does the process take to re-resolve DNS after the 'not connected' event?

The TTL of the FQDN's DNS record is not the problem here.

If i switch with the status button to off and on again, it works:

Thank you.

 

Edited August 4 by foschi

[foschi]

Hello @Le ecureuil.

Can you give me feedback?

[foschi]

Has anyone ever encountered this problem?

[foschi]

hi @Le ecureuil, can you give me feedback?

[Le ecureuil]

В 19.08.2024 в 20:25, foschi сказал:

hi @Le ecureuil, can you give me feedback?

I suppose it's better to write to support and to receive guaranteed answer.

If you want to proceed here at your risk:

please enable
interface Wireguard0 debug

then save it:

system configuration save

and then download the self-test file at the moment when wireguard doesn't work.

The file you can send to me in the direct messages.