# Can't get DDNS to work with WireGuard client

**URL:** <https://forum.gl-inet.com/t/cant-get-ddns-to-work-with-wireguard-client/53896>\
**Category:** VPN, DNS, Leaks\
**Created:** [January 31, 2025, 2:29am UTC](https://forum.gl-inet.com/t/cant-get-ddns-to-work-with-wireguard-client/53896 "2025-01-31T02:29:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![epiphoneaj220s](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/e/9f8e36/32.png) [@epiphoneaj220s](https://forum.gl-inet.com/u/epiphoneaj220s)\
**Post date:** [January 31, 2025, 2:29am UTC](https://forum.gl-inet.com/t/cant-get-ddns-to-work-with-wireguard-client/53896/1 "2025-01-31T02:29:04Z")

</div>

Hi there,

I'm currently using the Flint for my home router and configuring an Opal for my travel router to work remotely. I'm able to get most of the way but am running into issues when trying to change the endpoint in the config file to use my DDNS address. If I use the DDNS config file for the VPN client on the travel router, I run in the "The client is starting, please wait..." message and it never resolves.

I did notice when I check the Use DDNS Domain to create the wireguard client configuration file, it doesn't seem to stay checked. I'm not sure if that matters?

In addition, I configured the port forwarding on the flint to allow the opal to connect. However, if I enable it then wireguard doesn't seem to work even with the non DDNS configuration file on the client side.

Any suggestions would be much appreciated!

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [February 1, 2025, 7:00am UTC](https://forum.gl-inet.com/t/cant-get-ddns-to-work-with-wireguard-client/53896/2 "2025-02-01T07:00:01Z")

</div>

On Flint (VPN server), GL GUI \> Application \> GL DDNS, there is a DDNS test, click it to see if it is normal?

on others device which from source internet, ping \<your glddns address\> is normal?

---

<div class="post-metadata">

**Author:** ![epiphoneaj220s](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/e/9f8e36/32.png) [@epiphoneaj220s](https://forum.gl-inet.com/u/epiphoneaj220s)\
**Post date:** [February 13, 2025, 2:54am UTC](https://forum.gl-inet.com/t/cant-get-ddns-to-work-with-wireguard-client/53896/4 "2025-02-13T02:54:01Z")

</div>

Sorry for the late reply, Yes it shows up as normal

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [February 17, 2025, 7:21am UTC](https://forum.gl-inet.com/t/cant-get-ddns-to-work-with-wireguard-client/53896/5 "2025-02-17T07:21:55Z")

</div>

If the DDNS test of the VPN server router is normal, and others device (other VPN client like opal SSH, or Windows) which from source internet, ping is normal, the WireGuard connection with the DDNS should be no issue.

Please try it again.  
Please try that WireGuard profile on the PC to see if it works.  
Please confirm the WAN of Flint if has public IP.

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [October 30, 2025, 3:05am UTC](https://forum.gl-inet.com/t/cant-get-ddns-to-work-with-wireguard-client/53896/7 "2025-10-30T03:05:23Z")

</div>


