Exporting Duck DNS Client
-
When I set up Duck DNS as a VPN ddns service, the Host Name on the Dynamic DNS Client is blank. Having a blank Host Name prevents me from exporting the Client Config file. I can see the Custom DNS Client in the export list as a blank spot with a check mark, but each time I select it, the client export configuration tool doesn't recognize that anything has been selected for export.
I'm using the No-IP service, but I would prefer the Duck service as there is no need for monthly email confirmation. -
Can't see what you mean ....
"245809" is my HE.net Tunnelbroker Dynamic DNS Client host ID, and has nothing to do with 'dyndns', and I have a RFC2136 home.xxxxxxxxx.fr as a host name for my WAN IPv4, and that's the one I use for my OpenVPN client config files.
A bank spot or question mark can't be a valid host name for a client VPN config, as something like '?" isn't a host name. So your VPN client won't know where to connect.
-
@gertjan
I'm referring to when I'm setting up the Dynamic DNS client for the OpenVPN and when I'm trying to export the DNS Client in the OpenVPN export Utility.
-
Yep, that's strange.
Normally, what you've set here :
should be shown on the list with available WAN host names under the VPN =>Host Name Resolution
The same thing goes for the RC2136 - and that's the one I'm using :
Check your dyndns settings - the host name part.
It should look like this :
More info here : OpenVPN Client Export Package
-
@gertjan
For Duck DNS I'm using Custom, since it isn't in the list. I'm following a Duck DNS process used in pfSense through a YouTube channel, wundertech. Just wondered if anyone else got it working... -
@kevin-4 said in Exporting Duck DNS Client:
For Duck DNS I'm using Custom
Aha.
No 'host name' field in that custom setup.
Ok, there is :
but the OpenVPN client export can't access that one.
The host name also exist in your head : that's not accessible neither for the OpenVPN export package ;)Use the 'Other' and specify the host name manually :
-
@gertjan
I appreciate the advice, I hadn't tried that. Unfortunately, it didn't work either.
-
@kevin-4
This is an URL, not a host name.
Remove the part on front of "www." and the final slash and it should be accepted. -
@viragomann
Yep, that did it. Thank you!
