WireGuard Android: Cached resolved host

Heiko Friedel hf at hfnet.de
Mon Nov 5 17:56:49 CET 2018

How fast is turning on and off and on?

AddressCache.java already implements a cache with a fixed TTL of 2 seconds.

A quick fix was to re-resolve with every call to getResolvedEndpoint(). 
I'm testing this for a couple of days without issues.

Am 04.11.2018 um 18:25 schrieb Jason A. Donenfeld:

> It's mostly this way to prevent DNS lookup failures during the network
> connectivity changes, such as turning on and off and on a tunnel
> really fast. I agree the current implementation's behavior is
> suboptimal though. Probably instead we should invalidate based on the
> TTL.
> The code in question lives at
> app/src/main/java/com/wireguard/config/InetEndpoint.java if you want
> to take a stab at fixing it.

More information about the WireGuard mailing list