cryptostorm's community forum

@parityboy

I am not sure why your response would answer the question.
The free wireguard service does NOT require a CryptoStorm token at all, so it should make no difference whether token registration is broken or not.

The problem still persists, the free pubkey registration delivers
PublicKey = Unable to access interface: No such device

I have been using the descriptions at https://cryptostorm.is/#section6
in conjunction with the config files at https://cryptostorm.is/configs/cryptofree/ for OpenVPN implementations on various platforms, using arbitrary usernames and passwords.

The VPN connection is establishing fine (works for all of the config files provided), BUT the DNS resolution does NOT work. This is not a problem I have with other VPN services, hence I am very sure it is related to the VPN config files or the CryptoFree server(s) - and not related to the platforms or OpenVPN implementations I am using.

If someone has an idea what might be wrong and how to solve this, please step forwards.

Thanks and greetings
mando

Do the Cryptostorm DNS server support DNS over TLS?

What would be the correct parameters for "forward-address" in unbound?

forward-addr: "ip-of-dns-server"@"port"#"authname"

What would be the proper "port" and "authname" ?